Skip to main content
FHIR R4 Condition · US Core Condition (Problems and Health Concerns) · US Core Condition (Encounter Diagnosis)
Condition is used for two distinct purposes in the Patient Everything and Patient Summary bundles — the patient’s problem list, and the diagnosis attached to a specific encounter. Each uses a different US Core profile and is documented separately below. It is not produced for Bulk Medication History.

​
Usage 1: Problem list

Problem list Condition resources are top-level entries in the bundle.

​
Stable ID

The id is derived from the patient, the recorded date, the primary diagnosis code, the rate code, and whether the problem is active. The “primary” diagnosis code is chosen by preferring an ICD-10 code where one is available among the problem’s codes, and otherwise falling back to the source’s own primary code.
Only the primary code participates in the id — the additional translated codings described below do not. A problem is therefore assigned the same id regardless of how many translated codes accompany it, so gaining or losing a translation never changes a Condition’s identity.

​
Fields

verificationStatus, onset[x], abatement[x], and severity are not populated for problem list entries.

​
Usage 2: Encounter diagnosis

Each Encounter carries its diagnosis as a Condition contained inside the Encounter and referenced from Encounter.diagnosis.condition.

​
Stable ID

No id is assigned. The resource exists only inside its parent Encounter, so it is neither addressable on its own nor deduplicated. Use the parent Encounter’s id to track it over time.

​
Fields

recordedDate, recorder, onset[x], and encounter are not populated on the encounter diagnosis — the link to the encounter is expressed by containment and by Encounter.diagnosis.condition instead.