Carries a single row of data values corresponding to the column definitions provided in the preceding RDF segment, with each field mapping positionally to a defined column. It is used in tabular query responses and waveform data transmissions, enabling systems to exchange variable-format result data (such as query results or multi-channel waveform samples) in a generalized table structure.
from zato.hl7v2.v2_9 import RDT
rdt = RDT()
rdt.column_value = '88^10500^1.9'How to construct and work with real-world RDT segments.
Three values for score, steps, and hydration matching a three-column RDF
from zato.hl7v2.v2_9 import RDT
rdt = RDT()
rdt.column_value = '88^10500^1.9'Fiber and calories for a two-column RDF
from zato.hl7v2.v2_9 import RDT
rdt = RDT()
rdt.column_value = '28^1850'One aerobic capacity value for a single-column RDF
from zato.hl7v2.v2_9 import RDT
rdt = RDT()
rdt.column_value = '42.5'Step-by-step guides for working with HL7 v2 in Zato.
RDT holds one row of result data. The column_value field stores the encoded cells in RDF column order.
Use one component per RDF column, joined with ^ inside the single field unless your profile uses another varies encoding.
Receivers expect RDF first. Send RDF before RDT rows so parsers know column count and labels.
QRD and QRF frame legacy query filters while MSH and MSA wrap the message. DSC may follow when the response spans multiple chunks.
Assign a string that matches your RDF column count and encoding rules:
from zato.hl7v2.v2_9 import RDT
rdt = RDT()
rdt.column_value = '92^11200^2.0'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.
Complete list of fields in the RDT segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | column_value | varies | Required | No | - |
Get started with Zato and connect your systems in minutes.