This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CarePlan FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 1: | Line 1: | ||
| − | |||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
| Line 13: | Line 12: | ||
| − | = | + | =CarePlan= |
| + | --[[User:Lmckenzi|Lmckenzi]] 21:43, 10 February 2013 (UTC)Need to change instructions to "UpperCamel" | ||
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | FHIR Core Team (eventually [[PatientCare]]) |
==Interested Work Groups== | ==Interested Work Groups== | ||
| − | + | [[PatientCare]] | |
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) --> | ||
| − | |||
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | ??? | |
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
==Scope of coverage== | ==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) | ||
<!-- 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%" | ||
| Line 57: | Line 58: | ||
==RIM scope== | ==RIM scope== | ||
| + | |||
| + | Act[classCode=PCPR, moodCode=INT], 1..1 subject participation with role of Patient | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
==Resource appropriateness== | ==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. | ||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 77: | Line 84: | ||
==Expected implementations== | ==Expected implementations== | ||
| + | Part of CCDA | ||
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | <!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | ||
==Content sources== | ==Content sources== | ||
| + | |||
| + | * Patient Care DAM | ||
| + | * aspects of v2 (GOL) | ||
| + | * OpenEHR (need someone to review with this in mind) | ||
| + | * others? | ||
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | <!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | ||
| Line 86: | Line 99: | ||
==Resource Relationships== | ==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) | ||
<!-- What are the resources do you expect will reference this resource and in what context? | <!-- What are the resources do you expect will reference this resource and in what context? | ||
| Line 98: | Line 116: | ||
==Timelines== | ==Timelines== | ||
| + | Part of initial DSTU | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
==gForge Users== | ==gForge Users== | ||
| + | NA | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
Revision as of 21:43, 10 February 2013
This page documents a Pending FHIR Resource Proposal
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)
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
