Comment:

AdverseEvent.resultingCondition - inadequate and inappropriate for documenting adverse reactions associated with AdverseEvent incidents

Rationale - in very many cases an AdverseEvent incident is associated with a set of adverse reactions similar to the case of Allergy/Intolerance incidents.

Example use case - a patient with severe gingival recession requires tissue graph treatment to cover exposure root of tooth. Soft tissue graft is harvested from patient's oral cavity and attached to the graft site by sutures. A couple of days later, the patient developed intraoral itchness and swelling

The clinician needs to document the findings as adverse reactions

Eventually, the graft devitalised and failed. After further investigation, it was determined that the patient might have suffered from allergic reactions to the suture material

As there is no prior history, this will be recorded and reported eventually as an AdverseEvent incidence with associating allergic adverse reactions

Comment - very often, a resultingCondition cannot be determined at the time of assessing and documenting reactions. What can be known is a temporal relationship between the Event incidence and a set of reactions

This and many other similar use cases support the need for replacing AdverseEvent.resultingCondtion with a Choice for resultingCondition and an AdverseEvent.reaction element that references a new resource: AdverseReaction. This resource can be reused in AllergyIntolerance and other resources where appropriate

Summary:

AdverseEvent.resultingCondition - inadequate and inappropriate for documenting adverse reactions associated with AdverseEvent incidents