Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Medium
-
US QI Core (FHIR)
-
current
-
Clinical Quality Information
-
AdverseEvent example
-
QI-Core Profiles
-
-
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
Issue Links
- relates to
-
FHIR-41340 Change all US Core dependent QI-Core Profiles to inherit US Core Profiles 'as-is'
- Resolved - No Change