# OZI-RIS DICOM Conformance Statement — Integration Baseline

Version: P2 site-validation baseline, 20 July 2026

## Status and scope

OZI-RIS is a Radiology Information System. This document describes the application-layer workflow contract currently implemented. OZI-RIS does **not yet claim standalone DICOM conformance**. DIMSE services are provided by the separately operated, checked-in Python gateway, which still requires completed multi-vendor site acceptance and its own final conformance statement.

Reference baseline: ISO 12052:2026 Edition 3 and DICOM PS3 2026c.

## Application entities and roles

| Service | SOP Class UID | Intended role | Current implementation |
|---|---|---|---|
| Verification | 1.2.840.10008.1.1 | SCP through gateway | C-ECHO bridge implemented; simulator and supervised Fuji validation completed |
| Modality Worklist Information Model - FIND | 1.2.840.10008.5.1.4.31 | SCP through gateway | Secured RIS contract and pynetdicom bridge implemented; supervised Fuji C-FIND validated |
| Modality Performed Procedure Step | 1.2.840.10008.3.1.2.3.3 | SCP through gateway | N-CREATE/N-SET bridge and reconciliation implemented; Fuji N-CREATE and live N-SET acceptance partially validated |
| Storage Commitment Push Model | 1.2.840.10008.1.20.1 | Event consumer through gateway | Commitment result and SOP tracking implemented; DIMSE gateway pending |
| Study Root Query/Retrieve Information Model - FIND | 1.2.840.10008.5.1.4.1.2.2.1 | SCU through PACS/gateway | DICOMweb QIDO-RS study query implemented; DIMSE C-FIND pending |

Transfer syntaxes are negotiated by the external gateway and are not claimed by OZI-RIS itself.

## Worklist behavior

The worklist is organized by Scheduled Procedure Step and returns scheduled/arrived, non-cancelled studies. Supported filters are Scheduled Station AE Title and scheduled date. The RIS MRN is returned as Patient ID (0010,0020). When recorded, the Citizen/National ID is returned separately in Other Patient IDs Sequence (0010,1002) as a text identifier. Requesting Doctor is returned as Requesting Physician (0032,1032), while the requesting ward or department is returned as Requesting Service (0032,1033). Returned data also includes UTF-8 Specific Character Set, patient demographics, accession, Study Instance UID, Requested Procedure ID/description, Scheduled Procedure Step ID, station AE title, start date/time, modality, and timezone offset.

Patient names are emitted in DICOM person-name component form. Implementers must validate local character-set behavior with Malaysian names during site acceptance testing.

## MPPS behavior

The gateway contract accepts IN PROGRESS, COMPLETED, and DISCONTINUED events. Matching uses Study Instance UID and/or Accession Number. Conflicting or unmatched identifiers are not silently accepted; they enter the reconciliation queue. Series and SOP Instance UIDs can be retained with the study.

## Storage Commitment behavior

Committed and failed results are recorded with the transaction UID. A committed result records the completion time and referenced SOP Instance UIDs. Unmatched or conflicting identifiers enter reconciliation rather than updating a clinical study.

## PACS integration

PACS query uses HTTPS DICOMweb QIDO-RS with Study Instance UID. Viewer launch is restricted to a configured HTTPS host and substitutes Study Instance UID and Accession Number into an administrator-controlled URL template. API tokens are encrypted at rest.

## Security and audit

The gateway HTTP contract requires a bearer token supplied through `DICOM_GATEWAY_TOKEN`. Production traffic must use mutually authenticated or otherwise organization-approved TLS at the gateway/reverse-proxy boundary. Worklist, MPPS, Storage Commitment, PACS query, viewer launch, failures, and reconciliation decisions are recorded.

## Known limitations before a conformance claim

- No native DICOM association negotiation, presentation contexts, DIMSE status handling, or transfer-syntax implementation.
- The checked-in MWL/MPPS gateway has been exercised with one Fuji DR-ID 300CL / Console Advance workstation, but an operator-generated final N-SET and additional vendor/room acceptance remain pending.
- C-MOVE/C-GET and Storage Commitment N-ACTION/N-EVENT-REPORT require PACS/gateway deployment and site validation.
- No storage SCP is provided by OZI-RIS.
- Fuzzy person-name matching is not supported.
- Remaining site AE titles, network topology, TLS profiles, character sets, failure scenarios, and vendor-specific behavior remain to be validated.

The final product and gateway conformance statements must be completed after vendor selection and interoperability testing.
