You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a PlanDefinition resource that utilizes ActivityDefinition and other PlanDefinition resources in the actions. The ActivityDefinitions are targeted to create ServiceRequest resources. The PlanDefinitions seem to process ok , but the ActivityDefinitions do not appear to produce any output in the CarePlan RequestGroup.
Here is an example of the output for an action in the RequestGroup --
{
"id": "ENACT-5",
"title": "ACT-3",
"description": "Cognition Assessment",
"resource": {
"reference": "ENACT-5-ACT-3"
}
}
While there is a reference to I would expect to be the ServiceRequest generated by the ActivityDefinition, there are no ServiceRequest resources generated or other resources with that id. I also question whether references based solely on an id are valid. I would assume that references to other contained resources in the same parent context, the CarePlan in this case, would need to follow the #{resourceType}/{resourceId} semantics, but I will add that as a different issue.
The text was updated successfully, but these errors were encountered:
I have a PlanDefinition resource that utilizes ActivityDefinition and other PlanDefinition resources in the actions. The ActivityDefinitions are targeted to create ServiceRequest resources. The PlanDefinitions seem to process ok , but the ActivityDefinitions do not appear to produce any output in the CarePlan RequestGroup.
Here is an example of the output for an action in the RequestGroup --
{
"id": "ENACT-5",
"title": "ACT-3",
"description": "Cognition Assessment",
"resource": {
"reference": "ENACT-5-ACT-3"
}
}
While there is a reference to I would expect to be the ServiceRequest generated by the ActivityDefinition, there are no ServiceRequest resources generated or other resources with that id. I also question whether references based solely on an id are valid. I would assume that references to other contained resources in the same parent context, the CarePlan in this case, would need to follow the #{resourceType}/{resourceId} semantics, but I will add that as a different issue.
The text was updated successfully, but these errors were encountered: