Practitioner
A person who is directly or indirectly involved in the provisioning of healthcare.
- Schema
- Usage
- Relationships
- Background and Context
- Referenced By
Properties
Name | Required | Type | Description |
---|---|---|---|
identifier | Identifier[] | An identifier for the person as this agent DetailsAn identifier that applies to this person in this role. | |
active | boolean | Whether this practitioner's record is in active use DetailsWhether this practitioner's record is in active use. 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. | |
name | HumanName[] | The name(s) associated with the practitioner DetailsThe name(s) associated with the practitioner. 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: 1. There is more than 1 name 2. Use = usual 3. Period is current to the date of the usage 4. Use = official 5. Other order as decided by internal business rules. | |
telecom | ContactPoint[] | A contact detail for the practitioner (that apply to all roles) DetailsA contact detail for the practitioner, e.g. a telephone number or an email address. 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 to help with identification. These typically will have home numbers, or mobile numbers that are not role specific. | |
address | Address[] | Address(es) of the practitioner that are not role specific (typically home address) DetailsAddress(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. 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). | |
gender | code | male | female | other | unknown DetailsAdministrative Gender - the gender that the person is considered to have for administration and record keeping purposes. | |
birthDate | date | The date on which the practitioner was born DetailsThe date of birth for the practitioner. | |
photo | Attachment[] | Image of the person DetailsImage of the person. | |
qualification | PractitionerQualification[] | Certification, licenses, or training pertaining to the provision of care DetailsThe official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality. | |
id | string | Unique id for inter-element referencing DetailsUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
extension | Extension[] | Additional content defined by implementations DetailsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
modifierExtension | Extension[] | Extensions that cannot be ignored even if unrecognized DetailsMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
identifier | Identifier[] | An identifier for this qualification for the practitioner DetailsAn identifier that applies to this person's qualification in this role. | |
code | ✓ | CodeableConcept | Coded representation of the qualification DetailsCoded representation of the qualification. |
period | Period | Period during which the qualification is valid DetailsPeriod during which the qualification is valid. | |
issuer | Reference<Organization> | Organization that regulates and issues the qualification DetailsOrganization that regulates and issues the qualification. | |
communication | CodeableConcept[] | A language the practitioner can use in patient communication DetailsA language the practitioner can use in patient communication. The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type. |
Search Parameters
Name | Type | Description | Expression |
---|---|---|---|
address | string | A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text | Practitioner.address |
address-city | string | A city specified in an address | Practitioner.address.city |
address-country | string | A country specified in an address | Practitioner.address.country |
address-postalcode | string | A postalCode specified in an address | Practitioner.address.postalCode |
address-state | string | A state specified in an address | Practitioner.address.state |
address-use | token | A use code specified in an address | Practitioner.address.use |
token | A value in an email contact | Practitioner.telecom.where(system = 'email') | |
family | string | A portion of the family name | Practitioner.name.family |
gender | token | Gender of the practitioner | Practitioner.gender |
given | string | A portion of the given name | Practitioner.name.given |
phone | token | A value in a phone contact | Practitioner.telecom.where(system = 'phone') |
phonetic | string | A portion of either family or given name using some kind of phonetic matching algorithm | Practitioner.name |
telecom | token | The value in any kind of contact | Practitioner.telecom |
active | token | Whether the practitioner record is active | Practitioner.active |
communication | token | One of the languages that the practitioner can communicate with | Practitioner.communication |
identifier | token | A practitioner's Identifier | Practitioner.identifier |
name | string | A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text | Practitioner.name |
Inherited Properties
Name | Required | Type | Description |
---|---|---|---|
id | string | Logical id of this artifact DetailsThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | |
meta | Meta | Metadata about the resource DetailsThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |
implicitRules | uri | A set of rules under which this content was created DetailsA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. | |
language | code | Language of the resource content DetailsThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | |
text | Narrative | Text summary of the resource, for human interpretation DetailsA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | |
contained | Resource[] | Contained, inline Resources DetailsThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. | |
extension | Extension[] | Additional content defined by implementations DetailsMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | |
modifierExtension | Extension[] | Extensions that cannot be ignored DetailsMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Practitioner covers all individuals who are engaged in the healthcare process and healthcare-related services as part of their formal responsibilities and this Resource is used for attribution of activities and responsibilities to these individuals. Practitioners include (but are not limited to):
- physicians, dentists, pharmacists
- physician assistants, nurses, scribes
- midwives, dietitians, therapists, optometrists, paramedics
- medical technicians, laboratory scientists, prosthetic technicians, radiographers
- social workers, professional homecare providers, official volunteers
- receptionists handling patient registration
- IT personnel merging or unmerging patient records
- Service animal (e.g., ward assigned dog capable of detecting cancer in patients)
The Resource SHALL NOT be used for persons involved without a formal responsibility like individuals taking care for friends, relatives or neighbors. These can be registered as a Patient's Contact. If performing some action or being referenced by another resource, use the RelatedPerson resource.
The primary distinction between a Practitioner and a RelatedPerson is based on whether:
- The person/animal operates on behalf of the care delivery organization over multiple patients (Practitioner) or,
- Where the person/animal is not associated with the organization, and instead is allocated tasks specifically for the RelatedPerson's Patient (RelatedPerson).
A standard extension animalSpecies can be used to indicate the species of a service animal.
The PractitionerRole resource provides the details of roles that the practitioner is approved to perform for which organizations (and at which locations, and optionally what services too).
Practitioners are also often grouped into CareTeams independently of roles, where the CareTeam defines what specific role that they are fulfilling within the team, and might or might not have actual practitioner role resources created for the practitioner (and in the care team context, the organization the practitioner is representing)
Practitioner performs different roles within the same or even different organizations. Depending on jurisdiction and custom, it may be necessary to maintain a specific Practitioner Resource for each such role or have a single Practitioner with multiple roles. The role can be limited to a specific period, after which authorization for this role ends. Note that the represented organization need not necessarily be the (direct) employer of a Practitioner.
- Annotation
- Signature
- Account
- AdverseEvent
- AllergyIntolerance
- Appointment
- AppointmentResponse
- AuditEvent
- Basic
- BiologicallyDerivedProduct
- CarePlan
- CareTeam
- CatalogEntry
- ChargeItem
- Claim
- ClaimResponse
- ClinicalImpression
- Communication
- CommunicationRequest
- Composition
- Condition
- Consent
- Contract
- CoverageEligibilityRequest
- CoverageEligibilityResponse
- DetectedIssue
- DeviceRequest
- DeviceUseStatement
- DiagnosticReport
- DocumentManifest
- DocumentReference
- Encounter
- EnrollmentRequest
- EnrollmentResponse
- EpisodeOfCare
- ExplanationOfBenefit
- Flag
- Goal
- Group
- ImagingStudy
- Immunization
- Invoice
- Linkage
- List
- MeasureReport
- Media
- MedicationAdministration
- MedicationDispense
- MedicationRequest
- MedicationStatement
- MessageHeader
- NutritionOrder
- Observation
- Patient
- PaymentNotice
- PaymentReconciliation
- Person
- PractitionerRole
- Procedure
- Provenance
- QuestionnaireResponse
- RequestGroup
- ResearchStudy
- RiskAssessment
- Schedule
- ServiceRequest
- Specimen
- SupplyDelivery
- SupplyRequest
- Task
- VerificationResult
- VisionPrescription