1 / 33

Notification Options for Scheduled Workflow

Notification Options for Scheduled Workflow. Feedback Enhancements Andrei Leontiev L S Consulting. Charge Posting. Presentation of Grouped Procedures. Reporting Workflow. Key Image Notes. Simple Image & Numeric Reports. NM Image. Consistent Present- ation of Images. Evidence Docs.

tirza
Download Presentation

Notification Options for Scheduled Workflow

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Notification Options forScheduled Workflow Feedback Enhancements Andrei Leontiev L S Consulting Vendor Workshop, Sep 2004

  2. Charge Posting Presentation of Grouped Procedures Reporting Workflow KeyImageNotes Simple Image & Numeric Reports NMImage Consistent Present-ation of Images EvidenceDocs Access to Radiology Information Portable Data for Imaging IHE Radiology Integration Profiles Scheduled Workflow - Patient Info. Recon-ciliation Post-Processing Workflow Basic Security Vendor Workshop, Sep 2004

  3. Scheduled Workflow Profile report Registration Film Lightbox Image Manager & Archive Orders Filled Film Folder Diagnostic Workstation Film Report Repository Orders Placed AcquisitionModality acquisitioncompleted acquisitionin-progress imagesprinted Modality acquisitioncompleted Vendor Workshop, Sep 2004

  4. NEW SWF Options • Departmental Appointment Notification • Gives the Department System Scheduler an option to notify Order Placer of date and time of scheduled examinations. • Instance Availability Notification • Gives the Image Manager an option to notify Order Filler and other workflow management actors of availability status of evidence objects. Vendor Workshop, Sep 2004

  5. Scheduled Workflow Profile report Registration Film Lightbox Image Manager & Archive Orders Filled Film Folder Diagnostic Workstation Film Report Repository Orders Placed AcquisitionModality acquisitioncompleted acquisitionin-progress imagesprinted Modality acquisitioncompleted Vendor Workshop, Sep 2004

  6. Departmental Appointment Notification Option Vendor Workshop, Sep 2004

  7. Value Proposition • Provides a mechanism for the Order Placer to keep track of appointments scheduled for a patient within Radiology Department • Includes notifications of scheduling, re-scheduling and cancellation events • Helps synchronization of scheduling processes between enterprise and radiology Vendor Workshop, Sep 2004

  8. Background • Existing Placer Order Management Transaction allows Order Placer specify preferred date and time of an order fulfillment (i.e., radiological examination) • Order Filler is ultimately responsible for scheduling of examination as a succession of Procedure Steps that may require one or more appointments to be created • Currently, Order Placer has no way to know when or where exactly the appointment will take place. Vendor Workshop, Sep 2004

  9. Departmental Appointment Booking Use Case Vendor Workshop, Sep 2004

  10. Appointment Notification Transaction • Department System Scheduler/Order Filler generates Appointment Notification messages and sends them to the corresponding Order Placer actor. • Order Placer receives Appointment Notification messages and internally processes them. Vendor Workshop, Sep 2004

  11. Interaction Diagram Vendor Workshop, Sep 2004

  12. Appointment Notification Transaction • Three typical use cases • New booking: initial scheduling of an examination • Re-schedule: change in date/time of examination • Cancellation: examination cancellation • Mechanism • HL7 SIU messages • One message may convey multiple appointments corresponding to a single order • One appointment corresponds to one or more Scheduled Procedure Steps Vendor Workshop, Sep 2004

  13. SIU Message Structure Vendor Workshop, Sep 2004

  14. SCH Segment • Specifies common information for one or more appointments associated with single order • Placer Appointment ID is not used • Filler Appointment ID is required • Appointment timing is defined on the Resource Group level, per Scheduled Procedure Step • SCH-6 has fixed value of 1 • One message can have multiple resource groups, thus multiple appointments (procedure steps) • No patient identification information is required, thus Order Numbers are required Vendor Workshop, Sep 2004

  15. AIS Segment • Specifies Procedure Code and Description to for the Scheduled Procedure Step(s) included into this appointment • Procedure Code in components 1-3 • Not all steps of the procedure may be included • Those included are identified by a the text in component 5 • Date/Time of an appointment is expected to be in UTC • If local, UTC offset is required • No specification of location or resources (one should use AIG, AIL, AIP segments within the same group, as appropriate) Vendor Workshop, Sep 2004

  16. What is not in the option • Departmental Appointment Notification Option does not allow Order Placer to request re-scheduling – it only can do it by cancel and re-order • Transaction does not require AIL segment – thus notifications on re-scheduling of the service from one location to another may not be sent • This option does not address needs of enterprise-wide scheduling Vendor Workshop, Sep 2004

  17. References • Profile Option - Volume 1, Section 3.3.6 • Transactions - Volume 3, Section 4.48 Vendor Workshop, Sep 2004

  18. Instance Availability Notification Option Vendor Workshop, Sep 2004

  19. Value Proposition • Enhances mechanism that allows to obtain information about availability of newly-acquired images and other evidence objects, for further use in workflow • Provides this information to all workflow management actors Vendor Workshop, Sep 2004

  20. Background • DSS/Order Filler, Post-Processing Manager, Report Manager need to know when acquired evidence objects made it to the Archive • MPPS may be sent before objects are stored, and storage may fail • MPPS is not available to all “managers” • MPPS may fail or not be sent at all (media import) • Existing query mechanism forces “managers” to poll Image Manager/Archive for availability of SOP Instances. Vendor Workshop, Sep 2004

  21. Use Cases • This option only addresses the use case when MPPS referencing evidence objects has been received by Image Manager. • Image Manager generates Instance Availability Notification upon receiving of all objects referenced in particular MPPS. • Cross-referencing of MPPS in IAN may compensate for MPPS missed by OF Vendor Workshop, Sep 2004

  22. Instance Availability Notification Transaction Vendor Workshop, Sep 2004

  23. Instance Availability Notification Transaction • Image Manager/Image Archive generates an Instance Availability Notification message and send it to the DSS/Order Filler and optionally to other workflow managing actors (Post-Processing Manager, Report Manager). • DSS/Order Filler, Post-Processing Manager, Report Manager receive an Instance Availability Notification message and internally process it. Vendor Workshop, Sep 2004

  24. Interaction Diagram Vendor Workshop, Sep 2004

  25. Instance Availability Notification SOP Class • New SOP Class introduced in DICOM Supplement 93 • Normalized Service • N-CREATE Operation only • Can be used without association with MPPS • Does not convey and explicitly forbids adding of patient or procedure identifiers • Provides list of all object UIDs and their availability for retrieval, either over network or media (on per-image basis) Vendor Workshop, Sep 2004

  26. Instance Availability Notification SOP Class • New SOP Class introduced in DICOM Supplement 93 • No requirements when to generate notifications, for example: • availability of the first instance of a Performed Procedure Step or Study upon its reception, • availability of an entire set of instances comprising a completed Performed Procedure Step or Study Can be used without association with MPPS • Is not intended to satisfy scenarios or erroneous information reconciliation (see PIR profile) Vendor Workshop, Sep 2004

  27. Instance Availability Values • “ONLINE” means the instances are immediately available from the Retrieve AE Title, and if a C-MOVE were to be requested, it would succeed in a reasonably short time • “NEARLINE” means the instances need to be retrieved from relatively slow media such as optical disk or tape, and if a C-MOVE were to be requested from the Retrieve AE Title, it would succeed, but may take a considerable time • “OFFLINE” means that a manual intervention is needed before the instances may be retrieved, and if a C-MOVE were to be requested from the Retrieve AE Title, it would fail (e.g., by timeout) without such manual intervention. • “UNAVAILABLE” means the instances cannot be retrieved from the Retrieve AE Title, and if a C-MOVE were to be requested, it would fail. Note that SOP Instances that are unavailable from this AE may be available from other AEs, or may have an alternate representation that is available from this AE. Vendor Workshop, Sep 2004

  28. Trigger Events • Image Manager shall send only one IAN message for each MPPS referencing at least one evidence object. • Image Manager shall sent IAN when it received ALL instances referenced in MPPS • Image Manager shall send IAN to DSS/OF, and optionally to other actors Vendor Workshop, Sep 2004

  29. Message Semantics • Timing of a message can vary significantly depending on timing of MPPS and object storage • No message may be sent if complete object set never arrives • No message may be sent if objects arrive without corresponding MPPS • Even when objects are included in IAN, the retrieval request may fail due to errors Vendor Workshop, Sep 2004

  30. Expected Actions • Actors receiving IAN message are expected to use its content for workflow management. • Examples of internal actions: • The Department System Scheduler/Order Filler may update the procedure status internally, indicating that images for the procedure have been stored. • The Post-Processing Manager may add or re-arrange items to a corresponding worklist. • The Report Manager add items to a corresponding worklist. Vendor Workshop, Sep 2004

  31. References • Profile Option - Volume 1, Chapter 3 • Transactions - Volume 3, Section 4.49 Vendor Workshop, Sep 2004

  32. More information…. • IHE Web sites: http://www.himss.org/IHE http://www.rsna.org/IHE http://www.acc.org/quality/ihe.htm. • Technical Frameworks: • ITI V1.0, RAD V5.5, LAB V1.0 • Technical Framework Supplements - Trial Implementation • May 2004: Radiology • August 2004: Cardiology, IT Infrastructure • Non-Technical Brochures : • Calls for Participation • IHE Fact Sheet and FAQ • IHE Integration Profiles: Guidelines for Buyers • IHE Connect-a-thon Results • Vendor Products Integration Statements Vendor Workshop, Sep 2004

  33. Questions,Comments,and/orSuggestions? Vendor Workshop, Sep 2004

More Related