120 likes | 426 Views
Digital Mammography Workflow. IHE Technical Committee January 8, 2007. Focus. Scheduled Workflow Post-Processing Workflow Radiologist - Technologist Workflow Key Image Note or Other. Supplement 96?. Do We Go Down the Path? Extended Time for Deployment Due to “NEW” Standard?.
E N D
Digital MammographyWorkflow IHE Technical Committee January 8, 2007
Focus • Scheduled Workflow • Post-Processing Workflow • Radiologist - Technologist Workflow • Key Image Note or Other
Supplement 96? Do We Go Down the Path? Extended Time for Deployment Due to “NEW” Standard?
Path to Supplement 96 • Define complete transaction set within the current framework to ensure a common understanding. • Perform “Gap Analysis” between newly defined framework and Supplement 96. • Create working group to make the conversion.
Next Steps • Complete Baseline Transaction Documentation (In Process). • Connectathon • Use Case Profile Failure / Gap Analysis. • Complete Profile Set Review - Jan 22 - 23. • Complete Profile Sets (February 15). • Distribute Draft to Team for Review. • Meeting to Finalize and Release for Public Comment. (March ?)
Where We Stand • Object Model Designed • “Rules of Engagement” are Defined • Method of Defining Transactions Determined • Major Transactions Defined • Baseline Transactions for the Acquisition Modality in Draft
Assumptions for the Creation / Defining the "Objects" • Each object will contain an independent Workflow Manager. • The objects workflow manager will be the single point of communication to the other objects in the system. • All inter-object communications will be routed through the “Master” Workflow Manager. • All intra-object communications will be managed by the Local Master Workflow Manager. • No direct communications between the Local Master Workflow Managers will be allowed. (This is a gross violation of Object Oriented Design.)
Rules of Engagement • The Local Workflow Manager (LWFM) is the only object that communicates with the Master Workflow Manager (MWFM). • The LWFM is responsible for managing communications within the object. Local Objects will only communicate with the LWFM. • The MWFM is responsible for the broadcasting of key events of the study. The WFMs subscribe to the events that are relevant to their respective activities and those activities required by the local actor subscriptions.
The MWFM and LWFM are too be synchronized and if the synchronization is broken the operator is to be warned of the condition and a manual override needs to provided. • Worklists and changes to Worklists are sent from the MWFM then to the subscribing systems in real-time as driven by the DSS/OF. Events reported to the MWFM from the LWFMs Will allow for those systems to be aware of status. This will facilitate any preparation / operations that need to be completed prior to the completion of the exam. CAD can greatly benefit from this since it can begin “getting” images when the begin event is broadcast and stop “getting” images when the complete event is broadcast. • Local Objects will report to the LWFM at a minimum the following conditions. If the event is not relevant to the function of the slave then a fixed response will be sent. • o Available • o Not Available • o Pending • o In progress • o Failure.