ImageVault

What ImageVault does

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.

How you actually use it

1. 1Connect 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.
2. 2Schedule 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.
3. 3Let 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.
4. 4Report 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.

What it does not do

It stores no images. There are no pixels in this product, nothing is re-hosted or proxied, and the Open link goes to your own 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.

Questions clinics ask