Hi Medplum team, quick question for you. Do you have any near-term plans to augment the current functionality and use cases supported by the $apply operation on a

PlanDefinition

. If I understand the current Medplum implementation correctly, it appears the operation results in a newly created

RequestGroup

of Tasks with relatively static values and without references to the originating canonical

PlanDefinition.action

resource (aside from

Questionnaire

). We're currently referencing ActivityDefinitions (of

kind

Appointment, Communication, Medication and Task) in the

PlanDefintion

. Without retaining the reference to these ActivityDefinitions in the individual Tasks created within the RequestGroup, it limits the utility of our specific use case. If there are no plans to enhance this particular operation, we'll go ahead with building a custom solution for our needs, but we figured it was worth confirming with the MP team first.

Hi Andrew! So I would proceed with your own implementation - using Bot perhaps? In practice we are finding many folks are creating their own Tasks programatically and have custom logic at each step.

Sounds good, thanks for the follow up, Reshma!