Difference between revisions of "Cross-enterprise Basic eReferral Workflow Definition"

From IHE Wiki
Jump to navigation Jump to search
Line 105: Line 105:
 
[[Category:Template]]
 
[[Category:Template]]
 
[[Category:XDW]]
 
[[Category:XDW]]
[[Category:DS]]
 

Revision as of 09:00, 4 December 2017

This supplement is written according to the specific template defined for Workflow Definition profiles. The structure of this document differs from a PCC Content Profile. In particular the XBeR-WD profile establishes a common set of rules to share between participants involved in an eReferral workflow. The eReferral process, and workflow related to it, is applicable to many different sharing infrastructures. In this profile we present a specific XDS based use-case.

Summary

A common workflow pathway that illustrates the simplest process enabled by XBeR-WD profile is the use-case where the patient consults his GP for a health problem. As part of the consultation the patient is examined and some prior information is looked up by the GP. As a result of the visit the GP refers the patient to a specialist for further examination. The workflow connected to these organizational and clinical actions is composed of four steps:

  • 1) a physician refers a patient to another healthcare provider for a specialist’s consultation;
  • 2) the Health Care Provider (HCP), from the Hospital Information System, schedules the visit;
  • 3) the HIS admits the patient in hospital and the specialist can start the consultation which may span one or more visits;
  • 4) the specialist completes the consultation and produces a report;

These steps can be modeled in 3 different tasks of the eReferral workflow, (figure X.2-1):

  • 1) Request Referral: that tracks step A, performed by the Requester of the referral
  • 2) Schedule Referral: that tracks step B, performed by the Scheduler of the visit (This task is optional and doesn’t need to be tracked if the option “Process without scheduling phase” is selected)
  • 3) Perform Referral: that tracks steps C and D, performed by the HCP and the specialist.

Benefits

Cross-enterprise management of the workflow related to clinical processes is a fundamental topic with the increasing use by different sectors of document sharing related IHE profiles with their different types of document and information. This profile is built upon the ITI XDW Profile to manage the Cross Enterprise Basic eReferral Workflow. The management of the workflow related to the eReferral is involved in many clinical and organizational processes for its important role in the process of digitalization. The lack of a workflow management, at the moment, blocks the use of the eReferral in an extended way. The eReferral, without an instrument to manage its workflow, is only an order without any information about the status of the order itself. The definition of a workflow with fixed rules and tasks is needed in a cross-enterprise scenario in which many actors are involved in the same process. The creation of an eReferral by a GP, or Primary Care Provider (PCP) opens a clinical process that involves many actors and that is a cross-enterprise workflow. The purpose of the XBeR-WD profile is to precisely define the workflow associated with an eReferral Document, the actors involved and the digital documents related with this process (produced in this or in other processes, but related to the eReferral workflow).

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

  • HIS
  • EHR


Actors & Transactions:

ActorTransactionXBER.PNG

Specification

Profile Status: Trial Implementation

Documents:

XDW profile in Vol.1

XDW profile in Vol.3

XBeR-WD profile


Underlying Standards:

See Also

Related Profiles

This profile is based on XDW (Cross-Enterprise Document Workflow), in a specific XDS.b context.


This page is based on the Profile Overview Template