Difference between revisions of "CarePlan FHIR Resource Proposal"
Line 44: | Line 44: | ||
Deals with documentation of intended care for a specific human or animal for a particular (possibly implicit) time period. It does not (presently) cover non-healthcare-related care (e.g. device maintenance, plan for a specific specimen), nor does it deal with "definitional" plans that are not specific to a single patient and time-period. It does however cover all disciplines and all delivery environments. | Deals with documentation of intended care for a specific human or animal for a particular (possibly implicit) time period. It does not (presently) cover non-healthcare-related care (e.g. device maintenance, plan for a specific specimen), nor does it deal with "definitional" plans that are not specific to a single patient and time-period. It does however cover all disciplines and all delivery environments. | ||
− | Deals with the who (care team), the what (care activities) and the why (goals) | + | Deals with the who (care team), the what (care activities) and the why (goals). Can specify the problems for the Plan is intended to address. Also covers what are termed 'tasks' or 'actions' in PMS systems. |
+ | |||
+ | An individual patient may have multiple care plan resources active any any one time. | ||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" |
Revision as of 02:02, 22 June 2013
Contents
CarePlan
--Lmckenzi 21:43, 10 February 2013 (UTC)Need to change instructions to "UpperCamel"
Owning committee name
FHIR Core Team (eventually PatientCare)
Interested Work Groups
FHIR Resource Development Project Insight ID
???
Scope of coverage
Deals with documentation of intended care for a specific human or animal for a particular (possibly implicit) time period. It does not (presently) cover non-healthcare-related care (e.g. device maintenance, plan for a specific specimen), nor does it deal with "definitional" plans that are not specific to a single patient and time-period. It does however cover all disciplines and all delivery environments.
Deals with the who (care team), the what (care activities) and the why (goals). Can specify the problems for the Plan is intended to address. Also covers what are termed 'tasks' or 'actions' in PMS systems.
An individual patient may have multiple care plan resources active any any one time.
RIM scope
Act[classCode=PCPR, moodCode=INT], 1..1 subject participation with role of Patient
Resource appropriateness
Care plans are a well understood construct in healthcare, being created, updated and finally ending.
Care plans may be shared on their own or as part of referrals, discharge summaries, etc.
Expected implementations
Part of CCDA
Content sources
- Patient Care DAM
- aspects of v2 (GOL)
- OpenEHR (need someone to review with this in mind)
- others?
Resource Relationships
- Tied to a single Patient
- May have multiple participants (Providers, RelatedPersons, the Patient themselves)
- May be tied to one or more Conditions
- May have linkages from the planned activities to the various resources that realize those activities (orders, appointments, events)
Timelines
Part of initial DSTU
gForge Users
NA