Reference·PV1 Segment·PV1-19
HL7 v2 Reference

PV1-19 in HL7 v2: A Field Guide to Visit Number

Jul 27, 2026 · 4 min read
← PV1-18 PV1-20 →

PV1-19 is the field nearly every clinical result, order, and charge gets tied back to during a stay, which makes it one of the highest-stakes fields in the entire segment — and also one of the easiest to get wrong when a health system merges data from multiple source systems.

Quick answer

PV1-19 is the nineteenth field of the PV1 segment — a composite (CX data type) identifier that uniquely represents this specific visit or encounter, distinct from the patient's MRN.

What this field contains

Component 1
ID Number — the visit/encounter number itself
Component 4
Assigning Authority, when populated — identifies which system issued the number
Component 5
Identifier Type Code, e.g. VN for visit number

Example

Synthetic example Generated by Synthibase
PV1|1|I|3W^301^B^HOSP|U|||445566^PATEL^RAJ^S^^MD|667788^JONES^MARY^E^^MD|889900^LEE^DAVID^R^^MD|CAR||||7|||998877^CHEN^LISA^K^^MD|I|8827364501|MCR||||||||||||||||01||||||||202607261430

The 19th field (8827364501) is the unique visit number for this encounter. Synthetic patient — not a real person.

Where this trips people up

Visit numbers are frequently unique only within the facility or system that assigned them, not globally — a bare numeric value like "8827364501" can theoretically be reused at a different hospital in the same health system. Integrations that treat PV1-19 as a globally unique key without also checking the assigning authority component can accidentally merge two completely unrelated encounters the moment a second facility's data flows through the same pipeline.

Testing HL7 v2 PV1: The Fields Your System Actually Needs to Handle
How to Build a Test Environment Strategy for a Multi-Hospital System
Synthetic Patient Data: Complete Guide for Software Testing
Test visit number collisions before they happen
Synthibase generates synthetic PV1 segments with realistic, facility-scoped visit numbers — so encounter-merging bugs surface in testing, not production.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.