Technical Architecture

How Pacslens works

From DICOM ingestion to worklist re-ranking — the full technical architecture of the Pacslens triage pipeline.

Step 1

The DICOM-native pipeline

Studies enter via DICOM C-STORE (push) or Q/R (pull). Pacslens processes each series through a containerized inference stack. Results write back as DICOM Structured Report (SR) objects. No PHI leaves your network.

PACS Sectra / GE / Philips Fujifilm / Hyland DICOM C-STORE / Q-R DICOM TLS PACSLENS INFERENCE ENGINE containerized · single-tenant VPC or on-premise DICOM Ingestion AI Triage Scoring LVO · ICH · PE · AD · PTX · VFx SR Write Triage Score · Finding Flags · Structured Report (TID-1500) Accession: 2024-03891 · Score: 94 · Flag: LVO_POSITIVE HL7 FHIR ImagingStudy RIS / EHR Epic Radiant Cerner RadNet Re-ranked worklist DICOM SR writeback

Step 2

Triage scoring per indication

Each AI model is indication-specific: a convolutional model for LVO on CT Head, a 3D U-Net architecture for ICH volumetry, a detection model for PE on CTPA. Scores are normalized to a 0–100 criticality index per study. Threshold configuration is site-adjustable.

Radiologists see a normalized priority indicator — STAT / Urgent / Routine — not a raw model probability. This surfaces actionable triage context without creating alert fatigue from raw model scores.

TRIAGE SCORE ILLUSTRATION — Study 2024-03891

LVO
94
ICH
24
PE
12
PTX
8

COMPOSITE SCORE: 94 → STAT

PROCESSING TIME: 38 seconds

Step 3

Worklist re-ranking without replacing your RIS

Pacslens injects triage priority flags via HL7 FHIR ImagingStudy resource updates or Epic Radiant ORM message extension. Radiologists see a re-ordered worklist in their existing viewer — no new UI to learn.

  • Same worklist interface your radiologists already use
  • Priority indicator visible in RIS column — no separate tool to open
  • Radiologist can override any priority flag — they stay in control
BEFORE PACSLENS AFTER PACSLENS 07:00 MRI Knee 07:14 XR Wrist 07:28 CT Head — LVO? 07:41 MRI Shoulder 07:53 CT Chest CTPA arrival order STAT CT Head — LVO? URGENT CT Chest CTPA ROUTINE MRI Knee ROUTINE XR Wrist ROUTINE MRI Shoulder triage-ranked

Deployment

Deployment options for community hospital IT

Two paths to deployment — both designed for minimal IT overhead, both maintaining your PHI controls.

On-premise container

Your data stays on your hardware

Docker/Kubernetes on existing server hardware. IT installs once. Pacslens updates remotely via signed container images. No cloud egress, no PHI leaves the hospital network.

  • Single Docker compose install
  • Remote model update via signed image pull
  • Outbound DICOM TLS for telemetry only

Cloud VPC

Single-tenant VPC — no multi-tenancy PHI

Single-tenant VPC on AWS GovCloud or standard region. Outbound DICOM TLS only. BAA included. Dedicated infrastructure — your hospital's PHI is never co-located with another hospital's data.

  • Single-tenant isolated environment
  • BAA included with VPC deployment
  • AWS GovCloud option for higher compliance needs

See the pipeline in your environment

We run a live technical walkthrough using your actual PACS vendor stack. No generic demos.

Request Technical Demo