Stream: implementers
Topic: ActivityDefinition vs. PlanDefinition for an order set
Casey Thompson (Jul 29 2018 at 23:19):
For a heart failure admission order set, would you use PlanDefinition or ActivityDefinition? My understanding is that PlanDefinition describes how activities relate to eachother in the plan while ActivityDefinition only describes the activity itself. Is that the case?
In the IG, ActivityDefinition states "It may be used to specify actions to be taken as part of a workflow, order set, or protocol, or it may be used independently as part of a catalog of activities such as orderables."
Can anybody clarify when you would choose one over the other for an order set? Thanks in advance!
Lloyd McKenzie (Jul 30 2018 at 02:23):
Each order in the order set would be an ActivityDefinition. The PlanDefinition would establish which orders should be created and under which circumstances.
Casey Thompson (Jul 31 2018 at 14:46):
Thanks, Lloyd. So if ActivityDefinition cannot be used to define the order set, is the wording in the IG correct? "It may be used to specify actions to be taken as part of a workflow, order set, or protocol, or it may be used independently as part of a catalog of activities such as orderables." This reads as though it could be either the order itself or the entire order set. Can you clarify?
Lloyd McKenzie (Jul 31 2018 at 14:49):
"actions taken as part of" does not, to me, read as "the entire order set". However, if you'd like to propose clearer wording, feel free to submit a change request.
Last updated: Apr 12 2022 at 19:14 UTC
