Indicates that a message response is being split across multiple messages due to size or quantity limits. It carries a continuation pointer value that the querying system sends back in a subsequent query to retrieve the next batch of results. It appears at the end of query responses and large unsolicited messages, enabling paginated retrieval of large result sets.
from zato.hl7v2.v2_9 import DSC
dsc = DSC()
dsc.continuation_pointer = 'WELL-PAGE-02'
dsc.continuation_style = 'P'How to construct and work with real-world DSC segments.
Partial continuation style with a stable pointer for preventive-care chart pages
from zato.hl7v2.v2_9 import DSC
dsc = DSC()
dsc.continuation_pointer = 'WELL-CHART-PAGE-2'
dsc.continuation_style = 'P'Token referencing the next chunk of a structured fitness log extract
from zato.hl7v2.v2_9 import DSC
dsc = DSC()
dsc.continuation_pointer = 'FIT-LOG-TOKEN-88'
dsc.continuation_style = 'P'Pointer-only row when partners rely on the token string without a style code
from zato.hl7v2.v2_9 import DSC
dsc = DSC()
dsc.continuation_pointer = 'NUTRI-TIMELINE-NEXT'Step-by-step guides for working with HL7 v2 in Zato.
MSH-14 can carry a continuation pointer on the outbound message, while DSC often appears at the end of a query response group to request or supply the next page token for wellness or fitness payloads.
HL70398 describes whether the chunk is the first segment, a partial middle segment, or the last segment of a series. Partners align tokens with that metadata for reliable paging.
Assign a short opaque string your hub understands, optionally with a style code:
from zato.hl7v2.v2_9 import DSC
dsc = DSC()
dsc.continuation_pointer = 'PAGE-TOKEN-99'
dsc.continuation_style = 'P'Yes. Many wellness interfaces send only the pointer token when the style is implicitly partial or negotiated out of band.
DSC typically trails the data sections it summarizes, often after OBX or PID groups in query responses, so receivers know another GET or poll should use the supplied token.
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 DSC segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | continuation_pointer | ST | Optional | No | - |
| 2 | continuation_style | ID | Optional | No | HL70398 |
Get started with Zato and connect your systems in minutes.