Schedule a demo
Message type

Collaborative care message

Supports collaborative care coordination between providers. Key segments include MSH, PID, SCH, OBX. Care coordination platforms and clinical systems exchange this to share patient care information across organizational boundaries.

53segments
25required
13groups
v2.9HL7 version
ccm-i21.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CCM^I21^CCM_I21|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

Build and parse CCM^I21 messages in Python

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

1

Parse an incoming CCM^I21 message

Demonstrates receiving and extracting key fields from a collaborative care message transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CCM^I21^CCM_I21|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

Learn by building

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

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||CCM^I21^CCM_I21|MSG00001|P|2.9\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rNK1|1|JOHNSON^MICHAEL|SPO^Spouse|100 Oak Lane^^Portland^OR^97201|5035551234\rREL|1||HAS^Has^HL70948'
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, IN1, SCH, RGS, OBX, ORC, OBX, PV1. 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.

CCM^I21 segment composition

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

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5PIDRequiredNoPatient identification-
6PD1OptionalNoPatient additional demographic-
7NK1OptionalYesNext of kin / associated parties-
8IN1RequiredNoInsuranceINSURANCE
9IN2OptionalNoInsurance additional infoINSURANCE
10IN3OptionalNoInsurance additional info - certificationINSURANCE
11SCHRequiredNoScheduling activity informationAPPOINTMENT_HISTORY
12RGSRequiredNoResource groupAPPOINTMENT_HISTORY
13OBXRequiredNoObservation resultRESOURCE_DETAIL
14PRTOptionalYesParticipation informationRESOURCE_DETAIL
15ORCRequiredNoCommon orderCLINICAL_HISTORY
16OBXRequiredNoObservation resultCLINICAL_HISTORY_OBSERVATION
17PRTOptionalYesParticipation informationCLINICAL_HISTORY_OBSERVATION
18VAROptionalYesVarianceCLINICAL_HISTORY
19CTIOptionalYesClinical trial identificationCLINICAL_HISTORY
20PV1RequiredNoPatient visitPATIENT_VISITS
21PV2OptionalNoPatient visit - additional infoPATIENT_VISITS
22ORCRequiredNoCommon orderMEDICATION_HISTORY
23RXORequiredNoPharmacy / treatment orderMEDICATION_HISTORY
24RXRRequiredYesPharmacy / treatment routeMEDICATION_HISTORY
25RXCOptionalYesPharmacy / treatment component orderMEDICATION_HISTORY
26OBXRequiredNoObservation resultMEDICATION_ORDER_OBSERVATION
27PRTOptionalYesParticipation informationMEDICATION_ORDER_OBSERVATION
28RXERequiredNoPharmacy / treatment encoded orderMEDICATION_HISTORY
29RXRRequiredYesPharmacy / treatment routeMEDICATION_HISTORY
30RXCOptionalYesPharmacy / treatment component orderMEDICATION_HISTORY
31OBXRequiredNoObservation resultMEDICATION_ENCODING_OBSERVATION
32PRTOptionalYesParticipation informationMEDICATION_ENCODING_OBSERVATION
33RXARequiredYesPharmacy / treatment administrationMEDICATION_HISTORY
34RXRRequiredNoPharmacy / treatment routeMEDICATION_HISTORY
35OBXRequiredNoObservation resultMEDICATION_ADMINISTRATION_OBSERVATION
36PRTOptionalYesParticipation informationMEDICATION_ADMINISTRATION_OBSERVATION
37CTIOptionalYesClinical trial identificationMEDICATION_HISTORY
38PRBRequiredNoProblem detailPROBLEM
39VAROptionalYesVariancePROBLEM
40VAROptionalYesVariancePROBLEM
41OBXRequiredNoObservation resultPROBLEM
42PRTOptionalYesParticipation informationPROBLEM
43GOLRequiredNoGoal detailGOAL
44VAROptionalYesVarianceGOAL
45VAROptionalYesVarianceGOAL
46OBXRequiredNoObservation resultGOAL
47PRTOptionalYesParticipation informationGOAL
48PTHRequiredNoPathwayPATHWAY
49VAROptionalYesVariancePATHWAY
50VAROptionalYesVariancePATHWAY
51OBXRequiredNoObservation resultPATHWAY
52PRTOptionalYesParticipation informationPATHWAY
53RELOptionalYesClinical relationship segment-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python