Message type

Schedule request response

Responds to a scheduling request (SRM^S01). The SCH segment carries the confirmed or rejected appointment details.

22segments

9required

5groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'SRR^S01^SRR_S01|MSG001|P|2.9\r' \
      'SCH|SCH001||||||||30|MIN|^^30^20260701\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M'

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

# .. whose fields we can now access.
schedule_id = msg.sch.placer_appointment_id
duration = msg.sch.appointment_duration
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Python examples

Build and parse SRR^S01 messages in Python

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

Parse an incoming SRR^S01 message

Demonstrates receiving and extracting key fields from a schedule request response transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'SRR^S01^SRR_S01|MSG001|P|2.9\r' \
      'SCH|SCH001||||||||30|MIN|^^30^20260701\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M'

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

# .. whose fields we can now access.
schedule_id = msg.sch.placer_appointment_id
duration = msg.sch.appointment_duration
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

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||SRR^S01^SRR_S01|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|'
msg = HL7Message.parse(raw)

schedule_id = msg.sch.placer_appointment_id
duration = msg.sch.appointment_duration

Beyond the mandatory MSH header, the required segments are: MSA, SCH, PID, RGS, AIS, AIG, AIL, AIP. 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

SRR^S01 segment composition

Segments that make up the SRR^S01 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	`MSA`	Required	No	Message acknowledgment	-
4	`ERR`	Optional	Yes	Error	-
5	`SCH`	Required	No	Scheduling activity information	SCHEDULE
6	`TQ1`	Optional	Yes	Timing / quantity	SCHEDULE
7	`NTE`	Optional	Yes	Notes and comments	SCHEDULE
8	`PID`	Required	No	Patient identification	SCHEDULE
9	`PRT`	Optional	Yes	Participation information	SCHEDULE
10	`PV1`	Optional	No	Patient visit	SCHEDULE
11	`PV2`	Optional	No	Patient visit - additional info	SCHEDULE
12	`PRT`	Optional	Yes	Participation information	SCHEDULE
13	`DG1`	Optional	Yes	Diagnosis	SCHEDULE
14	`RGS`	Required	No	Resource group	SCHEDULE
15	`AIS`	Required	No	Appointment information - service	SERVICE
16	`NTE`	Optional	Yes	Notes and comments	SERVICE
17	`AIG`	Required	No	Appointment information - general resource	GENERAL_RESOURCE
18	`NTE`	Optional	Yes	Notes and comments	GENERAL_RESOURCE
19	`AIL`	Required	No	Appointment information - location resource	LOCATION_RESOURCE
20	`NTE`	Optional	Yes	Notes and comments	LOCATION_RESOURCE
21	`AIP`	Required	No	Appointment information - personnel resource	PERSONNEL_RESOURCE
22	`NTE`	Optional	Yes	Notes and comments	PERSONNEL_RESOURCE

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python