This page is part of the FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Publish-box (todo)

Compartment Patient

FHIR Infrastructure Work Group

Maturity Level : N/A

Standards Status : Trial Use

Formal URI	http://hl7.org/fhir/compartment/Patient
Description	The set of resources associated with a particular patient
Identity	There is an instance of the patient compartment for each patient resource, and the identity of the compartment is the same as the patient. When a patient is linked to another patient resource, the records associated with the linked patient resource will not be returned as part of the compartment search. Those records will be returned only with another compartment search using the "id" for the linked patient resource. In cases where two patients have been merged rather than linked, associated resources should be moved to the target patient as part of the merge process, so the patient compartment for the target patient would include all relevant data, and the patient compartment for the source patient would include only the linked Patient and possibly remnant resources like AuditEvent.
Membership	The patient compartment includes any resources where the subject of the resource is the patient, and some other resources that are directly linked to resources in the patient compartment
Formal Definition	CompartmentDefinition resource: XML or JSON

Resource based membership rules.

The following resources may be in this compartment:

Resource	Inclusion Criteria
Account	subject
AdverseEvent	subject
AllergyIntolerance	patient or participant asserter
Appointment	actor
AppointmentResponse	actor
AuditEvent	patient
Basic	patient or author
BiologicallyDerivedProductDispense	patient
BodyStructure	patient
CarePlan	patient
CareTeam	patient or participant
ChargeItem	subject
Claim	patient or payee
ClaimResponse	patient
ClinicalImpression ClinicalAssessment	subject
Communication	subject or sender or recipient
CommunicationRequest	subject or information-provider or recipient or requester
Composition	subject or author or attester
Condition	patient or participant-actor asserter
Consent	subject
Contract	patient
Coverage	policy-holder or subscriber or beneficiary or paymentby-party
CoverageEligibilityRequest	patient
CoverageEligibilityResponse	patient
DetectedIssue	patient
DeviceAlert	subject
DeviceAssociation	subject or operator
DeviceRequest	subject or performer
DeviceUsage	patient
DiagnosticReport	subject
DocumentReference	subject or author
Encounter	patient
EncounterHistory	patient
EnrollmentRequest	subject
EpisodeOfCare	patient subject
ExplanationOfBenefit	patient or payee
FamilyMemberHistory	patient
Flag	patient
GenomicStudy	patient
Goal	patient
Group	member
GuidanceResponse	patient
ImagingSelection	patient
ImagingStudy	patient
Immunization	patient
ImmunizationEvaluation	patient
ImmunizationRecommendation	patient
Invoice	subject or patient or recipient
List	subject or source
MeasureReport	patient
MedicationAdministration	patient or subject
MedicationDispense	subject or patient or receiver
MedicationRequest	subject
MedicationStatement	subject
MolecularSequence subject NutritionIntake	subject or source
NutritionOrder	patient
Observation	subject or performer
Patient	[base] or link
Person	patient
PersonalRelationship	source or target
Procedure	patient or performer
Provenance	patient
QuestionnaireResponse	subject or author
RelatedPerson	patient
RequestOrchestration	subject or participant
ResearchSubject	subject
RiskAssessment	subject
Schedule	actor
ServiceRequest	subject or performer
Specimen	subject
SupplyDelivery	patient
SupplyRequest	subject
Task	patient or focus
VisionPrescription	patient

A resource is in this compartment if the nominated search parameter (or chain) refers to the compartmentdefinition-patient 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.

See information about compartments .