Message type

Automated time intervals for reporting clinical trials

Reports automated time intervals for clinical trial monitoring. The CSR segment identifies the study and CSP/CSS segments carry phase and schedule details.

28segments

11required

6groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CSU^C09^CSU_C09|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Python examples

Build and parse CSU^C09 messages in Python

How to construct, send, receive, and extract fields from real-world CSU^C09 messages.

Parse an incoming CSU^C09 message

Demonstrates receiving and extracting key fields from a automated time intervals for reporting clinical trials transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CSU^C09^CSU_C09|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Tutorials

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

Frequently asked questions

Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.

from zato.hl7v2 import HL7Message

raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||CSU^C09^CSU_C09|MSG00001|P|2.9'
msg = HL7Message.parse(raw)

name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Beyond the mandatory MSH header, the required segments are: PID, PV1, CSR, ORC, OBR, TQ1, OBX, ORC. Optional segments provide additional detail when available.

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.

Reference

CSU^C09 segment composition

Segments that make up the CSU^C09 message, in order. Groups are shown with their child segments.

#	Segment	Usage	Repeats	Description	Group
1	`MSH`	Required	No	Message header	-
2	`ARV`	Optional	Yes	Access restriction	-
3	`SFT`	Optional	Yes	Software segment	-
4	`UAC`	Optional	No	User authentication credential	-
5	`PID`	Required	No	Patient identification	PATIENT
6	`PD1`	Optional	No	Patient additional demographic	PATIENT
7	`PRT`	Optional	Yes	Participation information	PATIENT
8	`ARV`	Optional	Yes	Access restriction	PATIENT
9	`NTE`	Optional	Yes	Notes and comments	PATIENT
10	`PV1`	Required	No	Patient visit	PATIENT
11	`PV2`	Optional	No	Patient visit - additional info	PATIENT
12	`PRT`	Optional	Yes	Participation information	PATIENT
13	`CSR`	Required	No	Clinical study registration	PATIENT
14	`CSP`	Optional	No	Clinical study phase	PATIENT
15	`CSS`	Optional	No	Clinical study data schedule segment	STUDY_SCHEDULE
16	`ORC`	Required	No	Common order	STUDY_OBSERVATION_ORDER
17	`PRT`	Optional	Yes	Participation information	STUDY_OBSERVATION_ORDER
18	`OBR`	Required	No	Observation request	STUDY_SCHEDULE
19	`PRT`	Optional	Yes	Participation information	STUDY_SCHEDULE
20	`TQ1`	Required	No	Timing / quantity	TIMING_QTY
21	`TQ2`	Optional	Yes	Timing / quantity relationship	TIMING_QTY
22	`OBX`	Required	No	Observation result	STUDY_SCHEDULE
23	`PRT`	Optional	Yes	Participation information	STUDY_SCHEDULE
24	`ORC`	Required	No	Common order	COMMON_ORDER
25	`PRT`	Optional	Yes	Participation information	COMMON_ORDER
26	`RXA`	Required	No	Pharmacy / treatment administration	RX_ADMIN
27	`RXR`	Required	No	Pharmacy / treatment route	RX_ADMIN
28	`PRT`	Optional	Yes	Participation information	RX_ADMIN

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python