eHealth Infrastructure (v2020.1)

StructureDefinition: ehealth-condition - Detailed Descriptions

Definitions for the ehealth-condition Profile.

1. Condition
Definition

A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

Control0..*
InvariantsDefined on this element
con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error (: verificationStatus='entered-in-error' or clinicalStatus.exists())
con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission (: abatement.empty() or (abatement as boolean).not() or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive')
dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty())
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty())
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty())
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
2. Condition.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typeid
Comments

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

3. Condition.meta
Definition

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

Control0..1
TypeMeta
4. Condition.implicitRules
Definition

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Control0..1
Typeuri
Is Modifiertrue
Comments

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

5. Condition.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
Max Binding: All Languages
Typecode
Comments

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

6. Condition.text
Definition

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Control0..1 This element is affected by the following invariants: dom-1
TypeNarrative
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

7. Condition.contained
Definition

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

Control0..*
TypeResource
Alternate Namesinline resources, anonymous resources, contained resources
Comments

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

8. Condition.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

9. Condition.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

10. 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).

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

11. Condition.clinicalStatus
Definition

The clinical status of the condition.

Control0..1 This element is affected by the following invariants: con-3, con-4
BindingThe clinical status of the condition or diagnosis.
The codes SHALL be taken from Condition Clinical Status Codes
Typecode
Is Modifiertrue
Comments

This element is labeled as a modifier because the status contains codes that mark the condition as not currently valid or of concern.

12. Condition.verificationStatus
Definition

The verification status to support the clinical status of the condition.

Control0..1 This element is affected by the following invariants: con-3
BindingThe verification status to support or decline the clinical status of the condition or diagnosis.
The codes SHALL be taken from ConditionVerificationStatus
Typecode
Is Modifiertrue
Comments

verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.

This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.

Default Valueunknown
13. Condition.category
Definition

A category assigned to the condition.

Control0..*
BindingA category assigned to the condition.
For example codes, see Condition Category Codes
TypeCodeableConcept
Comments

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

14. Condition.severity
Definition

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

Control0..1
BindingA subjective assessment of the severity of the condition as evaluated by the clinician.
The codes SHOULD be taken from Condition/Diagnosis Severity
TypeCodeableConcept
Comments

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

15. Condition.code
Definition

Identification of the condition, problem or diagnosis.

Control1..1
BindingThe codes SHALL be taken from Conditions
TypeCodeableConcept
Requirements

0..1 to account for primarily narrative only resources.

Alternate Namestype
16. Condition.code.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
17. Condition.code.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

SlicingThis element introduces a set of slices on Condition.code.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
18. Condition.code.coding
Definition

A reference to a code defined by a terminology system.

Control0..*
BindingIdentification of the condition or diagnosis.
The codes SHALL be taken from Conditions
TypeCoding
Requirements

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

Comments

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

19. Condition.code.text
Definition

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Control0..1
Typestring
Requirements

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Comments

Very often the text is the same as a displayName of one of the codings.

20. Condition.bodySite
Definition

The anatomical location where this condition manifests itself.

Control0..*
BindingCodes describing anatomical locations. May include laterality.
For example codes, see SNOMED CT Body Structures
TypeCodeableConcept
Comments

Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both.

21. Condition.subject
Definition

Indicates the patient or group who the condition record is associated with.

Control1..1
TypeReference(ehealth-patient | Group)
Requirements

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

Alternate Namespatient
22. Condition.context
Definition

Encounter during which the condition was first asserted.

Control0..1
TypeReference(Encounter | ehealth-episodeofcare)
Alternate Namesencounter
Comments

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

23. Condition.onset[x]
Definition

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

Control0..1
TypeChoice of: dateTime, Age, Period, Range, string
[x] NoteSee Choice of Data Types for further information about how to use [x]
Comments

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

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

Control0..1 This element is affected by the following invariants: con-4
TypeChoice of: dateTime, Age, boolean, Period, Range, string
[x] NoteSee Choice of Data Types for further information about how to use [x]
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. When abatementString exists, it implies the condition is abated.

25. Condition.assertedDate
Definition

The date on which the existance of the Condition was first asserted or acknowledged.

Control0..1
TypedateTime
Comments

The assertedDate 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.

26. Condition.asserter
Definition

Individual who is making the condition statement.

Control0..1
TypeReference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)
27. Condition.stage
Definition

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

Control0..1
TypeBackboneElement
InvariantsDefined on this element
con-1: Stage SHALL have summary or assessment (: summary.exists() or assessment.exists())
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
28. Condition.stage.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
29. Condition.stage.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

30. Condition.stage.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

31. Condition.stage.summary
Definition

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

Control0..1 This element is affected by the following invariants: con-1
BindingCodes describing condition stages (e.g. Cancer stages).
For example codes, see Condition Stage
TypeCodeableConcept
32. Condition.stage.assessment
Definition

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

Control0..* This element is affected by the following invariants: con-1
TypeReference(ehealth-clinicalimpression | DiagnosticReport | ehealth-observation)
33. Condition.evidence
Definition

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

Control0..*
TypeBackboneElement
Comments

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

InvariantsDefined on this element
con-2: evidence SHALL have code or details (: code.exists() or detail.exists())
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
34. Condition.evidence.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
35. Condition.evidence.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

36. Condition.evidence.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

37. Condition.evidence.code
Definition

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

Control0..* This element is affected by the following invariants: con-2
BindingCodes that describe the manifestation or symptoms of a condition.
For example codes, see Manifestation and Symptom Codes
TypeCodeableConcept
38. Condition.evidence.detail
Definition

Links to other relevant information, including pathology reports.

Control0..* This element is affected by the following invariants: con-2
TypeReference(Resource)
39. Condition.note
Definition

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

Control0..*
TypeAnnotation
40. Condition.note.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
41. Condition.note.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

SlicingThis element introduces a set of slices on Condition.note.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
42. Condition.note.author[x]
Definition

The individual responsible for making the annotation.

Control0..1
TypeChoice of: Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson), string
[x] NoteSee Choice of Data Types for further information about how to use [x]
43. Condition.note.time
Definition

Indicates when this particular annotation was made.

Control0..1
TypedateTime
44. Condition.note.text
Definition

The text of the annotation.

Control1..1
Typestring