1 / 6

Wrong / Poor Objects

Wrong / Poor Objects. Change Requester. Change Receiver. Reject Instances. Based on RAD-66 Image Rejection Note Stored For Quality Reason and For Patient Safety Reason Differences: No sop class restriction (i.e. support non-image obj) Different actors

lindsay
Download Presentation

Wrong / Poor Objects

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. Wrong / Poor Objects Change Requester Change Receiver Reject Instances • Based on RAD-66 Image Rejection Note Stored • For Quality Reason and For Patient Safety Reason • Differences: • No sop class restriction (i.e. support non-image obj) • Different actors • Add the following behaviour on Change Requester • Will reject subsequent re-appearance of sop instances that have been deleted

  2. Incorrect Demographics/Worklist (1) Reject Instances Change Requester Change Receiver Store Replacement Instance • Reject Instances • Specific content • Document Title (xxxxxxx, DCM, “Incorrect Modality Worklist”)

  3. Incorrect Demographics/Worklist (2) Reject Instances Change Requester Change Receiver Store Replacement Instance • Store Replacement Instance • Similar to RAD-70 Image Manager Instances Stored • New replacement objects shall have • the correct demographics and procedure information • new series and sop instance uids (i.e. they are new objects, not updated old objects)

  4. Incorrect Demographics/Worklist (3) Reject Instances Change Requester Change Receiver Store Replacement Instance • Store Replacement Instance • (cont.) New replacement objects shall have • Referenced Image Sequence (0008,1140)> Referenced SOP Class UID (same as source)> Referenced SOP Instance UID (replaced sop instance uid)> Purpose of Referenced Code Sequence (xxxxxx, DCM, “Replacement for Incorrect Worklist”) • Accumulate Referenced Image Sequence for each replacement

  5. Data Retention Data Retention Requester Data Retention Receiver Reject Instances • Reject Instances • Specific content and behaviour • Document Title (xxxxxx, DCM, “Data Retention Expire”) • Deprecation is not sticky (i.e. can accept the same sop instance that has been deprecated)

  6. Instance Confirmation Change Requester / Data Retention Requester Change Receiver / Data Retention Receiver Confirm Instances • Confirm Instances • Named Option • Instance Availability Notification including all instances that remain and deleted • Remaining instances have ONLINE/NEARLINE/OFFLINE • Deleted instances have UNAVAILABLE • Open questions: • Is it transaction necessary or not? If yes, required or optional?

More Related