Schedule a demo
Message type

Collaborative care query update

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

61segments
28required
15groups
v2.9HL7 version
cqu-i19.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CQU^I19^CQU_I19|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 CQU^I19 messages in Python

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

1

Parse an incoming CQU^I19 message

Demonstrates receiving and extracting key fields from a collaborative care query update transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'CQU^I19^CQU_I19|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||CQU^I19^CQU_I19|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|\rRF1||ROUTINE^Routine^HL70283||20260401|20260430\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: MSA, RF1, PRD, PID, IN1, SCH, RGS, OBX. 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.

CQU^I19 segment composition

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

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

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python