Patient additional demographic

PD1 carries additional patient demographics not found in PID - living arrangement, student status, immunization registry status, military service details, advance directive codes, and primary care facility. It appears in ADT and registration messages.

Create a PD1 segment and read its fields directly:

from zato.hl7v2.v2_9 import PD1, CWE

pd1 = PD1()
pd1.living_arrangement = CWE(identifier='A')
pd1.student_indicator = CWE(identifier='F')
pd1.immunization_registry_status = CWE(
    identifier='A'
)

arrangement = pd1.living_arrangement
student = pd1.student_indicator
registry = pd1.immunization_registry_status

Position 4 (Patient Primary Care Provider Name & ID No.) was withdrawn in HL7 v2.9. The field is retained as a gap to preserve the positional numbering of all subsequent fields. This is standard HL7v2 practice for deprecated fields.

The patient_primary_facility field uses the XON (extended composite organization name) datatype:

from zato.hl7v2.v2_9 import PD1, XON

pd1 = PD1()
pd1.patient_primary_facility = XON(
    organization_name='Greenvalley Wellness',
    id_number='12345'
)

Military branch, rank, and status each use the CWE datatype:

from zato.hl7v2.v2_9 import PD1, CWE

pd1 = PD1()
pd1.military_branch = CWE(identifier='USA')
pd1.military_rank_grade = CWE(
    identifier='CPT'
)
pd1.military_status = CWE(identifier='ACT')

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.