Date: May 24th, 2023
Time: 3:30pm ET
Attendees (11)
Name | Affiliation | Role | Attended? |
---|---|---|---|
Randi Kudner | ASTRO | Champion / Primary Point of Contact | X |
Samantha Dawes | ASTRO | Champion | |
Charlotte Raley | ASTRO | ASTRO measures and RT Support | |
Stephanie Jones | ASCO | Champion / Primary Point of Contact | X |
Caitlin Drumheller | ASCO | ASCO Measure SME | X |
Yvette Apura | ASCO | Clinical Informaticist / ASCO Measure SME | X |
Becky Metzger | Telligen | Champion / Primary Point of Contact | X |
Gail Winters | Telligen | Technical SME | X |
Sharon Labbate | Telligen | Technical / Terminology SME | |
Jessica Pugh | Telligen | Project Management for Telligen-focused tasks | X |
Dennis Blair | Evernorth | Champion / Primary Point of Contact | |
Rick Emery | Evernorth | Champion | |
Dr. Mary Kay Barton | Evernorth | Medical Oncology SME | X |
Dr. Vik Shah | Evernorth | Medical Oncology SME / Cigna Representative | |
Dr. Nimi Tuamokumo | Evernorth | Radiation Oncology SME | |
Sondra Berger | Evernorth | Business Development | |
Sharon Sebastian | MITRE | Clinical Informaticist / Terminology Support | X |
Rob Dingwell | MITRE | Technical Support | X |
Anthony DiDonato | MITRE | Project co-Coordinator | X |
Doug Williams | CentanniPark | Project co-Coordinator |
Action items
- See below
Planned Agenda Topics (Anthony to lead)
- Review action items from previous 5/10 Full Member meeting: 2023-05-10 Quality Measures Full Member Meeting (All)
Complete
- Draft agenda for 6/7 QM Demo (Gail Winters )
Review measure narrative spec
Review CQL / FHIR conversion
Review where bundles are stored in AWS (brief)
- How to upload bundle, etc.
- # of test cases (from ASCO) used for this demo
Evaluate measure from AWS environment / measure report
Review FHIR resource itself
Then, go to dashboard from AWS environment, and review results
Gail to connect with ASCO team (Caitlin) regarding ASCO measures used in the demo.
Anthony to share recording with Yvette for when she returns to office June 11th (for offline review/feedback)
- mCODE Executive Committee - Quality Measures presentation - ASCO on June 2nd
Karen Hagerty, staff lead for mCODE EC team, asked ASCO to provide QM update.
- USCDI+ Quality public comment opportunity (Stephanie Jones)
- See table below for additional details
Use "CodeX HL7 FHIR Accelerator" as signatory for pan-CodeX response
- Consolidate all responses from CodeX members
- Completeness: "Yes we love these" + if there is anything incomplete + rationale why its incomplete
- Specificity:
- Usefulness:
Interested in responding:
- Prior Auth → Randi to connect
- RTTD → Sharon and Randi to connect
- Quality Measures → informed
Overarching feedback: need for implementation timeline of subsequent versions. USCDI v1 required, but when for v2, v3, etc.?
Anthony DiDonato → see below notes for next steps
- Discuss call with PQA leadership
Next steps: the CodeX Quality Measures team is meeting on Wednesday (5/24) and we will use part of our call to identify/define where both PQA and ONC could fit into the workflow or phases of work. We will focus on clarifying questions, such as: is there a quick turn of the crank that ONC could neatly fold into by end of the fiscal year (i.e., testing on datasets, etc.)?
- Next steps: I also tracked a second action item for @Lisa Hines to connect with @Stephanie.Jones@asco.org at ASCO to learn more about how ASCO is engaging with CodeX on the Quality Measures use case.
- See notes here: https://app.hubspot.com/contacts/8047841/company/15393321234
PQA reached out to Stephanie on LinkedIn.
- Prepare for QM Public Call
- Outreach list: Quality Measures Outreach
- InfoWerks, CodeX D/I member, is interested in learning more during the demo and discussing how they can collaborate
- Timeline for Phase 0 roll-out
- Finalize Phase 0 demo
- 5/24 internal Full Member call
- 6/7 internal Full Member call, as well?
- Receive confirmation from CodeX PM about QM use case moving Planning stage
- Target QM Public Call mid- to late-June?
- Next steps:
- prepare outreach list
- set-up meeting invite
- confirm content
- prepare Public Call materials during 5/31 + 6/14 + 6/28 calls?
- Content topics:
- overview/background of CodeX and QM use case
- progress to date (Phase 0 completion and move to Planning stage)
- Demo of Phase 0
- Future plans – Phase 1 modeling of radiotherapy measures
- Call to Action - request for new orgs - vendors, etc.
- Next steps:
- Finalize Phase 0 demo
- Outreach list: Quality Measures Outreach
Team agrees with Public Call plans/content
- ASCO Quality Care Symposium 2023 - begin drafting abstract submission
- Abstract Category: Quality, Safety, and Implementation Science
- "Standardization and Technology Efforts to Improve Safety"
- Abstract Details:
- Each submission is allowed a maximum of 2,600 characters
- Sections include: Background, Methods, Results, Conclusions
- https://asco.confex.com/asco/qcs2023/sci/papers/index.cgi?stepsonly=1&username=427596&password=748817
- Abstract Category: Quality, Safety, and Implementation Science
As we build out the abstract submission, here is some content to pull from: Quality Measures - Use Case Development Guidelines Checklist
Date | USCDI+ Quality Public Comment details | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUMMARY: CMS/ONC’s USCDI+ Quality initiative has released its USCDI+ Quality data element list and is seeking comments on its level of completeness, level of specificity, and usefulness of companion guidance. https://ecqi.healthit.gov/uscdi-quality. Public comment is open until Jun 16. Must have a valid Jira account to submit comments. Of note, the following mCODE fields are included:
Others collecting comments that I know about:
TO NOTE: anything CodeX QM team submits would not be able to come from MITRE. We could address the submission on behalf of, for example, “the CodeX HL7 FHIR Accelerator” so long as someone with an active JIRA account is able to submit. Use "CodeX HL7 FHIR Accelerator" as signatory for pan-CodeX response
Interested in responding:
Overarching feedback: need for implementation timeline of subsequent versions. USCDI v1 required, but when for v2, v3, etc.? |