Stream: implementers
Topic: FHIR way to respond to a patient observation
Brian Reinhold (Jul 05 2019 at 00:03):
IN a remote patient monitoring scenario a doctor is monitoring several pregnant women. The women are at home but are at risk for certain complications. The women are instructed to take certain measurements which are uploaded to a FHIR server. The doctor subscribes to these measurements using a remote patient monitoring application. What would be the most appropriate FHIR-way for the doctor to respond to examination of these measurements or measurement history? A response may be to indicate everything looks okay, or there is something questionable and one should come in, or it could be an 'alarm' which basically says get in contact ASAP. The patient's uploader subscribes to these FHIR resources (whatever they are) and it will display the response. That may involve an alarm. If the uploader is on a cell phone the alarm may 'call' the patient but that is out of scope for the FHIR part.
Would a Flags resource be appropriate? It does not seem so from the description about that scenario. Would a Communication resource be appropriate? Is there a way to indicate all okay?
Lloyd McKenzie (Jul 05 2019 at 01:21):
I'd update the record with a tag that says the equivalent of "Dr. Smith has reviewed this". If it's not all ok, then presumably the clinician will take action and will create a resource appropriate to whatever action they're taking (Communicate to send it to someone else, Appointment to book a visit, ServiceRequest to order additional tests, etc.)
Brian Reinhold (Jul 07 2019 at 10:30):
@Lloyd McKenzie I was thinking (in this case) more for the patient to get the responses. The patient would get a notification on the uploader (it would need to subscribe to the appropriate resources or search for it if it were not continuously running), especially the all okay if that were indeed true.
Lloyd McKenzie (Jul 07 2019 at 17:38):
The equivalent of an email read receipt? That would be a completed Communication resource instance
Last updated: Apr 12 2022 at 19:14 UTC
