Previous Page TOC Index Next Page

3.3.3 PV1 - patient visit segment

The PV1 segment is used by Registration/ADT applications to communicate information on a visit-specific basis. This segment can be used to send multiple-visit statistic records to the same patient account or single-visit records to more than one account. Individual sites must determine the use for this segment.

Figure 3-3. PV1 attributes

SEQ

LEN

DT

OPT

RP/#

TBL#

ITEM#

ELEMENT NAME

1

4

SI

O



00131

Set ID - PV1

2

1

IS

R


0004

00132

Patient Class

3

80

PL

O



00133

Assigned Patient Location

4

2

IS

O


0007

00134

Admission Type

5

20

CX

O



00135

Preadmit Number

6

80

PL

O



00136

Prior Patient Location

7

60

XCN

O

Y

0010

00137

Attending Doctor

8

60

XCN

O

Y

0010

00138

Referring Doctor

9

60

XCN

O

Y

0010

00139

Consulting Doctor

10

3

IS

O


0069

00140

Hospital Service

11

80

PL

O



00141

Temporary Location

12

2

IS

O


0087

00142

Preadmit Test Indicator

13

2

IS

O


0092

00143

Readmission Indicator

14

3

IS

O


0023

00144

Admit Source

15

2

IS

O

Y

0009

00145

Ambulatory Status

16

2

IS

O


0099

00146

VIP Indicator

17

60

XCN

O

Y

0010

00147

Admitting Doctor

18

2

IS

O


0018

00148

Patient Type

19

20

CX

O



00149

Visit Number

20

50

CM

O

Y

0064

00150

Financial Class

21

2

IS

O


0032

00151

Charge Price Indicator

22

2

IS

O


0045

00152

Courtesy Code

23

2

IS

O


0046

00153

Credit Rating

24

2

IS

O

Y

0044

00154

Contract Code

25

8

DT

O

Y


00155

Contract Effective Date

26

12

NM

O

Y


00156

Contract Amount

27

3

NM

O

Y


00157

Contract Period

28

2

IS

O


0073

00158

Interest Code

29

1

IS

O


0110

00159

Transfer to Bad Debt Code

30

8

DT

O



00160

Transfer to Bad Debt Date

31

10

IS

O


0021

00161

Bad Debt Agency Code

32

12

NM

O



00162

Bad Debt Transfer Amount

33

12

NM

O



00163

Bad Debt Recovery Amount

34

1

IS

O


0111

00164

Delete Account Indicator

35

8

DT

O



00165

Delete Account Date

36

3

IS

O


0112

00166

Discharge Disposition

37

25

CM

O


0113

00167

Discharged to Location

38

2

IS

O


0114

00168

Diet Type

39

2

IS

O


0115

00169

Servicing Facility

40

1

IS

B


0116

00170

Bed Status

41

2

IS

O


0117

00171

Account Status

42

80

PL

O



00172

Pending Location

43

80

PL

O



00173

Prior Temporary Location

44

26

TS

O



00174

Admit Date/Time

45

26

TS

O



00175

Discharge Date/Time

46

12

NM

O



00176

Current Patient Balance

47

12

NM

O



00177

Total Charges

48

12

NM

O



00178

Total Adjustments

49

12

NM

O



00179

Total Payments

50

20

CX

O


0192

00180

Alternate Visit ID

51

1

IS

O


0326

01226

Visit Indicator

52

60

XCN

O

Y

0010

01224

Other Healthcare Provider

3.3.3.0 PV1 field definitions

3.3.3.1 Set ID - PV1 (SI) 00131

Definition: PV1-1-set ID-patient visit contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be 1, for second occurrence it shall be 2, etc.

3.3.3.2 Patient class (IS) 00132

Definition: This field is used by systems to categorize patients by site. It does not have a consistent industry-wide definition. It is subject to site-specific variations. Refer to user-defined table 0004 - Patient class for suggested values.

User-defined Table 0004 - Patient class

Value

Description

E

Emergency

I

Inpatient

O

Outpatient

P

Preadmit

R

Recurring Patient

B

Obstetrics

3.3.3.3 Assigned patient location (PL) 00133

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)

Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the patient’s initial assigned location or the location to which the patient is being moved. The first component may be the nursing station for inpatient locations, or clinic, department, or home for locations other than inpatient. For canceling a transaction or discharging a patient, the current location (after the cancellation event) should be in this field. If a value exists in the fifth component (bed status), it supersedes the value in PV1-40-bed status.

3.3.3.4 Admission type (IS) 00134

Definition: This field indicates the circumstances under which the patient was or will be admitted. Refer to user-defined Table 0007 - Admission type for suggested values.

User-defined Table 0007 - Admission type

Value

Description

A

Accident

E

Emergency

L

Labor and Delivery

R

Routine

3.3.3.5 Preadmit number (CX) 00135

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field uniquely identifies the patient’s pre-admit account. Some systems will continue to use the pre-admit number as the billing number after the patient has been admitted. For backward compatibility, an ST data type can be sent, however HL7 recommends use of the CX data type, like the account number, for new implementations.

3.3.3.6 Prior patient location (PL) 00136

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)

Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the prior patient location if the patient is being transferred. The old location is null if the patient is new. If a value exists in the fifth component (bed status), it supersedes the value in PV1-40-bed status.

3.3.3.7 Attending doctor (XCN) 00137

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the attending physician information. Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple attending doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. Depending on local agreements, either ID or the name may be absent in this field. Refer to user-defined table 0010 - Physician ID for suggested values.

3.3.3.8 Referring doctor (XCN) 00138

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the referring physician information. Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple referring doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. Depending on local agreements, either the ID or the name may be absent from this field. Refer to user-defined table 0010 - Physician ID for suggested values.

3.3.3.9 Consulting doctor (XCN) 00139

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the consulting physician information. The field sequences are used to indicate multiple consulting doctors. Depending on local agreements, either the ID or the name may be absent from this field. Refer to user-defined table 0010 - Physician ID for suggested values.

3.3.3.10 Hospital service (IS) 00140

Definition: This field contains the treatment or type of surgery that the patient is scheduled to receive. It is a required field with trigger events A01, A02, A14, A15. Refer to user-defined table 0069 - Hospital service for suggested values.

3.3.3.11 Temporary location (PL) 00141

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>

Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains a location other than the assigned location required for a temporary period of time (e.g., OR). If a value exists in the fifth component (bed status), it supersedes the value in PV1-40-bed status.

3.3.3.12 Preadmit test indicator (IS) 00142

Definition: This field indicates whether the patient must have pre-admission testing done in order to be admitted. Refer to user-defined table 0087 - Pre-admit test indicator for suggested values.

3.3.3.13 Re-admission indicator (IS) 00143

Definition: This field indicates that a patient is being re-admitted to the facility and gives the circumstances. We suggest using "R" for readmission or else null. Refer to user-defined table 0092 - Re-admission indicator for suggested values.

3.3.3.14 Admit source (IS) 00144

Definition: This field indicates where the patient was admitted. Refer to user-defined table 0023 - Admit source for suggested values.

3.3.3.15 Ambulatory status (IS) 00145

Definition: This field indicates any permanent or transient handicapped conditions. Refer to user-defined table 0009 - Ambulatory status for suggested entries.

User-defined Table 0009 - Ambulatory status

Value

Description

A0

No functional limitations

A1

Ambulates with assistive device

A2

Wheelchair/stretcher bound

A3

Comatose; non-responsive

A4

Disoriented

A5

Vision impaired

A6

Hearing impaired

A7

Speech impaired

A8

Non-English speaking

A9

Functional level unknown

B1

Oxygen Therapy

B2

Special equipment (tubes, IVs, catheters)

B3

Amputee

B4

Mastectomy

B5

Paraplegic

B6

Pregnant

3.3.3.16 VIP indicator (IS) 00146

Definition: This field identifies the type of VIP. Refer to user-defined table 0099 - VIP indicator.

3.3.3.17 Admitting doctor (XCN) 00147

Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the admitting physician information . Multiple names and identifiers for the same physician may be sent. The field sequences are not used to indicate multiple admitting doctors. The legal name must be sent in the first sequence. If the legal name is not sent, then a repeat delimiter must be sent in the first sequence. By local agreement, the name or ID may be absent in this field. Refer to user-defined table 0010 - Physician ID for suggested values.

3.3.3.18 Patient type (IS) 00148

Definition: This field contains site-specific values that identify the patient type. Refer to user-defined table 0018 - Patient type for suggested values.

3.3.3.19 Visit number (CX) 00149

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: For backward compatibility, an NM data type may be sent, but HL7 recommends that new implementations use the CX data type. This field contains the unique number assigned to each patient visit.

3.3.3.20 Financial class (CM) 00150

Components: <financial class (IS)> ^ <effective date (TS)>

Definition: This field contains the primary financial class assigned to the patient for the purpose of identifying sources of reimbursement. Repeats up to four times. Refer to user-defined table 0064 - Financial class for suggested values.

3.3.3.21 Charge price indicator (IS) 00151

Definition: This field contains the code used to determine which price schedule is to be used for room and bed charges. Refer to user-defined table 0032 - Charge/price indicator for suggested values.

3.3.3.22 Courtesy code (IS) 00152

Definition: This field indicates whether the patient will be extended certain special courtesies. Refer to user-defined table 0045 - Courtesy code for suggested values.

3.3.3.23 Credit rating (IS) 00153

Definition: This field contains the user-defined code to determine past credit experience. Refer to user-defined table 0046 - Credit rating for suggested values.

3.3.3.24 Contract code (IS) 00154

Definition: This field identifies the type of contract entered into by the facility and the guarantor for the purpose of settling outstanding account balances. Refer to user-defined table 0044 - Contract code for suggested values.

3.3.3.25 Contract effective date (DT) 00155

Definition: This field contains the date that the contract is to start or started.

3.3.3.26 Contract amount (NM) 00156

Definition: This field contains the amount to be paid by the guarantor each period according to the contract.

3.3.3.27 Contract period (NM) 00157

Definition: This field specifies the duration of the contract for user-defined periods.

3.3.3.28 Interest code (IS) 00158

Definition: This field indicates the amount of interest that will be charged the guarantor on any outstanding amounts. Refer to user-defined table 0073 - Interest rate code for suggested values.

3.3.3.29 Transfer to bad debt code (IS) 00159

Definition: This field indicates that the account was transferred to bad debts and gives the reason. Refer to user-defined table 0110 - Transfer to bad debt code for suggested values.

3.3.3.30 Transfer to bad debt date (DT) 00160

Definition: This field contains the date that the account was transferred to a bad debt status.

3.3.3.31 Bad debt agency code (IS) 00161

Definition: This field can be used as an ST type for backward compatibility. This field uniquely identifies the bad debt agency to which the account was transferred. This code is site defined. One possible implementation would be to edit against a table such as user-defined table 0021 - Bad debt agency code; however, this is not required.

3.3.3.32 Bad debt transfer amount (NM) 00162

Definition: This field contains the amount that was transferred to a bad debt status.

3.3.3.33 Bad debt recovery amount (NM) 00163

Definition: This field contains the amount recovered from the guarantor on the account.

3.3.3.34 Delete account indicator (IS) 00164

Definition: This field indicates that the account was deleted from the file and gives the reason. Refer to user-defined table 0111 - Delete account code for suggested values.

3.3.3.35 Delete account date (DT) 00165

Definition: This field contains the date that the account was deleted from the file.

3.3.3.36 Discharge disposition (IS) 00166

Definition: This field contains the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.). Refer to user-defined table 0112 - Discharged disposition for suggested values.

3.3.3.37 Discharged to location (CM) 00167

Components: <discharge location (IS)> ^ <effective date (TS)>

Definition: This field indicates a facility to which the patient was discharged. Refer to user-defined table 0113 - Discharged to location for suggested values.

3.3.3.38 Diet type (IS) 00168

Definition: This field indicates a special diet type for a patient. Refer to user-defined table 0114 - Diet type for suggested values.

3.3.3.39 Servicing facility (IS) 00169

Definition: This field is used in a multiple facility environment to indicate the facility with which this visit is associated. Refer to user-defined table 0115 - Servicing facility for suggested values.

An optional fourth component, the facility ID, may be valued in each individual location field in PV1, instead of placing it here.

3.3.3.40 Bed status (IS) 00170

Definition: This field has been retained for backward compatibility only. This field contains the status of the bed. Refer to user-defined table 0116 - Bed status for suggested values.

User-defined Table 0116 - Bed status

Value

Description

C

Closed

H

Housekeeping

O

Occupied

U

Unoccupied

K

Contaminated

I

Isolated

An optional fifth component, bed status, may be valued in each individual location field in PV1, instead of placing it here.

3.3.3.41 Account status (IS) 00171

Definition: This field contains the account status. Refer to user-defined table 0117 - Account status for suggested values.

3.3.3.42 Pending location (PL) 00172

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>

Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field indicates the point of care, room, bed, facility ID, and bed status to which the patient may be moved. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient. If a value exists in the fifth component (bed status), it supersedes the value in PV1-40-bed status.

3.3.3.43 Prior temporary location (PL) 00173

Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>

Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field is used to reflect the patient’s temporary location (such as the OR or XRAY) prior to a transfer from a temporary location to an actual location, or from a temporary location to another temporary location. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient. If a value exists in the fifth component (bed status), it supersedes the value in PV1-40-bed status.

3.3.3.44 Admit date/time (TS) 00174

Definition: This field contains the admit date/time. It is to be used if the event date/time is different than the admit date and time, i.e., a retroactive update. This field is also used to reflect the date/time of an outpatient/emergency patient registration.

3.3.3.45 Discharge date/time (TS) 00175

Definition: This field contains the discharge date/time. It is to be used if the event date/time is different than the admit date and time, that is, a retroactive update. This field is also used to reflect the date/time of an outpatient/emergency patient discharge.

3.3.3.46 Current patient balance (NM) 00176

Definition: This field contains the visit balance due.

3.3.3.47 Total charges (NM) 00177

Definition: This field contains the total visit charges.

3.3.3.48 Total adjustments (NM) 00178

Definition: This field contains the total adjustments for visit.

3.3.3.49 Total payments (NM) 00179

Definition: This field contains the total payments for visit.

3.3.3.50 Alternate visit ID (CX) 00180

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the alternative, temporary, or pending optional visit ID number to be used if needed. It is the ID used by the facility to identify a patient uniquely at the time of an admit or visit. Refer to HL7 table 0061 - Check digit scheme, as defined in Chapter 2, for valid values. Refer to user-defined table 0192 - Visit ID type for suggested values.

3.3.3.51 Visit indicator (IS) 01226

Definition: This field specifies the level on which data are being sent. It is the indicator used to send data at two levels, visit and account. HL7 recommends sending an ‘A’ or no value when the data in the message are at the account level, or ‘V’ to indicate that the data sent in the message is at the visit level. Refer to user-defined table 0326 - visit indicator for suggested values.

User-defined Table 0326 - Visit Indicator

Value

Description

A

Account Level (default)

V

Visit Level

3.3.3.52 Other healthcare provider (XCN) 01224

Components: <ID number (ST)> ^<family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^<assigning authority (HD)> ^<name type code(ID)> ^<identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the other healthcare providers (e.g., Nurse care practitioner, midwife, physician assistant). Multiple healthcare providers can be sent. Depending on local agreements, either the ID or the name may be absent from this field. Use values in user-defined table 0010 - Physician ID for first component.

3.3.3.53 PV1 usage notes

The facility (servicing) ID, the optional fourth component of each patient location field, is a string of up to six characters that is uniquely associated with the facility containing the location. A given institution, or group of intercommunicating institutions, should establish a list of facilities that may be potential assigners of patient locations. The list will be one of the institution’s master dictionary lists. Since third parties other than the assigners of patient locations may send or receive HL7 messages containing patient locations, the facility ID in the patient location may not be the same as that implied by the sending and receiving systems identified in the MSH. The facility ID must be unique across facilities at a given site. This field is required for HL7 implementations that have more than a single facility with bed locations, since the same <nurse unit> ^ <room> ^ <bed> combination may exist at more than one facility.

Previous Page TOC Index Next Page