Condition (CA-Core)

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at package/structuredefinition-condition-ca-core.json

This profile imposes the CA Baseline (v1.1.7) Condition Profile.

Profile

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
assertedDateI0..1Extension(dateTime)
modifierExtension?! I0..*Extension
identifierΣ0..*Identifier
clinicalStatusΣ ?! I0..1CodeableConceptBinding
verificationStatusΣ ?! I0..1CodeableConceptBinding
category0..*CodeableConceptBinding
severity0..1CodeableConceptBinding
codeΣ0..1CodeableConceptBinding
bodySiteΣ0..*CodeableConceptBinding
subjectΣ I1..1Reference(package/structuredefinition-patient-ca-core.json)
encounterΣ I0..1Reference(Encounter)
onsetAgeAge
onsetPeriodPeriod
onsetRangeRange
onsetStringstring
onsetDateTimeΣ0..1dateTime
abatementAgeAge
abatementPeriodPeriod
abatementRangeRange
abatementStringstring
abatementDateTimeI0..1dateTime
recordedDateΣ0..1dateTime
recorderΣ I0..1Reference(package/structuredefinition-practitioner-ca-core.json | Practitioner | package/structuredefinition-practitionerrole-ca-core.json | PractitionerRole | package/structuredefinition-patient-ca-core.json | Patient | RelatedPerson)
asserterΣ I0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
summaryI0..1CodeableConcept
assessmentI0..*Reference(ClinicalImpression | DiagnosticReport | Observation)
type0..1CodeableConcept
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
codeΣ I0..*CodeableConcept
detailΣ I0..*Reference(Resource)
note0..*Annotation

Obligations

Obligations are a new (and evolving) mechanism in FHIR to provide a consistent and machine processable way for profiles to define their expectations for system behaviors.

This profile utilizes the Obligation Extension to convey these expectations.

Note: Simplifier is working on rendering of Obligations. In the meantime the Obligations applied on the profile (see JSON & XML structure) have been rendered as a table below for easier viewing.

Obligation Code Actor Elements
SHALL:able-to-populate Server Actor (CA Core) clinicalStatus, verificationStatus, category, severity, code, bodySite, subject, onsetDateTime, abatementDateTime, assertedDateTime, recordedDateTime, recorder, stage, stage.summary, stage.assessment, stage.type, evidence, evidence.code, evidence.detail
SHALL:no-error Client Actor (CA Core) clinicalStatus, verificationStatus, category, severity, code, bodySite, subject, onsetDateTime, abatementDateTime, assertedDateTime, recordedDateTime, recorder, stage, stage.summary, stage.assessment, stage.type, evidence, evidence.code, evidence.detail

Terminology

This version of the guide is based on the early content development of the pan-Canadian Health Data Content Framework (pCHDCF). The pCHDCF is beginning to introduce recommended terminology for select concepts. Implementers should be aware that the identification of preferred terminology continues to progress and that some coded elements may have terminology recommendations added in future releases.

Note: Implementers should be aware of the limitations in some terminology referenced in this guide that is not fully expressed as an enumerated FHIR ValueSet or resolvable FHIR CodeSystems. Readers should refer to the Known Issues & Future Development page.

Bindings

Primary bindings are expressed in the rendering of the profile above (as well as can be found in the JSON/XML file).

Additional terminology bindings are also expressed in this profile to surface Alternate Value Sets expressed in the pCHDCF Data Content Standard. Currently, Simplifier does not render the additionalBinding extension that is applied within the profile to express these Alternate Value Sets. See Known Issues & Future Development page.

In the interim, the terminology that has been expressed as additionalBindings is rendered below for ease of use:

  • Condition.code:

    • ICD-9 CM codes package/valueset-ICD9CM.json is recommended as an alternate value set to support physician billing in Canada and as a classification for reporting and analysis
    • ICD-10 CA codes package/valueset-ICD10CA.json is recommended as an alternate value set to support physician billing in Canada and as a classification for reporting and analysis

    Note: In future releases, the additionalBinding extension will be used to express the valueSet for additional negation/exclusion codes for reporting the known absence of conditions. At the time of this release, the publisher of the current ValueSet for absence codes (IPS) is developing a SNOMED ValueSet that will replace the current http://hl7.org/fhir/uv/ips/ValueSet/absent-or-unknown-problems-uv-ips

Mappings to pCHDCF

Draft Data Content Standard Element (As of 2024-02-15) Draft Data Content Standard Element Definition (As of 2024-02-15) FHIR Profile Element Additional Notes
Health Concern Clinical Status The current status of the health concern or the condition, for example, whether it is active or resolved. Condition.clinicalStatus
Health Concern Verification Status Information about the status of the condition, such as confirmed or differential. Condition.verificationStatus
Health Concern Category Indicates whether the health concern is a problem list item, or an encounter diagnosis. Condition.category
Health Concern Severity The subjective assessment of the severity of the condition. Condition.severity
Health Concern(s) A broad classification of active and historical health-related conditions or issues requiring attention, typically encompassing various health complaints or challenges. Condition.code
Health Concern Body Site Information about the location on the body of the health concern. Condition.bodySite
Health Concern Date of Onset Information about the estimated or actual date of onset of the health concern. Condition.onset[x]:onsetDateTime
Health Concern Date of Resolution The date the health concern or condition subsided or resolved. Condition.abatement[x]:abatementDateTime
Health Concern Date of Diagnosis The date of diagnosis of the health concern. Condition.extension:assertedDate; Condition.recordedDate There is no single element in Condition that is used to unequivocally capture the date of diagnosis. Based on findings expressed in US Core 6.1.0 Condition profiles, existing systems may capture this concept in the assertedDate Extension, Condition.recordedDate, or Condition.onsetDateTime. This may be impacted by the workflow associated with the recording of the diagnosis (i.e., if the diagnosis is made in an encounter that the condition was captured during or had been asserted previously). At the time this profile is released, the assertedDate extension is undergoing review by the Patient Care Working Group at HL7 International. This specification will further evaluate further server expectations on assertedDate following resolution.
Health Concern Specialist Details Identifier information of an optional care provider who may have expertise related to a particular health concern. Condition.recorder Condition.recorder is used to link to these details housed in the practitioner resource (e.g. first name, last name, ID) as indicated in the pCHDCF artefacts.
Health Concern Stage Summary A summary of the stage of the condition or disease (e.g., stage 3). Condition.stage.summary
Health Concern Stage Assessment Reference to a formal record of the evidence on which the staging assessment is based. Condition.stage.assessment
Health Concern Stage Type The type of stages for a condition or disease (e.g., pathological or clinical staging) Condition.stage.type
Health Concern Evidence Code A code indicating a manifestation or a symptom that led to the reporting of this health concern. Condition.evidence.code
Health Concern Supporting Documents Other documents that provide context and/or supporting evidence related to a health concern or diagnosis (e.g., scan results). Condition.evidence.detail