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

Difference between revisions of "201801 Care Plan"

From HL7Wiki
Jump to navigation Jump to search
Line 53: Line 53:
 
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.
 
* HSPC sandbox server (FHIR 3.0.1) at https://api-stu3.hspconsortium.org/careplantest/open
 
* 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.
+
* Test data JSON files with several patient care plans 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===
Line 71: Line 71:
  
 
===CDS Service Requestor===
 
===CDS Service Requestor===
* [[201801_CDS_Hooks]]
+
* Coordinate with  [[201801_CDS_Hooks]] track
 
* 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.
 
* 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.
  
Line 79: Line 79:
 
===Chronic Care Management===
 
===Chronic Care Management===
 
This recommended clinical 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]. Because frequent transitions of care are common among patients with CKD, an electronic CKD care plan could potentially improve patient outcomes by helping to ensure that critical patient data are consistently available to both the patient and his/her providers.
 
This recommended clinical 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]. Because frequent transitions of care are common among patients with CKD, an electronic CKD care plan could potentially improve patient outcomes by helping to ensure that critical patient data are consistently available to both the patient and his/her providers.
* Personas
+
* Persona descriptions for patients with CKD and their care team members are available:
 +
** [https://www.niddk.nih.gov/-/media/Files/Health-Information/Communication-Programs/NKDEP/Patient_Personas_508.pdf?la=en Patient personas], out sample data is based on Betsy Johnson's persona
 +
** [https://www.niddk.nih.gov/-/media/Files/Health-Information/Communication-Programs/NKDEP/Provider_Personas_508.pdf?la=en Provider personas] for six members of a CKD patient's care team
 
* Data elements
 
* Data elements
 
* 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.
 +
** JSON sample FHIR resources for persona Betsy Johnson, contributions welcome!  See https://github.com/clinical-cloud/sample-data/chronic-conditions
 +
** These sample data are also loaded into this track's HSPC sandbox server,  https://api-stu3.hspconsortium.org/careplantest/open
  
 
===Scenario 1: Search a patient's care plan(s)===
 
===Scenario 1: Search a patient's care plan(s)===

Revision as of 22:18, 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
  • Cerner
  • 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 role:

  • CarePlan, Condition, Goal, CareTeam, and other resources referenced by 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).

Care Plan Protocol Creator

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

  • Create and share care protocol definitions via FHIR server endpoint
    • 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

CDS Service Requestor

  • Coordinate with 201801_CDS_Hooks track
  • 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.

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 recommended clinical scenario is based on the NIH Chronic Kidney Disease (CKD) Care Plan project. Because frequent transitions of care are common among patients with CKD, an electronic CKD care plan could potentially improve patient outcomes by helping to ensure that critical patient data are consistently available to both the patient and his/her providers.

Scenario 1: Search a patient's care plan(s)

Search for a patient's care plans(s) and associated resources (Conditions, Goals, activity references, CareTeam)

  • User client application
  • Server
    • e.g. a population health or analytics product vendor retrieves a patient's care plans and related resources for aggregation, analysis, and sharing with other care team members

Scenario 2: Create new care plan from protocol definition

Scenario 3: Request CDS 'patient-view' hook

  • Invoke 'patient-view' hook on one or more CDS Hook service providers
  • Display returned cards
    • Cards may include any combination of information (for reading), suggested actions (to be applied if a user selects them), and links (to launch an app if the user selects them). The EHR decides how to display cards, but CDS Hooks specification recommends displaying suggestions using buttons, and links using underlined text.

Example clinical scenarios for integrating CDS:

  • Evaluate progress toward care plan goals
    • Query and analyze relevant Observations related to a Goal target measure (e.g. blood glucose, weight, etc.)
    • Return CDS Hook cards notifying care team members about lack of progress on goal targets
  • Recommend additions to care plan activities based on current Patient status or revised diagnoses
    • Recommendations based on protocols for preventive care or chronic condition management