Stream: implementers
Topic: AdverseEvent Actuality
Jose Costa Teixeira (Oct 18 2018 at 06:24):
Hi. If AdverseEvent is an event, how does "actuality=potential" work? what information is it supposed to transmit?
Jose Costa Teixeira (Oct 18 2018 at 06:27):
in other words, what would be an example of an event that is a "potential adverse event"?
Mareike Przysucha (Oct 18 2018 at 06:35):
Just a guess: An unsafe situation, which might lead to an adverse event or to a near miss. The outcome is not yet fixed, but the unsafe situation is noticed. Is that a likely explanation?
Rik Smithies (Oct 18 2018 at 09:56):
As originally envisaged, it is for whether this is something that happened (water was spilled, regardless of if anyone slipped) versus something nearly happening, in an actual case (tap left running, but not actually a spillage problem).
So yes a near miss or a unsafe situation that arose.
It is not meant for theoretical events - risks. (e.g. be careful with water sources because people can slip)
However we do need something for that type of thing, for use in "undesirable effects" for medication definitions. I considered re-using AdverseEvent there but it is too concrete, in its current form (and I'm not really suggesting we change it).
Jose Costa Teixeira (Oct 18 2018 at 11:54):
Agree that adverseEvent should not be used for undesirable effects.
Just finished a pharmacovigilance discussion where this distinction was really needed.
Rik Smithies (Oct 18 2018 at 14:28):
there is this now, as a starter: http://build.fhir.org/medicinalproductundesirableeffect.html
Last updated: Apr 12 2022 at 19:14 UTC
