In case i have to populate the context (which might be a problem anyhow since its a problem_list … ).
What would be the start_time of a problem list composition ?
In my view, a Composition containing a problem list should represent the set of clinically relevant problems at the time that particular version of the composition was created. The context/start_time should indicate the start of the clinical follow-up episode that the Composition is intended to capture. For a persistent problem list that is continuously updated and versioned, the context/start_time remains constant, reflecting when the follow-up formally began. Meanwhile, each version’s audit/time_committed records the exact time that each version was created, capturing updates and modifications. For a lifelong problem list, the context/start_time becomes more symbolic, marking the start of the formal record. In contrast, the version history (time_committed) provides actionable temporal information for tracking the evolution of the patient’s problems.
1 Like
Interesting question. The specs are hazy on how to date persistent and episodic compositions, in part because originally the rm said that persistent compositions did not have context. That was relaxed to support episodic compositions.
I think currently most of our persistent and episodic comp just update the start-time for each list update but I think this idea of using start time for the date that the list was established is a good one.
I might use end time rather than the commit time as the latter is intended as a technical commit time not authored time.
1 Like
Yeah i agree with that:
" idea of using start time for the date that the list was established is a good one"
Also the composer is the person who established it then ?
1 Like