SEI Idea Portal
|
Description
User Story •Radiologists and Clinicians are doing research and need DICOM data from Production PACS.•For some research projects, the data needs to be de-identified.•The volume of studies can range from 1,000 to 50,000, depending on size and duration of research project.•User will search for the relevant batch of exams in RISi, either by date range, procedure description, body part, key words from report, or other criteria, then compile a list of accession numbers in a csv format.•Destination of extracted data can be another DICOM destination, or a shared folder designated by user. This is usually the user’s research repository.•PACS Admins can manually export from UV GUI, one study at a time.•Extraction of data must not impact the Production operations. Feature Request Description Users need a tool with GUI, to submit extraction requests to the PACS/EA on-demand without reliance on GEHC local ITPS team. Tool must support extraction in batches, with delayed start time so the job can run after office hours. User can select if the extracted data needs to be de-identified (using DICOM Tag Morphing). De-identification/renaming can be controlled by user, for example: Patient Name prefix with “Project 1”. Tool must have capability to search for the relevant batch of exams, either by date range, procedure description, key words from report, or other criteria. Tool will have rule-based/rights-based user access control. Destination of extracted data can be another DICOM destination, or shared folder designated by user. This is usually the user’s research repository. Automated processes for audit trail and logging. Benefits of Native Extraction Tool Users can extract required data on-demand, without reliance on Local ITPS team. Function is self-contained within PACS/EA, without 3rd party involvement. Local ITPS team can focus on more value-adding work. Potential revenue USD100K/site (which they would otherwise spend on the ITPS effort for extraction over a few years) x 4 sites in Singapore. |
