DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . For a full list of available versions, see the Directory of published versions . Page versions: . Page versions: R5 R4B R4 R3 R2

4.3.6 9.2.6 Resource Condition - Detailed Descriptions Resource Condition - Detailed Descriptions Detailed Descriptions for the elements in the Condition resource.

Detailed Descriptions for the elements in the Condition resource.

Type Summary © HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:43+1100. Links: Search | Version History | Table of Contents | Compare to DSTU1
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. 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
Summary true
To Do 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. * 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 processes 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). This records identifiers associated with this condition that are defined by business processes 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 This is a business identifer, not a resource identifier (see discussion )
Control 0..*
Type Identifier
Requirements

Need to allow connection to a wider workflow. Need to allow connection to a wider workflow.

Summary true
Condition.patient Condition.clinicalStatus
Definition

Indicates the patient who the condition record is associated with. The clinical status of the condition.

Control 1..1 0..1
Binding Condition Clinical Status Codes: The clinical status of the condition or diagnosis. ( Required )
Type Reference code ( Patient
Is Modifier ) true
Summary true
Condition.encounter Condition.verificationStatus
Definition

Encounter during which the condition was first asserted. The verification status to support the clinical status of the condition.

Control 0..1 1..1
Binding ConditionVerificationStatus: The verification status to support or decline the clinical status of the condition or diagnosis. ( Required )
Type Reference ( Encounter code )
Summary Is Modifier true
Comments Summary This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known". true
Condition.asserter Condition.category
Definition

Individual who is making the condition statement. A category assigned to the condition.

Control 0..1
Binding Condition Category Codes: A category assigned to the condition. ( Preferred )
Type Reference ( Practitioner | Patient CodeableConcept )
Summary true
Comments

The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.

Condition.dateRecorded Condition.severity
Definition

A date, when the Condition statement was documented. A subjective assessment of the severity of the condition as evaluated by the clinician.

Control 0..1
Binding Condition/Diagnosis Severity: A subjective assessment of the severity of the condition as evaluated by the clinician. ( Preferred )
Type date CodeableConcept
Summary true
Comments

The Date Recorded represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified.  The date of the last record modification can be retrieved from the resource metadata. Coding of the severity with a terminology is preferred, where possible.

Condition.code
Definition

Identification of the condition, problem or diagnosis. Identification of the condition, problem or diagnosis.

Control 1..1
Binding Condition/Problem/Diagnosis Codes: Identification of the condition or diagnosis. ( Condition/Problem/Diagnosis Codes: Identification of the condition or diagnosis. ( Example )
Type CodeableConcept
Summary true
Condition.category Condition.bodySite
Definition

A category assigned to the condition. The anatomical location where this condition manifests itself.

Control 0..1 0..*
Binding Condition Category Codes: A category assigned to the condition. ( Preferred SNOMED CT Body Structures: Codes describing anatomical locations. May include laterality. ( Example )
Type CodeableConcept
Summary true
Comments

The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. May be a summary code, or a reference to a very precise definition of the location, or both.

Condition.clinicalStatus Condition.subject
Definition

The clinical status of the condition. Indicates the patient or group who the condition record is associated with.

Control 0..1 1..1
Binding Type Condition Clinical Status Codes: The clinical status of the condition or diagnosis. Reference ( Preferred Patient | Group )
code Requirements Is Modifier true

Group is typically used for veterinary or public health use cases.

Summary true
Condition.verificationStatus Condition.context
Definition

The verification status to support the clinical status of the condition. Encounter during which the condition was first asserted.

Control 1..1 Binding ConditionVerificationStatus: The verification status to support or decline the clinical status of the condition or diagnosis. ( Required ) 0..1
Type code Reference ( Encounter | EpisodeOfCare )
Is Modifier Summary true
Summary Comments true

This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".

Condition.severity Condition.onset[x]
Definition

A subjective assessment of the severity of the condition as evaluated by the clinician. Estimated or actual date or date-time the condition began, in the opinion of the clinician.

Control 0..1
Binding Type Condition/Diagnosis Severity: A subjective assessment of the severity of the condition as evaluated by the clinician. dateTime ( Preferred | Age ) | Period | Range | string
Type [x] Note CodeableConcept See Choice of Data Types for further information about how to use [x]
Summary true
Comments

Coding of the severity with a terminology is preferred, where possible. Age is generally used when the patient reports an age at which the Condition began to occur.

Condition.onset[x] Condition.abatement[x]
Definition

Estimated or actual date or date-time the condition began, in the opinion of the clinician. 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 dateTime | Age | boolean | Period | Range | string
[x] Note [x] Note See Choice of Data Types for further information about how to use [x] See Choice of Data Types for further information about how to use [x]
Summary true
Comments

Age is generally used when the patient reports an age at which the Condition began to occur. 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.abatement[x] Condition.dateRecorded
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. A date, when the Condition statement was documented.

Control 0..1
Type dateTime | Age | boolean | Period | Range date | string
Summary true
[x] Note Comments See Choice of Data Types for further information about how to use [x]

The Date Recorded represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified.  The date of the last record modification can be retrieved from the resource metadata.

Condition.asserter
Definition

Individual who is making the condition statement.

Control true 0..1
Comments Type 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. Reference ( Practitioner | Patient )
Summary true
Condition.stage
Definition

Clinical stage or grade of a condition. May include formal severity assessments. Clinical stage or grade of a condition. May include formal severity assessments.

Control 0..1
Summary true
Invariants Defined on this element Defined on this element
con-1 : Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) : Stage SHALL have summary or assessment ( expression : summary.exists() or assessment.exists(), 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. A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.

Control 0..1
Binding Condition Stage: Codes describing condition stages (e.g. Cancer stages). ( Condition Stage: Codes describing condition stages (e.g. Cancer stages). ( Example )
Type CodeableConcept
Summary true
Invariants Affect this element Affect this element
con-1 : Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) : Stage SHALL have summary or assessment ( expression : summary.exists() or assessment.exists(), 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. Reference to a formal record of the evidence on which the staging assessment is based.

Control 0..*
Type Reference ( ClinicalImpression | | DiagnosticReport | | Observation )
Summary true
Invariants Affect this element Affect this element
con-1 : Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment)) : Stage SHALL have summary or assessment ( expression : summary.exists() or assessment.exists(), xpath: exists(f:summary) or exists(f:assessment))
To Do To Do When an assessment resource / framework is developed, this will be changed from Any to something narrower. 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. Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed.

Control 0..*
Summary true
Comments

The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. 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 Defined on this element
con-2 : evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) : evidence SHALL have code or details ( expression : code.exists() or detail.exists(), xpath: exists(f:code) or exists(f:detail))
Condition.evidence.code
Definition

A manifestation or symptom that led to the recording of this condition. A manifestation or symptom that led to the recording of this condition.

Control 0..1
Binding Manifestation and Symptom Codes: Codes that describe the manifestation or symptoms of a condition. ( Manifestation and Symptom Codes: Codes that describe the manifestation or symptoms of a condition. ( Example )
Type CodeableConcept
Summary true
Invariants Affect this element Affect this element
con-2 : evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) : evidence SHALL have code or details ( expression : code.exists() or detail.exists(), xpath: exists(f:code) or exists(f:detail))
Condition.evidence.detail
Definition

Links to other relevant information, including pathology reports. Links to other relevant information, including pathology reports.

Control 0..*
Type Reference ( Any )
Summary true
Invariants Affect this element Affect this element
con-2 : evidence SHALL have code or details (xpath: exists(f:code) or exists(f:detail)) Condition.bodySite Definition The anatomical location where this condition manifests itself. Control 0..* Binding SNOMED CT Body Structures: Codes describing anatomical locations. May include laterality. ( Example ) Type CodeableConcept Summary true Comments : evidence SHALL have code or details ( expression May be a summary code, or a reference to a very precise definition of the location, or both. : code.exists() or detail.exists(), xpath: exists(f:code) or exists(f:detail))
Condition.notes Condition.note
Definition

Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.

Control 0..1 0..*
Type string Annotation
Summary true