Stream: implementers
Topic: Appointment.patient
nicola (RIO/SS) (Oct 03 2017 at 12:49):
Why is patient a participant of Appointment, not direct ref like Appointment.patient - 20/80? From technical point of view, this is very inconvenient :(
Christiaan Knaap (Oct 03 2017 at 19:17):
What technique is causing this to be a problem? Appointment.patient is a search parameter, could that be help?
nicola (RIO/SS) (Oct 04 2017 at 07:59):
I think this level of abstraction higher than required :) - looks like v3. We have Encounter.patient, Observation.subject and do not have Appointment.patient - uniformity?
Lloyd McKenzie (Oct 04 2017 at 13:48):
You can't have an Encounter without a patient. You can have an appointment without a patient. The scheduling system is designed to manage scheduling that isn't patient-specific. We could take the route and say everyone participating is Appointment.subject (a la Observation), but that language wouldn't make a lot of sense to the community.
Eric Haas (Oct 04 2017 at 17:35):
@Brian Postlethwaite ? I also found this a bit incongruous at first but got used to it. But good to get the PA perspective on this...
Michelle (Moseman) Miller (Oct 04 2017 at 18:46):
This sounds similar to CareTeam, where the patient can be a participant -- and you can have a CareTeam without a patient (e.g. code red event team). Having both Appointment.patient AND Appointment.participant is the pattern CareTeam used. In sum, I would support the addition of Appointment.patient as long as we keep participant as is to make it clear when the patient is included or not.
Brian Postlethwaite (Oct 05 2017 at 05:45):
And when the appointment includes multiple patients?
Brian Postlethwaite (Oct 05 2017 at 05:46):
Jsut seems funny to have the appointment outside where the status on the participation, or the requirement for inclusion is not considered there either.
(required and status properties - these would then need to be replicated to the top level, and then try and scope them out)
Brian Postlethwaite (Oct 05 2017 at 05:47):
The way it is covers a usecase where 2 practitioners are going to discuss a patient but the patient is not present/required.
the patient does have a specific search parameter to easily search for them.
Last updated: Apr 12 2022 at 19:14 UTC
