Payer Master File

PM1 defines insurance plan attributes and data collection requirements in payer master file messages. It specifies which patient and claims data elements a payer requires for processing, allowing registration systems to enforce payer-specific validation rules.

The health_plan_id field uses the CWE datatype with HL7 table 0072:

from zato.hl7v2.v2_9 import PM1, CWE

pm1 = PM1()
pm1.health_plan_id = CWE(
    identifier='BCBS001',
    text='Blue Cross',
    name_of_coding_system='HL70072'
)

Use plan_effective_date and plan_expiration_date with date strings in YYYYMMDD format:

from zato.hl7v2.v2_9 import PM1

pm1 = PM1()
pm1.plan_effective_date = '20240101'
pm1.plan_expiration_date = '20241231'

Each requirement flag accepts Y (yes) or N (no) from HL7 table 0136:

from zato.hl7v2.v2_9 import PM1

pm1 = PM1()
pm1.patient_dob_required = 'Y'
pm1.patient_gender_required = 'Y'
pm1.diagnosis_required = 'Y'
pm1.service_required = 'Y'
pm1.patient_name_required = 'Y'
pm1.patient_signature_required = 'N'

Use policy_number_pattern and group_number_pattern to define regex validation patterns:

from zato.hl7v2.v2_9 import PM1

pm1 = PM1()
pm1.policy_number_pattern = 'POL-[0-9]{10}'
pm1.group_number_pattern = 'GRP-[0-9]{4}'

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.