Display send time

DST specifies where display data from an original-mode query response should be routed - for example, to a printer, terminal, or file. It accompanies DSP segments in tabular and display response messages.

The destination field uses the CWE datatype with HL7 table 0943:

from zato.hl7v2.v2_9 import DST, CWE

dst = DST()
dst.destination = CWE(
    identifier='PRINTER',
    text='Main printer',
    name_of_coding_system='HL70943'
)

Yes, for simple cases you can assign a plain string value directly:

from zato.hl7v2.v2_9 import DST

dst = DST()
dst.destination = 'PRINTER'

DST appears in original-mode tabular and display response messages (e.g., TBR, DSR). It is paired with DSP segments that carry the actual text rows to be displayed or printed.

DST tells the receiving system where to send the output, while DSP carries the actual text content. You typically have one DST and multiple DSP segments in a response:

from zato.hl7v2.v2_9 import DST, DSP, CWE

dst = DST()
dst.destination = CWE(
    identifier='TERM',
    text='Terminal',
    name_of_coding_system='HL70943'
)

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.