SWF.b Assisted Protocol Option Extension

From IHE Wiki
Jump to navigation Jump to search

This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and copy the contents of this page and paste the contents into your newly created page.

<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>

1. Proposed Workitem: <initial working name for profile/whitepaper/etc>

  • Proposal Editor: Chris Lindop
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: Radiology

2. The Problem

IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.

Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.

There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order.

This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.

3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>

<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>

4. Standards and Systems

<List existing systems that are/could be involved in the problem/solution.>

<If known, list standards which might be relevant to the solution>

5. Discussion

<Include additional discussion or consider a few details which might be useful for the detailed proposal>

<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>
<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>
<What are some of the risks or open issues to be addressed?>

<This is the brief proposal. Try to keep it to 1 or at most 2 pages>

<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>