Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a Diagnosis diagnosis during an Encounter; encounter; populating a problem List list or a Summary Statement, summary statement, such as a Discharge Summary. discharge summary.

This records identifiers associated with this condition that are defined by business processed and/ or 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).

Need to allow connection to a wider workflow.

Indicates the patient who the condition record is associated with.

Encounter during which the condition was first asserted.

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".

Individual who takes responsibility for asserting the existence of is making the condition as part of the electronic record. statement.

A date, when the condition/problem/diagnosis Condition statement was first detected/suspected. documented.

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.

Identification of the condition, problem or diagnosis.

A category assigned to the condition. E.g. complaint | symptom | finding | diagnosis.

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

The clinical status of the condition.

The degree verification status to support the clinical status of confidence that this condition is correct. the condition.

A subjective assessment of the severity of the condition as evaluated by the clinician.

Coding of the severity with a terminology is preferred, where possible.

Estimated or actual date or date-time the condition began, in the opinion of the clinician.

Age is generally used when the patient reports an age at which the Condition began to occur.

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.

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.

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

A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.

Reference to a formal record of the evidence on which the staging assessment is based.

Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed.

The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.

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

Links to other relevant information, including pathology reports.

The type of relationship that anatomical location where this condition has to the related item. manifests itself.

May be a code summary code, or a target (xpath: exists(f:code) != exists(f:target)) reference to a very precise definition of the location, or both.

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