Skip to main content
Deploy core HMIS first. Enable integration traffic only after the application, backup, security, and operational checks pass.
The current production Compose file creates OIE, Orthanc, OHIF, the mock analyzer, and the mock modality by default. This documentation cannot make those services optional at the Compose level. Keep unused services unrouted, stop both mocks after every deployment, and verify firewall state.

​
OIE foundation

1

Protect administration

Keep OIE browser administration behind a VPN, IP allow-list, or identity-aware access. Use an SSH tunnel or VPN for the desktop Administrator client on port 8443.
2

Create least-privilege HMIS tokens

Create separate Sanctum tokens for laboratory results, laboratory worklists, radiology worklists, and study events as required. Grant only the documented abilities and store the raw token once in the target connector’s secret configuration.
3

Import sanitized channels

Import the channel exports from infrastructure/oie/channels, replace placeholders through the secret process, validate every connector, and export a sanitized post-change copy for backup.
4

Restrict listeners

Bind analyzer, ASTM, MLLP, and DICOM listeners only to approved private interfaces and firewall sources. Never use a public bind merely to reach administration.

​
Laboratory integration

Use these guides in order:
  1. Integration context
  2. HMIS configuration
  3. OIE deployment
  4. OIE channels
  5. Testing and validation
  6. Production readiness
Before enabling a device, approve its test-code mappings, units, flags, specimen identifiers, transport, acknowledgements, duplicate handling, reconciliation process, and downtime workflow.

​
Radiology integration

1

Secure Orthanc

The supplied demonstration configuration is not sufficient for production. Apply authentication, network segmentation, access control, retention, audit, and backup requirements before storing real studies.
2

Configure OHIF

Route the protected {{OHIF_DOMAIN}} to the ohif service and set PACS_VIEWER_URL_TEMPLATE to its HTTPS viewer path.
3

Create the PACS endpoint

After setting the viewer URL and PACS code, run the targeted idempotent seeder if the deployment uses the supplied endpoint definition:
Review the created endpoint and replace demonstration assumptions before clinical use.
4

Validate the workflow

Complete worklist lookup, modality acquisition, DICOM store, stable-study event, HMIS reconciliation, and viewer launch with synthetic studies.
Use the Radiology architecture, Demo PACS and viewer, and End-to-end testing guides for implementation details.

​
Simulator policy

Record simulator state in every release checklist because a Compose redeployment can start the services again.

​
Integration go-live evidence

  • Approved network and firewall rules
  • Vendor interface and mapping sign-off
  • Token owner, abilities, creation date, and rotation record
  • Sanitized OIE channel export
  • Successful normal, abnormal, duplicate, unknown, and downtime cases
  • Backup coverage for OIE, Orthanc metadata, DICOM studies, extensions, and channel exports
  • Named reconciliation and incident owners