Patient visit - additional information

PV2 provides additional visit details that extend PV1, such as the reason for admission, expected length of stay, visit description, referral source, living will status, and organ donor code. It always accompanies a PV1 segment.

The admit_reason field is a CWE datatype with an identifier and descriptive text:

from zato.hl7v2.v2_9 import PV2, CWE

pv2 = PV2()
pv2.admit_reason = CWE(
    identifier='SC',
    text='Scheduled procedure'
)

Use the expected_admit_date_time and expected_discharge_date_time fields:

from zato.hl7v2.v2_9 import PV2

pv2 = PV2()
pv2.expected_admit_date_time = '20240601080000'
pv2.expected_discharge_date_time = '20240604120000'

The referral_source_code field uses the XCN (extended composite name) datatype to identify the referring clinician:

from zato.hl7v2.v2_9 import PV2, XCN

pv2 = PV2()
pv2.referral_source_code = XCN(
    person_identifier='7890',
    family_name='Garcia',
    given_name='Maria',
    suffix='MD'
)

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.