QI-Core Implementation Guide: STU 4 (v4.0.0 for FHIR 4.0.0)

QI-Core Implementation Guide, Clinical Quality Improvement WG - CI build for vesion 4.0.0). This version is based on the current content of https://github.com/cqframework/qi-core/ and changes regularly. See the Directory of published versions

7.1.0 Adverse Event

This QDM to QI-Core Mapping for the QDM Datatype "Adverse Event" has been updated from QDM 5.4 to QDM 5.5.

QDM defines Adverse Event as any untoward medical occurrence associated with the clinical care delivery, whether or not considered drug related. The concepts aligns with the FHIR R4 resource Adverse Event (http://hl7.org/fhir/adverseevent-definitions.html#AdverseEvent). The FHIR resource provides clearer expressivity as compared with QDM. QDM AdverseEvent references only the suspectEntity.instance (as code) and category (as type). It does not include any reference to an event’s actuality (i.e., potential Vs actual) which is available in FHIR. To expand on the ability to express such a concept, the mapping table includes adverseEvent.actuality.

QDM Context QI-Core R4 Comments
Adverse Event AdverseEvent
AdverseEvent.actuality
QDM Attributes
code AdverseEvent.event FHIR R4 replaces AdverseEvent.type with AdverseEvent.event
type AdverseEvent.category
severity AdverseEvent.severity
relevant dateTime AdverseEvent.date
FacilityLocations AdverseEvent.location
Author dateTime AdverseEvent.recordedDate
id AdverseEVent.id
recorder AdverseEvent.recorder