Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US QI Core (FHIR)
-
2.0 [deprecated]
-
Clinical Quality Information
-
QICore AdverseEvent
-
8.2 Adverse Event Mapping
-
-
Floyd Eisenberg/Peter Muir: 13-0-0
-
Correction
-
Non-substantive
Description
On this qdm-to-qicore mapping page, 8.2 Adverse Event, table shows that QDM.code maps to AdverseEvent.event, however, the descriptions above the table says “QDM AdverseEvent references only the suspectEntity.instance (as code) and category (as type).”, which suggests AdverseEvent.suspectEntity.instance would be the primary code, not the AdverseEvent.event. I see the fhir-modelinfo-4.0.1.xml shows the primaryCodePath=“event” that matches the table. It seems to me that definition of suspectEntity.instance makes it a better fit for primary code than the event element.
The main issue is that the QDM definition of the AdverseEvent datatype is the suspectEntity but it should probably be AdverseEvent.resultingCondition (reference to Condition), I.e., what happened to the patient. And there is a missing attribute, suspectEntity ( AdverseEvent.suspectEntity.Instance ). As stated in QDM v5.5 and 5.6, AdverseEvent defines the suspectEntity, not the event itself, and it does not have the attribute to reference the resulting condition. Thus, the mapping from AdverseEvent code should be to AdverseEvent.suspectEntity.Instance unless QDM were to update the definition.