This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). 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 Condition resource.
Condition | |
Definition | Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a Diagnosis during an Encounter; populating a problem List or a Summary Statement, such as a Discharge Summary. |
Control | 1..1 |
To Do | * Age is questionable, you might well need a range of Age or even (in practice) a text like "in their teens". => new ballot comment. * Todo: discuss the applicability of assessing stages * Change the description: it is circular. |
Condition.identifier | |
Definition | This records identifiers associated with this condition that are defined by business processed and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Need to allow connection to a wider workflow. |
Condition.patient | |
Definition | Indicates the patient who the condition record is associated with. |
Control | 1..1 |
Type | Reference(Patient) |
Condition.encounter | |
Definition | Encounter during which the condition was first asserted. |
Control | 0..1 |
Type | Reference(Encounter) |
Condition.asserter | |
Definition | Person who takes responsibility for asserting the existence of the condition as part of the electronic record. |
Control | 0..1 |
Type | Reference(Practitioner | Patient) |
Condition.dateAsserted | |
Definition | Estimated or actual date the condition/problem/diagnosis was first detected/suspected. |
Control | 0..1 |
Type | date |
Condition.code | |
Definition | Identification of the condition, problem or diagnosis. |
Control | 1..1 |
Binding | ConditionKind: Example: See http://hl7.org/fhir/vs/condition-code (Identification of the Condition or diagnosis.) |
Type | CodeableConcept |
Condition.category | |
Definition | A category assigned to the condition. E.g. complaint | symptom | finding | diagnosis. |
Control | 0..1 |
Binding | ConditionCategory: Required: See http://hl7.org/fhir/vs/condition-category (A category assigned to the condition. E.g. finding | Condition | diagnosis | concern | condition) |
Type | CodeableConcept |
Comments | The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. |
Condition.clinicalStatus | |
Definition | The clinical status of the condition. |
Control | 1..1 |
Binding | ConditionClinicalStatus: Required: http://hl7.org/fhir/condition-status (The clinical status of the Condition or diagnosis) |
Type | code |
Is Modifier | true |
Condition.severity | |
Definition | A subjective assessment of the severity of the condition as evaluated by the clinician. |
Control | 0..1 |
Binding | ConditionSeverity: Example: See http://hl7.org/fhir/vs/condition-severity (A subjective assessment of the severity of the condition as evaluated by the clinician.) |
Type | CodeableConcept |
Comments | Coding of the severity with a terminology is preferred, where possible. |
Condition.onset[x] | |
Definition | Estimated or actual date or date-time the condition began, in the opinion of the clinician. |
Control | 0..1 |
Type | dateTime|Age|Period|Range|string |
Comments | Age is generally used when the patient reports an age at which the Condition began to occur. |
Condition.abatement[x] | |
Definition | The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. |
Control | 0..1 |
Type | date|Age|boolean|Period|Range|string |
Comments | There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. |
Condition.stage | |
Definition | Clinical stage or grade of a condition. May include formal severity assessments. |
Control | 0..1 |
Invariants | Defined on this element con-1: Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) |
Condition.stage.summary | |
Definition | A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. |
Control | 0..1 |
Type | CodeableConcept |
Invariants | Affect this element con-1: Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) |
Condition.stage.assessment | |
Definition | Reference to a formal record of the evidence on which the staging assessment is based. |
Control | 0..* |
Type | Reference(ClinicalImpression | DiagnosticReport | Observation) |
Invariants | Affect this element con-1: Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) |
To Do | When an assessment resource / framework is developed, this will be changed from Any to something narrower. |
Condition.evidence | |
Definition | Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed. |
Control | 0..* |
Comments | The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. |
Invariants | Defined on this element con-2: evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) |
Condition.evidence.code | |
Definition | A manifestation or symptom that led to the recording of this condition. |
Control | 0..1 |
Binding | ManifestationOrSymptom: Example: See http://hl7.org/fhir/vs/manifestation-or-symptom (Codes that describe the manifestation or symptoms of a condition.) |
Type | CodeableConcept |
Invariants | Affect this element con-2: evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) |
Condition.evidence.detail | |
Definition | Links to other relevant information, including pathology reports. |
Control | 0..* |
Type | Reference(Any) |
Invariants | Affect this element con-2: evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) |
Condition.location | |
Definition | The anatomical location where this condition manifests itself. |
Control | 0..* |
Comments | May be a summary code, or a reference to a very precise definition of the location, or both. |
Condition.location.site[x] | |
Definition | Code that identifies the structural location. |
Control | 0..1 |
Binding | BodySite: Example: See http://hl7.org/fhir/vs/body-site (Codes describing anatomical locations. May include laterality) |
Type | CodeableConcept|Reference(BodySite) |
Comments | May include laterality. |
Condition.dueTo | |
Definition | Further conditions, problems, diagnoses, procedures or events or the substance that caused/triggered this Condition. |
Control | 0..* |
Comments | Although a condition may be caused by a substance, this is not intended to be used to record allergies/adverse reactions to substances. |
Invariants | Defined on this element con-4: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.dueTo.code | |
Definition | Code that identifies the target of this relationship. The code takes the place of a detailed instance target. |
Control | 0..1 |
Binding | ConditionCause: Example: See http://hl7.org/fhir/vs/condition-cause (Codes that describe causes of patient conditions. E.g. Surgical mishap, escalation of a previous condition, etc.) |
Type | CodeableConcept |
Invariants | Affect this element con-4: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.dueTo.target | |
Definition | Target of the relationship. |
Control | 0..1 |
Type | Reference(Condition | Procedure | MedicationAdministration | Immunization | MedicationStatement) |
Invariants | Affect this element con-4: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.occurredFollowing | |
Definition | Further conditions, problems, diagnoses, procedures or events or the substance that preceded this Condition. |
Control | 0..* |
Invariants | Defined on this element con-5: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.occurredFollowing.code | |
Definition | Code that identifies the target of this relationship. The code takes the place of a detailed instance target. |
Control | 0..1 |
Binding | ConditionPredecessor: Example: See http://hl7.org/fhir/vs/condition-predecessor (Codes that describe activities or observations that occurred prior to the condition) |
Type | CodeableConcept |
Invariants | Affect this element con-5: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.occurredFollowing.target | |
Definition | Target of the relationship. |
Control | 0..1 |
Type | Reference(Condition | Procedure | MedicationAdministration | Immunization | MedicationStatement) |
Invariants | Affect this element con-5: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target)) |
Condition.notes | |
Definition | Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. |
Control | 0..1 |
Type | string |