description: 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.
package_name: hl7.fhir.uv.extensions
derivation: constraint
name: ConditionAssertedDate
type: Extension
elements:
  extension: {index: 0}
  url:
    pattern: {type: Uri, value: 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'}
    index: 1
  value:
    choices: [valueDateTime]
    index: 3
  valueDateTime: {type: dateTime, choiceOf: value, index: 4}
package_version: 5.3.0-ballot
extensions: {}
class: extension
kind: complex-type
url: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
base: http://hl7.org/fhir/StructureDefinition/Extension
version: 5.3.0-ballot
required: [valueDateTime, value]