Telemonitoring of patients with chronic heart failure
Related Use Case
Involvement of chronic patients in electronic documentation of healthcare information
Scenario context
The patient has internet access, and can be expected to enter the measured data
Actors/Roles
- Monitoring Service – data collecting and monitoring software
- Medical Triage Service – healthcare professional(s)
- Healthcare Centre
Transactions
- Send Measurements
- Send Alert
Technical process flow
- (no software action)-
- Patient enters weight and blood pressure in a smartphone/tablet/pc application. The information is sent to and saved in the Monitoring Service software
- Information is monitored and checked against the min-max values that have been set for this patient, and against sudden changes compared to previous measurements
- Sudden rises or drops in the measured values trigger an alert message to the Medical Triage Centre
- The Medical Triage Centre contacts the patient (by phone, out of scope for this Use Case)
- The patient’s medication dosage is changed (out of scope for this Use Case)
- The Medical Triage Centre sends an alert to the Healthcare Centre
- The Healthcare Centre makes an appointment with the patient (out of scope for this Use Case)
Associated profiles, standards, and HL7 FHIR Implementation guides
- Policy: —
- Care process: —
- Information: MS (also called XDS-MS)
- Infrastructure: PIX/PDQ, XDS/XDR/XDM, CT, ATNA
- Infrastructure, Patient Care Device: HRN, WAN+, DEC*/RTM*, LAN+ or PAN+, (MHD, DEC)
- Access control: BPPC, XUA(++)
Possible issues
XDR enables sending a “push” alert to another party. This may be realised with XDR (which is a web service-based solution), or, within an XDS affinity domain, with either DSUB or NAV.