Back to Basics: Activities Queue

Sometimes, studies come into Ambra not quite ready to be published in the worklist and available to users. In these scenarios, the Activities Queue comes in handy! 

The Activities Queue functions as a holding pen for studies that might need some extra attention before publishing. Like many other Ambra functionalities, this is a customizable feature that functions as a great checkpoint in a client’s workflow, especially for organizational purposes. 

The Activities Queue can be turned on at the Organization level in Account Settings, with these two settings: 

Activities queue 1

It can also be turned on at the namespace level, under the same two namespace settings:

Activities Queue

Our wide variety of clients use the Activities Queue in a variety of ways, depending on what best suits their daily workflow.

A research client can utilize the Activities Queue to anonymize incoming data before publishing to the worklist. 

The Activities Queue Studies can simply be used as a checkpoint to confirm only the right kinds of imaging are coming into an account. For example, if a large hospital system allows patients to upload their imaging directly, it is important to ensure only the right kinds of imaging with the right information in the right format are coming into the system. The Activities Queue allows hospital administrators to approve or reject a study based on the internal protocols. 

If a client does not have an order feed, the Activities Queue can be used to manually correct protected health information (PHI). 

If the client does have an order feed, the Activities Queue can also be used in a Modality Worklist (MWL) workflow. This workflow allows users to match an order with an existing study to automatically fix up PHI. For example, a patient could come into Facility A with a CD of imaging they had done at Facility B. While this CD contains important medical history that is relevant to the patient’s care, it also likely contains identifying patient information assigned at Facility B because each facility creates their own medical records number (MRN) and accession number for every patient. This difference in information for the same patient is reconciled using the order feed at Facility A. 

Jio Chang

About Jio Chang

Jio Chang is an alumna of Colorado College with a degree in Molecular Biology and is currently based in Denver as part of the Ambra Analyst Program. As a Professional Services Analyst, she loves learning and troubleshooting the technical side of Ambra in order to deliver better care to patients everywhere. In her free time, she upcycles old clothing, trains for sprint triathlons, and watches terrible reality television.

Medical Imaging Software Buyer's Guide

Leave a comment

Your email address will not be published. Required fields are marked *