Stream: implementers
Topic: Practitioner
Amy Allen (Feb 23 2022 at 19:19):
We need to include additional designations in the practitioner resource to satisfy some business use cases (is practitioner a physician, is practitioner available). We have been looking at extensions and meta.tag as solutions to potentially accommodate these needs. Looking for suggestions, input please.
David Pyke (Feb 23 2022 at 19:27):
You could use qualification.code to show that they're a physician. I'm not sure what you mean for "is practitioner available"
Amy Allen (Feb 23 2022 at 19:41):
The "is available" is an internal business need to designate if a practitioner is available for certain activities.
Notification Bot (Feb 23 2022 at 19:51):
Lloyd McKenzie has marked this topic as resolved.
Notification Bot (Feb 23 2022 at 19:51):
Lloyd McKenzie has marked this topic as unresolved.
David Pyke (Feb 23 2022 at 19:52):
That would probably be a custom extension that would show the activities they're available for
Lloyd McKenzie (Feb 23 2022 at 19:52):
That could map to 'active' if "being available" means "still acting as a Practitioner".
Hans Michel (Feb 23 2022 at 20:25):
Is there any reason for not implementing PractitionerRole
?
With that (linking PractitionerRole
to/ref Practitioner
) one gets
code
, specialty
, and the family of (availableTime
, notAvailable
, availabilityExceptions
).
Amy Allen (Feb 24 2022 at 14:40):
Thank you all for the input, after internal discussion looks like we will be implementing the extensions, which lend to expansion as other needs come up for further designations on our practitioner list for internal business needs.
Last updated: Apr 12 2022 at 19:14 UTC