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

Difference between revisions of "201701 Clinical Reasoning Track"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 1: Line 1:
 
+
[http://wiki.hl7.org/index.php?title=Category:201701_FHIR_Connectathon_Track_Proposals Return to January 2017 Proposals]
 
[[Category:201701_FHIR_Connectathon_Track_Proposals|Jan 2017 Proposals]]
 
[[Category:201701_FHIR_Connectathon_Track_Proposals|Jan 2017 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=Clinical Reasoning Track=
 +
 
 +
This track defines several scenarios related to clinical quality that exercise the resources defined by the Clinical Decision Support and Clinical Quality Information Work Groups, as well as profiles and usage guidance defined in the Clinical Quality Framework Implementation Guide.
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
+
*[[Clinical_Decision_Support_Workgroup|Clinical Decision Support Work Group]]
 +
*[[Clinical_Quality_Information_Work_Group|Clinical Quality Information Work Group]]
 +
*[http://cqframework.info Clinical Quality Framework Initiative]
  
 
==Justification==
 
==Justification==
 +
 +
The CDS and CQI Work Groups are incorporating feedback from previous ballots, prior connect-a-thons, as well as other work groups to refine and improve the structures used to enable the representation and evaluation of quality artifacts using FHIR. These efforts have resulted in several resources and related implementation guides that will be balloted both as part of the FHIR STU 3 ballot and as separate implementation guides in the upcoming September 2016 ballot cycle. The scenarios in this connect-a-thon track proposal are intended to support that ballot by exercising key resources and use cases in the implementation guides.
 +
 
<!--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. -->
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
 
 +
* Bryn Rhodes
 +
** Email: bryn at databaseconsultinggroup dot com
 +
** Skype: bryn.rhodes
 +
 
 
See [[Connectathon_Track_Lead_Responsibilities]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
  
 
==Expected participants==
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 +
 +
* National Comprehensive Cancer Care Network (NCCN)
 +
* Evinance
 +
* ESAC, Inc.
 +
* HarmonIQ Health Systems Corporation
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
===Guidance Service===
===Role 1 Name===
+
The Guidance Service role provides real-time clinical decision support services. This component enables a consumer to request clinical decision support based on the current context. The consumer provides relevant contextual information as part of the request, and receives clinically relevant guidance as a set of resources describing potential actions to be taken.
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
 
 +
===Guidance Client===
 +
The Guidance Client role consumes real-time clinical decision support services. The client integrates decision support at appropriate points in clinical workflow, allowing users of the system to respond to the guidance presented by the decision support system.
 +
 
 +
===Knowledge Management Repository===
 +
A FHIR Server that implements search and retrieval functionality for the various quality artifact resources.
 +
 
 +
===Knowledge Artifact Consumer===
 +
A system that consumes knowledge artifacts from a knowledge management repository
 +
 
 +
===Order Set Service===
 +
A service capable of evaluating order set definitions to produce order sets applicable to a specific patient and/or context.
 +
 
 +
===Order Set Client===
 +
A client capable of requesting the evaluation of an order set definition for a specific patient and/or context, and consuming the resulting order set instance.
 +
 
 +
===InfoButton Service===
 +
A service that exposes an InfoButton decision support service module and implements the $evaluate operation to return InfoButton guidance.
 +
 
 +
===InfoButton Client===
 +
A client that consumes InfoButton documentation via the $evaluate operation and a GuidanceResponse.
 +
 
 +
===Measure Reporting Service===
 +
A system that provides measure evaluation results
  
 
==Scenarios==
 
==Scenarios==
<!-- What will be the actions performed by participants? -->
+
 
 +
The [http://build.fhir.org/clinicalreasoning-module.html Clinical Reasoning Module] provides documentation for the resources that will be exercised by the above roles. Specifically, the following resources are utilized as part of those scenarios:
 +
 
 +
*[http://build.fhir.org/activitydefinition.html ActivityDefinition]
 +
*[http://build.fhir.org/guidanceresponse.html GuidanceResponse]
 +
*[http://build.fhir.org/library.html Library]
 +
*[http://build.fhir.org/measure.html Measure]
 +
*[http://build.fhir.org/plandefinition.html PlanDefinition]
 +
*[http://build.fhir.org/requestgroup.html RequestGroup]
 +
*[http://build.fhir.org/servicedefinition.html ServiceDefinition]
  
 
===Scenario Step 1 Name===
 
===Scenario Step 1 Name===
Line 32: Line 80:
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
  
<!-- Provide a description of each task -->
+
===NCCN Chemotherapy Regimen Scenario===
 +
 
 +
In this scenario, a Knowledge Artifact Provider defines and distributes an NCCN Chemotherapy Regimen to a Knowledge Artifact Consumer.
 +
 
 +
====Create an Order Template====
 +
 
 +
====Search for an Order Template====
 +
 
 +
====Ingest an Order Template====
 +
 
 +
====Apply an Order Template for a specific patient====
 +
 
 +
====Determine Adherence (On/Off Protocol)====
 +
 
 +
===Zika Virus Reporting Scenario===
 +
 
 +
In this scenario, a patient presents at the point-of-care, and Zika Virus management is triggered if the patient is a woman of child-bearing age. As an alternative, Zika Virus management may be triggered by a mobile application that detects travel to an area where Zika exposure is an identified risk.
 +
 
 +
===Payer Extract Scenario===
 +
 
 +
In this scenario, a Payer uses a Measure Processing Component to extract relevant data from an EHR to enable computation of payer quality measures.
  
 
==TestScript(s)==
 
==TestScript(s)==

Revision as of 22:08, 31 October 2016

Return to January 2017 Proposals

Clinical Reasoning Track

This track defines several scenarios related to clinical quality that exercise the resources defined by the Clinical Decision Support and Clinical Quality Information Work Groups, as well as profiles and usage guidance defined in the Clinical Quality Framework Implementation Guide.

Submitting WG/Project/Implementer Group

Justification

The CDS and CQI Work Groups are incorporating feedback from previous ballots, prior connect-a-thons, as well as other work groups to refine and improve the structures used to enable the representation and evaluation of quality artifacts using FHIR. These efforts have resulted in several resources and related implementation guides that will be balloted both as part of the FHIR STU 3 ballot and as separate implementation guides in the upcoming September 2016 ballot cycle. The scenarios in this connect-a-thon track proposal are intended to support that ballot by exercising key resources and use cases in the implementation guides.


Proposed Track Lead

  • Bryn Rhodes
    • Email: bryn at databaseconsultinggroup dot com
    • Skype: bryn.rhodes

See Connectathon_Track_Lead_Responsibilities

Expected participants

  • National Comprehensive Cancer Care Network (NCCN)
  • Evinance
  • ESAC, Inc.
  • HarmonIQ Health Systems Corporation

Roles

Guidance Service

The Guidance Service role provides real-time clinical decision support services. This component enables a consumer to request clinical decision support based on the current context. The consumer provides relevant contextual information as part of the request, and receives clinically relevant guidance as a set of resources describing potential actions to be taken.

Guidance Client

The Guidance Client role consumes real-time clinical decision support services. The client integrates decision support at appropriate points in clinical workflow, allowing users of the system to respond to the guidance presented by the decision support system.

Knowledge Management Repository

A FHIR Server that implements search and retrieval functionality for the various quality artifact resources.

Knowledge Artifact Consumer

A system that consumes knowledge artifacts from a knowledge management repository

Order Set Service

A service capable of evaluating order set definitions to produce order sets applicable to a specific patient and/or context.

Order Set Client

A client capable of requesting the evaluation of an order set definition for a specific patient and/or context, and consuming the resulting order set instance.

InfoButton Service

A service that exposes an InfoButton decision support service module and implements the $evaluate operation to return InfoButton guidance.

InfoButton Client

A client that consumes InfoButton documentation via the $evaluate operation and a GuidanceResponse.

Measure Reporting Service

A system that provides measure evaluation results

Scenarios

The Clinical Reasoning Module provides documentation for the resources that will be exercised by the above roles. Specifically, the following resources are utilized as part of those scenarios:

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:

NCCN Chemotherapy Regimen Scenario

In this scenario, a Knowledge Artifact Provider defines and distributes an NCCN Chemotherapy Regimen to a Knowledge Artifact Consumer.

Create an Order Template

Search for an Order Template

Ingest an Order Template

Apply an Order Template for a specific patient

Determine Adherence (On/Off Protocol)

Zika Virus Reporting Scenario

In this scenario, a patient presents at the point-of-care, and Zika Virus management is triggered if the patient is a woman of child-bearing age. As an alternative, Zika Virus management may be triggered by a mobile application that detects travel to an area where Zika exposure is an identified risk.

Payer Extract Scenario

In this scenario, a Payer uses a Measure Processing Component to extract relevant data from an EHR to enable computation of payer quality measures.

TestScript(s)