Difference between revisions of "201801 Care Plan"

From HL7Wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
| __TOC__
 
| __TOC__
 
|}
 
|}
=Care Management (including Care Plan)=
+
=Care Management and Planning=
  
'''Dedicated [https://chat.fhir.org/#narrow/stream/connectathon.20mgmt/subject/C17.20Care.20Plan.20Track Zulip chat stream] for this track.'''
+
'''Dedicated [https://chat.fhir.org/#narrow/stream/connectathon.20mgmt/subject/C17.20Care.20Management.20and.20Planning.20Track Zulip chat stream] for this track.'''
  
 
'''Previous Care Plan Connectathons'''
 
'''Previous Care Plan Connectathons'''
Line 23: Line 23:
 
==Justification==
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
This track is intended to advance the maturity of FHIR resources for care management ([http://hl7.org/fhir/careplan.html CarePlan], [http://hl7.org/fhir/careteam.html CareTeam], [http://hl7.org/fhir/goal.html Goal], [http://hl7.org/fhir/condition.html Condition], and others), the definition of computable clinical protocols ([http://hl7.org/fhir/plandefinition.html PlanDefinition], [http://hl7.org/fhir/activitydefinition.html ActivityDefinition]), and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of more comprehensive implementation guides and profiles for care management based on FHIR Release 3 (STU), which is the primary target for testing in this track. This connectathon track will be coordinated with evaluation of Care Plan by [http://wiki.hl7.org/index.php?title=Clinician_on_FHIR_2017 Clinicians on FHIR] where they focus on ''clinical interoperability'' and harmonizing differences between the technical and clinical perspectives of FHIR resources.
+
This track is intended to advance the maturity of FHIR resources for care management ([http://hl7.org/fhir/careplan.html CarePlan], [http://hl7.org/fhir/careteam.html CareTeam], [http://hl7.org/fhir/goal.html Goal], [http://hl7.org/fhir/condition.html Condition], and others), the definition of computable clinical protocols ([http://hl7.org/fhir/plandefinition.html PlanDefinition], [http://hl7.org/fhir/activitydefinition.html ActivityDefinition]), and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of more comprehensive implementation guides and profiles for care management based on FHIR Release 3 (STU), which is the primary target for testing in this track. This connectathon track will be coordinated with the Chronic Conditions track at [http://wiki.hl7.org/index.php?title=Clinicians_on_FHIR_-_Jan_2018,_New_Orleans._LA Clinicians on FHIR] where they focus on ''clinical interoperability'' and harmonizing differences between the technical and clinical perspectives of FHIR resources.
  
In addition to advancing the maturity of FHIR resources for care management, this track invites participation by clinicians and implementers who are interested in ''using'' these FHIR standards to realize the benefits of comprehensive shared care management coordinated across provider organizations. Two participant roles are included (CDS Service Requestor & Care Plan Protocol Creator) that engage the practitioner community to evaluate and demonstrate use of FHIR care management resources for the active management of a patient's healthcare.
+
In addition to advancing the maturity of FHIR resources for care management, this track invites participation by clinicians and implementers who are interested in ''using'' these FHIR standards to realize the benefits of comprehensive shared care management coordinated across provider organizations. Two participant roles are included (Care Plan Protocol Creator & CDS Service Requestor) that engage the practitioner community to evaluate and demonstrate use of FHIR care management resources for the active management of a patient's healthcare.
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
Line 49: Line 49:
 
A FHIR server (version 3.0) should support the following resources for this track:
 
A FHIR server (version 3.0) should support the following resources for this track:
 
* CarePlan, CareTeam, Goal, Condition
 
* CarePlan, CareTeam, Goal, Condition
* Other resources as needed for value of CarePlan.activity.reference
+
** Other resources as needed for value of CarePlan.activity.reference
 +
* PlanDefinition and ActivityDefinition
 +
** Bonus points for use of CQL as part of the plan definition
  
 
A FHIR server is available for testing with sample data that represent one or more care plan scenarios.
 
A FHIR server is available for testing with sample data that represent one or more care plan scenarios.
Line 61: Line 63:
 
* 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 enable patients to view, contribute to, or check off completed activities included in a care plan created by their care team member(s).
 
* 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).
 +
 +
===Care Plan Protocol Creator===
 +
* Create and share care protocol definitions via FHIR server endpoint ([http://hl7.org/fhir/plandefinition.html PlanDefinition], [http://hl7.org/fhir/activitydefinition.html ActivityDefinition])
 +
** Care guidelines, e.g. for new diabetes diagnosis, or managing the progression of chronic kidney disease
 +
** Order set definitions that recommend modification of activities in existing care plans, e.g. modify medications based on vital sign or lab observation feedback; see CDS integration
 +
* Generate a [http://hl7.org/fhir/careplan.html CarePlan] from a [http://hl7.org/fhir/plandefinition.html PlanDefinition] protocol, customized using the current [http://hl7.org/fhir/patient.html Patient]'s context
 +
** Uses PlanDefinition [http://hl7.org/fhir/plandefinition-operations.html#apply $apply operation]
  
 
===CDS Service Requestor===
 
===CDS Service Requestor===
Line 71: Line 80:
 
** Recommend additions to care plan activities
 
** Recommend additions to care plan activities
 
*** CDS service uses [http://hl7.org/fhir/plandefinition.html PlanDefinition] protocols for preventive care or chronic condition management
 
*** CDS service uses [http://hl7.org/fhir/plandefinition.html PlanDefinition] protocols for preventive care or chronic condition management
 
===Care Plan Protocol Creator===
 
* Create and share care protocol definitions via FHIR server endpoint ([http://hl7.org/fhir/plandefinition.html PlanDefinition], [http://hl7.org/fhir/activitydefinition.html ActivityDefinition])
 
** Care guidelines, e.g. for new diabetes diagnosis, or managing the progression of chronic kidney disease
 
** Order set definitions that recommend modification of activities in existing care plans, e.g. modify medications based on vital sign or lab observation feedback; see CDS integration
 
* Generate a [http://hl7.org/fhir/careplan.html CarePlan] from a [http://hl7.org/fhir/plandefinition.html PlanDefinition] protocol, customized using the current [http://hl7.org/fhir/patient.html Patient]'s context
 
** Uses PlanDefinition [http://hl7.org/fhir/plandefinition-operations.html#apply $apply operation]
 
  
  
 
==Scenarios==
 
==Scenarios==
This track emphasizes dynamic care management scenarios where one or more care plans are created, accessed, or updated by one or more members of the care team during the provision of healthcare, and the care plan is used by a patient or his/her caregivers to perform assigned activities.  These scenarios illustrate communication flow of care plan(s) between a patient, his or her primary care provider, consulted specialists, home health care, telehealth care, and family caregivers involved in management of care for one or more health conditions.
+
This track emphasizes dynamic care management scenarios where one or more care plans are created, accessed, or updated by one or more members of the care team during the provision of healthcare, and the care plans are used by a patient or his/her caregivers to perform assigned activities.  These scenarios illustrate communication flow of care plan(s) between a patient, his or her primary care provider, consulted specialists, home health care, telehealth care, and family caregivers involved in management of care for one or more health conditions.
 
 
===Chronic Conditions===
 
This scenario is based on Section 3.4 of the [http://wiki.hl7.org/index.php?title=Care_Plan_Project_-_PCWG#Care_Plan_Domain_Analysis_Model_.28DAM.29_Documents HL7 Care Plan Domain Analysis Model (DAM)] documents dated 2015-11-04.
 
* Primary Care Plan
 
** Patient has a current care plan for one or more pre-existing condition (e.g. Hypertension, COPD, Depression, etc.)
 
* Diagnosis of a new condition (e.g. Diabetes)
 
** Update the care plan to reference the new Condition, Goal(s) for care, and intervention activities
 
** Add members to the care team, as needed
 
* Include patient-assigned goals and activities
 
** daily measurement of blood pressure, blood glucose, etc.
 
** daily or weekly exercise goals
 
** scheduled follow-up appointments, or patient-assigned activities to schedule future appointment(s)
 
 
 
===Multi-Provider Care Coordination===
 
  
* Primary Care Physician (PCP)
+
===Chronic Care Management===
** PCP manages care for existing conditions, as in the first scenario
+
This scenario is based on the [https://www.niddk.nih.gov/health-information/communication-programs/nkdep/working-groups/health-information-technology/development-electronic-ckd-care-plan NIH Chronic Kidney Disease (CKD) Care Plan project].
* Specialist referral to a different provider organization
+
* Summarize...
** e.g. referral to OB/GYN for prenatal care, or to physical therapist for rehab
 
* Specialist practitioner creates a new care plan using his/her organization's EHR system
 
* Coordinate and notify care plan updates between provider organizations
 
  
==Clinical Domain Scenarios==
 
These clinical scenarios are complementary to the general care planning and care coordination scenarios listed in the previous section. Each clinical scenario described below is based on contributions from communities interested in solutions using FHIR Care Plan.
 
  
===Maternity Care Coordination===
 
This scenario is based on a [https://veteransaffairsuxguide.com/practice-areas/user-personas/ realistic Veteran Persona developed by the U.S. Department of Veterans Affairs], but may also represent coordination of care for any pregnancy. "Meghan" is a post-9/11 Veteran who served in Afghanistan and is recovering from a Traumatic Brain Injury (TBI) and PTSD. Meghan recently became pregnant with her third child and is coordinating care plans between her primary care provider at VA and a community provider outside of VA for her OB/GYN and prenatal care. Meghan has concerns about possible negative effects from Teratogenic medications prescribed for her TBI-caused seizures and PTSD anxiety.
 
  
 
* Test data JSON files for Meghan's care plans are [https://github.com/clinical-cloud/sample-data available in a GitHub repository] and may be loaded into any FHIR v3.0 server.
 
* Test data JSON files for Meghan's care plans are [https://github.com/clinical-cloud/sample-data available in a GitHub repository] and may be loaded into any FHIR v3.0 server.

Revision as of 17:59, 22 January 2018

Return to Jan 2018 Proposals

Care Management and Planning

Dedicated Zulip chat stream for this track.

Previous Care Plan Connectathons

Summary presentation slides after conclusion of Care Management track

  • Presentation slides TBD

Submitting WG/Project/Implementer Group

Justification

This track is intended to advance the maturity of FHIR resources for care management (CarePlan, CareTeam, Goal, Condition, and others), the definition of computable clinical protocols (PlanDefinition, ActivityDefinition), and to document industry best practices for improving care coordination using shared care plans. This work will inform the development of more comprehensive implementation guides and profiles for care management based on FHIR Release 3 (STU), which is the primary target for testing in this track. This connectathon track will be coordinated with the Chronic Conditions track at Clinicians on FHIR where they focus on clinical interoperability and harmonizing differences between the technical and clinical perspectives of FHIR resources.

In addition to advancing the maturity of FHIR resources for care management, this track invites participation by clinicians and implementers who are interested in using these FHIR standards to realize the benefits of comprehensive shared care management coordinated across provider organizations. Two participant roles are included (Care Plan Protocol Creator & CDS Service Requestor) that engage the practitioner community to evaluate and demonstrate use of FHIR care management resources for the active management of a patient's healthcare.

Proposed Track Lead

Dave Carlson – VHA
E-mail: dcarlson@ClinicalCloud.solutions
Zulip: Dave Carlson

Expected participants

The following organizations have indicated an interest in participating in this track:

  • Allscripts
  • Clinical Cloud Solutions
  • Healthcare Services Platform Consortium (HSPC)
  • InterSystems
  • Veterans Health Administration (VHA)
  • Zynx Health
  • Your organization here!

Roles

Care Plan Server

A FHIR server (version 3.0) should support the following resources for this track:

  • CarePlan, CareTeam, Goal, Condition
    • Other resources as needed for value of CarePlan.activity.reference
  • PlanDefinition and ActivityDefinition
    • Bonus points for use of CQL as part of the plan definition

A FHIR server is available for testing with sample data that represent one or more care plan scenarios.

Care Plan Requestor

This connectathon track imposes few requirements for interested participants to evaluate and test retrieval of care plan resources from a Care Plan Server. We wish to encourage discussion and testing that will lead to robust industry support for shared care plans. Thus, a requestor role could be fulfilled by a range of applications, such as the following:

  • Debug testing tools for RESTful services, e.g. Postman, that allow query of participating Care Plan Server 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).

Care Plan Protocol Creator

  • Create and share care protocol definitions via FHIR server endpoint (PlanDefinition, ActivityDefinition)
    • Care guidelines, e.g. for new diabetes diagnosis, or managing the progression of chronic kidney disease
    • Order set definitions that recommend modification of activities in existing care plans, e.g. modify medications based on vital sign or lab observation feedback; see CDS integration
  • Generate a CarePlan from a PlanDefinition protocol, customized using the current Patient's context

CDS Service Requestor

  • 201801_CDS_Hooks
  • Invoke a CDS Hooks Service that guides a clinician or a patient toward fulfillment of a Care Plan's goals, or suggests additional activities based on clinical practice guidelines. The CDS Hooks Service provides real-time clinical decision support as a remote service, where the CDS Server is invoked on a desired hook and returns the decision support in the form of CDS cards.
    • Evaluate progress toward care plan goals
      • Invoke 'patient-view' hook on all known CDS service endpoints
      • Query and analyze relevant Observations related to a Goal target measure (e.g. blood glucose, weight, etc.)
      • Notify care team members when insufficient progress
    • Recommend additions to care plan activities
      • CDS service uses PlanDefinition protocols for preventive care or chronic condition management


Scenarios

This track emphasizes dynamic care management scenarios where one or more care plans are created, accessed, or updated by one or more members of the care team during the provision of healthcare, and the care plans are used by a patient or his/her caregivers to perform assigned activities. These scenarios illustrate communication flow of care plan(s) between a patient, his or her primary care provider, consulted specialists, home health care, telehealth care, and family caregivers involved in management of care for one or more health conditions.

Chronic Care Management

This scenario is based on the NIH Chronic Kidney Disease (CKD) Care Plan project.

  • Summarize...