Stream: implementers
Topic: Practitioner.role vs PractitionerRole
Pascal Pfiffner (Aug 12 2016 at 09:55):
Is there a reason there is Practitioner.role and PractitionerRole in v1.6? They are identical.
Pascal Pfiffner (Aug 12 2016 at 10:03):
Well, they are close, anyway.
Aleksandra Pavlyshina (Aug 12 2016 at 11:29):
As I know, PractitionerRole resource is waiting to be approved to replace the Practitioner.role.
Josh Mandel (Aug 12 2016 at 12:06):
http://hl7.org/fhir/2016Sep/practitionerrole.html#bnr corroborates :)
Josh Mandel (Aug 12 2016 at 12:09):
What I don't see on http://hl7.org/fhir/2016Sep/practitionerrole.html is an explanation of why this had been modeled as a standalone resource (I'm sure there's a good reason; I just can't find it there.).
Brian Postlethwaite (Aug 12 2016 at 12:11):
That's right, there is. And I do need to write it up.
Michelle (Moseman) Miller (Dec 05 2016 at 23:33):
@Brian Postlethwaite , your blog, https://brianpos.com/2016/10/16/practitioner-role-vs-practitionerrole/, says
We would not need to change anything that references Practitioner to now reference Practitioner Role, as in most cases the role was either irrelevant or implied by the property(Observation), and where it is relevant (such as in an Appointment, Encounter, CareTeam) the specific role details are already defined on the resource itself
However, I am starting to wonder about use cases when we need to convey both the PractitionerRole.practitioner and PractitionerRole.organization. For example, when a patient is assigned to a PCP at a specific organization, it feels like the Patient.generalPractitioner (and/or CareTeam.participant.member) might need to reference PractitionerRole. I saw in PA meeting minutes there might have been a similar discussion on ReferralRequest needing to know the practitioner at a specific org as well.
Also, if Practitioner.role is replaced with a reference to PractitionerRole, then doesn't that create a circular reference?
ravi.kuchi (Dec 06 2016 at 04:46):
I do not see any major benefits in defining the role (PractitionerRole) as a separate resource and I agree with @Michelle (Moseman) Miller that it complicates the associations. We have implemented Practitioner(DSTU2) in production and have not seen or foresee any performance(filtering) issues that the blog brings up
Last updated: Apr 12 2022 at 19:14 UTC
