Inbound Reports
AdvaPACS can receive reports from external reporting systems using HL7 ORU^R01 messages. These messages contain the patient, order, and report information required to associate the incoming report with an existing study. Report content is provided in the OBX segment and can be sent as text, formatted text, or encapsulated data such as HTML or PDF.
Supported Trigger Events
The following trigger events are supported by AdvaPACS.
| Trigger Event | Action |
|---|---|
ORU^R01 | Observation result message used to create or update a report in AdvaPACS. |
Expected Actions
When an ORU^R01 message is received, AdvaPACS processes the patient, order, and report information contained in the message.
| Resource | Action |
|---|---|
| Patient | The patient is created or updated based on matching with the Patient ID(s). |
| Order | The order-related segments are processed according to the supported order creation and update behaviour. |
| Report | The report is created for the associated study. If a report already exists, it is overwritten by the incoming report. |
Message Structure
Inbound Report messages use the standard ORU^R01 message structure. The following segments are supported:
| Segment | Required | Description |
|---|---|---|
MSH | Yes | Identifies the message type, sender, receiver, and other message-level information. |
PID | Yes | Contains the patient identifiers and demographics. |
PV1 | Optional | Contains patient visit information, including the patient class and referring doctor where applicable. |
ORC | Yes | Contains common order information and identifiers associated with the report. |
OBR | Yes | Identifies the order, procedure, and study associated with the report. |
OBX | Yes | Contains the report content and related observation information. Multiple OBX segments may be included where required. |
ZDS | Optional | Contains the DICOM Study Instance UID used to identify the study associated with the report. |
The following reference provides the supported fields for each HL7 segment used in this workflow. Unless otherwise stated, fields not listed are ignored during processing.
MSH
The MSH (Message Header) segment identifies the message type, sender, receiver, version and other information required to process an HL7 message. All patient registration messages sent to AdvaPACS must include a valid MSH segment.
| FIELD | NAME | LENGTH | DATA TYPE | OPT. | TABLE |
|---|---|---|---|---|---|
| MSH-1 | Field Separator | 1 | ST | R | - |
| MSH-2 | Encoding Characters | 4 | ST | R | - |
| MSH-3 | Sending Application | 227 | HD | R+ | - |
| MSH-4 | Sending Facility | 227 | HD | R+ | - |
| MSH-5 | Receiving Application | 227 | HD | R | - |
| MSH-6 | Receiving Facility | 227 | HD | R+ | - |
| MSH-7 | Date/Time of Message | 26 | TS | R | - |
| MSH-9 | Message Type | 15 | MSG | R | 0076 |
| MSH-10 | Message Control ID | 199 | ST | R | - |
| MSH-11 | Processing ID | 3 | PT | R | 0103 |
| MSH-12 | Version ID | 60 | VID | R | 0104 |
| MSH-15 | Accept Acknowledgment Type | 2 | ID | O | 0155 |
| MSH-16 | Application Acknowledgment Type | 2 | ID | O | 0155 |
PID
The PID (Patient Identifier) segment contains the patient identifiers and demographic information used to identify the patient associated with the report.
| FIELD | NAME | LENGTH | DATA TYPE | OPT. | TABLE |
|---|---|---|---|---|---|
| PID-1 | Set ID - PID | 4 | SI | O | - |
| PID-3 | Patient Identifier List | 20 | CX | R | - |
| PID-5 | Patient Name | 48 | XPN | R | - |
| PID-7 | Date/Time of Birth | 26 | TS | R2 | - |
| PID-8 | Sex | 1 | IS | R | 0001 |
| PID-13 | Phone Number - Home | 40 | XTN | O | - |
| PID-29 | Patient Death Date and Time | 26 | TS | O | - |
| PID-30 | Patient Death Indicator | 1 | ID | O | 0136 |
If the Assigning Authorities feature of AdvaPACS is enabled, Patient IDs must include Assigning Authority. The first subcomponent (namespace ID) of Assigning Authority shall be populated. If the second and third subcomponents (universal ID and universal ID type) are also populated, they shall reference the same entity as is referenced in the first subcomponent.
PV1
The PV1 (Patient Visit) segment contains visit information associated with the patient and report, including the patient class, referring doctor, and visit number.
| FIELD | NAME | LENGTH | DATA TYPE | OPT. | TABLE |
|---|---|---|---|---|---|
| PV1-1 | Set ID - PV1 | 4 | SI | O | - |
| PV1-2 | Patient Class | 1 | IS | R | 0004 |
| PV1-8 | Referring Doctor | 60 | XCN | C | 0010 |
| PV1-19 | Visit Number | 20 | CX | C | - |
ORC
The ORC (Common Order) segment contains common order information used to identify and process the order associated with the report. This includes the order control, order numbers, order status, scheduled date and time, and organisation information.
| FIELD | NAME | LENGTH | DATA TYPE | OPT. | TABLE |
|---|---|---|---|---|---|
| ORC-1 | Order Control | 2 | ID | R | 0119 |
| ORC-2 | Placer Order Number | 22 | EI | R2 | - |
| ORC-3 | Filler Order Number | 22 | EI | R | - |
| ORC-4 | Placer Group Number | 22 | EI | O | - |
| ORC-5 | Order Status | 2 | ID | R | 0038 |
| ORC-7 | Quantity/Timing | 200 | TQ | R | - |
| ORC-10 | Entered By | 250 | XCN | O | 0010 |
| ORC-13 | Enterer's Location | 80 | PL | R2 | - |
| ORC-17 | Entering Organization | 60 | CE | R2 | - |
All (ORC, OBR) segment pairs sent in the Procedure Scheduled message shall be present in the Procedure Update message, not only the pairs introducing a change.
Quantity/Timing shall be the date and time of the Scheduled Procedure Step (in the fourth component).