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

Difference between revisions of "04 January 2018 CQI Conference call Minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 470: Line 470:
 
** Why is a C-CDA considered supplemental and how are payers & ACOs audited
 
** Why is a C-CDA considered supplemental and how are payers & ACOs audited
 
** What is the current and planned NCQA approach for “validating HIE data feeds” with C-CDA in 2019
 
** What is the current and planned NCQA approach for “validating HIE data feeds” with C-CDA in 2019
* See slide deck provided by Wendy Talbot.  The primary issue is the need to validate the original source of information. Once a reviewer/auditor has reviewed a specific source, the information can be considered "standard" when checked in subsequent years.  If 2 sources are using the same EHR, can the answer work for two different providers.  The requirement is to assure the data are coming from the right place within the program. The effort is to assure NCQA is receiving the information expected (provenance, correct fields, etc.). Without validation back to the source causes challenges with reliability and validity of data. Claims are also validated, not just C-CDAs.  To avoid receiving information about ordered procedures Vs completed procedures, QDM and/or FHIR profiles can increase eCQM specificity that may help with the need to audit in the future.  The auditors also work with plans and vendors to address issues identified. <br>
+
** See slide deck provided by Wendy Talbot.  The primary issue is the need to validate the original source of information. Once a reviewer/auditor has reviewed a specific source, the information can be considered "standard" when checked in subsequent years.  If 2 sources are using the same EHR, can the answer work for two different providers.  The requirement is to assure the data are coming from the right place within the program. The effort is to assure NCQA is receiving the information expected (provenance, correct fields, etc.). Without validation back to the source causes challenges with reliability and validity of data. Claims are also validated, not just C-CDAs.  To avoid receiving information about ordered procedures Vs completed procedures, QDM and/or FHIR profiles can increase eCQM specificity that may help with the need to audit in the future.  The auditors also work with plans and vendors to address issues identified. <br>
Some health plans capture a lot of information, not only those required for specific measured. Therefore, all the information is passed through a C-CDA.<br>
+
** Some health plans capture a lot of information, not only those required for specific measured. Therefore, all the information is passed through a C-CDA.<br>
C-CDA provenance not necessarily included in files. C-CDA elements allow author, performer, dateTime, recorder but these are not necessarily shared at the data level.<br>
+
** C-CDA provenance not necessarily included in files. C-CDA elements allow author, performer, dateTime, recorder but these are not necessarily shared at the data level.<br>
Sharing of the logs of issues found by NCQA auditors would help with standards reviews.<br>
+
** Sharing of the logs of issues found by NCQA auditors would help with standards reviews.<br>
Provenance is not the major problem, it is more an issue of building C-CDAs. Feedback will be very helpful to encourage better implementations.  The C-CDA scorecard will not be sufficient.  The Examples Task Force provides another path to provide standard examples. [https://sitenv.org/ccda-smart-scorecard/ C-CDA Scorecard]  
+
** Provenance is not the major problem, it is more an issue of building C-CDAs. Feedback will be very helpful to encourage better implementations.  The C-CDA scorecard will not be sufficient.  The Examples Task Force provides another path to provide standard examples. [https://sitenv.org/ccda-smart-scorecard/ C-CDA Scorecard]  
 
* STU Comment Review (Monthly)
 
* STU Comment Review (Monthly)
 
** [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=198 QRDA Category I R4]
 
** [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=198 QRDA Category I R4]

Revision as of 18:49, 4 January 2019

Back to CQI Agenda and Minutes Page
Back to CQI Wiki Page

DRAFT January 4, 2019 - CQI Conference Call Meeting Minutes

HL7 Clinical Quality Information Workgroup
January 4, 2019 – 1-3 PM EDT
Dial in: 770-657-9270 Passcode: 217663
https://join.freeconferencecall.com/hl7cqi
CQI Co-chairs: Patty Craig, Floyd Eisenberg, Juliet Rubini, KP Sethi, Yan Heras
Meeting Chair: Juliet
Meeting Scribe: Floyd

January 4, 2019 - CQI Conference Call Attendance

Attendee Attendee's Organization Attendee's email Present
Abdul Malik Hi3 Solutions abdulmalik.shakir@hi3solutions.com
Abrar Salam The Joint Commission asalam@jointcommission.org
Alex Liu EPIC aliu@epic.com
Andrey Soares U C Denver andrey.soares@ucdenver.edu yes
Angela Flanagan Lantana Consulting Group angela.flanagan@lantanagroup.com yes
Ann Phillips NCQA phillps@ncqa.org
Anne Smith NCQA smith@ncqa.org yes
Ben Ghahhari CMS benjamin.ghahhari@cms.hhs.gov
Ben Hamlin NCQA hamlin@ncqa.org yes
Bo Borgnakke Michigan Shared Services Network borgnakke@mihin.org
Bob Dieterle Enable Care, LLC rdieterle@enablecare.us
Bob Keyes Telligen bkeyes@telligen.com
Brett Marquard River Rock Associates brett@riverockassociates.com
Brian Alper EBSCO balper@ebsco.com
Bryn Rhodes ESAC bryn@databaseconsultinggroup.com yes
Chana West ESAC Inc chana.west@esacinc.com
Claudia Hall Mathematica chall@mathematicampr.org yes
Craig Newman Altartum craig.newman@altarum.org yes
Crystal Kallem CK Consulting crystal.kallem@ckconsultingllc.com
Dan Donahue ESAC dan.donahue@esacinc.com
David Sundaram-Stukel EPIC dsandara@epic.com yes
Dipti Ghandi The Joint Commission dghandi@jointcommission.org yes
Durwin Day BCBSA dday@bsbsil yes
Eric Askegaard UHG eric_askegaard@uhg.org yes
Floyd Eisenberg iParsimony, LLC FEisenberg@iParsimony.com yes
Fareeda Nazeer The Joint Commission fnazeer@jointcommission.org
Gay Dolin IMO gdolin@imoonline.com
Hafsa Subhan The Joint Commission hsubhan@jointcommission.org
Howard Strasberg Wolters Kluwer howard.strasberg@wolterskluwer.com
Humberto Mandirola Biocom hmandirola@biocom.com
iIkka Kunnamo Duodecim jilkkakunnamo@duodecim.fl
isabel Zaru-Roque ESAC isabel.zaru-roque@esacinc.com
James Bradley Mitre jhbradley@mitre.org
Jamie Lehner PCPI jamie.lehner@thepcpi.org
Jeff Schmitz Health eFilings jschmitz@healthefilings.com
Jenny Brush ESAC jennifer.brush@esacinc.com
Joe Kunisch Memorial Hermann kunisch@memorialhermann.org
Joe Quinn Optum joseph.quinn@optum.com yes
John Damore Diameter Health jdamore@diameterhealth.com
Julia Skapik Cognitive Medicine jskapik@cognitivemedicine.com
Juliet Rubini Mathematica jrubini@mathematicampr.com yes
Kanwarpreet Sethi Lantana Consulting Group kp.sethi@lantanagroup.com yes
Kathleen Connor US Dept of Veterans Affairs kathleen_connor@comcast.net
Kurt Allen US Dept of Veterans Affairs kurta@gjoll.com
Ken Hall Veradigm Health kenneth.hall@veradigmhealth.com yes
Lenel James BCBSA lenel.james@bcbsa.org yes
Linda Michaelsen Optum linda.michaelsen@optum.com yes
Lisa Anderson The Joint Commission landerson@jointcommission.org yes
Lisa Nelson Life Over Time Solutions, LLC LisaRNelson@cox.net
Liz Hartley-Sommers BCBSA elizabeth.hartley@bcbsa.org yes
Lizzie Charbonneau Mitre lizzie@mitre.org
Lorraine Constable HL7 Canada lorraine@constable.ca
Luke Osborne MITRE lwosborne@mitre.org
Lynn Perrine Lantana lynn.perrine@lantanagroup.org yes
Matthew Tiller ESAC matthew.tiller@esacinc.com yes
Michael Okeefe MITRE mokeefe@mitre.org
Mike Hunt Experian mike.hunt@experian.com
Mia Nievera The Joint Commission mnievera@jointcommission.org yes
Mitra Biglari The Joint Commission mbiglari@jointcommission.org
Michelle Mish Turner UHC michelle-p-turner@uhc.org yes
Nancy Whipple GE nancy.whipple@ge.com
Nick Radov UHC nradov@uhc.org yes
Pamela Mahan-Rudolph Memorial pamela.mahanrudolph@memorialhermann
Patty Craig The Joint Commission pcraig@jointcommission.org
Paul Denning MITRE pauld@mitre.org yes
Ping Jiang The Joint Commission pjiang@jointcommission.org
Rathore Garima rathore.garima1@gmail.com
Rebeccah Baer NCQA baer@ncqa.org
Rich Boyce codehop.dev@gmail.com
Rob McClure MD Partners Inc rmcclure@mdpartners.com
Robert Samples ESAC Inc robert.samples@esacinc.com
Rukma Joshi ESAC Inc rukma.joshi@esacinc.com
Ryan Clark NCQA ryan@ncqa.org yes
Sam Sayer Mitre ssayer@mitre.org
Stan Rankins Telligen SRankins@telligen.com yes
Steve Hufnagel steve.hufnagel.hl7@gmail.com
Sue Kent CCF kents@ccf.org
Sweta Ladwa ESAC inc sweta.ladwa@esacinc.com
Thomas Reese U of Utah thomas.reese@hsc.utah.edu
Thomson Kuhn ACP tkuhn@acponline.org yes
Serafina Versaggi JP Systems serafina.versaggi@jpsystems.com yes
Viet Nguyen Strata Metrics vietnguyen@stratametrics.com yes
Walter Suarez Kaiser Permanente walter.g.suarez@kp.org
Wendy Talbot NCQA talbot@ncqa.org yes
Yan Heras Optimum eHealth yanheras@gmail.com yes
Yanyan Hu The Joint Commission yhu@jointcommission.org yes
Zach May ESAC Inc zachary.may@esacinc.com yes
Zabrina Gonzaga Lantana Consulting Group zabriana.gonzaga@lantanagroup.com

Meeting Minutes

  • Roll call and agenda review
  • Secondary use of CDAs from provider EHR or from local-to-provider HIEs for Reporting Quality Measure Information - Attachments Workgroup invited for presentation [Wendy Talbot (NCQA] - Questions addressed by the presentation:
    • What is role of primary and supplemental data for quality reporting under HEDIS?
    • What is the NCQA audit process?
    • Why is a C-CDA considered supplemental and how are payers & ACOs audited
    • What is the current and planned NCQA approach for “validating HIE data feeds” with C-CDA in 2019
    • See slide deck provided by Wendy Talbot. The primary issue is the need to validate the original source of information. Once a reviewer/auditor has reviewed a specific source, the information can be considered "standard" when checked in subsequent years. If 2 sources are using the same EHR, can the answer work for two different providers. The requirement is to assure the data are coming from the right place within the program. The effort is to assure NCQA is receiving the information expected (provenance, correct fields, etc.). Without validation back to the source causes challenges with reliability and validity of data. Claims are also validated, not just C-CDAs. To avoid receiving information about ordered procedures Vs completed procedures, QDM and/or FHIR profiles can increase eCQM specificity that may help with the need to audit in the future. The auditors also work with plans and vendors to address issues identified.
    • Some health plans capture a lot of information, not only those required for specific measured. Therefore, all the information is passed through a C-CDA.
    • C-CDA provenance not necessarily included in files. C-CDA elements allow author, performer, dateTime, recorder but these are not necessarily shared at the data level.
    • Sharing of the logs of issues found by NCQA auditors would help with standards reviews.
    • Provenance is not the major problem, it is more an issue of building C-CDAs. Feedback will be very helpful to encourage better implementations. The C-CDA scorecard will not be sufficient. The Examples Task Force provides another path to provide standard examples. C-CDA Scorecard
  • STU Comment Review (Monthly)
  • Reminder: Sub groups for ballot content refinement
    • Potential sub groups include: Composite scoring (Tuesdays at 1015a ET)
    • QUICK (to be scheduled post discussion at the HL7 WGM in San Antonio)
    • FHIR measures (time: potentially use second half Friday CQI meetings
  • Review San Antonio schedule
    • Found on confluence here
  • Confluence is coming!
    • Confluence will replace the Wiki for agendas and the HL7 work group page for document posting
    • Please sign up for an account here
    • Draft confluence page available here
  • Project Updates
  • Notifications and Announcements
    • Cancel January 11, 2019 meeting due to travel to San Antonio WGM
    • Next CQI WG meeting - at San Antonio HL7 WGM
    • Balloting Milestones
      • December 7, 2018 – January 7, 2019 – NOTE BALLOT COMMENT DEADLINE January 7, 2019
  • Meeting Adjourned at: