Difference between revisions of "Computable Care Guidelines"

From IHE Wiki
Jump to navigation Jump to search
 
(21 intermediate revisions by one other user not shown)
Line 1: Line 1:
  
The Computable Care Guidelines (CCG) profile supports the expression of and sharing of health care guidelines in a grammar that can be ingested and understood by a software application.
+
The Computable Care Guidelines ('''CCG''') profile supports the expression of and sharing of health care guidelines in a grammar that can be ingested and understood by a software application.
  
 
__TOC__
 
__TOC__
Line 6: Line 6:
 
==Summary==
 
==Summary==
  
The evidence shows that improved adherence to care guidelines can yield significant population health impacts. The Computable Care Guidelines (CCG) profile helps close what WHO calls the ''know-do'' gap; the sometimes wide chasm between what we '''know''' are the evidence-based best practices and what is actually '''done''' during health care encounters. CCG provides a standards-based way to describe and to share:  
+
The evidence shows that improved adherence to care guidelines can yield significant population health impacts. The Computable Care Guidelines (CCG) profile helps close what WHO calls the ''know-do'' gap; the sometimes wide chasm between what we '''know''' are the evidence-based best practices and what is actually '''done''' during health care encounters. To close this gap, CCG provides a standards-based way to describe and to share:  
* the minimum data set that should be collected during an encounter;  
+
* the minimum data set (including coded content) that should be collected during an encounter;  
* the "business logic" that is to be triggered based on collected content; and
+
* the "workflow logic" that is to be triggered based on collected content; and
 
* the reportable health system management indicators that may be automatically generated from the person-centric healthcare transactions.  
 
* the reportable health system management indicators that may be automatically generated from the person-centric healthcare transactions.  
  
Importantly, CCG gives us a way to '''track and monitor''' the care delivery activities (''what happened'') ''and'' it provides us with a way to '''increase guideline-adherence''' by indicating what ''should happen''. In this way, it supports both feedback and feed-forward process control.  
+
Importantly, CCG provides us with a mechanism to '''track and monitor''' the care delivery activities (''what happened'') ''and'' it provides us with a mechanism to '''increase guideline-adherence''' by indicating what ''should happen''. In this way, it supports both feedback and feed-forward process control.  
  
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+
[[File:CCG_workflow_PNG.png]]
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
 
 +
It is expected that guideline-development organizations (e.g. WHO, CDC, Diabetes Canada) would create and publish CCGs. These CCGs may be contextualized by implementing jurisdictions (e.g. Kenya Ministry of Health) to create localized versions. The jurisdictional CCGs would be ingested by computer, tablet and phone-based digital health solutions to operationalize guideline-based care across the health system. The digital health solutions will generate person-centric records based on the CCG's minimum dataset; these will support care continuity and quality assurance. In a feedback loop, these data may be employed to develop and report analytics. The analytics will support management and continuous quality improvement of both the care delivery network and of the guidelines themselves.  
  
 
==Benefits==
 
==Benefits==
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
“Health care in all global settings today suffers from high levels of defects in quality across many domains, and this poor-quality care causes ongoing damage to human health. Hospitalizations in low- and middle-income countries (LMICs) lead to '''134 million adverse events''' each year, and these adverse events contribute to more than 2.5 million deaths annually. More than '''830 million people''' with a diagnosed noncommunicable disease (NCD) are not being treated, and more than '''4 million avoidable quality-related deaths''' each year are attributable to ineffective care for NCDs. In total, '''between 5.7 and 8.4 million deaths occur annually from poor quality of care in LMICs''' for the selected set of conditions the committee analyzed… which represents '''between 10 and 15 percent of the total deaths in LMICs''' reported by the World Health Organization (WHO) in 2015. For some conditions, deaths due to poor quality contribute to more than half of overall deaths." ([https://www.nap.edu/catalog/25152/crossing-the-global-quality-chasm-improving-health-care-worldwide Crossing the Global Quality Chasm (2018)])
  
 
==Details==
 
==Details==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
The CCG profile leverages IHE's '''Dynamic Care Planning''' ([https://wiki.ihe.net/index.php/Dynamic_Care_Planning DCP]) profile. Similar to DCP, CCG expresses the care guideline using the [https://www.hl7.org/fhir/careplan.html CarePlan], [https://www.hl7.org/fhir/plandefinition.html PlanDefinition], [https://www.hl7.org/fhir/activitydefinition.html ActivityDefinition] and [https://www.hl7.org/fhir/task.html Task] resources defined in the '''HL7 FHIR''' standard. CCG particularly focuses on the definition of the minimum data sets needed to operationalize the evidence-based care and on the use of IHE's '''mobile Aggregate Data Exchange''' ([https://wiki.ihe.net/index.php/Mobile_Aggregate_Data_Exchange mADX]) profile to define reportable indicators that may be generated from these data sets. The mADX profile leverages the [https://www.hl7.org/fhir/measure.html Measure] and [https://www.hl7.org/fhir/measurereport.html MeasureReport] FHIR resources.
  
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
 
 
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 
 
 
==Systems Affected==
 
==Systems Affected==
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+
* Guideline-development bodies will generate CCGs and publish them as FHIR bundles hosted on a '''FHIR server'''
 
+
* Jurisdictions will contextual CCGs and publish them as FHIR bundles hosted on a '''FHIR server'''
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* '''Digital health solution''' developers will modify their applications to enable them to ingest CCGs, to operationalize a UI based on the minimum data sets and the care workflow logic, to persist person-centric health data, and to generate and report the management metrics (mADX messages) as defined by the CCG
* ''Display systems may query, retrieve and display Evidence Documents.''
 
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
 
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
''TBD''
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| In Development]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
 
'''Documents:'''  
 
'''Documents:'''  
 
+
''TBD''
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
 
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
+
:* [http://hl7.org/fhir/ HL7 FHIR]
:* [http://dicom.nema.org DICOM]
+
:* [https://icd.who.int/en/ ICD-11]
:* [http://www.hl7.org HL7]
+
:* [https://loinc.org/ LOINC]
:* ...
+
:* [https://www.who.int/classifications/ichi/en/ ICHI]
 +
:* [http://www.snomed.org/ SNOMED]
 +
:* [https://www.who.int/classifications/icf/en/ ICF]
  
==See Also==
+
'''To participate in developing the CCG work item:'''
 +
:* [https://wiki.ihe.net/index.php/Quality,_Research_and_Public_Health  QRPH wiki]
 +
:* email qrph@ihe.net with subject line: Participate in CCG
  
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
  
 +
[[Category:QRPH Profile]]
  
'''Related Profiles'''
 
  
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
+
Categorize key standards used in your Profile with one or more of the following (delete the rest):
 
 
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
 
 
 
 
'''Consumer Information'''
 
  
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
 
 
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
 
 
'''Implementer Information'''
 
 
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 
 
'''Reference Articles'''
 
 
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
 
 
[[Category:Profiles]]
 
 
This page is based on the [[Profile Overview Template]]
 
 
[[Category:Templates]]
 
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 
 
<!--
 
Categorize the Domain of your Profile with one of the following (delete the rest):
 
[[Category:CARD Profile]]
 
[[Category:DENT Profile]]
 
[[Category:ENDO Profile]]
 
[[Category:EYECARE Profile]]
 
[[Category:ITI Profile]]
 
[[Category:PaLM Profile]]
 
[[Category:PCC Profile]]
 
[[Category:PCD Profile]]
 
[[Category:PHARM Profile]]
 
[[Category:QRPH Profile]]
 
[[Category:RO Profile]]
 
[[Category:RAD Profile]]
 
 
Categorize key standards used in your Profile with one or more of the following (delete the rest):
 
[[Category:CDA]]
 
 
[[Category:FHIR]]
 
[[Category:FHIR]]
[[Category:DICOM]]
 
[[Category:DICOMweb]]
 
[[Category:HL7v2]]
 
[[Category:XDW]]
 
[[Category:DocShare]]
 
 
And if people forget to do this, we'll comment this out and you can forget to opt-in. :-)
 
-->
 

Latest revision as of 16:04, 28 February 2020

The Computable Care Guidelines (CCG) profile supports the expression of and sharing of health care guidelines in a grammar that can be ingested and understood by a software application.

Summary

The evidence shows that improved adherence to care guidelines can yield significant population health impacts. The Computable Care Guidelines (CCG) profile helps close what WHO calls the know-do gap; the sometimes wide chasm between what we know are the evidence-based best practices and what is actually done during health care encounters. To close this gap, CCG provides a standards-based way to describe and to share:

  • the minimum data set (including coded content) that should be collected during an encounter;
  • the "workflow logic" that is to be triggered based on collected content; and
  • the reportable health system management indicators that may be automatically generated from the person-centric healthcare transactions.

Importantly, CCG provides us with a mechanism to track and monitor the care delivery activities (what happened) and it provides us with a mechanism to increase guideline-adherence by indicating what should happen. In this way, it supports both feedback and feed-forward process control.

CCG workflow PNG.png


It is expected that guideline-development organizations (e.g. WHO, CDC, Diabetes Canada) would create and publish CCGs. These CCGs may be contextualized by implementing jurisdictions (e.g. Kenya Ministry of Health) to create localized versions. The jurisdictional CCGs would be ingested by computer, tablet and phone-based digital health solutions to operationalize guideline-based care across the health system. The digital health solutions will generate person-centric records based on the CCG's minimum dataset; these will support care continuity and quality assurance. In a feedback loop, these data may be employed to develop and report analytics. The analytics will support management and continuous quality improvement of both the care delivery network and of the guidelines themselves.

Benefits

“Health care in all global settings today suffers from high levels of defects in quality across many domains, and this poor-quality care causes ongoing damage to human health. Hospitalizations in low- and middle-income countries (LMICs) lead to 134 million adverse events each year, and these adverse events contribute to more than 2.5 million deaths annually. More than 830 million people with a diagnosed noncommunicable disease (NCD) are not being treated, and more than 4 million avoidable quality-related deaths each year are attributable to ineffective care for NCDs. In total, between 5.7 and 8.4 million deaths occur annually from poor quality of care in LMICs for the selected set of conditions the committee analyzed… which represents between 10 and 15 percent of the total deaths in LMICs reported by the World Health Organization (WHO) in 2015. For some conditions, deaths due to poor quality contribute to more than half of overall deaths." (Crossing the Global Quality Chasm (2018))

Details

The CCG profile leverages IHE's Dynamic Care Planning (DCP) profile. Similar to DCP, CCG expresses the care guideline using the CarePlan, PlanDefinition, ActivityDefinition and Task resources defined in the HL7 FHIR standard. CCG particularly focuses on the definition of the minimum data sets needed to operationalize the evidence-based care and on the use of IHE's mobile Aggregate Data Exchange (mADX) profile to define reportable indicators that may be generated from these data sets. The mADX profile leverages the Measure and MeasureReport FHIR resources.

Systems Affected

  • Guideline-development bodies will generate CCGs and publish them as FHIR bundles hosted on a FHIR server
  • Jurisdictions will contextual CCGs and publish them as FHIR bundles hosted on a FHIR server
  • Digital health solution developers will modify their applications to enable them to ingest CCGs, to operationalize a UI based on the minimum data sets and the care workflow logic, to persist person-centric health data, and to generate and report the management metrics (mADX messages) as defined by the CCG

Actors & Transactions:

TBD

Specification

Profile Status: In Development

Documents: TBD

Underlying Standards:

To participate in developing the CCG work item:

  • QRPH wiki
  • email qrph@ihe.net with subject line: Participate in CCG


Categorize key standards used in your Profile with one or more of the following (delete the rest):