IHE Integration Statement
This page lists the IHE (Integrating the Healthcare Enterprise) integration profiles, actors and transactions that AdvaPACS supports. It is written for integration engineers who connect a RIS, HIS, EMR, modality, reporting system or viewer to AdvaPACS.
AdvaPACS is a cloud imaging platform. Sites usually connect to it in one of two ways:
- AdvaPACS Cloud, for direct DICOM, DICOMweb, HL7 and FHIR connections over the internet.
- AdvaPACS Gateway, an on-premises appliance that provides local DICOM and HL7 endpoints and relays traffic to the cloud.
Where support differs between the two, this page says so.
This IHE Integration Statement is a self-declaration by AdvaHealth Solutions Pty. Ltd. It describes the IHE integration profiles, actors and options implemented in AdvaPACS. It has not been reviewed, tested or certified by IHE International. IHE International does not certify products, and makes no statement about the accuracy of this document or the conformance of AdvaPACS.
Support for an integration profile does not guarantee interoperability with another product that claims the same profile. Interoperability should be confirmed by testing between the specific systems involved. The capabilities described here reflect the current release of AdvaPACS and may change in future releases.
Summary of Supported Profiles
| Integration Profile | Actor | Options | Notes |
|---|---|---|---|
| Scheduled Workflow (SWF.b) | Image Manager / Image Archive | — | See Scheduled Workflow. Modality Performed Procedure Step (MPPS) is not supported. |
| Scheduled Workflow (SWF.b) | Order Filler (worklist provider) | — | Provides the Modality Worklist and receives patient and order messages. |
| Patient Information Reconciliation (PIR) | Image Manager / Image Archive | — | Patient updates and merges are applied to stored studies. |
| Multiple Identity Management (MIMA) | Image Manager / Image Archive, Order Filler | — | Manages multiple patient identifiers, each with its own assigning authority. |
| Web-based Image Access (DICOMweb) | Image Manager / Image Archive | — | Supports QIDO-RS, WADO-RS, STOW-RS and WADO-URI. |
| Audit Trail and Node Authentication (ATNA) | Secure Application, Audit Record Repository | — | See Security and Audit. |
Scheduled Workflow (SWF.b)
AdvaPACS receives patient and order information from a RIS or HIS over HL7. It provides a Modality Worklist to acquisition devices, then stores, commits, and makes images available for query and retrieval.
HL7 Transactions
| Transaction | Direction | Messages Supported |
|---|---|---|
| RAD-1 Patient Registration | Inbound | ADT^A01, ADT^A04, ADT^A05, ADT^A28 |
| RAD-2 Placer Order Management | Inbound | ORM^O01 (v2.3.1), OMI^O23 (v2.5.1) |
| RAD-4 Procedure Scheduled | Inbound | ORM^O01 (v2.3.1), OMI^O23 (v2.5.1) |
| RAD-12 Patient Update | Inbound | ADT^A08, ADT^A40, ADT^A11, ADT^A38, ADT^A45 |
| RAD-13 Procedure Update | Inbound | ORM^O01 (v2.3.1), OMI^O23 (v2.5.1) |
Order control:
- An
ORC-1value ofNWcreates a new order. ORC-1values ofCA,DC,XO,XX,REandSCupdate an existing order.- The order status is set from
ORC-5(Order Status). It is not inferred from the order control code, so cancellations and discontinuations must also send the matchingORC-5value (CAorDC). ORC-5is required when creating an order.
See Procedure Scheduled and Procedure Updated for field-level details.
DICOM Transactions
| Transaction | AdvaPACS Role | DICOM Service | Cloud | Gateway |
|---|---|---|---|---|
| RAD-5 Query Modality Worklist | SCP | Modality Worklist Information Model – FIND | ✔ | ✔ |
| RAD-8 Modality Images Stored | SCP | Storage (C-STORE), all storage SOP classes | ✔ | ✔ |
| RAD-10 Storage Commitment | SCP | Storage Commitment Push Model | ✔ | ✔ |
| RAD-11 Images Availability Query | SCP | Patient Root and Study Root Query/Retrieve – FIND | ✔ | ✔ |
| RAD-14 Query Images | SCP | Patient Root and Study Root Query/Retrieve – FIND | ✔ | ✔ |
| RAD-16 Retrieve Images | SCP | Query/Retrieve – GET | ✔ | — |
| RAD-16 Retrieve Images | SCP | Query/Retrieve – MOVE | — | ✔ |
Notes:
- C-FIND supports the Patient, Study, Series and Image levels, including fuzzy semantic matching and combined date-time matching.
- On the cloud, Storage Commitment results (N-EVENT-REPORT) are returned on the same association. On the gateway, they are sent on a new association.
- C-MOVE destinations must be configured as remote AEs in AdvaPACS.
- Presentation States, Key Object Selection documents and Structured Reports are stored and returned in the same way as images.
- Modality Performed Procedure Step (RAD-6, RAD-7) and Instance Availability Notification (RAD-49) are not supported.
Patient Information Reconciliation (PIR)
When a patient is updated or merged over HL7, the change appears in all DICOM and DICOMweb responses for that patient's studies. This includes C-FIND, C-GET, C-MOVE, WADO and metadata responses.
| Event | Behaviour |
|---|---|
ADT^A08 Update Patient Information | Updates demographics and adds any new identifiers received in PID-3 |
ADT^A40 Merge Patient – Patient Identifier List | Merges the patient identified in MRG-1 into the patient identified in PID-3 |
ADT^A45 Move Visit Information | Moves orders for the visit to the patient identified in PID-3 |
ADT^A11 / ADT^A38 | Cancels the registration or pre-admission |
ADT^A31 (Update Person Information) is not supported. Send ADT^A08 for demographic updates.
Multiple Identity Management (MIMA)
AdvaPACS can hold multiple identifiers for a single patient, each qualified by an assigning authority (issuer). This lets one AdvaPACS environment serve several organisations or identifier domains without patient ID collisions.
- Assigning authorities are configured in AdvaPACS. Each one has a Namespace ID, a Universal ID and a Universal ID Type. See Assigning Authorities.
- Inbound HL7: each repetition of
PID-3(andMRG-1) is stored with its assigning authority (CX.4) and identifier type code (CX.5). - Default issuers can be set for each HL7 interface and each DICOM remote AE. These are used when a message or object does not name its assigning authority, for both Patient ID and Accession Number.
- DICOM output: the Patient ID returned to a remote AE is chosen by that AE's default issuer, and Issuer of Patient ID is filled in. Other identifiers are returned in Other Patient IDs Sequence.
- Outbound HL7:
PID-3contains every identifier held for the patient, each with its full assigning authority.
| Event | Behaviour |
|---|---|
ADT^A47 Change Patient Identifier List | Replaces a single identifier in a given assigning authority |
ADT^A43 Move Patient Information – Patient Identifier List | Moves an identifier from one patient to another |
ADT^A40 Merge Patient – Patient Identifier List | Merges two patient records, keeping all identifiers |
If an identifier's assigning authority can't be resolved to exactly one configured authority, the message is rejected.
Report Distribution
AdvaPACS sends finalised reports to downstream systems as ORU^R01 messages:
ORC-1isRE.- The report status is in
OBX-11. - The report content is sent as encapsulated data (
ED).
AdvaPACS also accepts reports from external reporting systems as ORU^R01. Supported OBX-2 value types are TX, FT and ED. See Reports.
DICOMweb
AdvaPACS Cloud provides a DICOMweb service. The AdvaPACS Gateway also exposes it locally as a proxy.
| Transaction | Service | Support |
|---|---|---|
| RAD-129 Query for Studies, Series and Instances | QIDO-RS | Study, series and instance levels. The patient level is not supported. |
| RAD-107 WADO-RS Retrieve | WADO-RS | Instances, metadata, frames, bulk data, rendered images and thumbnails, at the study, series, instance and frame levels |
| RAD-108 Store Instances over the Web | STOW-RS | multipart/related; type="application/dicom" |
| RAD-55 WADO Retrieve | WADO-URI | Supported |
UPS-RS (worklist) is not supported.
HL7 Interface Characteristics
| Characteristic | Support |
|---|---|
| Versions | v2.3.1, v2.5.1 (OMI^O23 requires v2.5.1) |
Processing ID (MSH-11) | P |
| Acknowledgement mode | Original mode only. Enhanced acknowledgement requests (MSH-15/MSH-16 other than NE/AL) are rejected with AR. |
| Character sets | ASCII (default), UNICODE, UNICODE UTF-8 (v2.5.1) |
| Transport, AdvaPACS Cloud | MLLP over mutual TLS (TLS 1.2/1.3); HL7 over HTTPS |
| Transport, AdvaPACS Gateway | MLLP on the local network, with an IP allow-list; file-based exchange |
See HL7 Introduction and Connectivity for more information.
DICOM Transfer Syntaxes
AdvaPACS accepts all standard uncompressed and compressed transfer syntaxes. It can transcode on retrieval, including:
- Implicit and Explicit VR Little Endian
- JPEG Baseline, JPEG Extended, JPEG Lossless (Process 14 and SV1)
- JPEG-LS Lossless and Near-Lossless
- JPEG 2000 Lossless and Lossy
- High-Throughput JPEG 2000 (HTJ2K) Lossless, Lossless RPCL and Lossy
- RLE Lossless
- MPEG-2 and MPEG-4 video
Storage: images are stored losslessly in JPEG 2000 or HTJ2K.
Retrieval: when an object is retrieved, AdvaPACS returns its stored transfer syntax if the requester accepts it. Otherwise it falls back to a lossless compressed syntax, then to an uncompressed syntax, and only then to a lossy syntax.
Security and Audit (ATNA)
Node authentication:
- DICOM connections to AdvaPACS Cloud use mutual TLS (TLS 1.2 or 1.3), with cipher suites following the DICOM BCP 195 profile.
- Each client certificate is mapped to a configured remote AE, and the calling AE title must match it. Revoked certificates are rejected.
- HL7 MLLP connections to AdvaPACS Cloud also require mutual TLS.
- DICOM TLS can be turned on for each local AE on the AdvaPACS Gateway.
Audit Record Repository:
- AdvaPACS acts as the Audit Record Repository for the platform. Audit events from across AdvaPACS are stored centrally.
- Audit records use the DICOM PS3.15 audit message format (RFC 3881 schema).
- Recorded events include user authentication, patient record access, study access, export, query, merge and audit log access.
- Administrators can review audit records in AdvaPACS.
Sending audit records to an external Audit Record Repository over syslog, and FHIR AuditEvent (BALP) audit records, are not currently supported.
Related Standards
The following interfaces are not IHE profiles, but they support related imaging workflows:
- FHIR R4 and R5 API. Provides ImagingStudy, DiagnosticReport, Patient, ServiceRequest and other resources. See FHIR.
- FHIRcast 3.0 Hub. Supports
DiagnosticReport-open,DiagnosticReport-update,DiagnosticReport-selectandDiagnosticReport-closefor context synchronisation with reporting applications. This aligns with the event set used by IHE Integrated Reporting Applications (IRA).ImagingStudy-openandImagingStudy-closeare not currently supported. - Viewer launch. Studies can be opened in integrated viewers through the AdvaPACS Viewer API. See Viewer API. This API is not an IHE Invoke Image Display (IID) interface.