A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.

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.

Business Identifiers that are specific to a role/location.

Often, specific identities are assigned for the agent.

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.

Whether this practitioner role record is in active use. Some systems may use this property to mark non-active practitioners, such as those that are not currently employed.

Need to be able to mark a practitioner role record as not to be used because it was created in error, or otherwise no longer in active use.

If this value is false, you may refer to the period to see when the role was in active use. If there is no period specified, no inference can be made about when it was active.

The period during which the person is authorized to act as a practitioner in these role(s) for the organization.

Even after the agencies is revoked, the fact that it existed must still be recorded.

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.

Practitioner that is able to provide the defined services for the organization.

The organization where the Practitioner performs the roles associated.

Roles which this practitioner is authorized to perform for the organization.

Need to know what authority the practitioner has - what can they do?

A person may have more than one role.

Specific The specialty of a practitioner that describes the practitioner. functional role they are practicing at a given organization or location.

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.

The location(s) at which this practitioner provides care.

The list of healthcare services that this worker provides for this role's Organization/Location(s).

Contact The contact details that are specific of communication devices available relevant to the role/location/service. specific PractitionerRole. This can include addresses, phone numbers, fax numbers, mobile numbers, email addresses and web sites.

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.

A collection Collection of times the practitioner is available or performing this role at the location and/or healthcareservice. Cardinality 0..* Summary false Comments More detailed availability information may be provided in associated Schedule/Slot resources. characteristics (attributes).

Is These could be such things as is the service mode used by this always available? (hence times are irrelevant) e.g. 24 hour service. role.

A language the practitioner can use in patient communication. The opening time of day. Note: If practitioner may know several languages (listed in practitioner.communication), however these are the AllDay flag is set, then this time is ignored. languages that could be advertised in a directory for a patient to search.

Knowing which language a practitioner speaks can help in facilitating patients to locate practitioners that speak their language.

The timezone structure aa-BB with this exact casing is expected to be one the most widely used notations for where locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.

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 is provided at. and PractitionerRole only include languages that are available for interacting with patients.

The A collection of times the practitioner is not available or performing this role during this period of time due to at the provided reason. location and/or healthcareservice.

A description of site More detailed availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions information may be provided in associated Schedule/Slot resources.

Systems may choose to normal site render availability as details in differently than it is exchanged on the available Times interface. For example, rather than "Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm" as would be implied by two availableTime repetitions, an application could render this information as "Mon-Fri 9-12am and 1-5pm".

The NotAvailableTime(s) included indicate the general days/periods where the practitioner is not available Times. (for things such as vacation time, or public holidays).

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.

Organizations have multiple systems that provide various services and ,ay may also be different for practitioners too.

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.