The camera lands inside the product shell.

The story resolves into a real command surface: worklist context, scan evidence, draft report, verifier state, and audit trail held inside one governed product shell.

Evidence ledger · Demo mode
Export locked
Worklist
PatientStudyStatusReport
SYN-001CT · CT chest with contrastReadyDraft
SYN-002US · Abdominal ultrasoundUploadedBlocked
SYN-001CT · CT chest with contrastReadyDraft
SYN-002US · Abdominal ultrasoundUploadedBlocked

A report sentence becomes a chain of custody.

The landing film follows one claim through imaging source, structured finding, report draft, verifier result, and audit event. The chain is visible because trust cannot be implied.

DICOM series / slice / frame

Imaging source

Series 2 · Slice 48 · IM 48/96

Structured finding

Ledger row

finding_01 · right upper lobe nodule candidate

Report sentence

Draft linked

Small right upper lobe pulmonary nodule candidate, under clinician review.

Verifier check

Verifier controlled

Evidence present · Review pending · Export locked

Audit event

Traceable

verifier_check · export_blocked · study_001

Governed states before a report can leave the system.

The product shell surfaces each transition. Frontend clients never bypass backend policy for storage, models, or export.

01

DICOM intake

Raw artifact stored

Backend import to Orthanc

PHI stays server side

02

Classifier

Support status assigned

Deterministic local adapter

Research mode is explicit

03

Finding ledger

Evidence reference required

Series, slice, model, review state

No orphan claims

04

Report composer

Structured findings only

Sentence references preserved

Draft locked by verifier

05

Export gate

Watermark and audit event

Review, mode, evidence, support

Blocked until passing

The corridor continues after the film.

The same governed evidence object travels through operational states that matter to radiologists, imaging centers, health-system IT, and investors evaluating platform depth.

01

Intake

Backend-owned DICOM session ingests study files through server-side Orthanc scope.

Server owned
02

Classify

Modality and body-region routing assigns support status without diagnostic overclaim.

Routed
03

Analyze

Model-supported finding candidates attach series, slice, and model version references.

Evidence linked
04

Review

Clinician accepts, edits, or rejects each finding — review authority stays human.

Human authority
05

Compose

Report sentences are composed only from structured findings with preserved evidence links.

Sentence scoped
06

Verify

Unsupported or export-blocked states stop unsafe output before any file leaves the system.

Verifier gated
07

Export

Gated by verifier status, operating mode, review completion, and support posture.

Locked output
08

Audit

Each action — view, edit, verify, block, export — leaves a traceable audit event.

Traceable

No finding without evidence.

Every model finding carries a series, slice, and region — or it is labeled unlocalized. Evidence is never fabricated to look complete.

No report without review.

Drafts compose only from structured findings. A clinician accepts, edits, or rejects each one before anything is finalized.

No export without verification.

A deterministic verifier checks every sentence against evidence, operating mode, and review state. Failures block export — not warn.

The browser never becomes the clinical boundary.

The public page shows the product posture without implying clinical clearance: backend-owned DICOM intake, tenant scope, model support gates, verifier policy, and audit-backed export control.

Server-owned imaging architecture

Boundary enforced
01

Frontend

02

API Gateway

03

Backend Services

04

Storage

Server import

Backend-owned DICOM intake

Browser clients never talk directly to Orthanc, object storage, or imaging archives. Upload sessions and import scope stay server-side.

Tenant scoped

PHI and security boundary

HTTP-only sessions, org memberships, and RBAC hydrate active tenant context. PHI handling follows configured site policy — not implied clearance.

Module gated

Model support status

Modules run behind provider adapters with explicit support posture. Unsupported studies remain viewable without unlocking diagnostic claims.

Export gated

Audit and export governance

Verifier checks evidence, mode, review state, and support before export. Blocked exports and watermarking remain visible in demo posture.

Auth boundaryHTTP-only sessions, org memberships, RBAC, active membership hydration

Data boundaryBackend-owned DICOM, MinIO/S3 artifacts, Orthanc adapter, no browser storage access

AI boundaryDeterministic local adapter first, Bedrock/SageMaker adapters disabled by default

Report boundaryStructured findings only, verifier-gated export, visible non-clinical watermark

Platform breadth is broad. Clinical claims are module-gated.

Platform intake can be broad while clinical claims stay narrow, validated, and policy-gated. This section is the page contract with clinicians, buyers, and regulators.

Module support board

Color is secondary. The text state is the contract: what can be viewed, what can be drafted, and what remains locked.

CT chestthoracic-triage v0.3.2Supported

Research workflow support with evidence-linked review and verifier gates.

X-ray chestcxr-triage v0.2.1Validation 64%

Validation cohort in progress; report export stays restricted by site policy.

MR brainviewer-onlyPlanned

DICOM intake and viewing available; diagnostic assistance planned after validation.

US abdomenmetadata-onlyNot supported

Visible as a study record without model claims, composition, or export unlock.

Demo / Research / Not for Clinical Use · Clinical use requires validation, governance, and clearance

Final frame

See the governed workflow from first slice to final gate.

Walk through backend-owned DICOM intake, evidence-linked findings, clinician review, verifier-gated export, and audit trails in a non-clinical product demo.

Demo modeNot for clinical use
finding_01 settled

Report draft linked · verifier pending · export locked

Demo / Research / Not for Clinical Use · No autonomous diagnosis · No clinical clearance implied