This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201709 Care Plan"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "[http://wiki.hl7.org/index.php?title=Category:201709_FHIR_Connectathon_Track_Proposals Return to September 2017 Proposals] Category:201709_FHIR_Connectathon_Track_Proposals|...")
 
 
(44 intermediate revisions by the same user not shown)
Line 1: Line 1:
[http://wiki.hl7.org/index.php?title=Category:201709_FHIR_Connectathon_Track_Proposals Return to September 2017 Proposals]
+
[[FHIR_Connectathon_16 | Return to September 2017 FHIR Connectathon 16]]
 
[[Category:201709_FHIR_Connectathon_Track_Proposals|September 2017 Proposals]]
 
[[Category:201709_FHIR_Connectathon_Track_Proposals|September 2017 Proposals]]
 
{| align="right"
 
{| align="right"
 
| __TOC__
 
| __TOC__
 
|}
 
|}
=Care Plan and Care Team=
+
=Care Plan=
  
'''Dedicated [https://chat.fhir.org/#narrow/stream/implementers/topic/201709.20Care.20Plan.20Track Zulip chat stream] for this track.'''
+
'''Dedicated [https://chat.fhir.org/#narrow/stream/connectathon.20mgmt/subject/C16.20Care.20Plan.20Track Zulip chat stream] for this track.'''
 +
 
 +
==Submitting WG/Project/Implementer Group==
 +
* [[Patient_Care | HL7 Patient Care Workgroup]]
 +
* [http://hspconsortium.org Healthcare Services Platform Consortium (HSPC)]
  
 
'''Previous Care Plan Connectathons'''
 
'''Previous Care Plan Connectathons'''
 
* [[201701 Care Plan]], January 2017, San Antonio, TX
 
* [[201701 Care Plan]], January 2017, San Antonio, TX
* [[Value-Based Care FHIR Connectathon 201704]], April 2017, Chicago, IL
+
* [[201704 Care Plan]], April 2017, Chicago, IL
 
 
==Submitting WG/Project/Implementer Group==
 
[[Patient_Care | Patient Care Workgroup]]
 
  
[http://hspconsortium.org Healthcare Services Platform Consortium (HSPC)]
+
'''Summary presentation slides after conclusion of CarePlan track'''
 +
* Presentation slides [http://wiki.hl7.org/images/c/c7/CarePlanTrackSummary_September-2017.pdf as PDF], or [http://wiki.hl7.org/images/0/00/CarePlanTrackSummary_September-2017.pptx as PowerPoint]
  
 
==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 planning ([http://hl7.org/fhir/2016Sep/careplan.html CarePlan], [http://hl7.org/fhir/2016Sep/careteam.html CareTeam], [http://hl7.org/fhir/2016Sep/goal.html Goal], [http://hl7.org/fhir/2016Sep/condition.html Condition], and others) 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 planning based on FHIR release 3. The January 2017 published build of FHIR STU-3 is the primary target for testing in this track. However, we recognize that there are organizations with DSTU-2 implementations (e.g. from the HL7 Argonaut Project) that are deploying support for CarePlan, and we'd like to invite those organizations to participate in this connectathon track and share lessons learned from implementation.
+
This track is intended to advance the maturity of FHIR resources for care planning ([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) 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 planning based on FHIR Release 3 (STU), which is the primary target for testing in this track. This connectathon track will be coordinated with testing of CarePlan by [http://wiki.hl7.org/index.php?title=Clinicians_on_FHIR_-_Sept_2017,_San_Diego Clinicians on FHIR] where they focus on ''clinical interoperability'' and harmonizing differences between the technical and clinical perspectives of FHIR resources.
 
 
This connectathon track will be coordinated with testing of CarePlan by [http://wiki.hl7.org/index.php?title=Clinician_on_FHIR_-_January_2017,_San_Antonio HL7 Clinicians on FHIR] where they focus on ''clinical interoperability'' and harmonizing differences between the technical and clinical perspectives of FHIR resources. Clinicians on FHIR has met at each HL7 WGM since May 2014 and has the following objectives:
 
* to test the accuracy, validity and usability of clinical resources
 
* to identify any issues arising from clinical use of clinical resources tested
 
* to provide recommendations to enhance/improve the clinical resources tested
 
* to identify lessons learnt such that future FHIR resources development methodology and processes may be improved
 
  
 
The U.S. Department of Health and Human Services (HHS) recently published an article that describes a vision for a [http://catalyst.nejm.org/making-the-comprehensive-shared-care-plan-a-reality/ Comprehensive Shared Care Plan (CSCP)]. HHS identifies these goals for a CSCP:
 
The U.S. Department of Health and Human Services (HHS) recently published an article that describes a vision for a [http://catalyst.nejm.org/making-the-comprehensive-shared-care-plan-a-reality/ Comprehensive Shared Care Plan (CSCP)]. HHS identifies these goals for a CSCP:
Line 33: Line 29:
 
* It should follow the person through high-need episodes (e.g., acute illness), as well as periods of health improvement and maintenance.
 
* It should follow the person through high-need episodes (e.g., acute illness), as well as periods of health improvement and maintenance.
  
==Proposed Track Leads==
+
In addition to advancing the maturity of FHIR resources for care planning, this track invites participation by clinicians and implementers who are interested in ''using'' these FHIR standards to achieve the vision of comprehensive shared care plans. As a first step toward this vision, we have included a new participant role, CDS Service Requestor, that begins to evaluate and demonstrate use of FHIR care planning resources for the active management of a patient's healthcare.
 +
 
 +
==Proposed Track Lead==
 
:Dave Carlson &ndash; VA
 
:Dave Carlson &ndash; VA
 
::E-mail:  Dave.Carlson@BookZurman.com
 
::E-mail:  Dave.Carlson@BookZurman.com
 
::Zulip:  Dave Carlson
 
::Zulip:  Dave Carlson
 
:Russ Leftwich MD &ndash; InterSystems (Clinical Lead)
 
::E-mail:  Russell.Leftwich@intersystems.com
 
  
 
==Expected participants==
 
==Expected participants==
Participants using both FHIR STU-3 and DSTU-2 are welcome! Including a mix of FHIR versions will reduce opportunities for interoperability testing, but all participants will benefit from discussion and comparing implementations of FHIR support for care plans and care coordination. Test data prepared for this connectathon track will be based on the January 2017 published build of FHIR STU-3, including use of the the new STU-3 resource for CareTeam.
 
 
 
The following organizations have indicated an interest in participating in this track:
 
The following organizations have indicated an interest in participating in this track:
  
* VA &ndash; Dave Carlson
+
* VA
* HSPC &ndash; Dave Carlson
+
* HSPC
* InterSystems &ndash; Russ Leftwich MD (clinical)
+
* Allscripts
* Allscripts &ndash; Emma Jones (clinical)
+
* InterSystems
* HarmonIQ Health Systems Corporation
 
* A|D Vault, Inc.
 
* ZeOmega, Inc.
 
* Janie Appleseed powered by MaxMD
 
 
 
 
* ''Your organization here!''
 
* ''Your organization here!''
 
==Questions for Discussion==
 
* Review of existing FHIR profiles on CarePlan and CareTeam, including but not limited to:
 
** [http://hl7.org/fhir/us/core/index.html US-Core IG] profiles (formerly DAF-Core profiles)
 
** IHE PCC Dynamic Care Plan
 
* ValueSet bindings &ndash; '''Note:''' work is underway by ONC and HL7 to define these value sets
 
** CarePlan.category
 
** CarePlan.detail.category
 
** CarePlan.detail.code
 
** CareTeam.type
 
** CareTeam.participant.role
 
  
 
==Roles==
 
==Roles==
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 +
 +
===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
 +
 +
A FHIR server is available for testing with sample data that represent one or more care plan scenarios.
 +
* HSPC sandbox server (FHIR 3.0.1) at https://api-stu3.hspconsortium.org/careplantest/open
 +
* Test data JSON files are [https://github.com/clinical-cloud/sample-data available in a GitHub repository] that may be loaded into other FHIR v3.0 servers.
  
 
===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, a requestor role could be fulfilled by a range of applications, such as the following:
+
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 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 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 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 [http://hl7.org/fhir/2016Sep/goal.html Goals] to a plan created by their primary care physician.
+
* 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).
* Provider EMR or Care Plan Management solution that allows a provider to request and/or accept information from a patient that can be used when creating or updating the person's care plan. (Patient Voice Scenario)
 
 
 
===Care Plan Responder===
 
A responder FHIR server should support the following resources for this track:
 
* Patient
 
* CarePlan
 
* CareTeam (when using STU-3)
 
* Goal
 
* Condition
 
* Other resources as needed for value of CarePlan.activity.reference
 
 
 
For robust support of CareTeam, responder should also support:
 
* Practitioner
 
* RelatedPerson
 
* Organization
 
* Patient (See Patient Voice Scenario)
 
  
Default responder service for testing, and sample data for loading into FHIR servers:
+
===CDS Service Requestor===
* HSPC sandbox server, STU3 FHIR 1.8.0, contains all test resources for Diabetes storyboard scenario
+
* [[201709_CDS_Hooks]]
** https://api3.hspconsortium.org/fhirconnect14/open
+
* Invoke a [http://cds-hooks.org/ 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.
* See the Type II Diabetes Mellitus use case section below for a GitHub link to FHIR transaction Bundle files with test data that may be loaded into FHIR STU-3 v1.8.0 servers.
+
** Evaluate progress toward care plan goals
** [https://github.com/clinical-cloud/sample-careplans/raw/master/Care%20Plan%20Storyboard%20-%20Diabetes%20Mellitus.pdf Type II Diabetes Mellitus] storyboard as PDF
+
*** 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 clinical practice guidelines for preventive care or chronic condition management
  
===Care Plan Creator===
+
==Optional Roles==
* Generate a CarePlan from a [http://hl7.org/fhir/2016Sep/plandefinition.html PlanDefinition] for protocols or care pathways, customized using the current Patient's context.
 
* Using a SMART on FHIR application that enables care team members working within existing EHR systems to add/edit Goals, activity details, schedule, or other aspects of a Care Plan.
 
* Generate a Personal Advance Care Plan document that permits a patient to share his or her care goals, preferences and priorities with with care providers so this information can be taking into consideration when making a care plan in circumstance when the person can't communicate this information for his or herself.
 
  
==Basic Resource Scenarios==
+
* [[201709_FHIR_Subscriptions]]
Two sets of scenarios are included in this connectathon track. The first Basic Resource Scenarios describe interactions with a FHIR server to support care planning and may be implemented on existing EHR systems or using generic FHIR servers. The second Use Case Scenarios describe more advanced and realistic interactions required for dynamic care planning and care coordination.
 
  
===Search for all Care Plans for a patient===
+
* [[201709_Provider_Directories_and_Scheduling]]
This is intended as a "getting started" scenario with minimal requirements for Requestors and Respondors.
 
  
:Action: Server and Client support query of CarePlan based on patient.id using '''GET [base]/CarePlan?patient=[id]'''
 
:Bonus point: Search for all of a patient's Care Plans with a specific category, e.g. cancer care plan
 
:* query CarePlan based on patient.id and category = "395082007" using '''GET [base]/CarePlan?patient=[id]&category=395082007'''
 
  
===Search for all Care Teams for a patient===
+
==Scenarios==
This is another "getting started" scenario with minimal requirements for Requestors and Respondors.
+
This track emphasizes dynamic care planning scenarios where the care plan is 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.
  
:Action: Server and Client support query of CareTeam based on patient.id using '''GET [base]/CareTeam?patient=[id]'''
+
===Chronic Conditions===
:Precondition: Server implements FHIR STU-3.
+
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)
  
===Search for all Care Plans where the given Practioner is a member of the Care Team===
+
===Multi-Provider Care Coordination===
:Action: Search CarePlan (''TODO: example of search parameters'')
 
:Bonus point: Filter Care Plans to include only those for a given Condition, e.g. Diabetes
 
  
===Display Care Plan activity definitions===
+
* Primary Care Physician (PCP)
We are interested in implementer feedback on the two alternatives included for expressing care plan activities: as a reference to another resource (e.g. DiagnosticRequest, ProcedureRequest, etc.) or by describing the activity detail with schedule, performer, quantity, etc.
+
** PCP manages care for existing conditions, as in the first scenario
 +
* Specialist referral to a different provider organization
 +
** 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
  
* CarePlan.activity.reference
+
==Clinical Domain Scenarios==
* CarePlan.activity.detail
+
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.
  
==Use Case Scenarios==
+
===Prenatal Care Coordination===
This track is coordinating test scenarios with [http://wiki.hl7.org/index.php?title=Clinician_on_FHIR_-_January_2017,_San_Antonio#Care_Plan Clinicians on FHIR CarePlan testing] that will occur on Friday following the connectathon at HL7. Participants should study the planning notes on that wiki page and be prepared to provide technical input experience on those topics. The track scenarios are also based on 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. They emphasize dynamic care planning clinical scenarios where the care plan is created, accessed, updated or used by multiple providers during the provision of healthcare.
+
This scenario is based on a 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 of her PTSD anti-anxiety medication on her new baby.  
  
===Type II Diabetes Mellitus===
+
The key actors in this scenario are:
The purpose of the chronic conditions care plan scenario is to illustrate the communication flow and documentation of a care plan between a patient, his or her primary care provider and the home health
+
* Meghan, the patient
specialists involved in the ''discovery and treatment of a case of Type II Diabetes Mellitus''.  This storyboard is based on Section 3.4 of the HL7 Care Plan DAM. This health issue thread (simplified) consists of four encounters, although in reality there could be many more encounters:
+
* Dr. Francis, MD, primary care provider at VA
* Primary Care Physician Initial Visit
+
* Dr.Beach, PsyD, VA Psychotherapist counselor for Meghan's PTSD and anxiety conditions
* Dietitian
+
* Vera, RN, the Maternity Care Coordinator (MCC) at VA helps manage Meghan's non-VA prenatal care
* Podiatrist
+
* Dr. Rattle, OB/GYN from non-VA provider, responsible for Meghan's prenatal care plan
* Primary Care Follow-up Visits
 
  
Storyboard document and test data:
+
===Malnutrition Care Coordination===
* A storyboard for the [https://github.com/clinical-cloud/sample-careplans/raw/master/Care%20Plan%20Storyboard%20-%20Diabetes%20Mellitus.pdf Type II Diabetes Mellitus] scenario was prepared to guide Connectathon participants.
+
This scenario was created by the [[Nutrition_Management | HL7 Nutrition Management project team]].
* Test data JSON files for this storyboard are [https://github.com/clinical-cloud/sample-careplans available in a GitHub repository] based on FHIR v1.8.0, the Jan 2017 build prepared for this Connectathon.
 
  
==TestScript(s)==
+
An elderly male (70 year old) with existing conditions (previous smoker with lung cancer &amp; COPD), living alone in home with limited income, recent unintended wt loss >20 lbs. Admitted to hospital due to injury from a fall.
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested. 
+
* Malnutrition screen
These should be committed to SVN under trunk/connectathons/[connectathon]
+
** [https://static.abbottnutrition.com/cms-prod/abbottnutrition-2016.com/img/Malnutrition%20Screening%20Tool_FINAL_tcm1226-57900.pdf Malnutrition Screening Tool] (3 part questionnaire, validated screening tool) = 2 (at risk)
-->
+
* Nutrition/Dietitian Consult Order (inpatient) (Referral Request)
 +
* Nutrition Assessment performed by dietitian including nutrition focused physical exam with findings of muscle wasting and loss of subcutaneous fat, poor daily intake < estimated nutrient needs
 +
** Explore using new method of recording actual/reported intake by patient
 +
*Nutrition Care Plan developed including reference to:
 +
**Nutrition Intervention &ndash; Nutrition Orders to modify diet and add high calorie/high protein oral nutritional supplement 2x/day (see [http://hl7.org/fhir/nutritionorder.html NutritionOrder] Resource)
 +
**Nutrition Education &ndash; referral to outpatient dietitian for follow-up
 +
* Care Coordination &ndash; (referral for community services - e.g. Meals on Wheels, and Home Health Services upon discharge)
 +
* Care plans should be updated and shared with outpatient dietitian, PCP and Home Health Agency, patient, and family caregiver (daughter)

Latest revision as of 19:31, 10 September 2017

Return to September 2017 FHIR Connectathon 16

Care Plan

Dedicated Zulip chat stream for this track.

Submitting WG/Project/Implementer Group

Previous Care Plan Connectathons

Summary presentation slides after conclusion of CarePlan track

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 more comprehensive implementation guides and profiles for care planning based on FHIR Release 3 (STU), which is the primary target for testing in this track. This connectathon track will be coordinated with testing of CarePlan by Clinicians on FHIR where they focus on clinical interoperability and harmonizing differences between the technical and clinical perspectives of FHIR resources.

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.

In addition to advancing the maturity of FHIR resources for care planning, this track invites participation by clinicians and implementers who are interested in using these FHIR standards to achieve the vision of comprehensive shared care plans. As a first step toward this vision, we have included a new participant role, CDS Service Requestor, that begins to evaluate and demonstrate use of FHIR care planning resources for the active management of a patient's healthcare.

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
  • HSPC
  • Allscripts
  • InterSystems
  • 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

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).

CDS Service Requestor

  • 201709_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 clinical practice guidelines for preventive care or chronic condition management

Optional Roles


Scenarios

This track emphasizes dynamic care planning scenarios where the care plan is 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.

Chronic Conditions

This scenario is based on Section 3.4 of the 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)
    • PCP manages care for existing conditions, as in the first scenario
  • Specialist referral to a different provider organization
    • 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.

Prenatal Care Coordination

This scenario is based on a 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 of her PTSD anti-anxiety medication on her new baby.

The key actors in this scenario are:

  • Meghan, the patient
  • Dr. Francis, MD, primary care provider at VA
  • Dr.Beach, PsyD, VA Psychotherapist counselor for Meghan's PTSD and anxiety conditions
  • Vera, RN, the Maternity Care Coordinator (MCC) at VA helps manage Meghan's non-VA prenatal care
  • Dr. Rattle, OB/GYN from non-VA provider, responsible for Meghan's prenatal care plan

Malnutrition Care Coordination

This scenario was created by the HL7 Nutrition Management project team.

An elderly male (70 year old) with existing conditions (previous smoker with lung cancer & COPD), living alone in home with limited income, recent unintended wt loss >20 lbs. Admitted to hospital due to injury from a fall.

  • Malnutrition screen
  • Nutrition/Dietitian Consult Order (inpatient) (Referral Request)
  • Nutrition Assessment performed by dietitian including nutrition focused physical exam with findings of muscle wasting and loss of subcutaneous fat, poor daily intake < estimated nutrient needs
    • Explore using new method of recording actual/reported intake by patient
  • Nutrition Care Plan developed including reference to:
    • Nutrition Intervention – Nutrition Orders to modify diet and add high calorie/high protein oral nutritional supplement 2x/day (see NutritionOrder Resource)
    • Nutrition Education – referral to outpatient dietitian for follow-up
  • Care Coordination – (referral for community services - e.g. Meals on Wheels, and Home Health Services upon discharge)
  • Care plans should be updated and shared with outpatient dietitian, PCP and Home Health Agency, patient, and family caregiver (daughter)