Dynamic Care Planning
The Dynamic Care Planning (DCP) Profile provides the structures and transactions for care planning, sharing Care Plans that meet the needs of many, such as providers, patients and payers.
The Dynamic Care Planning (DCP) Profile provides the structures and transactions for care planning, sharing Care Plans that meet the needs of many, such as providers, patients and payers. Care Plans can be dynamically updated as the patient interacts with the healthcare system. FHIR® resources and transactions are used by this profile. This profile does not define, nor assume, a single Care Plan for a patient.
The ability to target appropriate services and to coordinate care over time, across multiple clinicians and sites of service, with the engagement of the individual (i.e., longitudinal coordination of care) is essential to alleviating fragmented, duplicative and costly care for these medically-complex and/or functionally impaired persons.
Care planning is needed to manage medically complex and/or functionally impaired individuals as they interact with the health care system. Often, these individuals require real time coordination of the care as they receive care from multiple care providers and care settings. HL7® Care Plan Domain Analysis Model depicts the care plan as a tool used by clinicians to plan and coordinate care . Effective care planning and care coordination for patient with complex health problems and needs are needed throughout the world.
This profile depicts how multiple care plans can be shared and used to plan and coordinate care.
- EHR systems may manage care plans and also contribute to other care plans.
- Patients may query, retrieve and update care plans.
Actors & Transactions:
Profile Status: Trial Implementation
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
<list all the standards on which the profile is based; if possible with links to sources>
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template
<Delete this Category Templates line since your Profile page is no longer a template.>