PV1: Patient visit

The card at the end of the bed: which ward, which room, which consultant, admitted when. PID says who the patient is; PV1 says where they are and what kind of stay this is.

PV1 describes one visit. It says where the patient is, what kind of stay it is, who is responsible for them and what the visit is called.

The shape of one line

PV1segmentwhat kind of line this is

1PV1-1Set ID - PV1

IPV1-2Patient Class

3W^312^A^STJOSEPHPV1-3Assigned Patient Location

PV1-4Admission Type

PV1-5Preadmit Number

PV1-6Prior Patient Location

1447312^OKONKWO^ADAEZE^^^^MDPV1-7Attending Doctor

required empty in this messageevery box is one | apart

Where PV1 appears

Message	Segment order
ADT^A01 admit	MSH → EVN → PID → [PD1] → [{NK1}] → PV1 → [PV2]
ADT^A08 update	MSH → EVN → PID → [PD1] → PV1 → [PV2] → [{OBX}]
ORU^R01 result	MSH → {PID → [PV1] → {OBR → {OBX}}}
DFT^P03 charge	MSH → EVN → PID → [PV1] → [PV2] → {FT1}

PV1 appears in 82 of the 202 message structures the standard defines.

A whole message

PV1 from an inpatient admission to a medical ward

MSH|^~\&|EPIC|STJOSEPH|LABSYS|STJOSEPH|20240314093015||ADT^A01^ADT_A01|MSG00017|P|2.5.1
EVN||20240314093000
PID|1||1000345678^^^STJOSEPH^MR||CARTWRIGHT^ELEANOR^MAY^^^^L||19510822|F
PV1|1|I|3W^312^A^STJOSEPH^^N^3 WEST^BED A||||1447312^OKONKWO^ADAEZE^^^^MD|2288104^HALVORSEN^PETER^^^^MD||MED||||1|||1447312^OKONKWO^ADAEZE^^^^MD|I|V100034567|SELF|||||||||||||||||||SJ||A|||20240314093000
PV2|||||||||20240321||||||||||||N

Every field

SEQ LEN DT OPT RP/# TBL# ITEM# Element name Cardinality

PV1-1 4 SI O 00131 Set ID - PV1 0..1

PV1-2 1 IS R 0004 00132 Patient Class 1..1

PV1-3 80 PL O 00133 Assigned Patient Location 0..1

PV1-3 is a PL, which holds 11 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
PL.1	20	IS	O	0302	Point of Care
PL.2	20	IS	O	0303	Room
PL.3	20	IS	O	0304	Bed
PL.4	227	HD	O		Facility
PL.5	20	IS	O	0306	Location Status
PL.6	20	IS	C	0305	Person Location Type
PL.7	20	IS	O	0307	Building
PL.8	20	IS	O	0308	Floor
PL.9	199	ST	O		Location Description
PL.10	427	EI	O		Comprehensive Location Identifier
PL.11	227	HD	O		Assigning Authority for Location

PV1-4 2 IS O 0007 00134 Admission Type 0..1

PV1-5 250 CX O 00135 Preadmit Number 0..1

PV1-5 is a CX, which holds 10 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
CX.1	15	ST	R		ID Number
CX.2	1	ST	O		Check Digit
CX.3	3	ID	O	0061	Check Digit Scheme
CX.4	227	HD	O	0363	Assigning Authority
CX.5	5	ID	O	0203	Identifier Type Code
CX.6	227	HD	O		Assigning Facility
CX.7	8	DT	O		Effective Date
CX.8	8	DT	O		Expiration Date
CX.9	705	CWE	O		Assigning Jurisdiction
CX.10	705	CWE	O		Assigning Agency or Department

PV1-6 80 PL O 00136 Prior Patient Location 0..1

PV1-6 is a PL, which holds 11 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
PL.1	20	IS	O	0302	Point of Care
PL.2	20	IS	O	0303	Room
PL.3	20	IS	O	0304	Bed
PL.4	227	HD	O		Facility
PL.5	20	IS	O	0306	Location Status
PL.6	20	IS	C	0305	Person Location Type
PL.7	20	IS	O	0307	Building
PL.8	20	IS	O	0308	Floor
PL.9	199	ST	O		Location Description
PL.10	427	EI	O		Comprehensive Location Identifier
PL.11	227	HD	O		Assigning Authority for Location

PV1-7 250 XCN O Y 0010 00137 Attending Doctor 0..*

PV1-7 is a XCN, which holds 23 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
XCN.1	15	ST	O		ID Number
XCN.2	194	FN	O		Family Name
XCN.3	30	ST	O		Given Name
XCN.4	30	ST	O		Second and Further Given Names or Initials Thereof
XCN.5	20	ST	O		Suffix (e.g., JR or III)
XCN.6	20	ST	O		Prefix (e.g., DR)
XCN.7	5	IS	B	0360	Degree (e.g., MD)
XCN.8	4	IS	C	0297	Source Table
XCN.9	227	HD	O	0363	Assigning Authority
XCN.10	1	ID	O	0200	Name Type Code
XCN.11	1	ST	O		Identifier Check Digit
XCN.12	3	ID	C	0061	Check Digit Scheme
XCN.13	5	ID	O	0203	Identifier Type Code
XCN.14	227	HD	O		Assigning Facility
XCN.15	1	ID	O	0465	Name Representation Code
XCN.16	483	CE	O	0448	Name Context
XCN.17	53	DR	B		Name Validity Range
XCN.18	1	ID	O	0444	Name Assembly Order
XCN.19	26	TS	O		Effective Date
XCN.20	26	TS	O		Expiration Date
XCN.21	199	ST	O		Professional Suffix
XCN.22	705	CWE	O		Assigning Jurisdiction
XCN.23	705	CWE	O		Assigning Agency or Department

PV1-8 250 XCN O Y 0010 00138 Referring Doctor 0..*

PV1-8 is a XCN, which holds 23 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
XCN.1	15	ST	O		ID Number
XCN.2	194	FN	O		Family Name
XCN.3	30	ST	O		Given Name
XCN.4	30	ST	O		Second and Further Given Names or Initials Thereof
XCN.5	20	ST	O		Suffix (e.g., JR or III)
XCN.6	20	ST	O		Prefix (e.g., DR)
XCN.7	5	IS	B	0360	Degree (e.g., MD)
XCN.8	4	IS	C	0297	Source Table
XCN.9	227	HD	O	0363	Assigning Authority
XCN.10	1	ID	O	0200	Name Type Code
XCN.11	1	ST	O		Identifier Check Digit
XCN.12	3	ID	C	0061	Check Digit Scheme
XCN.13	5	ID	O	0203	Identifier Type Code
XCN.14	227	HD	O		Assigning Facility
XCN.15	1	ID	O	0465	Name Representation Code
XCN.16	483	CE	O	0448	Name Context
XCN.17	53	DR	B		Name Validity Range
XCN.18	1	ID	O	0444	Name Assembly Order
XCN.19	26	TS	O		Effective Date
XCN.20	26	TS	O		Expiration Date
XCN.21	199	ST	O		Professional Suffix
XCN.22	705	CWE	O		Assigning Jurisdiction
XCN.23	705	CWE	O		Assigning Agency or Department

PV1-9 250 XCN B Y 0010 00139 Consulting Doctor deprecated 0..*

PV1-9 is a XCN, which holds 23 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
XCN.1	15	ST	O		ID Number
XCN.2	194	FN	O		Family Name
XCN.3	30	ST	O		Given Name
XCN.4	30	ST	O		Second and Further Given Names or Initials Thereof
XCN.5	20	ST	O		Suffix (e.g., JR or III)
XCN.6	20	ST	O		Prefix (e.g., DR)
XCN.7	5	IS	B	0360	Degree (e.g., MD)
XCN.8	4	IS	C	0297	Source Table
XCN.9	227	HD	O	0363	Assigning Authority
XCN.10	1	ID	O	0200	Name Type Code
XCN.11	1	ST	O		Identifier Check Digit
XCN.12	3	ID	C	0061	Check Digit Scheme
XCN.13	5	ID	O	0203	Identifier Type Code
XCN.14	227	HD	O		Assigning Facility
XCN.15	1	ID	O	0465	Name Representation Code
XCN.16	483	CE	O	0448	Name Context
XCN.17	53	DR	B		Name Validity Range
XCN.18	1	ID	O	0444	Name Assembly Order
XCN.19	26	TS	O		Effective Date
XCN.20	26	TS	O		Expiration Date
XCN.21	199	ST	O		Professional Suffix
XCN.22	705	CWE	O		Assigning Jurisdiction
XCN.23	705	CWE	O		Assigning Agency or Department

PV1-10 3 IS O 0069 00140 Hospital Service 0..1

PV1-11 80 PL O 00141 Temporary Location 0..1

PV1-11 is a PL, which holds 11 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
PL.1	20	IS	O	0302	Point of Care
PL.2	20	IS	O	0303	Room
PL.3	20	IS	O	0304	Bed
PL.4	227	HD	O		Facility
PL.5	20	IS	O	0306	Location Status
PL.6	20	IS	C	0305	Person Location Type
PL.7	20	IS	O	0307	Building
PL.8	20	IS	O	0308	Floor
PL.9	199	ST	O		Location Description
PL.10	427	EI	O		Comprehensive Location Identifier
PL.11	227	HD	O		Assigning Authority for Location

PV1-12 2 IS O 0087 00142 Preadmit Test Indicator 0..1

PV1-13 2 IS O 0092 00143 Re-admission Indicator 0..1

PV1-14 6 IS O 0023 00144 Admit Source 0..1

PV1-15 2 IS O Y 0009 00145 Ambulatory Status 0..*

PV1-16 2 IS O 0099 00146 VIP Indicator 0..1

PV1-17 250 XCN O Y 0010 00147 Admitting Doctor 0..*

PV1-17 is a XCN, which holds 23 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
XCN.1	15	ST	O		ID Number
XCN.2	194	FN	O		Family Name
XCN.3	30	ST	O		Given Name
XCN.4	30	ST	O		Second and Further Given Names or Initials Thereof
XCN.5	20	ST	O		Suffix (e.g., JR or III)
XCN.6	20	ST	O		Prefix (e.g., DR)
XCN.7	5	IS	B	0360	Degree (e.g., MD)
XCN.8	4	IS	C	0297	Source Table
XCN.9	227	HD	O	0363	Assigning Authority
XCN.10	1	ID	O	0200	Name Type Code
XCN.11	1	ST	O		Identifier Check Digit
XCN.12	3	ID	C	0061	Check Digit Scheme
XCN.13	5	ID	O	0203	Identifier Type Code
XCN.14	227	HD	O		Assigning Facility
XCN.15	1	ID	O	0465	Name Representation Code
XCN.16	483	CE	O	0448	Name Context
XCN.17	53	DR	B		Name Validity Range
XCN.18	1	ID	O	0444	Name Assembly Order
XCN.19	26	TS	O		Effective Date
XCN.20	26	TS	O		Expiration Date
XCN.21	199	ST	O		Professional Suffix
XCN.22	705	CWE	O		Assigning Jurisdiction
XCN.23	705	CWE	O		Assigning Agency or Department

PV1-18 2 IS O 0018 00148 Patient Type 0..1

PV1-19 250 CX O 00149 Visit Number 0..1

PV1-19 is a CX, which holds 10 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
CX.1	15	ST	R		ID Number
CX.2	1	ST	O		Check Digit
CX.3	3	ID	O	0061	Check Digit Scheme
CX.4	227	HD	O	0363	Assigning Authority
CX.5	5	ID	O	0203	Identifier Type Code
CX.6	227	HD	O		Assigning Facility
CX.7	8	DT	O		Effective Date
CX.8	8	DT	O		Expiration Date
CX.9	705	CWE	O		Assigning Jurisdiction
CX.10	705	CWE	O		Assigning Agency or Department

PV1-20 50 FC O Y 0064 00150 Financial Class 0..*

PV1-20 is a FC, which holds 2 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
FC.1	20	IS	R	0064	Financial Class Code
FC.2	26	TS	O		Effective Date

PV1-21 2 IS O 0032 00151 Charge Price Indicator 0..1

PV1-22 2 IS O 0045 00152 Courtesy Code 0..1

PV1-23 2 IS O 0046 00153 Credit Rating 0..1

PV1-24 2 IS O Y 0044 00154 Contract Code 0..*

PV1-25 8 DT O Y 00155 Contract Effective Date 0..*

PV1-26 12 NM O Y 00156 Contract Amount 0..*

PV1-27 3 NM O Y 00157 Contract Period 0..*

PV1-28 2 IS O 0073 00158 Interest Code 0..1

PV1-29 4 IS O 0110 00159 Transfer to Bad Debt Code 0..1

PV1-30 8 DT O 00160 Transfer to Bad Debt Date 0..1

PV1-31 10 IS O 0021 00161 Bad Debt Agency Code 0..1

PV1-32 12 NM O 00162 Bad Debt Transfer Amount 0..1

PV1-33 12 NM O 00163 Bad Debt Recovery Amount 0..1

PV1-34 1 IS O 0111 00164 Delete Account Indicator 0..1

PV1-35 8 DT O 00165 Delete Account Date 0..1

PV1-36 3 IS O 0112 00166 Discharge Disposition 0..1

PV1-37 47 DLD O 0113 00167 Discharged to Location 0..1

PV1-37 is a DLD, which holds 2 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
DLD.1	20	IS	R	0113	Discharge Location
DLD.2	26	TS	O		Effective Date

PV1-38 250 CE O 0114 00168 Diet Type 0..1

PV1-38 is a CE, which holds 6 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
CE.1	20	ST	O		Identifier
CE.2	199	ST	O		Text
CE.3	20	ID	O	0396	Name of Coding System
CE.4	20	ST	O		Alternate Identifier
CE.5	199	ST	O		Alternate Text
CE.6	20	ID	O	0396	Name of Alternate Coding System

PV1-39 2 IS O 0115 00169 Servicing Facility 0..1

PV1-40 1 IS B 0116 00170 Bed Status deprecated 0..1

PV1-41 2 IS O 0117 00171 Account Status 0..1

PV1-42 80 PL O 00172 Pending Location 0..1

PV1-42 is a PL, which holds 11 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
PL.1	20	IS	O	0302	Point of Care
PL.2	20	IS	O	0303	Room
PL.3	20	IS	O	0304	Bed
PL.4	227	HD	O		Facility
PL.5	20	IS	O	0306	Location Status
PL.6	20	IS	C	0305	Person Location Type
PL.7	20	IS	O	0307	Building
PL.8	20	IS	O	0308	Floor
PL.9	199	ST	O		Location Description
PL.10	427	EI	O		Comprehensive Location Identifier
PL.11	227	HD	O		Assigning Authority for Location

PV1-43 80 PL O 00173 Prior Temporary Location 0..1

PV1-43 is a PL, which holds 11 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
PL.1	20	IS	O	0302	Point of Care
PL.2	20	IS	O	0303	Room
PL.3	20	IS	O	0304	Bed
PL.4	227	HD	O		Facility
PL.5	20	IS	O	0306	Location Status
PL.6	20	IS	C	0305	Person Location Type
PL.7	20	IS	O	0307	Building
PL.8	20	IS	O	0308	Floor
PL.9	199	ST	O		Location Description
PL.10	427	EI	O		Comprehensive Location Identifier
PL.11	227	HD	O		Assigning Authority for Location

PV1-44 26 TS O 00174 Admit Date/Time 0..1

PV1-44 is a TS, which holds 2 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
TS.1	24	DTM	R		Time
TS.2	1	ID	B	0529	Degree of Precision

PV1-45 26 TS O Y 00175 Discharge Date/Time 0..*

PV1-45 is a TS, which holds 2 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
TS.1	24	DTM	R		Time
TS.2	1	ID	B	0529	Degree of Precision

PV1-46 12 NM O 00176 Current Patient Balance 0..1

PV1-47 12 NM O 00177 Total Charges 0..1

PV1-48 12 NM O 00178 Total Adjustments 0..1

PV1-49 12 NM O 00179 Total Payments 0..1

PV1-50 250 CX O 0203 00180 Alternate Visit ID 0..1

PV1-50 is a CX, which holds 10 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
CX.1	15	ST	R		ID Number
CX.2	1	ST	O		Check Digit
CX.3	3	ID	O	0061	Check Digit Scheme
CX.4	227	HD	O	0363	Assigning Authority
CX.5	5	ID	O	0203	Identifier Type Code
CX.6	227	HD	O		Assigning Facility
CX.7	8	DT	O		Effective Date
CX.8	8	DT	O		Expiration Date
CX.9	705	CWE	O		Assigning Jurisdiction
CX.10	705	CWE	O		Assigning Agency or Department

PV1-51 1 IS O 0326 01226 Visit Indicator 0..1

PV1-52 250 XCN B Y 0010 01274 Other Healthcare Provider deprecated 0..*

PV1-52 is a XCN, which holds 23 components separated by carets.

SEQ	LEN	DT	OPT	TBL#	Component name
XCN.1	15	ST	O		ID Number
XCN.2	194	FN	O		Family Name
XCN.3	30	ST	O		Given Name
XCN.4	30	ST	O		Second and Further Given Names or Initials Thereof
XCN.5	20	ST	O		Suffix (e.g., JR or III)
XCN.6	20	ST	O		Prefix (e.g., DR)
XCN.7	5	IS	B	0360	Degree (e.g., MD)
XCN.8	4	IS	C	0297	Source Table
XCN.9	227	HD	O	0363	Assigning Authority
XCN.10	1	ID	O	0200	Name Type Code
XCN.11	1	ST	O		Identifier Check Digit
XCN.12	3	ID	C	0061	Check Digit Scheme
XCN.13	5	ID	O	0203	Identifier Type Code
XCN.14	227	HD	O		Assigning Facility
XCN.15	1	ID	O	0465	Name Representation Code
XCN.16	483	CE	O	0448	Name Context
XCN.17	53	DR	B		Name Validity Range
XCN.18	1	ID	O	0444	Name Assembly Order
XCN.19	26	TS	O		Effective Date
XCN.20	26	TS	O		Expiration Date
XCN.21	199	ST	O		Professional Suffix
XCN.22	705	CWE	O		Assigning Jurisdiction
XCN.23	705	CWE	O		Assigning Agency or Department

Open this PV1 message in HL7 Studio

Field notes

PV1-2Patient Class
Patient class, bound to table 0004, and the field that decides how the rest of the message should be read. I is inpatient, O is outpatient, E is emergency, P is preadmit, R is recurring, B is obstetrics, N is not applicable. It drives billing, bed management and clinical workflow all at once, which is why a system that gets it wrong gets several things wrong at the same time. It is required in v2.5.1 and senders do populate it.
Open PV1-2 in HL7 Studio
PV1-3Assigned Patient Location
Assigned patient location, a PL, and rarely understood in full. Component 1 is the point of care, usually the ward or unit; component 2 is the room; component 3 is the bed; component 4 is the facility. Sites use the components inconsistently, and a common local convention puts a whole location string in component 1 with the rest empty. Read all four and reconstruct, do not parse component 1 as free text.
Open PV1-3 in HL7 Studio
PV1-4Admission Type
Admission type, bound to table 0007. A is accident, E is emergency, L is labour and delivery, R is routine, N is newborn, C is elective, U is urgent. It says how the patient came to be admitted, and it is not the same question as PV1-2, which says what kind of stay resulted.
Open PV1-4 in HL7 Studio
PV1-7Attending Doctor
Attending doctor, an XCN with the identifier in component 1 and the name in components 2 to 6. PV1-8 is the referring doctor, PV1-9 the consulting doctor and PV1-17 the admitting doctor. They are different roles and a message often carries the same person in several of them. Mapping all of them to one participant collapses information that the receiving system will later be asked for.
Open PV1-7 in HL7 Studio
PV1-10Hospital Service
Hospital service, bound to table 0069. This is the clinical service responsible for the patient, such as medicine or surgery, and it is distinct from the physical location in PV1-3. A patient on a medical service can occupy a surgical bed.
Open PV1-10 in HL7 Studio
PV1-19Visit Number
Visit number, and the identifier that ties everything about this encounter together. Later messages about the same stay carry the same value, which is what lets a receiver update the visit instead of creating a second one. It is not PID-18, the account number, though sites exist where the two happen to be equal and code written against such a site breaks when it meets one where they are not.
Open PV1-19 in HL7 Studio
PV1-44Admit Date/Time
Admit date and time, and PV1-45 the discharge date and time. The presence of PV1-45 is a stronger signal that the visit ended than the event code is, because a correction or update sent later can carry a discharge date while being an A08. Where the two disagree, the field is the fact and the trigger event is the reason it was sent.
Open PV1-44 in HL7 Studio
PV1-51Visit Indicator
Visit indicator, which says what PV1-19 is identifying: A for an account and V for a visit. When it is absent, assume a visit. A feed that sets it to A is telling you PV1-19 is account-scoped and will be shared across several encounters.
Open PV1-51 in HL7 Studio

Vendor behaviour

What follows describes patterns common to these systems' standard interfaces. Every installation is configured, so confirm against the interface specification for the site you are integrating with.

Epic

Epic populates PV1-3 with the point of care, room and bed as separate components, and the values correspond to the department and bed records in the system, not to anything printed on a door. PV1-19 carries the contact serial number, which is stable for the encounter and is the correct key for updating an existing visit.

Cerner

Cerner feeds distinguish the encounter identifier in PV1-19 from the financial number, and the two are separate concepts in Millennium. Treating PV1-19 as a billing key on a Cerner interface produces encounters that appear to merge and split across a stay.

Mapping to FHIR

PV1 maps to FHIR Encounter, and the two line up well because both are modelling a stay. Patient class becomes Encounter.class, the assigned location becomes an Encounter.location entry, and the doctor fields become Encounter.participant entries distinguished by participant type. The visit number becomes Encounter.identifier and is what makes the mapping idempotent across the A01, A02 and A03 that describe the same stay.

HL7 v2	FHIR R4	Note
PV1-2	Encounter.class	via the v2-to-FHIR class ConceptMap
PV1-3	Encounter.location.location	resolve the PL components to a Location resource
PV1-7	Encounter.participant	type ATND
PV1-8	Encounter.participant	type REF
PV1-17	Encounter.participant	type ADM
PV1-19	Encounter.identifier	the key that decides update or create
PV1-44, PV1-45	Encounter.period	start and end
PV1-36	Encounter.hospitalization.dischargeDisposition

Parsing pitfalls

PV1-19 and PID-18 are treated as interchangeable
The visit number identifies an encounter and the account number identifies a billing account. One account can span several visits. Sites where they happen to carry the same value are common enough to hide the bug until the interface meets a site where they do not.
The location is read as a single string
PV1-3 is a PL with four meaningful components. Storing the raw field as a display string works until someone asks which ward the patient is on, and then the answer has to be re-derived from text that different senders formatted differently.
Assuming an A03 is the only way a visit ends
Discharge information arrives on corrections and updates too. Keying discharge handling on the trigger event instead of on PV1-45 leaves visits open when the discharge was communicated by an A08.
Every doctor field mapped to the same role
Attending, referring, consulting and admitting are four different fields answering four different questions. Flattening them loses the distinction that clinical and billing systems downstream will need.
PV1-2 changing mid-stay is not an error
A patient admitted from the emergency department moves from class E to class I on the same visit number. Code that treats a class change as a data problem will reject the message that reports it.

Message types carrying PV1

PV1 appears in 82 message structures, belonging to 45 message types.

PV1: Patient visit

The shape of one line

Where PV1 appears

A whole message

Every field

Field notes

PV1-2Patient Class

PV1-3Assigned Patient Location

PV1-4Admission Type

PV1-7Attending Doctor

PV1-10Hospital Service

PV1-19Visit Number

PV1-44Admit Date/Time

PV1-51Visit Indicator

Vendor behaviour

Epic

Cerner

Mapping to FHIR

Parsing pitfalls

PV1-19 and PID-18 are treated as interchangeable

The location is read as a single string

Assuming an A03 is the only way a visit ends

Every doctor field mapped to the same role

PV1-2 changing mid-stay is not an error

Related

Message types carrying PV1