Stream: implementers
Topic: Implementing patient notification types
Florian Apolloner (Jan 28 2021 at 14:47):
Hi there,
I am not exactly sure what to search for and searching for notification/subscription has to many meanings in FHIR hence I am trying here.
We store several telecom items on the Patient resource (mainly email and phone numbers). Now we do have certain types of actions in our system where we want to notify the patient via sms or email. For instance if an appointment is rescheduled and originally would have happened within the next hour we schedule an appointment_changed_urgent event in our system and notify the patient (most likely via SMS). If it is more than one hour we simple schedule an appointment_changed event and also notify the patient (probably via mail). The patient is able to choose which communication medium he wants for which event (well not exactly the patient themself, but you get the idea). Now I also want to be able to provide this information to integrators. Does such an extension (or even core resource) already exist? If no, where would you attach such an extension? I am leaning towards the individual telecom items. Do you have other ideas on how to implement such a thing?
Thanks,
Florian
René Spronk (Jan 28 2021 at 14:54):
It's kind of tempting add a repeating complex extension to each telecom to denote which telecom is to be used for which event notification. That may get complex really quickly 9especially of the list of events is longish), so I'm not that sure this is a good idea. One could use Basic to construct a 'communication preference' resource, but then one would have to manage telecom updates both in patient as well as in this Basic resource.
Florian Apolloner (Jan 28 2021 at 15:10):
Assuming I would go down the Basic route, how would that look like? Have the patient as subject and then encode the individual events? How would the events refer to the communication transport (sms/phone?) -- our telecoms currently do not have individual IDs, which would making the link rather awkward.
Currently I am kinda leaning towards the extension on the telecom, seems easier for us.
Last updated: Apr 12 2022 at 19:14 UTC
