Patient death and autopsy

PDA carries death and autopsy information for a patient. It includes the death location, certification status, certificate signing date, the certifying provider, autopsy indicator, autopsy date range and performer, and whether a coroner was involved. It appears in ADT death notification messages.

The death_location field uses the PL (person location) datatype:

from zato.hl7v2.v2_9 import PDA, PL

pda = PDA()
pda.death_location = PL(
    point_of_care='ICU',
    room='Room 4',
    facility='Main Hospital'
)

The autopsy_start_and_end_date_time field uses the DR (date/time range) datatype:

from zato.hl7v2.v2_9 import PDA, DR

pda = PDA()
pda.autopsy_start_and_end_date_time = DR(
    range_start_date_time='20240602080000',
    range_end_date_time='20240602170000'
)

The death_certified_by field uses the XCN (extended composite ID) datatype:

from zato.hl7v2.v2_9 import PDA, XCN

pda = PDA()
pda.death_certified_by = XCN(
    person_identifier='5544',
    family_name='JONES',
    given_name='MARIA',
    suffix='MD'
)

The coroner_indicator field uses HL7 table 0136 with standard Y/N values:

from zato.hl7v2.v2_9 import PDA

pda = PDA()
pda.coroner_indicator = 'Y'

pda2 = PDA()
pda2.coroner_indicator = 'N'

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.