Schedule a demo
Segment

Imaging procedure control

Carries the workflow context for imaging procedure fulfillment, including the accession identifier, requested procedure identifier, study instance UID, scheduled procedure step identifier, modality, and protocol code. Developed in collaboration with DICOM, it appears in OMI (Imaging Order) messages exchanged between order entry systems, RIS, and PACS, enabling imaging systems to share the scheduling and tracking context of imaging studies.

10fields
4required
v2.9HL7 version
ipc.py
from zato.hl7v2.v2_9 import IPC
from zato.hl7v2.v2_9 import EI, CWE

ipc = IPC()
ipc.accession_identifier = EI(entity_identifier='ACC20240115001')
ipc.requested_procedure_id = EI(entity_identifier='PROC001')

Build IPC segments in Python

How to construct and work with real-world IPC segments.

1

CT scan procedure

CT imaging workflow

from zato.hl7v2.v2_9 import IPC
from zato.hl7v2.v2_9 import EI, CWE

ipc = IPC()
ipc.accession_identifier = EI(entity_identifier='ACC20240115001')
ipc.requested_procedure_id = EI(entity_identifier='PROC001')
ipc.study_instance_uid = EI(entity_identifier='1.2.840.10008.5.1.4.1.1.2')
ipc.scheduled_procedure_step_id = EI(entity_identifier='CT')
2

MRI procedure

MRI imaging workflow

from zato.hl7v2.v2_9 import IPC
from zato.hl7v2.v2_9 import EI, CWE

ipc = IPC()
ipc.accession_identifier = EI(entity_identifier='ACC20240115002')
ipc.requested_procedure_id = EI(entity_identifier='PROC002')
ipc.study_instance_uid = EI(entity_identifier='1.2.840.10008.5.1.4.1.1.4')
ipc.scheduled_procedure_step_id = EI(entity_identifier='MRI')
3

X-ray procedure

X-ray imaging workflow

from zato.hl7v2.v2_9 import IPC
from zato.hl7v2.v2_9 import EI, CWE

ipc = IPC()
ipc.accession_identifier = EI(entity_identifier='ACC20240115003')
ipc.requested_procedure_id = EI(entity_identifier='PROC003')
ipc.study_instance_uid = EI(entity_identifier='1.2.840.10008.5.1.4.1.1.1')
ipc.scheduled_procedure_step_id = EI(entity_identifier='XR')

Learn by building

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

Frequently asked questions

IPC contains imaging procedure control information including accession identifiers, study UIDs, and procedure codes for radiology workflow.

A study instance UID is a unique identifier for a DICOM study, used to link HL7 messages with DICOM images.

Use accession_identifier field with EI datatype:

from zato.hl7v2.v2_9 import IPC
from zato.hl7v2.v2_9 import EI

ipc = IPC()
ipc.accession_identifier = EI(entity_identifier='ACC20240115001')

IPC contains imaging-specific control information while OBR contains the general observation request. IPC follows OBR in radiology messages.

action_code documents scheduling and follow-up steps for preventive imaging, helping teams coordinate bone health, cardiovascular fitness, and nutrition-related screening studies.

from zato.hl7v2.v2_9 import IPC

ipc = IPC()
ipc.action_code = 'U'

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.

IPC field reference

Complete list of fields in the IPC segment, HL7 v2.9.

#Python nameDatatypeUsageRepeatableTable
1accession_identifierEIRequiredNo-
2requested_procedure_idEIRequiredNo-
3study_instance_uidEIRequiredNo-
4scheduled_procedure_step_idEIRequiredNo-
5modalityCWEOptionalNoHL70604
6protocol_codeCWEOptionalYesHL70605
7scheduled_station_nameEIOptionalNo-
8scheduled_procedure_step_locationCWEOptionalYesHL70606
9scheduled_station_ae_titleSTOptionalNo-
10action_codeIDOptionalNo-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python