This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
Continuous
Integration
Build
of
available
versions,
see
FHIR
(will
be
incorrect/inconsistent
at
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
Responsible
Owner:
Patient
Administration
Work
Group
|
Normative
|
|
Compartments : Practitioner |
Detailed Descriptions for the elements in the PractitionerRole resource.
| PractitionerRole | |||||
|
| PractitionerRole | ||||
| Definition |
A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. |
||||
| Short Display | Roles/organizations the practitioner is associated with | ||||
|
|
0..* | ||||
|
| DomainResource | ||||
| Requirements |
Need to track services that a healthcare provider is able to provide at an organization's location, and the services that they can perform there. |
||||
| Summary | false | ||||
| PractitionerRole.identifier | |||||
|
|
PractitionerRole.identifier | ||||
| Definition |
Business Identifiers that are specific to a role/location. |
||||
|
| Identifiers for a role/location | ||||
| Note |
This
is
a
business
|
||||
|
|
0..* | ||||
| Type | Identifier | ||||
| Requirements |
Often, specific identities are assigned for the agent. |
||||
| Summary | true | ||||
| Comments | A specific identifier value (e.g. Minnesota Registration ID) may appear on multiple PractitionerRole instances which could be for different periods, or different Roles (or other reasons). A specific identifier may be included multiple times in the same PractitionerRole instance with different identifier validity periods. | ||||
| PractitionerRole.active | |||||
|
|
PractitionerRole.active | ||||
| Definition |
Whether
this
|
||||
| Short Display | Whether this practitioner role record is in active use | ||||
| Cardinality | 0..1 | ||||
| Type | boolean | ||||
|
|
|
||||
| Requirements |
Need
to
be
able
to
mark
a
practitioner
role
record
as
not
to
be
used
because
it
was
created
in
|
||||
| Summary | true | ||||
| Comments |
|
||||
| PractitionerRole.period | |||||
|
| PractitionerRole.period | ||||
| Definition |
The period during which the person is authorized to act as a practitioner in these role(s) for the organization. |
||||
| Short Display | The period during which the practitioner is authorized to perform in these role(s) | ||||
|
|
0..1 | ||||
| Type | Period | ||||
| Requirements |
Even after the agencies is revoked, the fact that it existed must still be recorded. |
||||
| Summary | true | ||||
| Comments | If a practitioner is performing a role within an organization over multiple, non-adjacent periods, there should be a distinct PractitionerRole instance for each period. For example, if a nurse is employed at a hospital, leaves the organization for a period of time due to pandemic related stress, but returns post-pandemic to the same job role, there would be two PractitionerRole instances for the different periods of employment. | ||||
| PractitionerRole.practitioner | |||||
|
| PractitionerRole.practitioner | ||||
| Definition |
Practitioner
that
is
able
to
provide
the
defined
services
for
the
|
||||
| Short Display | Practitioner that provides services for the organization | ||||
|
|
0..1 | ||||
| Type | Reference ( Practitioner ) | ||||
| Summary | true | ||||
| PractitionerRole.organization | |||||
|
|
PractitionerRole.organization | ||||
| Definition |
The
organization
where
|
||||
| Short Display | Organization where the role is available | ||||
| Cardinality | 0..1 | ||||
| Type | Reference ( Organization ) | ||||
| Summary | true | ||||
| Comments | Some relationships (represented as PractitionerRoles) that may exist between practitioners and organizations include:
Each of the examples above above, would be represented as different PractitionerRole instances, each with a different values for PractitionerRole.organization. | ||||
| PractitionerRole.network | |||||
| Element Id | PractitionerRole.network | ||||
| Definition | The network in which the PractitionerRole provides the role's services (if defined) at the indicated locations (if defined). | ||||
| Short Display | The network in which the PractitionerRole provides the role's services (if defined) at the indicated locations (if defined) | ||||
| Cardinality | 0..* | ||||
| Type | Reference ( Organization ) | ||||
| Summary | true | ||||
| Comments | e.g. Commonly used for Health Insurance provider networks. | ||||
| PractitionerRole.code | |||||
|
| PractitionerRole.code | ||||
| Definition |
Roles which this practitioner is authorized to perform for the organization. |
||||
| Short Display | Roles which this practitioner may perform | ||||
|
|
0..* | ||||
| Terminology Binding |
|
||||
| Type | CodeableConcept | ||||
| Requirements |
Need to know what authority the practitioner has - what can they do? |
||||
| Summary | true | ||||
| Comments |
A
person
may
have
more
than
one
role.
|
||||
| PractitionerRole.display | |||||
| Element Id | PractitionerRole.display | ||||
| Definition |
A
value
that
describes
the
intersection
of
the
practitioner,
organization,
and
the
role
of
the
practitioner
within
the
organization.
This
is
|
||||
| Short Display | Denormalized practitioner name, role, organization and location | ||||
| Cardinality | 0..1 | ||||
| Type | string | ||||
| Summary | true | ||||
| Comments | The PractitionerRole display value may be considered a de-normalized value from Practitioner and/or Organization for the purposes of convenient display in both the PractitionerRole resources and reference to it. When a system is consuming a PractitionerRole resource and displaying a name to a user, they may choose to use PractitionerRole.display, or they could use one or both of the names from the referenced Practitioner and/or Organization resources along with the role or other relevant properties in PractitionerRole. | ||||
| PractitionerRole.specialty | |||||
|
| PractitionerRole.specialty | ||||
| Definition |
|
||||
| Short Display | Specific specialty of the practitioner | ||||
| Cardinality | 0..* | ||||
| Terminology Binding |
Practice
Setting
Code
Value
Set
(
|
||||
| Type | CodeableConcept | ||||
| Summary | true | ||||
| Comments | The specialty represents the functional role a practitioner is playing within an organization/location. This role may require the individual have certain qualifications, which would be represented in the Practitioner.qualifications property. Note that qualifications may or might not relate to or be required by the practicing specialty. | ||||
| PractitionerRole.location | |||||
|
| PractitionerRole.location | ||||
| Definition |
The location(s) at which this practitioner provides care. |
||||
| Short Display | Location(s) where the practitioner provides care | ||||
|
|
0..* | ||||
| Type | Reference ( Location ) | ||||
| Summary | true | ||||
| PractitionerRole.healthcareService | |||||
|
| PractitionerRole.healthcareService | ||||
| Definition |
The list of healthcare services that this worker provides for this role's Organization/Location(s). |
||||
| Short Display | Healthcare services provided for this role's Organization/Location(s) | ||||
| Cardinality | 0..* | ||||
| Type | Reference ( HealthcareService ) | ||||
| Summary | false | ||||
|
|
|||||
|
| PractitionerRole.contact | ||||
| Definition |
|
||||
| Short Display | Official contact details relating to this PractitionerRole | ||||
| Cardinality | 0..* | ||||
| Type |
|
||||
| Requirements |
Often practitioners have a dedicated line for each location (or service) that they work at, and need to be able to define separate contact details for each of these. Sometimes these also include a named person/organization that handles contact for specific purposes, such as a receptionist, or accounts clerk etc. |
||||
| Summary |
|
||||
|
|
|||||
|
|
|
||||
|
|
|
||||
|
|
|
||||
|
|
0..* | ||||
| Terminology Binding |
|
||||
| Type |
|
||||
|
Summary
|
false | ||||
|
|
|
||||
|
|
|||||
| Element Id | PractitionerRole.communication | ||||
| Definition |
A
language
the
practitioner
can
use
in
patient
communication.
The
|
||||
|
|
|
||||
|
|
|
||||
|
|
All
Languages
(
Required
)
|
||||
| Type |
|
||||
|
|
|
||||
|
Summary
|
false | ||||
|
|
The
Note that for non-patient oriented communication, see Practitioner.communication. Note that all 'person' type resources (Person, RelatedPerson, Patient, Practitioner) have a communication structure that includes preferences. Role or service oriented resources such as HealthcareService and PractitionerRole only include languages that are available for interacting with patients. |
||||
|
|
|||||
|
|
|
||||
| Definition |
A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. |
||||
|
|
|
||||
|
|
0..1 | ||||
| Type |
|
||||
|
Summary
|
false | ||||
|
|
Systems
may
choose
to
The
NotAvailableTime(s)
included
indicate
the
general
days/periods
where
the
practitioner
is
not
available
|
||||
|
|
|||||
| Element Id | PractitionerRole.endpoint | ||||
| Definition |
Technical endpoints providing access to services operated for the practitioner with this role. Commonly used for locating scheduling services, or identifying where to send referrals electronically. |
||||
| Short Display | Endpoints for interacting with the practitioner in this role | ||||
| Cardinality | 0..* | ||||
| Type | Reference ( Endpoint ) | ||||
| Requirements |
Organizations
have
multiple
systems
that
provide
various
services
and
So the endpoint satisfies the need to be able to define the technical connection details for how to connect to them, and for what purpose. |
||||
| Summary | false | ||||