Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-41263

Remove Must Supports and Adverse Event Profile

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US QI Core (FHIR)
    • current
    • Clinical Quality Information
    • AdverseEvent example
    • QI-Core Profiles
    • Hide

      Based on Discussion July 7, 2023, retain AdverseEvent and add a ballot question about potentially removing it from QI-Core - FHIR-41545

      [QI-Core AdverseEvent|http://hl7.org/fhir/us/qicore/2022Sep/StructureDefinition-qicore-adverseevent.html] - Patient Care Workgroup documented some use cases and supporting information for this resource - https://confluence.hl7.org/display/PC/Adverse+Event+Use+Cases 
      https://confluence.hl7.org/display/PC/Adverse+Event+and+consequences; however, most adverse event information is more identifiable in clinical records as findings, conditions, or observations. References for information regarding potential adverse event triggers: CMS Hospital-Acquired Condition Reduction Program.
      Also useful: Institute for Healthcare Improvement Trigger Tool for Measuring Adverse Drug Events (requires registration).

      Show
      Based on Discussion July 7, 2023, retain AdverseEvent and add a ballot question about potentially removing it from QI-Core - FHIR-41545 .  [QI-Core AdverseEvent| http://hl7.org/fhir/us/qicore/2022Sep/StructureDefinition-qicore-adverseevent.html ] - Patient Care Workgroup documented some use cases and supporting information for this resource - https://confluence.hl7.org/display/PC/Adverse+Event+Use+Cases   https://confluence.hl7.org/display/PC/Adverse+Event+and+consequences ; however, most adverse event information is more identifiable in clinical records as findings, conditions, or observations. References for information regarding potential adverse event triggers: CMS Hospital-Acquired Condition Reduction Program . Also useful: Institute for Healthcare Improvement Trigger Tool for Measuring Adverse Drug Events (requires registration).
    • Floyd Eisenberg/Jen Seeman: 24-0-0
    • Clarification
    • Non-substantive

    Description

      Experience with capturing AdverseEvent has been limited and suggests that clinical systems generally avoid identifying a category/class of adverse events. Instead, most organizations have a separate risk management system that captures adverse events of healthcare as part of a legal/risk management process. Specific events can still be identified as findings or conditions (e.g., fall, injury, fracture) and causative agents probably best identified with ICD-10 codes (e.g., fracture due to xxx). Thus, the measure expression can more likely capture what might be an adverse event by identifying a new observation or condition (e.g., fracture) with onsetDate after admission (for hospital admissions) or initiating at the time or after a procedure (inpatient or ambulatory).  Continuing AdverseEvent in eCQMs, dQMs, and CDS artifacts is likely adding burden to implementers and provider systems until such time as USCDI includes a requirement to capture and share Adverse Events with interoperable messages.

      Attachments

        Activity

          People

            jen_seeman Jennifer Seeman
            feisenberg Floyd Eisenberg
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: