PV1 Segment

Set ID - PV1

Patient Class

The correct classification of encounters into inpatient, outpatient, emergency, recurring, etc. is key to both HIEBus Beacon alerting and Galileo™ population health analytics. HIEBus relies on values in line with HL7 Table 0004. If other values are used for PV1-2, a dictionary will need to be provided.

Assigned Patient Location

If PV1-3.4 Facility is not present, MSH-4.1 Sending Facility Namespace ID is used as facility. If a value is present in PV1-3.4, HIEBus can optionally prefix it with the value in MSH-4.1.

Admission Type

A dictionary of the values used will be needed.

Preadmit Number

Prior Patient Location

Attending Doctor

HL7 specifies that multiple repetitions of this field are not used to represent multiple attending doctors. Instead, multiple repetitions are used to specify multiple names and identifiers for the same physician. If multiple caregivers are intended, then ROL segments should be used. However, some source systems are not capable of utilizing ROL segments for this purpose. Therefore, during setup, HIEBus provides the option to treat multiple repetitions as multiple caregivers.HIEBus will need to know what identifier is being provided and at what scope that identifier is valid. NPI is strongly preferred, but local identifiers are accepted.

Referring Doctor

HL7 specifies that multiple repetitions of this field are not used to represent multiple referring doctors. Instead, multiple repetitions are used to specify multiple names and identifiers for the same physician. If multiple caregivers are intended, then ROL segments should be used. However, some source systems are not capable of utilizing ROL segments for this purpose. Therefore, during setup, HIEBus provides the option to treat multiple repetitions as multiple caregivers.HIEBus will need to know what identifier is being provided and at what scope that identifier is valid. NPI is strongly preferred, but local identifiers are accepted.

Consulting Doctor

HIEBus will need to know what identifier is being provided and at what scope that identifier is valid. NPI is strongly preferred, but local identifiers are accepted.

Hospital Service

A dictionary of the values used will be needed.

Temporary Location

Preadmit Test Indicator

Re-admission Indicator

Admit Source

Ambulatory Status

VIP Indicator

Admitting Doctor

HL7 specifies that multiple repetitions of this field are not used to represent multiple admitting doctors. Instead, multiple repetitions are used to specify multiple names and identifiers for the same physician. If multiple caregivers are intended, then ROL segments should be used. However, some source systems are not capable of utilizing ROL segments for this purpose. Therefore, during setup, HIEBus provides the option to treat multiple repetitions as multiple caregivers.HIEBus will need to know what identifier is being provided and at what scope that identifier is valid. NPI is strongly preferred, but local identifiers are accepted.

Patient Type

A dictionary of the values used will be needed.

Visit Number

HIEBus by default uses PID-18 as the encounter identifier. However, during configuration, HIEBus provides the option of using PV1-19 instead, or using PV1-19 only when PID-18 is not present.

Financial Class

Charge Price Indicator

Courtesy Code

Credit Rating

Contract Code

Contract Effective Date

Contract Amount

Contract Period

Interest Code

Transfer to Bad Debt Code

Transfer to Bad Debt Date

Bad Debt Agency Code

Bad Debt Transfer Amount

Bad Debt Recovery Amount

Delete Account Indicator

Delete Account Date

Discharge Disposition

A dictionary of the values used will be needed.

Discharged to Location

Diet Type

Servicing Facility

Bed Status

Account Status

Pending Location

Prior Temporary Location

Admit Date/Time

Discharge Date/Time

Current Patient Balance

Total Charges

Total Adjustments

Total Payments

Alternate Visit ID

Visit Indicator

Other Healthcare Provider

Service Episode Description

Service Episode Identifier