The "features" of a case should be modeled explicitly, where

cpg-casefeaturedefinition is a profile of StructureDefinition with optional formal computability semantics. This would support defining patient data primitives and assertions up through inferences and enrichments.

cpg-casefeature would then be a set of resource-specific profiles, one for each kind of patient-specific resource, that would indicate instances of case feature definitions. (Or perhaps a cpg-casefeature extension that would indicate that a resource was an instantiation of a particular case feature definition).

Note specifically that case features are about patient state, they specifically do not include actions that are planned, or proposed, but have not yet been taken. That's strategy and/or workflow state.

cpg-casefeaturegroupdefinition - A profile of GraphDefinition specifying a group of case features relevant to a particular focus.

cpg-casefeaturegroup - A Bundle as realized from the GraphDefinition for a case feature group definition.