Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Use Case Table of Contents

FHIR Write Use Cases

Meducation Write PDF Back

When Meducation materials are printed out for the patient, those materials (PDF) should be stored in the patient record.   Hospitals require there be a record of any materials that were provided to a patient.  As well, those documents should be tagged as "patient materials" so that they are automatically posted to the patient portal (this is how many EHRs work – if a document associated with a certain patient record is tagged as being for patient use, then that document is automatically accessible from the patient portal). 

Pediatric Growth Chart Write Back of Z-Score

When a clinician sees a pediatric patient and views the pediatric growth chart, the clinician documents Z% score to be stored as part of the patients longitudinal record inside the EHR using the Pediatric Growth Chart Application.

Bilirubin Chart Writes a Transcutaneous Bilirubin Observations

To assess the risk of hyperbilirubinemia in new borns, a clinician uses a transcutaneous bilirubinometer to read the serum bilirubin levels. The clinician then documents the reading to be stored as part of the patients longitudinal record inside the EHR using the Bilirubin Chart Application.

Bilirubin Monitor Writes an Alert/Notification

When the Bilirubin Monitor sees that a bilirubin observation has not been stored for a new born within a certain amount of time after birth, it needs to raise an alert to relevant clinicians reminding them to do a serum bilirubin reading.

When the Bilirubin Monitor sees a bilirubin observation with serum bilirubin levels that exceed a certain threshold, it needs to raise an alert to relevant clinicians providing advice on how to intervene and treat the patient along with a link so the Bilirubin Chart Application can be opened directly from the Alert/Notification.

Ideally, the Bilirubin Monitor would raise alerts inside of the EHR in the way that is standard for that EHR. The goal being that alerts generated by the Bilirubin Monitor are treated the way all alerts generated by EHR are treated. 

Eventing Use Cases

Bilirubin Monitor Responds to 'Baby Born' & Bilirubin Observations

When a baby's birth is documented in the EHR, the Bilirubin Monitor is notified by the EHR with an event containing enough relevant information so that the Bilirubin Monitor can query the EHR through it's FHIR services to collect relevant details about the patient.

When ever a serum bilirubin is stored in the EHR, the Bilirubin Monitor is notified by the EHR. (This could be handled by an implementation of the FHIR Subscription resource).

Work is underway to support this in the HSPC Reference Implementation.

Backend Service Use Case

Bilirubin Monitor Is Authorized to subscribe to certain clinical event published by the EHR 

The Bilirubin Monitor needs to authorized to listen to relevant events happening inside of the EHR. Such as: Baby is born, bilirubin observation written/updated. It also needs to be authorized to read patient demographics, observations, and write alerts/notifications.

 

  • No labels