Stream: implementers
Topic: Need advice with placing properties on FHIR Practitioner
Dan Siwiec (Nov 06 2017 at 18:14):
Hi, I'm implementing an API following the FHIR STU3 standard and would like to ask for advice with placing some properties, so that I don't deviate from the standard too much. I'm looking at 3 properties:
- available for online scheduling A flag describing whether the Practitioner is accepts online scheduling
- activation date A date when this practitioner will become available for accepting appointments
- hidden A flag allowing to temporarily hide a Practitioner
Here's my thinking - can I treat online scheduling as a separate Role in itself? I'm currently using the Practitioner Role to list all the organizations the Practitioner is part of. Would this make sense or should I try to add online scheduling as properties on existing Roles?
I'm thinking of using some properties on the PractitionerRole for the other two fields, namely the active flag for my hidden field and the period start field for the activation date.
Thoughts?
Lloyd McKenzie (Nov 06 2017 at 22:45):
@Brian Postlethwaite ?
Brian Postlethwaite (Nov 10 2017 at 06:57):
Yes, I'd be considering the scheduling to be matched up with the PractitionerRole rather than the Practitioner, as is operating at a practice (even if its his own sole practitioner practice) and when working at multiple places, then is there.
This also needs to tie into the Schedule and Slot resources where those actual things can give you fine grain control over things.
Brian Postlethwaite (Nov 10 2017 at 06:58):
No available appointments is no schedule.
Brian Postlethwaite (Nov 10 2017 at 07:02):
If you have a scheduling system, then its likely to have the window of available appointments (slots) defined in the schedule (so from today for the next 2 months, or the booking window is only open for next month)
Last updated: Apr 12 2022 at 19:14 UTC
