Cross-enterprise TeleHome Monitoring Workflow Definition

From IHE Wiki
Jump to: navigation, search

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 XTHM-WD Profile establishes a common set of rules to share between participants involved in a telemonitoring workflow. The telemonitoring process, and workflow related to it, is applicable to many different sharing infrastructures. In this profile we present a specific XDS based use-case.


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

<See Help - Tips and Tricks for details on inserting an image/graphic.>


The workflow related to the management of patients with chronic diseases (e.g., heart failure, COPD, diabetes) followed by a telemonitoring service is a cross-enterprise workflow since many different individuals from different enterprises can be involved: specialists and physicians, working in hospitals, rural areas or urban areas, general practitioners (GP), and general caregivers, as well as the telemonitoring centre’s staff.

For the correct management of these patients, each of these individuals, managing his part of the telemonitoring workflow, should have also the possibility to share and manage the patient’s complete clinical history. However, at the moment there are no technical specifications allowing this to be done in a standardized manner.

This profile provides guidelines to define this kind of cross-enterprise workflow using the XDW profile, allowing every participant involved in a patient's care to share the complete telemonitoring workflow, including all related documents produced for each event occurring during the process (data sending, request for a visit, change of therapy), and the related workflow status.

This proposal focuses on the Cross Enterprise TeleHomeMonitoring Workflow Definition in support of telemonitoring workflow document and status management.

The key elements are:

  • managing telemonitoring cross-enterprise workflow, tracking all events and related documents;
  • managing workflow specific status with relationship to one or more documents;
  • tracking status of all events in telemonitoring process (in progress, completed, etc.).

With the increase in the elderly population and the consequent increase in the prevalence of patients with chronic diseases (as diabetes, chronic heart failure and COPD), the introduction of a telemonitoring service for these patients, with good workflow management, as defined in this profile, would entail a considerable advantage in terms of quality of life for patients and cost savings.

To demonstrate the scale of the problem, an analysis has been performed on some European data about the most relevant chronic diseases: now COPD affects approximately 44 million people (Eur Respir J 2011); heart failure affects about 15 million people (ESC 2008). The introduction of a telemonitoring service for these patients, with good workflow management, as defined in this profile, would entail a considerable advantage in terms of quality of life for patients and cost savings.


The general telemonitoring process flow can be described with the following steps:

A. The Telemonitoring process starts when a GP or a general caregiver requests the activation of a telemonitoring service for his patient to a telemonitoring service provider. In this initial phase of the process the GP defines the telemonitoring protocol for the patient and produces a telemonitoring Workflow Document with a “Request Activation” task as the first entry.

B. The service provider now evaluates and approves the physician's request and activates the service; the workflow document is updated with a new “Approve Request” task.

C. The patient starts to collect the required clinical parameters at his home or place of residence. The data collected is transmitted to the service provider that manages the data, making them available to any clinicians involved in the process. The Workflow Document is updated with a “Telemonitoring” task.

D. If the data sent by the patient goes outside the threshold levels defined in the protocol, the service provider alerts the referring physician and updates the Workflow Document with a “Consult Request” task.

E. The physician analyses the patient's data and decides if the patient needs to change their therapy, to have a specialist visit, or if there is no need to perform any action. The Workflow Document is updated with a task that depends on the decision taken by the clinician:

Template:PadE1. “Analyze and Request Visit”;

Template:Hidden textE2. “Analyze and Change Protocol”;

E3. “Analyze and Take Clinical Action”;

E4. “Analyze and Take No Action”.

F. Depending on the resulting task from step E, two options can result:

F1. If the decision is to schedule a visit, an eReferral process is activated. When the eReferral workflow ends the clinician that performed the referral updates the Workflow Document with the task “Visit Result”.

F2. If the result includes a need to change the protocol, the service provider receives the protocol from the clinician and activates it, updating the Workflow Document with the task “New Protocol Activation”.

G. If needed the Telemonitoring service can be closed by the Service Provider or by the referring physician according to a shared management of the service closing: if the request of closing is started by the referring physician, the Service Provider has to confirm the closing; if the request of closing is started by the Service Provider, the referring physician has to confirm the closing. This allows to acknowledge about the service closing both these actors that have in charge the patient during the telemonitoring process, the Service Provider from the technical point of view, the referring physician from the clinical point of view.

The patient now continues with the telemonitoring service. These steps can be tracked in eleven different tasks throughout the workflow:

  1. Request Activation: tracks step A, performed by the patient’s clinician;
  2. Approve Request: tracks step B, performed by the telemonitoring service provider;
  3. Telemonitoring: tracks step C, performed by the telemonitoring service provider;
  4. Consult Request: tracks step D, performed by the telemonitoring service provider;
  5. Analyze and Request Visit: tracks step E1, performed by the patient’s clinician;
  6. Visit Result: tracks step F1, performed by the patient’s clinician;
  7. Analyze and Change Protocol: tracks step E2, performed by the patient’s clinician;
  8. New Protocol Activation: tracks step F2, performed by the telemonitoring service provider;
  9. Analyze and Take Clinical Action: tracks step E3, performed by the patient’s clinician;
  10. Analyze and Take No Action: tracks step E4, performed by the patient’s clinician.
  11. Close Telemonitoring Service

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

Actors & Transactions:


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


Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>


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

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

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

This page is based on the Profile Overview Template