Stream: implementers
Topic: patientInstructions structured
Mathijs Kreijkes (Jan 30 2020 at 13:47):
Hi,
Does anyone have ideas about the following? We have an Appointment in which we want to place patientInstructions.. the field Appointment.patientInstructions field seems to discribe our use-case but its an 0..1 multiplicity String type.. we would like to keep the different instructions seperated.
Based on a current HL7V2 OML message OML->ORC->OBR->OBX the instruction is placed in the OBX segment. which makes me beleive the FHIR Oberservation is also an option. Appointment.reasonReference but then again if i see that description:
Reason the appointment has been scheduled to take place, as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.
It may be used as the admission diagnosis.. is telling the patient that he/she has to be sober to attent the appointment an admission diagnosis and thus a right use-case to use the Appointment.reasonReference?
Is there an other Resource (could't find one)? Or is making an extension an better solution?
Vassil Peytchev (Jan 30 2020 at 18:31):
Sounds like proposing an improvement to the Appointment resource is a good next step. You may still need an extension to use the improvement in an earlier version,.
Brian Postlethwaite (Jan 31 2020 at 01:56):
@Cooper Thompson, is this an area you guys already handle?
Cooper Thompson (Feb 04 2020 at 16:24):
We really only have one Appointment-level, textual patient instruction field. However we do have other types of Appointment-related patient communications, such as letters, visit guides, questionnaires, etc., but all of those have a home in other FHIR resources. Though maybe it makes sense to have a more specific link to those from Appointment than supportingInformation. For example, Communication does have a "reasonReference", but that doesn't include Appointment. If it did, then you could probably satisfy this by using a few different Communication resources that reference the Appointment.
Brian Postlethwaite (Feb 04 2020 at 21:18):
If this worth taking a tracker for it?
Cooper Thompson (Feb 05 2020 at 18:25):
Last updated: Apr 12 2022 at 19:14 UTC
