Product detail country

PDC carries country-specific product registration details including the country code, brand name, generic name, product code, marketing basis, approval ID, and shelf life information. It supports product experience reports by providing the regulatory and commercial context for a product in a specific jurisdiction.

The country field uses the CWE datatype with HL7 table 0675:

from zato.hl7v2.v2_9 import PDC, CWE

pdc = PDC()
pdc.country = CWE(
    identifier='USA',
    text='United States',
    name_of_coding_system='ISO3166'
)

The product_code field uses the CWE datatype with HL7 table 0677:

from zato.hl7v2.v2_9 import PDC, CWE

pdc = PDC()
pdc.product_code = CWE(
    identifier='DYB',
    text='ECG Monitor',
    name_of_coding_system='FDA'
)

The marketing_basis field uses HL7 table 0330 for the regulatory clearance type:

from zato.hl7v2.v2_9 import PDC

pdc = PDC()

# 510K = 510(k) clearance
pdc.marketing_basis = '510K'

# PMA = Pre-market approval
pdc.marketing_basis = 'PMA'

Use date_first_marketed and date_last_marketed to track when the product entered and left the market:

from zato.hl7v2.v2_9 import PDC

pdc = PDC()
pdc.date_first_marketed = '20200601'
pdc.date_last_marketed = '20240101'

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.