This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Detailed Descriptions for the elements in the Practitioner resource.
Practitioner | |
Definition | A person who is directly or indirectly involved in the provisioning of healthcare. |
Control | 1..1 |
Requirements | Need to track doctors, staff, locums etc. for both healthcare practitioners, funders, etc. |
Comments | Note that a cab driver no longer fits the bill. You probably would be interested in the organization rather than the individual? |
Practitioner.identifier | |
Definition | An identifier that applies to this person in this role. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Often, specific identities are assigned for the agent. |
Summary | true |
Practitioner.active | |
Definition | Whether this practitioner's record is in active use. |
Control | 0..1 |
Type | boolean |
Default Value | true |
Requirements | Need to be able to mark a practitioner record as not to be used because it was created in error. |
Summary | true |
Comments | Default is true. If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role. |
Practitioner.name | |
Definition | The name(s) associated with the practitioner. |
Control | 0..* |
Type | HumanName |
Requirements | The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display. |
Summary | true |
Comments | The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate. In general select the value to be used in the ResourceReference.display based on this:
|
Practitioner.telecom | |
Definition | A contact detail for the practitioner, e.g. a telephone number or an email address. |
Control | 0..* |
Type | ContactPoint |
Requirements | Need to know how to reach a practitioner independent to any roles the practitioner may have. |
Summary | true |
Comments | Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification These typically will have home numbers, or mobile numbers that are not role specific. |
Practitioner.address | |
Definition | Address(es) of the practitioner that are not role specific (typically home address). Work addresses are not typically entered in this property as they are usually role dependent. |
Control | 0..* |
Type | Address |
Requirements | The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations. |
Summary | true |
Comments | The PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address). |
Practitioner.gender | |
Definition | Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes. |
Control | 0..1 |
Terminology Binding | AdministrativeGender (Required) |
Type | code |
Requirements | Needed to address the person correctly. |
Summary | true |
Practitioner.birthDate | |
Definition | The date of birth for the practitioner. |
Control | 0..1 |
Type | date |
Requirements | Needed for identification. |
Summary | true |
Practitioner.photo | |
Definition | Image of the person. |
Control | 0..* |
Type | Attachment |
Requirements | Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too. |
Practitioner.role | |
Definition | The list of roles/organizations that the practitioner is associated with. |
Control | 0..* |
Comments | The address to be used for this PractitionerRole is in the referenced location (removing duplication across all the services provided at the location). |
Practitioner.role.organization | |
Definition | The organization where the Practitioner performs the roles associated. |
Control | 0..1 |
Type | Reference(Organization) |
Practitioner.role.code | |
Definition | Roles which this practitioner is authorized to perform for the organization. |
Control | 0..1 |
Terminology Binding | PractitionerRole (Example) |
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. At least one role is required. |
Practitioner.role.specialty | |
Definition | Specific specialty of the practitioner. |
Control | 0..* |
Terminology Binding | PractitionerSpecialty (Example) |
Type | CodeableConcept |
Summary | true |
Practitioner.role.identifier | |
Definition | Business Identifiers that are specific to a role/location. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Some business identifiers are specific to a location and should be able to be associated. |
Summary | true |
Practitioner.role.telecom | |
Definition | Contact details that are specific to the role/location/service. |
Control | 0..* |
Type | ContactPoint |
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. |
Summary | true |
Practitioner.role.period | |
Definition | The period during which the person is authorized to act as a practitioner in these role(s) for the organization. |
Control | 0..1 |
Type | Period |
Requirements | Even after the agencies is revoked, the fact that it existed must still be recorded. |
Summary | true |
Practitioner.role.location | |
Definition | The location(s) at which this practitioner provides care. |
Control | 0..* |
Type | Reference(Location) |
Practitioner.role.healthcareService | |
Definition | The list of healthcare services that this worker provides for this role's Organization/Location(s). |
Control | 0..* |
Type | Reference(HealthcareService) |
Practitioner.role.endpoint | |
Definition | Technical endpoints providing access to services operated for the PractitonerRole. |
Control | 0..* |
Type | Reference(Endpoint) |
Practitioner.qualification | |
Definition | Qualifications obtained by training and certification. |
Control | 0..* |
Practitioner.qualification.identifier | |
Definition | An identifier that applies to this person's qualification in this role. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Often, specific identities are assigned for the qualification. |
Practitioner.qualification.code | |
Definition | Coded representation of the qualification. |
Control | 1..1 |
Terminology Binding | ANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2 (Example) |
Type | CodeableConcept |
Practitioner.qualification.period | |
Definition | Period during which the qualification is valid. |
Control | 0..1 |
Type | Period |
Requirements | Qualifications are often for a limited period of time, and can be revoked. |
Practitioner.qualification.issuer | |
Definition | Organization that regulates and issues the qualification. |
Control | 0..1 |
Type | Reference(Organization) |
Practitioner.communication | |
Definition | A language the practitioner is able to use in patient communication. |
Control | 0..* |
Terminology Binding | Common Languages (Extensible but limited to ??) |
Type | CodeableConcept |
Requirements | Knowing which language a practitioner speaks can help in facilitating communication with patients. |
Comments | The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type. |