This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v5.0.0:
R5
-
STU
).
This
is
the
current
published
version
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
| Responsible Owner: FHIR Infrastructure Work Group | Standards Status : Trial Use |
| Formal URI | http://hl7.org/fhir/compartment/Practitioner |
| Description | The set of resources associated with a particular practitioner |
| Identity | There is an instance of the practitioner compartment for each Practitioner resource, and the identity of the compartment is the same as the Practitioner |
| Membership | The practitioner compartment includes any resources where the resource is explicitly linked to a Practitioner (usually as author, but other kinds of linkage exist) |
| Formal Definition | CompartmentDefinition resource: XML or JSON |
The
following
resources
may
be
are
in
this
compartment:
| Resource | Inclusion Criteria | Start Date Parameter | End Date Parameter Criteria |
| Account | subject | period | period |
| AdverseEvent | recorder | occurrence | occurrence |
| AllergyIntolerance |
| date | date |
| Appointment | actor | date | date |
| AppointmentResponse | actor | ||
| AuditEvent | agent | date | date |
| Basic | author | created | created |
|
|
| ||
| CareTeam | participant |
|
|
| Claim | enterer or provider or payee or care-team | created | created |
| ClaimResponse | requestor | created | created |
|
|
performer | date | date |
| Communication | sender or recipient | sent | sent |
| CommunicationRequest | information-provider or recipient or requester | authored | authored |
| Composition | subject or author or attester | date | date |
| Condition |
| ||
| CoverageEligibilityRequest | enterer or provider | created | created |
| CoverageEligibilityResponse | requestor | created | created |
| DetectedIssue | author | identified | identified |
| DeviceAlert | acknowledged-by | occurrence | occurrence |
| DeviceAssociation |
| date | date |
| DeviceRequest | requester or performer | event-date | event-date |
| DiagnosticReport | performer | date | date |
| DocumentReference | subject or author or attester | date | date |
| Encounter | practitioner or participant | date-start | date-start |
| EpisodeOfCare | care-manager | date | date |
| ExplanationOfBenefit | enterer or provider or payee or care-team | created | created |
| Flag | author | date | date |
| Group | member | ||
| Immunization | performer | date | date |
| Invoice | participant | date | date |
| Linkage | author | ||
| List | source | date | date |
| MedicationDispense | performer or receiver | whenhandedover | whenhandedover |
| MedicationRequest | requester | combo-date | combo-date |
| MedicationStatement | source | effective | effective |
| MessageHeader |
receiver
|
||
| NutritionIntake | source | date | date |
| NutritionOrder |
| datetime | datetime |
| Observation | performer | date | date |
| Patient | general-practitioner | ||
| PaymentNotice | reporter | created | created |
| PaymentReconciliation | requestor | created | created |
| Person | practitioner | ||
| Practitioner | [base] | ||
| PractitionerRole | practitioner | date | date |
| Procedure | performer | date | date |
| Provenance | agent | when | when |
| QuestionnaireResponse | author or source | answer-date | answer-date |
| RequestOrchestration | participant or author | ||
| RiskAssessment | performer | date | date |
| Schedule | actor | date | date |
| ServiceRequest | performer or requester |
|
|
|
|
|
|
|
| VisionPrescription | prescriber | datewritten | datewritten |
A resource is in this compartment if the nominated search parameter (or chain) refers to the compartmentdefinition-practitioner resource that defines the compartment.
All resources not explicitly listed above are not defined as part of the compartment because they do not have a relevant element, or an appropriate specified search parameter. Some non-listed resources may still be relevant for certain compartment uses, such as access control - e.g. Binary.