Difference between revisions of "Cross Enterprise Workflow"

From IHE Wiki
Jump to navigation Jump to search
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
'''Cross Enterprise Workflow (XDW)''' coordinates human and applications mediated workflows across multiple organizations.
+
coordinates human and applications mediated workflows across multiple organizations.
−
 
 
  
 
__TOC__
 
__TOC__
  
−
==Summary==
 
−
The Cross-Enterprise Document Workflow (XDW) profile enables participants in a multi-organizational environment to manage and track the tasks related to patient-centric workflows as the systems hosting workflow management applications coordinate their activities for the health professionals and patients they support.
 
−
 
−
XDW builds upon the sharing of health documents provided by other IHE profiles such as XDS, adding the means to associate documents conveying clinical facts to a patient-specific workflow. XDW provides a common interoperability infrastructure upon which a wide range of specific workflow definitions may be supported. It is designed to support the complexity of health services delivery with flexibility to adapt as workflows evolve.
 
−
 
−
[[Image:XDWereferral-workflow.jpg]]
 
−
 
−
==Benefits==
 
−
 
−
XDW provides a common, workflow-independent interoperability infrastructure that:
 
−
* provides a platform upon which a wide range of specific workflows can be defined with minimal specification and application implementation efforts on the workflow definition (e.g., Medical Referrals Workflow, Prescriptions Workflow, Home Care Workflow);
 
−
* benefits many clinical and non-clinical domains by avoiding different competing approaches to workflow management;
 
−
* increases the consistency of workflow interoperability, and enables the development of interoperable workflow management applications where workflow-specific customization is minimized;
 
−
* facilitates the integration of multi-organizational workflows with the variety of existing workflow management systems used within the participating organizations;
 
−
* offers the necessary flexibility to support a large variety of different healthcare workflows by not being overly constrained.
 
−
 
−
==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.>''
+
==Formal Specification==
  
−
''<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.>''
+
===[https://profiles.ihe.net/ITI/TF/Volume1/ch-30.html XDW (html) specification]===
−
+
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-30.html Final Text]
−
==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:''' [[Comments| Final Text]] 
 
−
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
−
 
 
−
'''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.>''
 
−
 
 
−
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
−
 
 
−
'''Underlying Standards:'''
 
−
 
 
−
''<list all the standards on which the profile is based; if possible with links to sources>''
 
−
:* [http://dicom.nema.org DICOM]
 
−
:* [http://www.hl7.org HL7]
 
−
:* ...
 
  
 
==See Also==
 
==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'''
 
'''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.>''
+
The XDW profile depends on other IHE profiles:
−
 
 
−
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
−
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
−
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
−
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
−
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
−
 
 
−
 
 
−
'''Consumer Information'''
 
−
 
 
−
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>''
 
−
 
 
−
'''Implementer Information'''
 
−
 
 
−
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 
−
 
 
−
'''Reference Articles'''
 
−
 
 
−
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
 
  
 +
* [[Cross-Enterprise Document Sharing]] [XDS] may be used to share the XDW Workflow Documents and the  input and output documents referenced by each workflow instance.
 +
* [[Cross-Enterprise Document Media Interchange]] [XDM] may be used to share via e-mail push or media interchange the XDW Workflow Documents as well as the  input and output documents referenced by each workflow instance.
 +
* [[Cross-Enterprise Document Reliable Interchange]] [XDR] may be used to push the XDW Workflow Documents and the input and output documents referenced by each workflow instance.
  
  
Line 95: Line 23:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:ITI Profile]]
 +
[[Category:DocShare]]
 +
[[Category:XDW]]
 +
 +
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].

Latest revision as of 12:42, 19 November 2021

coordinates human and applications mediated workflows across multiple organizations.


Formal Specification

XDW (html) specification

See Also

Related Profiles

The XDW profile depends on other IHE profiles:


This page is based on the Profile Overview Template

Current: IT Infrastructure Technical Framework.

Retrieved from "http://wiki.ihe.net/index.php?title=Cross_Enterprise_Workflow&oldid=126824"