ClinicalLive · in the productClinical record

ImageVault

The worklist, the study and the viewer link that make a radiology report an image.

Get ImageVault Open the appAvailable nowHow pricing works →

What it is

A radiology report that carries no image is a template. ImageVault is the four things your archive cannot know on its own: the worklist a scanner reads before it scans, keyed by an accession number from your own numbering series; the mapping from an acquired study back to the request it answers; the link a signed report carries into your own viewer; and the queue of studies that answer nothing, which a person resolves. MedAppz stores no images and implements no DICOM stack — the archive is the one you already run, Orthanc or dcm4chee or your vendor’s, reached over DICOMweb when it answers on https, and otherwise through a small bridge that sits beside it on the imaging network, reads this worklist and posts studies back. Where ImageVault dials the archive over DICOMweb, the Image viewer opens a study in the browser for viewing: its series in order, scrolled image by image, at the scanner’s window or one you set, zoomed or inverted. Each picture is the archive’s own rendered frame, passed through and never kept, so it is a compressed view for the ward round and the patient conversation, not the diagnostic read.

Who uses it: Built for: Diagnostics & Labs · Hospitals
Reads: Imaging orders, patients, the study list your archive answers with
Writes: Worklist entries with their accession numbers, study records and what they were matched to, the study link on a radiology report
Never: It stores no images.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: The worklist, the study records and the links stay with the tenant. The images were never ours: they stay in your archive under your own retention policy.

How it works

Connect the archive, or the bridge to itIf your archive answers on an https address, point ImageVault at it. If it sits on the imaging network — which is usual — run the bridge beside it instead. Add the viewer link so a report can open the pictures.
Schedule the requestAn imaging order becomes a worklist entry with an accession number and a machine. That is the list the scanner reads before the patient is on the table.
Let the studies come backStudies arrive by poll or from the bridge and join their request by accession. Anything that matches nothing waits under Unmatched for somebody to place it.
Report against the imagesOpen the study from the report, write it, sign it. The signed report carries the study, and anyone reading it later can open the same pictures.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It stores no images.

Nothing is re-hosted: the Image viewer passes the archive’s rendered frames through and keeps none, measures nothing and says nothing about what an image shows; it is not a diagnostic viewer, it has no 3D or multi-planar views, and it cannot reach an archive that sits behind the bridge.

The Open link goes to your own diagnostic viewer built from the study’s identifiers.

It never guesses which patient a study belongs to: a study joins a request by an exact accession number or because a person picked the request, and one that matches neither waits in a queue rather than being attached or dropped.

A report may only name a study matched to that same patient’s own request, and a signed report never changes.

It refuses an archive address that resolves inside a private network, and re-checks that at every request rather than once when it was typed.

It does not speak DICOM’s own protocol — the worklist your console asks for over C-FIND is answered by the bridge beside your archive, not by this.

AI in ImageVault

AskQuestions about what is on screen — “What needs attention in ImageVault today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

ImageVault — Imaging — Book the scan, find the study, and open it from the report — 01Imaging — Book the scan, find the study, and open it from the reportCaptured from the running demo clinic

01Imaging — Book the scan, find the study, and open it from the reportCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 3

LabBridge Patient Registry RadioReport

Hands to · 2

RadDose RadioReport

See the whole clinic →

Questions clinics ask

What does ImageVault do?

The worklist, the study and the viewer link that make a radiology report an image. A radiology report that carries no image is a template. ImageVault is the four things your archive cannot know on its own: the worklist a scanner reads before it scans, keyed by an accession number from your own numbering series; the mapping from an acquired study back to the request it answers; the link a signed report carries into your own viewer; and the queue of studies that answer nothing, which a person resolves. MedAppz stores no images and implements no DICOM stack — the archive is the one you already run, Orthanc or dcm4chee or your vendor’s, reached over DICOMweb when it answers on https, and otherwise through a small bridge that sits beside it on the imaging network, reads this worklist and posts studies back. Where ImageVault dials the archive over DICOMweb, the Image viewer opens a study in the browser for viewing: its series in order, scrolled image by image, at the scanner’s window or one you set, zoomed or inverted. Each picture is the archive’s own rendered frame, passed through and never kept, so it is a compressed view for the ward round and the patient conversation, not the diagnostic read.

What data does ImageVault read and write?

ImageVault reads imaging orders, patients, the study list your archive answers with and writes worklist entries with their accession numbers, study records and what they were matched to, the study link on a radiology report. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does ImageVault deliberately not do?

It stores no images. Nothing is re-hosted: the Image viewer passes the archive’s rendered frames through and keeps none, measures nothing and says nothing about what an image shows; it is not a diagnostic viewer, it has no 3D or multi-planar views, and it cannot reach an archive that sits behind the bridge. The Open link goes to your own diagnostic viewer built from the study’s identifiers. It never guesses which patient a study belongs to: a study joins a request by an exact accession number or because a person picked the request, and one that matches neither waits in a queue rather than being attached or dropped. A report may only name a study matched to that same patient’s own request, and a signed report never changes. It refuses an archive address that resolves inside a private network, and re-checks that at every request rather than once when it was typed. It does not speak DICOM’s own protocol — the worklist your console asks for over C-FIND is answered by the bridge beside your archive, not by this.

What happens to our data if we uninstall ImageVault?

The worklist, the study records and the links stay with the tenant. The images were never ours: they stay in your archive under your own retention policy.

Is ImageVault available today?

Yes — ImageVault is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see ImageVault running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Clinical

All 300 →

Featured inRadiology