Stream: workflow
Topic: Values for CarePlan.activity.detail.scheduledString
Georg Zweyer (Mar 15 2019 at 15:27):
Hello everyone,
What kind of string values should go into CarePlan.activity.detail.scheduledString? The examples contain dateTime values, which totally makes sense, but shouldn't the attribute than be called scheduledDateTime?
Thank you for your assistance.
Lloyd McKenzie (Mar 15 2019 at 15:32):
sheduledString could be all sorts of things. "After the sidewalks are free of ice" or "before my daughter's wedding" or "the Mondays when my husband is able to watch the kids" - it's typically used for timings that either can't be formally expressed in a reasonable way or when the source system doesn't capture time information as discrete elements and all it can do is propagate the string it has.
Georg Zweyer (Mar 15 2019 at 15:58):
Wouldn't it make sense than to add an additional scheduledDateTime attribute for when you want to capture a precise time? Otherwise, if your system can handle concrete times, it would have to check if the string is a dateTime. Or should it use scheduledTiming.event for this? In this case, however, PlanDefinition.action.timingDateTime would also not be needed.
Lloyd McKenzie (Mar 15 2019 at 16:02):
The work group's initial analysis led them to believe that care plans identifying a specific date for something wasn't that common - that that tended to be more of an appointment/scheduling thing than a planning thing. However, if you believe this determination was incorrect, you can certainly submit a change request. (Evidence of support by existing systems that do care planning would be good too.)
Georg Zweyer (Mar 15 2019 at 16:17):
Sounds reasonable. Actualy i don't do any care planning at all. I want to use CarePlan as instantiation of a PlanDefinition in a ResearchStudy scenario, because i want to use as less different resource types as possible to keep it simple and CarePlan has this nice forward referencing on outcomes of actions.
Lloyd McKenzie (Mar 15 2019 at 16:53):
So the PlanDefinition determines that the event must happen on a specific day - as opposed to sometime within a specified time-range?
Georg Zweyer (Mar 18 2019 at 08:52):
It is a possibility. The initial question was more of a do i understand the specification correctly type.
Lloyd McKenzie (Mar 18 2019 at 19:11):
You understand the specification correctly. Right now, PlanDefinition doesn't support saying that something will happen on a specific day - at least not without pointing to one of the Request resources that would allow that (e.g. Appointment). That doesn't necessarily mean it shouldn't allow that. You could propose a change if you think that support for dateTime should be added to the core spec
Last updated: Apr 12 2022 at 19:14 UTC
