Difference between revisions of "Cross Enterprise Cardiovascular Heart Team"

From IHE Wiki
Jump to navigation Jump to search
Line 8: Line 8:
 
[[image:XTCH1.png]]
 
[[image:XTCH1.png]]
  
−
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
 
  
 
==Benefits==
 
==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.>''
+
 
 +
The XCHT-WD Profile provides a common workflow that:
 +
*facilitate the management of a dynamic and flexible team of professionals as Heart Team, involved in many cardiological clinical cases, that has to support the cardiologist in the taking decision
 +
*improve the efficient sharing of information (right data to right professionals)
 +
*accelerate taking decision
 +
 
 +
 
  
 
==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 XCHT-WD Profile defines rules and tasks of members of Heart Team and data to be shared, in a common workflow applied to Heart Team. This profile is built upon the XDW Profile, it needs to be supported by
 +
*XDS.b and XDS-I Profiles to allow for the sharing of clinical documents and workflow documents
 +
*DSUB Profile to allow for the notification of availability
 +
XCHT-WD Profile will be one alternative to help to fill the gap in workflow management, providing links for relevant/required clinical information to specific workflow tasks of the HT.
 +
 
 +
==Systems Affected==
 +
Systems that can be involved in the process described above are:
 +
*CIS system
 +
*Hospital EHR system
 +
*HIS
  
−
''<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.>''
+
'''Actors & Transactions:'''
  
−
''<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.>''
+
The systems participating into XCHT-WD needs to create the XDW Workflow Document, consume and update its.
−
 
−
==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.''
+
[[image:XTCH2.png]]
−
* ''Display systems may query, retrieve and display Evidence Documents.''
 
−
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
 
  
−
'''Actors & Transactions:'''
+
These transactions defined how the actors have to create and update the workflow document on bases of their rules and how the workflow document has to be shared and notified. These transactions is based on existing IHE document sharing profiles in particular XDS profile.
  
−
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[image:XTCH3.png]]
  
 
==Specification==
 
==Specification==
  
−
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Trial Implementation]]   
−
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
 
'''Documents:'''  
 
'''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.>''
+
*[XCHT-WD Supplement]
  
−
[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:'''
 
'''Underlying Standards:'''
  
−
''<list all the standards on which the profile is based; if possible with links to sources>''
+
*OASIS Web Services – Human Task (WS-HumanTask) Specification Version 1.1
−
:* [http://dicom.nema.org DICOM]
+
*HL7 CDA Release 2.0 and Reference Information Model.
−
:* [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 XCHT-WD profile depends on other IHE profiles:
−
 
+
*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.
−
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
*Cross Enterprise Workflow coordinates human and applications mediated workflows across multiple organizations.
−
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
+
*Document Metadata Subscription describes the use of subscription and notification mechanism for use within an XDS Affinity Domain and across communities.
−
* ''[[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'''
 
'''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>''
+
none
−
 
 
−
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'''
 
'''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>''
+
none
  
 
'''Reference Articles'''
 
'''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. >''
+
none
−
 
 
  
  
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
−
 
−
[[Category:Template]]
 
−
 
−
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 

Revision as of 15:38, 21 July 2016

Cross Enterprise Cardiovascular Heart Team Workflow Definition Profile (XCHT-WD) orchestrates the creation of a dynamic network of cardiovascular professionals called Heart Team (HT), across multiple organizations and the exchange of data between their clinical health information systems.

Summary

It is difficult to manage and coordinate remote interaction among healthcare professionals involved in a multidisciplinary and dynamic team on cardiac diseases (Heart Team) that they support community hospitals. The sharing of information is a critical component in establishing an efficient use of the HT. It is critical that different types of documents and information are easily accessible while the HT is making its evaluation. There are existing profiles that define the sharing of documents and the notification but is not enough to manage dynamic team. The XCHT-WD Profile defines the workflow, intended as a common set of rules and activities, related to the collaboration of the members of a dynamic network of cardiovascular professionals that belong to different hospitals, called a Heart Team (HT), to facilitate appropriate decision making on the treatment or intervention used for patients and to better manage the knowledge exchange. XTCH1.png


Benefits

The XCHT-WD Profile provides a common workflow that:

  • facilitate the management of a dynamic and flexible team of professionals as Heart Team, involved in many cardiological clinical cases, that has to support the cardiologist in the taking decision
  • improve the efficient sharing of information (right data to right professionals)
  • accelerate taking decision


Details

The XCHT-WD Profile defines rules and tasks of members of Heart Team and data to be shared, in a common workflow applied to Heart Team. This profile is built upon the XDW Profile, it needs to be supported by

  • XDS.b and XDS-I Profiles to allow for the sharing of clinical documents and workflow documents
  • DSUB Profile to allow for the notification of availability

XCHT-WD Profile will be one alternative to help to fill the gap in workflow management, providing links for relevant/required clinical information to specific workflow tasks of the HT.

Systems Affected

Systems that can be involved in the process described above are:

  • CIS system
  • Hospital EHR system
  • HIS

Actors & Transactions:

The systems participating into XCHT-WD needs to create the XDW Workflow Document, consume and update its.

XTCH2.png

These transactions defined how the actors have to create and update the workflow document on bases of their rules and how the workflow document has to be shared and notified. These transactions is based on existing IHE document sharing profiles in particular XDS profile.

XTCH3.png

Specification

Profile Status: Trial Implementation

Documents:

  • [XCHT-WD Supplement]


Underlying Standards:

  • OASIS Web Services – Human Task (WS-HumanTask) Specification Version 1.1
  • HL7 CDA Release 2.0 and Reference Information Model.

See Also

Related Profiles

The XCHT-WD profile depends on other IHE profiles:

  • 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 Workflow coordinates human and applications mediated workflows across multiple organizations.
  • Document Metadata Subscription describes the use of subscription and notification mechanism for use within an XDS Affinity Domain and across communities.


Consumer Information

none

Implementer Information

none

Reference Articles

none


This page is based on the Profile Overview Template

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