Stream: Patient Care WG
Topic: AdverseEvent
Priya Gopal (Nov 17 2021 at 20:37):
In the current AE resource, I have the following questions:
- AdverseEvent for Oncology contains toxicity grades not severity. Please include toxicity grade attribute to AE?
- AE outcome code contains ONGOING as one of the choices. What exactly does ONGOING mean? does it mean NOT RECOVERED/NOT RESOLVED?
- There are not anatomical location of AE attribute available. Please add anatomical location of AE.
- An AE event could have an end date or might be ongoing. Can we have another end date time attribute and ongoing attribute as well?
Michelle (Moseman) Miller (Nov 18 2021 at 22:57):
Patient Care discussed this today (meeting minutes: https://confluence.hl7.org/display/PC/2021-11-18+Patient+Care+FHIR+Conference+Call)
- Log a change request - PC questioned if toxicity is an attribute of the AdverseEvent or medication/substance itself or observed effects of the toxicity?
- Changed to an example binding to a new value set with SNOMED codes, Valueset-adverse-event-outcome - FHIR v4.6.0, but in R4, it was required binding. ONGOING means symptom has not resolved yet, nor is it recovering. ONGOING could mean worsening.
- AdverseEvent.resultingCondition has a bodySite for anatomical location. If AdverseEvent.resultingCondition is extended to also support Observation (when symptom doesn't rise to the level of concern to have a Condition), then Observation also has bodySite. If the location isn't specific to the condition or observation, then log a change request with a specific example
- Similar to above - use the Condition dates or else log a change request with a specific use case / example where those dates are needed at the event level
Last updated: Apr 12 2022 at 19:14 UTC
