...
Agenda Outline | Agenda Item | Minutes | ||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Announcements |
| Paul reviewed the announcements and provided highlight of agenda. Workgroups have been asked to provide comment on USCDI v4 by HL7 by April 6, if they have any comments. CDS is reviewing and plans to provide comments. Please review. CQI will be discussing next week. Specifically, look at medication duration related elements. | 2|||||||||||||||||||||||||||||||||||||||||||||||||
| New project/ proposal review | https://confluence.hl7.org/display/TPTF (comment on all Proposals and only Vote on the PSS if it includes our WG as a co-sponsor or interested party) | |||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | Clinical Reasoning FHIR Resources (owned by CQI)
| CQI Tracker Status - FHIR Core https://jira.hl7.org/secure/Dashboard.jspa?selectPageId=12005
| Motion made to re-open FHIR-23926: Juliet Rubini/Stan Rankins: 17-0-0 Updated disposition for FHIR-23296 - rejected request to extend reporter capability. Motion made to approve: Bryn Rhodes/Juliet Rubini: 20-0-0 Cannot vote on FHIR-38002. MeasureReport now has FMM 4 level. Bryn will take action to put thread on Zulip to get implementer feedback. Revisit next week. | |||||||||||||||||||||||||||||||||||||||||||||||||
| 4 | Quality Measure (IG) | Jan2023 Ballot: https://hl7.org/fhir/us/cqfmeasures/2023Jan/ To discuss: For vote:
| FHIR-40443 - This ticket was pulled back. Conversations are still ongoing. FHIR-39729 - Some words would be added to package section to provide direction on what should occur under certain circumstances. Motion made to approve disposition as written: Juliet Rubini/Anne Smith: 22-0-0. FHIR-40457 - This ticket corrects issues around related bindings for:
Motion made to approve disposition as written: Juliet Rubini/Anne Smith: 21-0-0. Pursuant to conversations around FHIR-40457, discussions occurred around Supplemental Data Element differences between QRDA and FHIR. In patient level reporting, there is no difference. Values for a patient are reported. In summary level reporting, QRDA and FHIR differ. In QRDA III, Supplemental Data Elements are reported like stratifiers and breakdown counts are provided per population. Supplemental Data Elements are only applied at the initial population level in FHIR. Discussions also occurred about placement of narrative for Supplemental Data Elements, Risk Adjustment Variables and Stratification. Measure developers would prefer one description area for SDE, one description area for Risk Adjustment and one description area of Stratification as opposed to how the Measure resource currently handles the narrative for these measure components. This will require a specification update. Bryn will investigate what options are available. FHIR-40562 - The value for the qualityProgram useContext slice in the CQFM Publishable Measure profile is bound to the Quality Programs value set. The binding strength is extensible in QMIG STU 3. The binding strength needs to be updated to example in QMIG STU 4. In addition, the qualityProgram useContext slice should no longer be required. Motion made to approve disposition as written: Juliet Rubini/Stan Rankins: 20-0-0. | 5|||||||||||||||||||||||||||||||||||||||||||||||||
| QI Core |
| QI-Core STU 5 is in the queue for publication, but there are issues being worked out with the publication tooling. | 6||||||||||||||||||||||||||||||||||||||||||||||||||
| DEQM IG/ Gaps in Care | Jan2023 Ballot: http://hl7.org/fhir/us/davinci-deqm/2023Jan/ For discussion:
For vote: | No update | 7||||||||||||||||||||||||||||||||||||||||||||||||||
| Da Vinci Risk Adjustment | May 2023 ballot status update https://build.fhir.org/ig/HL7/davinci-ra/
| No update | 8||||||||||||||||||||||||||||||||||||||||||||||||||
| Measure & MeasureReport Maturity | FMM level 4 | For FHIR Releaese 5, the maturity level for the Measure and MeasureReport resources should be moved to FMM 4. Do we agree that Measure and MeasureReport maturity has reached this level? If the resources are moved to FMM 4, certain restrictions apply - among them, the implementer community must be consulted and agree to any changes that would be made to Measure and MeasureReport resources in the future. The process for getting this agreement is not formally defined. However, the recommended approach currently involves reaching out to implementers on Zulip. Motion made to make Measure and MeasureReport maturity level FMM 4: Bryn Rhodes/Floyd Eisenberg: 22-0-0. | 9||||||||||||||||||||||||||||||||||||||||||||||||||
| May WGM+ Update |
...