Difference between revisions of "Management of Acquisition Protocols"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "__TOC__ ==Summary== Management of Acquisition Protocols (MAP) lets image acquisition protocols be sent between scanners, archives and protocol management workstations for the...")
 
Line 54: Line 54:
  
  
'''Consumer Information''' - Replace this with direct sample RFP language, here or higher up in the document. Should appear in TOC
+
'''Consumer Information''' - Replace this with direct sample RFP language, here or higher up in the document. Should appear in TOC. Maybe after Systems Affected
  
 
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
 
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''

Revision as of 20:46, 10 October 2018

Summary

Management of Acquisition Protocols (MAP) lets image acquisition protocols be sent between scanners, archives and protocol management workstations for the purpose of review and management. DICOM currently handles CT protocols, but work is under way to also handle MR and X-ray Angiography protocols.

<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases). Don't get into how it works, leave that to the Details section.>

<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>

Benefits

<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>

Details

<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>

<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>

<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>

Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

  • PACS systems may store, manage, and/or display Evidence Documents.
  • Display systems may query, retrieve and display Evidence Documents.
  • Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Trial Implementation

Documents:

IHE Management of Acquisition Protocols (MAP) Supplement

Underlying Standards:

See Also

Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>

  • Scheduled Workflow [SWF.b] has an Assisted-Protocol Setting Option that would benefit from management of protocol labels.
  • Portable Data for Imaging [PDI] could be used to export/import DICOM protocol instances to media for sharing with another facility or organization. (e.g., protocols for multiple models in a given clinical trial, reference protocols for a particular diagnostic task, or a full backup catalog of protocols)
  • Radiation Exposure Monitoring [REM] could be used on the protocol manager to coordinate a dose reduction program with protocol management.


Consumer Information - Replace this with direct sample RFP language, here or higher up in the document. Should appear in TOC. Maybe after Systems Affected

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>


Reference Articles

This page is based on the Profile Overview Template