What this does not do
It records where a study came from, where its images are and whose they are. It does not report on a study and it does not interpret an image.
See images arriving, where a study's images are stored, and any question about whose images they are.
It records where a study came from, where its images are and whose they are. It does not report on a study and it does not interpret an image.
Reading a clinical image needs a validated monitor and the right viewing conditions. A browser on an ordinary screen is neither, so do not read from here.
If images arrive again under the same identifier they join the study that already exists. That stops a study ending up split in two, which is how somebody reports on three of five series without knowing the other two are there.
It is almost always a misconfigured sending device. Filing the images under whoever received them second would be wrong every time, so it is raised for somebody to look at.
While a question is open the study cannot be made ready to read, and that is checked when you save rather than when the screen loaded. The wrong name on a scan is one of the few imaging mistakes that reaches the patient as harm.
A series does not keep its own tally. The count is read from where the images actually are, so it cannot drift from what is stored.
Bringing a study back from the archive is recorded as a request with your name on it. A restore nobody asked for never finishes, and somebody waiting needs to see it is in hand.