Comment:

From my point of view the Plandefinition resource will not be used exclusively by decision support solutions but rather from many workflow based products/solutions as well, such as workflow brokers, plans for medical collaborations, laboratory workflows etc. which may have no decision support component at all.

Even the introduction of this resource states that:

This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols.

which shows that the focus of this resource is not just bound to decision support but to many other processes like orders, or executable workflows.

Especially the description of the PlanDefinition The definition of a plan for a series of actions, independent of any specific patient or context sounds like description of a general workflow. This resource also uses the patterns for request, event or definition which are created and maintained by the workflow group. Therefore I would propose to move this resource from the decision support group to the workflow group but of course retaining a close coordination when it comes to potential changes for this resource.

Summary:

Proposal to move the PlanDefinition resource from the decision support work group to the workflow work group.