2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Profile U.S. Data Access Framework (DAF) Condition (a.k.a Problem) Profile - Definitions

Todo

Definitions for the condition-daf-dafcondition Profile.

Condition(DAFCondition)
Definition

The occurrence of a condition.

Control1..1
Requirements
Comments
Condition.id
Definition

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

Control0..1
Typeid
Requirements
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. Bundles always have an id, though it is usually a generated UUID.

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
Requirements
Comments
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
Requirements
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 as much as possible.

Condition.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language
The codes SHALL be taken from http://tools.ietf.org/html/bcp47
Typecode
Requirements
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).

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
Requirements
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

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

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
Requirements
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. The slicing rules are:
  • unordered
  • open
  • discriminators: url
Condition.extension (http://hl7.org/fhir/ExtensionDefinition/us-core-concernStatus)
Definition

This communicates the status of the Concern associated with a condition. Values can be Active/Inactive/Resolved.

Control0..1
TypeCodeableConcept
Requirements
Comments
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
Requirements
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.

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

Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

Comments
Condition.subject
Definition

Indicates the patient who the condition record is associated with.

Control1..1
TypeReference(Profile = (Profile = http://hl7.org/fhir/Profile/patient-daf-dafpatient))
Must Supporttrue
Requirements
Comments
Condition.encounter
Definition

Encounter during which the condition was first asserted.

Control0..1
TypeReference(Profile = (Profile = http://hl7.org/fhir/Profile/encounter-daf-dafencounter))
Must Supporttrue
Requirements
Comments
Condition.asserter
Definition

Person who takes responsibility for asserting the existence of the condition as part of the electronic record.

Control0..1
TypeChoice of: Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Practitioner)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Patient))
Requirements
Comments
Condition.dateAsserted
Definition

Estimated or actual date the condition/problem/diagnosis was first detected/suspected.

Control0..1
Typedate
Must Supporttrue
Requirements
Comments
Condition.code
Definition

Identification of the condition, problem or diagnosis.

Control1..1
BindingValueset to describe the actual problem experienced by the patient
The codes SHALL be taken from Problem Value Set
TypeCodeableConcept
Must Supporttrue
Requirements
Comments
Condition.category
Definition

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

Control0..1
BindingValueset to identify if the problem is a Finding, Symptom, Condition etc.
The codes SHALL be taken from Problem Type Value Set
TypeCodeableConcept
Must Supporttrue
Requirements
Comments

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

Condition.status
Definition

The clinical status of the condition.

Control1..1
BindingThe clinical status of the Condition or diagnosis
The codes SHALL be taken from ConditionStatus
Typecode
Is Modifiertrue
Must Supporttrue
Requirements
Comments
Condition.certainty
Definition

The degree of confidence that this condition is correct.

Control0..1
BindingThe degree of confidence that this condition is correct
For example codes, see Condition/Diagnosis Certainty
TypeCodeableConcept
Is Modifiertrue
Requirements
Comments

May be a percentage.

Condition.severity
Definition

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

Control0..1
BindingValueset to identify the severity of the problem
The codes SHALL be taken from Problem Severity
TypeCodeableConcept
Must Supporttrue
Requirements
Comments

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

Condition.onsetDateTime
Definition

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

Control0..1
TypedateTime
Must Supporttrue
Requirements
Comments

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

Condition.abatementBoolean
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
Typeboolean
Must Supporttrue
Requirements
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.

Control0..1
Requirements
Comments
InvariantsDefined on this element
con-1: Stage SHALL have summary or assessment (xpath: exists(f:summary) or exists(f:assessment))
Condition.stage.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Requirements
Comments
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
Requirements
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.

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

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
TypeCodeableConcept
Requirements
Comments
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(Profile = http://hl7.org/fhir/Profile/Any)
Requirements
Comments
Condition.evidence
Definition

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

Control0..*
Requirements
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 (xpath: exists(f:code) or exists(f:detail))
Condition.evidence.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Requirements
Comments
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
Requirements
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.

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

Condition.evidence.code
Definition

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

Control0..1 This element is affected by the following invariants: con-2
TypeCodeableConcept
Requirements
Comments
Condition.evidence.detail
Definition

Links to other relevant information, including pathology reports.

Control0..* This element is affected by the following invariants: con-2
TypeReference(Profile = http://hl7.org/fhir/Profile/Any)
Requirements
Comments
Condition.location
Definition

The anatomical location where this condition manifests itself.

Control0..*
Requirements
Comments

May be a summary code, or a reference to a very precise definition of the location, or both.

InvariantsDefined on this element
con-3: location SHALL have code or details (xpath: exists(f:code) or exists(f:detail))
Condition.location.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Requirements
Comments
Condition.location.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
Requirements
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.

Condition.location.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
Requirements
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.

Condition.location.code
Definition

Code that identifies the structural location.

Control0..1 This element is affected by the following invariants: con-3
TypeCodeableConcept
Requirements
Comments

May include laterality.

Condition.location.detail
Definition

Detailed anatomical location information.

Control0..1 This element is affected by the following invariants: con-3
Typestring
Requirements
Comments
Condition.dueTo
Definition

Further conditions, problems, diagnoses, procedures or events or the substance that caused/triggered this Condition.

Control0..*
Requirements
Comments

Although a condition may be caused by a substance, this is not intended to be used to record allergies/adverse reactions to substances.

InvariantsDefined on this element
con-4: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target))
Condition.dueTo.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Requirements
Comments
Condition.dueTo.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
Requirements
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.

Condition.dueTo.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
Requirements
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.

Condition.dueTo.codeableConcept
Definition

Code that identifies the target of this relationship. The code takes the place of a detailed instance target.

Control0..1 This element is affected by the following invariants: con-4
BindingIdentification of the Condition or diagnosis.
For example codes, see Condition/Problem/Diagnosis Codes
TypeCodeableConcept
Requirements
Comments
Condition.dueTo.target
Definition

Target of the relationship.

Control0..1 This element is affected by the following invariants: con-4
TypeChoice of: Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Condition)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Procedure)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/MedicationAdministration)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Immunization)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/MedicationStatement))
Requirements
Comments
Condition.occurredFollowing
Definition

Further conditions, problems, diagnoses, procedures or events or the substance that preceded this Condition.

Control0..*
Requirements
Comments
InvariantsDefined on this element
con-5: Relationship SHALL have either a code or a target (xpath: exists(f:code) != exists(f:target))
Condition.occurredFollowing.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Requirements
Comments
Condition.occurredFollowing.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
Requirements
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.

Condition.occurredFollowing.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
Requirements
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.

Condition.occurredFollowing.codeableConcept
Definition

Code that identifies the target of this relationship. The code takes the place of a detailed instance target.

Control0..1 This element is affected by the following invariants: con-5
BindingIdentification of the Condition or diagnosis.
For example codes, see Condition/Problem/Diagnosis Codes
TypeCodeableConcept
Requirements
Comments
Condition.occurredFollowing.target
Definition

Target of the relationship.

Control0..1 This element is affected by the following invariants: con-5
TypeChoice of: Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Condition)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Procedure)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/MedicationAdministration)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/Immunization)), Reference(Profile = (Profile = http://hl7.org/fhir/Profile/MedicationStatement))
Requirements
Comments
Condition.notes
Definition

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

Control0..1
Typestring
Must Supporttrue
Requirements
Comments