Stream: Vulcan/SoA
Topic: PlanDefinition vs EventDefinition
Geoff Low (Jan 14 2021 at 19:27):
Ok, I think I know why didn't look at EventDefinition -> we started with the workflow section of the documentation and that doesn't reference EventDefinition so it wasn't really on the radar. We were primarily interested in the initiation of events to satisfy the protocol requirements and the combination of PlanDefinition (for complex activities) and ActivityDefintion (for 'simple' activities) seemed to work (per the deck Hugh shared). Looking at the EventDefinition resource I still think PlanDefinition and ActivityDefinition align better with what we laid out. Happy to be proved wrong
Hugh Glover (Jan 14 2021 at 19:41):
I was just digging too. EventDefinition so far as I can see is just a sub-set of PlanDefinition (I suspect it is an earlier attempt that has got lost). I don't think there is anything you can do with EventDefinition that can't also be done with PlanDefinition, but PlanDefinition allows an assortment of additional features (actions, goals, related actions). Like Geoff happy to be proved wrong ...
Hugh Glover (Jan 14 2021 at 19:50):
See #implementers>EventDefinition vs PlanDefinition for an authoritative statement
Last updated: Apr 12 2022 at 19:14 UTC
