Difference between revisions of "201701 Care Plan"
| Line 46: | Line 46: | ||
===Care Plan Requestor=== | ===Care Plan Requestor=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| − | This connectathon track imposes few requirements for interested participants to evaluate and test retrieval of care plan and care team resources from servers. We wish to encourage discussion and testing that will lead to robust industry support for shared care plans. Thus, requestor in this track may | + | This connectathon track imposes few requirements for interested participants to evaluate and test retrieval of care plan and care team resources from servers. We wish to encourage discussion and testing that will lead to robust industry support for shared care plans. Thus, a requestor in this track may use: |
| − | * Debug testing tools for RESTful services, e.g. Postman that allow query of participating Responders using a variety of parameters such as plan category or date. | + | * Debug testing tools for RESTful services, e.g. Postman, that allow query of participating Responders using a variety of parameters such as plan category or date. |
* SMART on FHIR applications that embed Care Plan review and editing capabilities into any EHR system that supports these services. | * SMART on FHIR applications that embed Care Plan review and editing capabilities into any EHR system that supports these services. | ||
| − | * SMART on FHIR mobile applications that | + | * SMART on FHIR mobile applications that enable patients to view, contribute to, or check off completed activities included in a care plan created by their care team member(s). A patient-centric mobile application could enable a patient to add personal [http://hl7.org/fhir/2016Sep/goal.html Goal]s to a plan created by their primary care physician. |
* ''TODO'' link to HSPC sandbox with test data. | * ''TODO'' link to HSPC sandbox with test data. | ||
Revision as of 16:28, 21 October 2016
Return to January 2017 Proposals
Care Plan and Care Team
Submitting WG/Project/Implementer Group
Healthcare Services Platform Consortium (HSPC)
Justification
This track is intended to advance the maturity of FHIR resources for care planning (CarePlan, CareTeam, Goal, Condition, and others) and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of a more comprehensive US Realm implementation guide and profiles for care planning based on FHIR release 3.
Participants using both FHIR DSTU-2 and STU-3 are welcome!
The U.S. Department of Health and Human Services (HHS) recently published an article that describes a vision for a Comprehensive Shared Care Plan (CSCP). HHS identifies these goals for a CSCP:
- It should allow a clinician to electronically view information that is directly relevant to his or her role in the care of the person; to easily identify which clinician is doing what; and to update other members of an interdisciplinary team on new developments.
- It should put the person’s goals (captured in his or her own words) at the center of decision-making and give that individual direct access to his or her information in the CSCP.
- It should be holistic and describe both clinical and nonclinical (including home- and community-based) needs and services.
- It should follow the person through high-need episodes (e.g., acute illness), as well as periods of health improvement and maintenance.
TODO: describe use of APIs vs document-based care coordination. APIs enable development of vendor-independent applications for clinicians/providers and for patients/caregivers, e.g. mobile app for patients.
Relationship with other Connectathon tracks
- DAF-Core / US-Core IG and Argonaut
- Coordination of Care Service (CCS) – TBD?
Proposed Track Lead
- Dave Carlson – VA
- E-mail: Dave.Carlson@BookZurman.com
- Zulip: Dave Carlson
Expected participants
The following organizations have indicated an interest in participating in this track:
- VA – Dave Carlson
- HSPC – Dave Carlson
- 'Your organization here!'
Roles
Care Plan Requestor
This connectathon track imposes few requirements for interested participants to evaluate and test retrieval of care plan and care team resources from servers. We wish to encourage discussion and testing that will lead to robust industry support for shared care plans. Thus, a requestor in this track may use:
- Debug testing tools for RESTful services, e.g. Postman, that allow query of participating Responders using a variety of parameters such as plan category or date.
- SMART on FHIR applications that embed Care Plan review and editing capabilities into any EHR system that supports these services.
- SMART on FHIR mobile applications that enable patients to view, contribute to, or check off completed activities included in a care plan created by their care team member(s). A patient-centric mobile application could enable a patient to add personal Goals to a plan created by their primary care physician.
- TODO link to HSPC sandbox with test data.
Care Plan Responder
Care Plan Creator
- e.g. from ProcessDefinition for protocols or care pathways
Scenarios
1. Search for all Care Plans for a patient
- Action: Server and Client support query of CarePlan based on patient.id using GET [base]/CarePlan?patient=[id]
- Bonus point:
- Client and Server support date/period based querying of CarePlan using GET [base]/CarePlan?patient=[id]&date=[eq|lt|gt|geyyyy-mm-dd{&eq|lt|gt|geyyyy-mm-dd}]
2. Search for all Care Plans for a patient with a cancer care plan
- Action: Server and Client support query of CarePlan based on patient.id and category = "395082007" using GET [base]/CarePlan?patient=[id]&category=395082007
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
