The PV1 segment is used by Registration/Patient Administration applications to communicate information on an account or visit-specific basis. The default is to send account level data. To use this segment for visit level data PV1-51 - Visit Indicator must be valued to "V". The value of PV-51 affects the level of data being sent on the PV1, PV2, and any other segments that are part of the associated PV1 hierarchy (e.g., ROL, DG1, or OBX).
The facility ID, the optional fourth component of each patient location field, is a HD data type that is uniquely associated with the healthcare facility containing the location. A given institution, or group of intercommunicating institutions, should establish a list of facilities that may be potential assignors of patient locations. The list will be one of the institution's master dictionary lists. Since third parties other than the assignors 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 healthcare facility with bed locations, since the same <point of care> ^ <room> ^ <bed> combination may exist at more than one facility.
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
PV1
|
|||||||||
1
|
Set ID - PV1 | SI | O | [0..1] | 00131 | [1..4] | |||
|
2
|
Patient Class | CWE | R | [1..1] | 00132 | ||||
|
3
|
Assigned Patient Location | PL | O | [0..1] | 00133 | ||||
|
4
|
Admission Type | CWE | O | [0..1] | 00134 | ||||
|
5
|
Preadmit Number | CX | O | [0..1] | 00135 | ||||
|
6
|
Prior Patient Location | PL | O | [0..1] | 00136 | ||||
|
7
|
Attending Doctor | XCN | O | [0..*] | 00137 | ||||
|
8
|
Referring Doctor | XCN | O | [0..*] | 00138 | ||||
|
9
|
Consulting Doctor | XCN | B | [0..*] | 00139 | ||||
|
10
|
Hospital Service | CWE | O | [0..1] | 00140 | ||||
|
11
|
Temporary Location | PL | O | [0..1] | 00141 | ||||
|
12
|
Preadmit Test Indicator | CWE | O | [0..1] | 00142 | ||||
|
13
|
Re-admission Indicator | CWE | O | [0..1] | 00143 | ||||
|
14
|
Admit Source | CWE | O | [0..1] | 00144 | ||||
|
15
|
Ambulatory Status | CWE | O | [0..*] | 00145 | ||||
|
16
|
VIP Indicator | CWE | O | [0..1] | 00146 | ||||
|
17
|
Admitting Doctor | XCN | O | [0..*] | 00147 | ||||
|
18
|
Patient Type | CWE | O | [0..1] | 00148 | ||||
|
19
|
Visit Number | CX | O | [0..1] | 00149 | ||||
|
20
|
Financial Class | FC | O | [0..*] | 00150 | ||||
|
21
|
Charge Price Indicator | CWE | O | [0..1] | 00151 | ||||
|
22
|
Courtesy Code | CWE | O | [0..1] | 00152 | ||||
|
23
|
Credit Rating | CWE | O | [0..1] | 00153 | ||||
|
24
|
Contract Code | CWE | O | [0..*] | 00154 | ||||
|
25
|
Contract Effective Date | DT | O | [0..*] | 00155 | ||||
|
26
|
Contract Amount | NM | O | [0..*] | 00156 | 12 | # | ||
|
27
|
Contract Period | NM | O | [0..*] | 00157 | 3 | # | ||
|
28
|
Interest Code | CWE | O | [0..1] | 00158 | ||||
|
29
|
Transfer to Bad Debt Code | CWE | O | [0..1] | 00159 | ||||
|
30
|
Transfer to Bad Debt Date | DT | O | [0..1] | 00160 | ||||
|
31
|
Bad Debt Agency Code | CWE | O | [0..1] | 00161 | ||||
|
32
|
Bad Debt Transfer Amount | NM | O | [0..1] | 00162 | 12 | # | ||
|
33
|
Bad Debt Recovery Amount | NM | O | [0..1] | 00163 | 12 | # | ||
|
34
|
Delete Account Indicator | CWE | O | [0..1] | 00164 | ||||
|
35
|
Delete Account Date | DT | O | [0..1] | 00165 | ||||
|
36
|
Discharge Disposition | CWE | O | [0..1] | 00166 | ||||
|
37
|
Discharged to Location | DLD | O | [0..1] | 00167 | ||||
|
38
|
Diet Type | CWE | O | [0..1] | 00168 | ||||
|
39
|
Servicing Facility | CWE | O | [0..1] | 00169 | ||||
|
40
|
Bed Status | CWE | W | [0..1] | 00170 | ||||
|
41
|
Account Status | CWE | O | [0..1] | 00171 | ||||
|
42
|
Pending Location | PL | O | [0..1] | 00172 | ||||
|
43
|
Prior Temporary Location | PL | O | [0..1] | 00173 | ||||
|
44
|
Admit Date/Time | DTM | O | [0..1] | 00174 | ||||
|
45
|
Discharge Date/Time | DTM | O | [0..1] | 00175 | ||||
|
46
|
Current Patient Balance | NM | O | [0..1] | 00176 | 12 | # | ||
|
47
|
Total Charges | NM | O | [0..1] | 00177 | 12 | # | ||
|
48
|
Total Adjustments | NM | O | [0..1] | 00178 | 12 | # | ||
|
49
|
Total Payments | NM | O | [0..1] | 00179 | 12 | # | ||
|
50
|
Alternate Visit ID | CX | O | [0..*] | 00180 | ||||
|
51
|
Visit Indicator | CWE | O | [0..1] | 01226 | ||||
|
52
|
Other Healthcare Provider | W | [0..1] | 01274 | |||||
|
53
|
Service Episode Description | ST | O | [0..1] | 02290 | 50 | # | ||
54
|
Service Episode Identifier | CX | O | [0..1] | 02291 | ||||
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
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 in Chapter 2C, Code Tables, for suggested values.
"Commercial Account" is used by reference labs for specimen processing when the service is billed back to a third party. A registration is processed for the specimen to facilitate the subsequent billing. The identity of the patient may be known or unknown. In either case, for billing and statistical purposes, the patient class is considered a commercial account due to the third party billing responsibility.
"Not Applicable" is used only in cases where the PV1 segment itself is not applicable but is retained in the message definitions for backwards compatibility (for example when a managed care system sends A28, A29, or A31 messages to indicate the enrolment of a patient in the system and there is no scheduled "visit" or "encounter" and hence the entire PV1 segment is not applicable).
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 or department, for locations other than inpatient. For canceling a transaction or discharging a patient, the current location (after the cancellation event or before the discharge event) should be in this field. If a value exists in the fifth component (location status), it supersedes the value in PV1-40 - Bed Status.
Definition: This field indicates the circumstances under which the patient was or will be admitted. Refer to User-defined Table 0007 - Admission Type in Chapter 2C, Code Tables, for suggested values. In the US, entities required to be compliant with the US Healthcare Information Technology Standards Panel (HITSP) are required to use the Official Universal Billing (UB) 04 2008 numeric codes found on form locator 14. Refer to External Table UB04FL14 for valid values.
For example:
Non-US |E^Emergency^HL70007|
US: |1^Emergency^UB04FL14^^^^2008, v 2.0|
To report that information is not available:
Non-US: |NI^No Information^HL70597|
US: |9^Information not available^ UB04FL14^^^^2008, v 2.0|
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, a ST data type can be sent; however, HL7 recommends use of the CX data type, like the account number, for new implementations. The assigning authority and identifier type codes are strongly recommended for all CX data types.
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 (location status), it supersedes the value in PV1-40 - Bed Status.
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. As of v2.7, if XCN.1 ID Number is populated, then the XCN.13 Identifier Type Code and the XCN.9 Assigning Authority or XCN.22 Assigning Jurisdiction or XCN.23 Assigning Agency or Department are required. If XCN.2 Family Name is populated, then the XCN.10 Name Type Code is required. No assumptions can be safely made based on position or sequence. Specification of meaning based on sequence is deprecated. Depending on local agreements, either ID or the name may be absent in this field. Refer to User-defined Table 0010 - Physician ID in Chapter 2C, Code Tables, for suggested values.
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. As of v 2.7 if XCN.1 ID Number is populated, then the XCN.13 Identifier Type Code and the XCN.9 Assigning Authority or XCN.22 Assigning Jurisdiction or XCN.23 Assigning Agency or Department are required. If XCN.2 Family Name is populated, then the XCN.10 Name Type Code is required. No assumptions can be safely made based on position or sequence. Specification of meaning based on sequence is deprecated. Depending on local agreements, either the ID or the name may be absent from this field. Refer to User-defined Table 0010 - Physician ID in Chapter 2C, Code Tables, for suggested values.
From V2.4 onward, this field has been retained for backward compatibility only. It is recommended to use the PRT - Participation segment for consulting physicians instead.
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 (admit/visit notification), A02 (transfer a patient), A14 (pending admit), A15 (pending transfer). Refer to User-defined Table 0069 - Hospital Service in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains a location other than the assigned location required for a temporary period of time (e.g., OR, operating theatre, etc.). If a value exists in the fifth component (location status), it supersedes the value in PV1-40 - Bed Status.
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 in Chapter 2C, Code Tables, for suggested values.
Definition: This field indicates that a patient is being re-admitted to the healthcare facility and gives the circumstances. We suggest using "R" for readmission or else null. Refer to User-defined Table 0092 - Re-Admission Indicator in Chapter 2C, Code Tables, for suggested values.
Definition: This field indicates from where the patient was admitted. Refer to User-defined Table 0023 - Admit Source in Chapter 2C, Code Tables, for suggested values. In the US, this field should use the Official Uniform Billing (UB) 04 2008 numeric codes found on form locator 15. Refer to External Table UB04FL15 Source of Origin for valid values. The UB has redefined the Admission Source as the Point of Origin for Admission or Visit. The new UB definition is the code indicating the Point of Origin for this Admission or Visit
For Example:
US: |1^Physician Referral^UB04FL15^^^^2008, v 2.0|
To report that information is not available:
US: |9^Information not available^ UB04FL15^^^^2008, v 2.0|
Definition: This field indicates any permanent or transient handicapped conditions. Refer to User-defined Table 0009 - Ambulatory Status in Chapter 2C, Code Tables, for suggested entries.
Definition: This field identifies the type of VIP. Refer to User-defined Table 0099 - VIP Indicator in Chapter 2C, Code Tables, for suggested values.
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. As of v2.7 if XCN.1 ID Number is populated, then the XCN.13 Identifier Type Code and the XCN.9 Assigning Authority or XCN.22 Assigning Jurisdiction or XCN.23 Assigning Agency or Department are required. If XCN.2 Family Name is populated, then the XCN.10 Name Type Code is required. No assumptions can be safely made based on position or sequence. Specification of meaning based on sequence is deprecated. By local agreement, the name or ID may be absent in this field. Refer to User-defined Table 0010 - Physician ID in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains site-specific values that identify the patient type. Refer to User-defined Table 0018 - Patient Type in Chapter 2C, Code Tables, for suggested values.
Definition: For backward compatibility, a 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. The assigning authority and identifier type code are strongly recommended for all CX data types.
Definition: This field contains the financial class(es) assigned to the patient for the purpose of identifying sources of reimbursement. Refer to User-defined Table 0064 - Financial Class in Chapter 2C, Code Tables, for suggested values.
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 in Chapter 2C, Code Tables, for suggested values.
Definition: This field indicates whether the patient will be extended certain special courtesies. Refer to User-defined Table 0045 - Courtesy Code in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the user-defined code to determine past credit experience. Refer to User-defined Table 0046 - Credit Rating in Chapter 2C, Code Tables, for suggested values.
Definition: This field identifies the type of contract entered into by the healthcare facility and the guarantor for the purpose of settling outstanding account balances. Refer to User-defined Table 0044 - Contract Code in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the date that the contract is to start or started.
Definition: This field contains the amount to be paid by the guarantor each period according to the contract.
Definition: This field specifies the duration of the contract for user-defined periods.
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 in Chapter 2C, Code Tables, for suggested values.
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 in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the date that the account was transferred to a bad debt status.
Definition: This field can be used as a 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; in chapter 2C, however, this is not required.
Definition: This field contains the amount that was transferred to a bad debt status.
Definition: This field contains the amount recovered from the guarantor on the account.
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 in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the date that the account was deleted from the file.
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 - Discharge Disposition in Chapter 2C, Code Tables, for suggested values. In the US, this field should use the Official Uniform Billing (UB) 04 2008 numeric codes found on form locator 17. Refer to External Table UB04FL17 Patient Discharge Status for valid values.
Examples:
US: |01^ Discharged to home or self care (routine discharge)^UB04FL17^^^^2008, v 2.0|
Usage Note: NUBC does not supply a null value for this field.
Definition: This field indicates the healthcare facility to which the patient was discharged and the date. Refer to User-defined Table 0113 - Discharged to Location in Chapter 2C, Code Tables, for suggested values.
Definition: This field indicates a special diet type for a patient. Refer to User-defined Table 0114 - Diet Type in Chapter 2C, Code Tables, for suggested values.
Definition: This field is used in a multiple facility environment, e.g., multiple campuses or buildings, to indicate the healthcare facility with which this visit is associated. Refer to User-defined Table 0115 - Servicing Facility in Chapter 2C, Code Tables, for suggested values.
An optional sixth component, the facility ID, may be valued in each individual location field in PV1, instead of placing it here.
Definition: The PV1-40 field was retained for backward compatibility only as of v 2.3, and the field withdrawn as of v 2.7. The information is now held in the fifth component of the PL datatype in PV1-3.
Definition: This field contains the account status. Refer to User-defined Table 0117 - Account Status in Chapter 2C, Code Tables, for suggested values.
Definition: This field indicates the point of care, room, bed, healthcare 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 (location status), it supersedes the value in PV1-40 - Bed Status.
Definition: This field is used to reflect the patient's temporary location (such as the operating room/theatre or x-ray) 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.
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.
Definition: This field contains the discharge date/time. It is to be used if the event date/time is different than the discharge date and time, that is, a retroactive update. This field is also used to reflect the date/time of an outpatient/emergency patient discharge.
Definition: This field contains the visit balance due.
Definition: This field contains the total visit charges.
Definition: This field contains the total adjustments for visit.
Definition: This field contains the total payments for visit.
Definition: This field contains the alternative, temporary, or pending optional visit ID number to be used if needed. Multiple alternate identifiers may be sent. Refer to HL7 Table 0061 - Check Digit Scheme in Chapter 2C, Code Tables, for valid values. Refer to HL7 Table 0203 - Identifier Type in Chapter 2C, Code Tables, for valid values. The assigning authority and identifier type codes are strongly recommended for all CX data types.
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 are at the visit level. Refer to User-defined Table 0326 - Visit Indicator in Chapter 2C, Code Tables, for suggested values.
The value of this element affects the context of data sent in PV1, PV2 and any associated hierarchical segments (e.g., DB1, AL1, DG1, etc.).
Definition: The PV1-52 field was retained for backward compatibility only as of v 2.4 and withdrawn as of v 2.7. The reader is advised to use the PRT segment to communicate providers not specified elsewhere. Refer to Chapter 7 for the definition of the PRT segment.
Definition: This field contains a brief user-defined description of a Service Episode in or for which the visit occurs. A Service Episode is the context in which the treatment or management of an arbitrary subset of a Patient’s medical conditions occurs. The definition of the start time, stop time, and included events of a Service Episode is entirely arbitrary; it may include a single outpatient visit or a hospitalization, or extend over significant period of time, e.g., the duration of a pregnancy, or an oncology treatment regimen, or a cardiac episode from infarction through rehabilitation. A Service Episode may involve one or more Healthcare Organizations.
Definition: This field contains the identifier of a Service Episode in or for which the visit occurs.
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
