HL7 IPC Imaging Procedure Control Segment
HL7 field reference IPC fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| IPC.1 | Accession Identifier | Yes | No | EI | |
| IPC.2 | Requested Procedure ID | Yes | No | EI | |
| IPC.3 | Study Instance UID | Yes | No | EI | |
| IPC.4 | Scheduled Procedure Step ID | Yes | No | EI | |
| IPC.5 | Modality | No | No | CE | |
| IPC.6 | Protocol Code | No | Yes | CE | |
| IPC.7 | Scheduled Station Name | No | No | EI | |
| IPC.8 | Scheduled Procedure Step Location | No | Yes | CE | |
| IPC.9 | Scheduled AE Title | No | No | ST |
IPC links imaging orders to procedure and accession identifiers used by radiology and imaging systems.
The standard describes IPC this way: The IPC segment contains information about tasks that need to be performed in order to fulfill the request for imaging service. The information includes location, type and instance identification of equipment (acquisition modality) and stages (procedure steps)
Imaging control data links orders and reports to accession numbers, requested procedures, scheduled steps, modalities, and imaging-system workflow.
The important distinction is between the clinical order, the imaging procedure instance, and the accession/study identifiers used by RIS, PACS, and modalities.
The v2.5.1 structures show IPC in OMI_O23 - OMI - Imaging order and ORI_O24 - ORI - Imaging order response message to any OMI. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
IPC-1 identifies the Accession Identifier for this imaging workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
IPC-2 identifies the Requested Procedure ID for this imaging workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
IPC-3 carries Study Instance UID for this imaging workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
IPC-4 identifies the Scheduled Procedure Step ID for this imaging workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
IPC-5 carries Modality for this imaging workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
IPC-6 identifies the Protocol Code for this imaging workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
IPC-7 identifies a person, provider, staff member, or contact involved in this imaging workflow. Use the structured name or provider datatype instead of flattening everything into display text.
IPC-8 places the imaging workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
IPC-9 carries Scheduled AE Title for this imaging workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.