Difference between revisions of "Image-Enabled Office Workflow"

From IHE Wiki
Jump to: navigation, search
(Created page with "''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.'' __TOC__ ==Summary== ''<Describe the profile in ...")
 
(See Also)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
+
''Image-Enabled Office Workflow (IEO) defines integration of an imaging suite with an electronic health record system in an ambulatory office setting.''
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
''<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.>''
+
The Image-Enabled Office (IEO) Profile specifies the integration of an imaging suite (modalities, storage server, and workstations) with an electronic health record system in an ambulatory office settingThis is a fully bi-directional integration, including ordering/scheduling of an imaging exam, status reporting for that exam, report creation, and web-based imaging exam review integration.  
  
''<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==
  
 +
From a PACS and imaging device perspective, IEO facilitates the adoption of imaging in the office environment, because the imaging assets can be deployed with almost no changes.
  
==Benefits==
+
From the office EHR perspective, the profile provides integration to the imaging suite using commonly used interface technologies, including HL7v2 messages and web services.
  
''<List the key benefits the profile provides (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.  If possible, identify benefits that help users and vendors make the business case for the profile.>''
+
From an in-patient imaging IT perspective (RIS / CVIS / broker), the DICOM-related imaging workflow management assets can be packaged for integration with office EMRs in two different architectural approaches.
 +
 
 +
IEO is of particular interest to those providers and vendors who want to bring their existing in-patient experience into the office domain. It also provides a roadmap as to how those providers and vendors in the office space can leverage capabilities from the in-patient domain to deliver effective imaging workflows to the end-user.
  
 
==Details==
 
==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.>''
+
The imaging suite of an ambulatory office is expected to operate in the same manner as a hospital imaging suite.   
 
+
''<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 shortE.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==
 
==Systems Affected==
Line 34: Line 33:
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
+
  
 
'''Documents:'''  
 
'''Documents:'''  
Line 71: Line 69:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:Cardiac Profile]]
 +
[[Category:DICOM]]

Latest revision as of 14:29, 4 November 2019

Image-Enabled Office Workflow (IEO) defines integration of an imaging suite with an electronic health record system in an ambulatory office setting.

Summary

The Image-Enabled Office (IEO) Profile specifies the integration of an imaging suite (modalities, storage server, and workstations) with an electronic health record system in an ambulatory office setting. This is a fully bi-directional integration, including ordering/scheduling of an imaging exam, status reporting for that exam, report creation, and web-based imaging exam review integration.

Benefits

From a PACS and imaging device perspective, IEO facilitates the adoption of imaging in the office environment, because the imaging assets can be deployed with almost no changes.

From the office EHR perspective, the profile provides integration to the imaging suite using commonly used interface technologies, including HL7v2 messages and web services.

From an in-patient imaging IT perspective (RIS / CVIS / broker), the DICOM-related imaging workflow management assets can be packaged for integration with office EMRs in two different architectural approaches.

IEO is of particular interest to those providers and vendors who want to bring their existing in-patient experience into the office domain. It also provides a roadmap as to how those providers and vendors in the office space can leverage capabilities from the in-patient domain to deliver effective imaging workflows to the end-user.

Details

The imaging suite of an ambulatory office is expected to operate in the same manner as a hospital imaging suite.

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:

IEO.PNG

Specification

Profile Status: Trial Implementation

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

  • Vol. 1 - Section 5 (SWF Profile)
  • Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
  • Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


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.>


This page is based on the Profile Overview Template