Application Overview
A map of the Xenrad web app—what each area does and how everything connects.
Xenrad is a web-based radiology workflow tool. Studies arrive from imaging equipment, staff triage and verify them, radiologists review and report, and external systems can exchange clinical data through standard protocols.
Here's a quick map of the major areas.
Worklist
The worklist is your home base—a live table of imaging studies for your organization. You filter by status, date, modality, or patient; open a study for detail; and hand work off to the next step.
Every study has a status that moves through a defined lifecycle: New → Ready → Reporting → Finalized. The worklist reflects that status in real time.
Study detail
Clicking into a study shows you the imaging metadata, the linked patient record, and the actions available at that stage. Depending on your permissions, you can:
- Review and correct patient demographics
- Mark the study ready for reporting after demographics are verified
- Open in Prism to review images
→ Study lifecycle · Patients and editing
Prism — imaging viewer
Prism is the diagnostic viewer built into Xenrad. It opens in context of the study you selected, so you don't need to manually enter study UIDs. Features include multi-viewport layouts, window/level presets, measurements, annotations, and optional segmentation.
Patients
The patient profile holds full demographics and a structured medical history—conditions, allergies, observations, procedures, and documents. You can access it from a study or navigate to it directly.
Editing has rules: if another study for the same patient is currently in the "ready" state, demographic edits are locked until that study moves forward.
Reporting
Structured reports are built in named sections. The system autosaves as you work. When the report is complete, a radiologist (or designated user) finalizes it, which locks the content and moves the study to "Finalized."
Site administration
Administrators manage sites, devices (DICOM modality associations), and API keys for external integrations. API keys control which external systems can connect, which protocols they can use, and what data they can access.
→ OAuth2, API keys, and client assertions
Sessions and permissions
Users sign in to the web app and get site-scoped permissions. What you can see and do—edit patients, change study status, manage API keys—depends on your role within that site.
External integrations (FHIR, HL7) use separate integration client credentials, not the interactive user's login.
How external systems fit in
| What it does | Protocol |
|---|---|
| Delivers imaging studies | DICOM ingest |
| Reads or writes patient and clinical data | FHIR R4 |
| Sends ADT and observation messages | HL7 v2.5.1 |
FHIR and HL7 complement DICOM ingest—they handle patient demographics and clinical data, not images.