Stream: Patient Care WG
Topic: Dynamic Care Plan
Jay Lyle (Jan 13 2022 at 23:16):
What's "Dynamic" about a "Dynamic Care Plan"?
IHE document text (& line #s)
"Care Plans can be dynamically updated as the patient interacts with the healthcare system." 263
"Care Plans can be dynamically created from tools used to support evidence-base practice. " 390
"Dynamic care planning expands the concept of care planning from being only discipline specific to an interdisciplinary process" 541
Impressions I get from conversation:
- Volatile, not static: i.e., application-based, not a document
- flexible scope, not tied to a specific plan definition, profile, or IG, but capable of representing any condition, goal, intervention, etc. of need.
Re #1:
an EHR asset is always modifiable
an interaction payload is always static
our remit for specifying "standard" application functionality is limited
but we can represent interactions in more detail, at a lower level of granularity
and recognize data requirements implied by more advanced functionality (api interactions)
Re #2:
OK - not a content-oriented profile, but the resource, and possibly some functionality-oriented profiling
And much more complex
John Moehrke (Jan 14 2022 at 13:16):
Jay, I think that is the right interpretation. Previous IG was based on CDA, so the name was picked to distinguish this new from the old. -- This is just a title of an interoperability "Implementation Guide"
John Moehrke (Jan 14 2022 at 13:25):
@Emma Jones ?
Emma Jones (Jan 14 2022 at 15:22):
@Jay Lyle the IHE profile is meant to convey Care Planning as a workflow using API interactions for example. It is not a static document captured at a point in time like CDA documents.
Last updated: Apr 12 2022 at 19:14 UTC
