HL7 PV2 Segment: Patient Visit – Additional Information | Vorro Academy

The PV2 segment carries supplementary visit information that does not fit in PV1: the reason for admission, transfer, expected admit and discharge times, estimated length of stay, visit priority, mode of arrival, and a long tail of clinical and administrative flags. PV2 always follows PV1 and never appears without it — where PV1 holds the core administrative visit data, PV2 adds the detail that downstream clinical and scheduling systems use.

Purpose

PV2 extends PV1 with the additional context of a single visit: admit and transfer reasons, expected admit/discharge timestamps, estimated and actual length of stay, referral source, visit priority and publicity, mode of arrival, and a set of clinical indicators (precautions, advance directives, organ donor, living will). Fields are populated per trigger event — a pre-admit fills the expected dates an admit later confirms.

Used in

PV2 appears in ADT messages as the companion to PV1, carrying the additional visit detail that PV1 cannot hold. It is sent only when PV1 is present and is used by registration, scheduling, and clinical systems that need the expected dates, reason, and arrival context. See ADT.

Field-by-field reference

Source: the Vorro HL7 segment database (extracted from the official v2-to-FHIR IG). R = required (cardinality min ≥ 1). Repeat = field may repeat. Length is not carried by the FHIR source and is shown as —.

Seq	Name	Data Type	Length	Req	Repeat	Table #	Description
PV2-1	Prior Pending Location	PL	—	O	—	—	Location a pending transfer was set to.
PV2-2	Accommodation Code	CWE	—	O	—	HL70129	Accommodation type requested or assigned.
PV2-3	Admit Reason	CWE	—	O	—	—	Reason the patient was admitted.
PV2-4	Transfer Reason	CWE	—	O	—	—	Reason the patient was transferred.
PV2-5	Patient Valuables	ST	—	O	Y	—	Description of patient valuables held.
PV2-6	Patient Valuables Location	ST	—	O	—	—	Where the valuables are stored.
PV2-7	Visit User Code	CWE	—	O	Y	HL70130	Site-defined categorization of the visit.
PV2-8	Expected Admit Date/Time	DTM	—	O	—	—	Planned date and time of admission.
PV2-9	Expected Discharge Date/Time	DTM	—	O	—	—	Planned date and time of discharge.
PV2-10	Estimated Length of Inpatient Stay	NM	—	O	—	—	Estimated number of inpatient days.
PV2-11	Actual Length of Inpatient Stay	NM	—	O	—	—	Actual number of inpatient days.
PV2-12	Visit Description	ST	—	O	—	—	Free-text description of the visit.
PV2-13	Referral Source Code	XCN	—	O	Y	—	Person or entity that referred the patient.
PV2-14	Previous Service Date	DT	—	O	—	—	Date of the prior service for this condition.
PV2-15	Employment Illness Related Indicator	ID	—	O	—	—	Whether the visit relates to employment.
PV2-16	Purge Status Code	CWE	—	O	—	HL70213	Record purge status.
PV2-17	Purge Status Date	DT	—	O	—	—	Date the record is eligible for purge.
PV2-18	Special Program Code	CWE	—	O	—	HL70214	Special program the visit falls under.
PV2-19	Retention Indicator	ID	—	O	—	—	Whether the record is retained.
PV2-20	Expected Number of Insurance Plans	NM	—	O	—	—	Count of insurance plans expected.
PV2-21	Visit Publicity Code	CWE	—	O	—	HL70215	Disclosure level allowed for the visit.
PV2-22	Visit Protection Indicator	ID	—	O	—	—	Whether visit data is protected.
PV2-23	Clinic Organization Name	XON	—	O	Y	—	Clinic or organization name for the visit.
PV2-24	Patient Status Code	CWE	—	O	—	HL70216	Status of the patient within the visit.
PV2-25	Visit Priority Code	CWE	—	O	—	HL70217	Urgency or priority of the visit.
PV2-26	Previous Treatment Date	DT	—	O	—	—	Date of previous treatment.
PV2-27	Expected Discharge Disposition	CWE	—	O	—	—	Anticipated discharge disposition.
PV2-28	Signature on File Date	DT	—	O	—	—	Date the signature was placed on file.
PV2-29	First Similar Illness Date	DT	—	O	—	—	First occurrence date of a similar illness.
PV2-30	Patient Charge Adjustment Code	CWE	—	O	—	—	Charge adjustment applied to the patient.
PV2-31	Recurring Service Code	CWE	—	O	—	HL70219	Whether the visit is a recurring service.
PV2-32	Billing Media Code	ID	—	O	—	—	Media used for billing the visit.
PV2-33	Expected Surgery Date and Time	DTM	—	O	—	—	Planned date and time of surgery.
PV2-34	Military Partnership Code	ID	—	O	—	—	Military partnership treatment flag.
PV2-35	Military Non-Availability Code	ID	—	O	—	—	Military non-availability status.
PV2-36	Newborn Baby Indicator	ID	—	O	—	—	Whether the patient is a newborn.
PV2-37	Baby Detained Indicator	ID	—	O	—	—	Whether the baby is detained after the mother.
PV2-38	Mode of Arrival Code	CWE	—	O	—	HL70430	How the patient arrived (ambulance, walk-in).
PV2-39	Recreational Drug Use Code	CWE	—	O	Y	HL70431	Recreational drug use reported.
PV2-40	Admission Level of Care Code	CWE	—	O	—	HL70432	Level of care at admission.
PV2-41	Precaution Code	CWE	—	O	Y	HL70433	Precautions to take with the patient.
PV2-42	Patient Condition Code	CWE	—	O	—	HL70434	Patient condition (e.g. stable, critical).
PV2-43	Living Will Code	CWE	—	O	—	HL70315	Whether a living will exists.
PV2-44	Organ Donor Code	CWE	—	O	—	HL70316	Organ donor status.
PV2-45	Advance Directive Code	CWE	—	O	Y	HL70435	Advance directive on file.
PV2-46	Patient Status Effective Date	DT	—	O	—	—	Date the patient status took effect.
PV2-47	Expected LOA Return Date/Time	DTM	—	O	—	—	Expected return from leave of absence.
PV2-48	Expected Pre-admission Testing Date/Time	DTM	—	O	—	—	Planned pre-admission testing time.
PV2-49	Notify Clergy Code	CWE	—	O	Y	HL70534	Whether clergy should be notified.
PV2-50	Advance Directive Last Verified Date	DT	—	O	—	—	Date the advance directive was last verified.

Most-used fields

PV2-3 Admit Reason gives the clinical reason for the visit and maps directly to Encounter.reasonCode, feeding downstream clinical and reporting logic.
PV2-8 Expected Admit Date/Time and PV2-9 Expected Discharge Date/Time drive pre-admit and bed-planning workflows before the actual admit fills PV1-44.
PV2-11 Actual Length of Inpatient Stay supplies the encounter length used for utilization and analytics.
PV2-25 Visit Priority Code conveys urgency and maps to Encounter.priority.
PV2-38 Mode of Arrival Code (ambulance, walk-in, public transport) is widely used by emergency-department systems for triage.

Version differences (2.3 to 2.8.2)

2.3: PV2 introduced with the core reason, expected-date, and length-of-stay fields.
2.4/2.5: PV2-38 through PV2-45 added — Mode of Arrival, Recreational Drug Use, Admission Level of Care, Precaution, Patient Condition, Living Will, Organ Donor, Advance Directive.
2.5+: coded fields move from CE toward CWE.
2.6/2.7: PV2-46 through PV2-50 added — Patient Status Effective Date, Expected LOA Return, Pre-admission Testing, Notify Clergy, Advance Directive Last Verified.
Receivers built for an earlier version ignore the trailing fields they do not recognize.

Common mistakes

Sending PV2 without a preceding PV1 — PV2 is a companion segment and must follow PV1.
Confusing PV2-8/PV2-9 expected dates with PV1-44/PV1-45 actual admit/discharge times.
Treating PV2-3 Admit Reason as the encounter reason while ignoring diagnosis segments (DG1) that may carry the coded condition.
Reading only the first repetition of repeating fields such as PV2-41 Precaution Code or PV2-45 Advance Directive Code.
Dropping clinical flags (PV2-43/44/45) that some receivers rely on for consent and care-planning.

Examples

Minimal valid PV2 (admit reason only):

PV2|||Chest pain

Fully-populated PV2 (pre-admit with expected dates and arrival):

PV2|3WEST^310^B^MERCYGEN|PVT|Chest pain|||||20260609080000|20260612080000|3||Cardiology workup|1234^JONES^ROBERT^^^^MD||||||||||EM|||||||||||||AMB||3A||STABLE|||||||||

Annotated breakdown of the fully-populated example (selected fields):

PV2                              ← segment ID
3WEST^310^B^MERCYGEN             ← PV2-1  Prior Pending Location (unit^room^bed^facility)
PVT                              ← PV2-2  Accommodation Code (private)
Chest pain                       ← PV2-3  Admit Reason
20260609080000                  ← PV2-8  Expected Admit Date/Time
20260612080000                  ← PV2-9  Expected Discharge Date/Time
3                                ← PV2-10 Estimated Length of Inpatient Stay (days)
Cardiology workup                ← PV2-12 Visit Description
1234^JONES^ROBERT^^^^MD          ← PV2-13 Referral Source Code
EM                               ← PV2-25 Visit Priority Code (emergency)
AMB                              ← PV2-38 Mode of Arrival Code (ambulance)
3A                               ← PV2-40 Admission Level of Care Code
STABLE                           ← PV2-42 Patient Condition Code

In-context inside an ADT^A01 (admit), PV2 immediately after PV1:

MSH|^~&|REG|MERCYGEN|EHR|MERCYGEN|20260609120000||ADT^A01^ADT_A01|MSG002|P|2.5.1
EVN|A01|20260609120000
PID|1||MR12345^^^MERCYGEN^MR||DOE^JOHN^Q||19800101|M
PV1|1|I|3WEST^301^A||||1234^SMITH^JANE^A^^^MD|||MED||||ADM|||||V0001|||||||||||||||||||||||20260609120000
PV2|||Chest pain|||||20260609120000|20260612080000|3||Cardiology workup||||||||||||EM

In-context inside an ADT^A05 (pre-admit, expected dates set before the visit begins):

MSH|^~&|REG|MERCYGEN|EHR|MERCYGEN|20260607090000||ADT^A05^ADT_A05|MSG031|P|2.5.1
EVN|A05|20260607090000
PID|1||MR12345^^^MERCYGEN^MR||DOE^JOHN^Q||19800101|M
PV1|1|P|3WEST^310^B||||1234^SMITH^JANE^A^^^MD|||MED|||||||||V0007
PV2|||Elective cardiac cath|||||20260609080000|20260610080000|1||Pre-admit testing|||||||||||||R||||STABLE

FHIR mapping

Primary (and only) target resource: Encounter. PV2 supplies the supplementary visit details that complement the core PV1 mapping — reason, planned dates, length, referral source, priority, and mode of arrival. Official ConceptMap: Encounter.

Key Encounter mappings (from the DB):

PV2 field	FHIR target (Encounter)
PV2-1 Prior Pending Location	`Encounter.location[5].location` (Location), `location[5].status` = `planned`
PV2-3 Admit Reason	`Encounter.reasonCode[1]`
PV2-8 Expected Admit Date/Time	`Encounter.extension[1]` (plannedStartDate)
PV2-9 Expected Discharge Date/Time	`Encounter.extension[2]` (plannedEndDate)
PV2-11 Actual Length of Inpatient Stay	`Encounter.length` (Duration)
PV2-12 Visit Description	`Encounter.text.div`
PV2-13 Referral Source Code	`Encounter.participant.individual` (Practitioner, type REF)
PV2-22 Visit Protection Indicator	`Encounter.meta.security`
PV2-25 Visit Priority Code	`Encounter.priority`
PV2-38 Mode of Arrival Code	`Encounter.extension[1].valueCoding` (encounter-modeOfArrival)

Unmapped fields: the DB publishes no Encounter mapping for the remaining PV2 fields — the accommodation, valuables, visit-user, purge, billing, military, newborn, and most clinical-flag fields (PV2-2, PV2-4 through PV2-7, PV2-10, PV2-14 through PV2-21, PV2-23, PV2-24, PV2-26 through PV2-37, PV2-39 through PV2-50 except PV2-38). These carry administrative or clinical detail not represented on the Encounter resource.

Engine considerations

PV2 has no required fields; populate only what a receiver actually consumes, and always send it after PV1.
Parse PV2-1 as a structured PL so unit, room, bed, and facility survive.
Distinguish PV2-8/PV2-9 expected dates from PV1-44/PV1-45 actual times when building the encounter period and planning extensions.
Preserve repeating fields (PV2-5, PV2-7, PV2-13, PV2-23, PV2-39, PV2-41, PV2-45, PV2-49) as arrays.
Map coded fields against their HL7 tables (e.g. PV2-25 priority, PV2-38 mode of arrival) rather than passing raw codes through.

How Vorro parses and produces PV2

Vorro reads PV2 in the context of its preceding PV1, maps PV2-3 to Encounter.reasonCode, PV2-25 to Encounter.priority, and PV2-8/PV2-9 to the planned-start and planned-end extensions. Expected dates are kept distinct from PV1 actuals, repeating clinical and referral fields are preserved as arrays, and on the FHIR side Vorro emits the supplementary Encounter elements per the official ConceptMap while leaving unmapped administrative fields available for site-specific extensions.

PV1 — the core patient visit segment PV2 complements.
PID — the patient the visit belongs to.
ADT messages — where PV2 accompanies PV1 in admit, transfer, and discharge events.

Sources

← Back to HL7 v2 Guide

HL7 PV2 Segment: Patient Visit – Additional Information