FHIR Extensions Pack
5.2.0-ballot - 5.2.0 Ballot - September 2024) International flag

FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions

Extension: Condition Asserted Date

Official URL: http://hl7.org/fhir/StructureDefinition/condition-assertedDate Version: 5.2.0-ballot
Standards status: Trial-use Maturity Level: 3 Responsible: HL7 International / Patient Care Computable Name: ConditionAssertedDate
Other Identifiers: OID:2.16.840.1.113883.4.642.5.1310

When the asserter identified the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern. For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain. Asserted date supports the recognition that information is not always entered in a system immediately. Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time. If this difference is significant for your use case, assertion date may be useful.

Context of Use

This extension may be used on the following element(s):

  • Element ID Condition
  • Element ID AllergyIntolerance

Usage info

Usage:

  • This Extension is not used by any profiles in this Implementation Guide

Changes since version 1.0.0:

  • The resource metadata has changed (publisher, description)
  • The data elements list has changed
  • One or more text definitions, invariants or bindings have changed

    • Formal Views of Extension Content

    Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

    This structure is derived from Extension

    Summary

    Simple Extension of type dateTime: When the asserter identified the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern. For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain. Asserted date supports the recognition that information is not always entered in a system immediately. Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time. If this difference is significant for your use case, assertion date may be useful.

    Maturity: 3

    This structure is derived from Extension

    NameFlagsCard.TypeDescription & Constraintsdoco
    .. Extension 0..1 Extension Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/condition-assertedDate"
    ... value[x] 1..1 dateTime Value of extension

    doco Documentation for this format
    NameFlagsCard.TypeDescription & Constraintsdoco
    .. Extension 0..1 Extension Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted
    ... id 0..1 id Unique id for inter-element referencing
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/condition-assertedDate"

    doco Documentation for this format

    This structure is derived from Extension

    Summary

    Simple Extension of type dateTime: When the asserter identified the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern. For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain. Asserted date supports the recognition that information is not always entered in a system immediately. Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time. If this difference is significant for your use case, assertion date may be useful.

    Maturity: 3

    Differential View

    This structure is derived from Extension

    NameFlagsCard.TypeDescription & Constraintsdoco
    .. Extension 0..1 Extension Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/condition-assertedDate"
    ... value[x] 1..1 dateTime Value of extension

    doco Documentation for this format

    Snapshot View

    NameFlagsCard.TypeDescription & Constraintsdoco
    .. Extension 0..1 Extension Date the allergy, intolerance, condition, problem, or diagnosis or other event, situation, issue, or clinical concept was first asserted
    ... id 0..1 id Unique id for inter-element referencing
    ... extension 0..0
    ... url 1..1 uri "http://hl7.org/fhir/StructureDefinition/condition-assertedDate"

    doco Documentation for this format

     

    Other representations of profile: CSV, Excel, Schematron

    Constraints

    IdGradePath(s)DetailsRequirements
    ele-1error**ALL** elementsAll FHIR elements must have a @value or children
    : hasValue() or (children().count() > id.count())
    ext-1error**ALL** extensionsMust have either extensions or value[x], not both
    : extension.exists() != value.exists()

    Search Parameters for this Extension

    (none found)