2021-12-02 Risk Adjustment Use Case Meeting

The 29^th HL7 FHIR Connectathon, Jan 10 – 12, 2022  (virtual event): https://www.hl7.org/events/fhir/connectathon/2022/01/

• Early bird ends Dec 4, 2021
• Online registration ends Dec 13, 2021

January 2022 Ballot Cycle:

• 11/8 through 12/9 Ballot sign up

Review IG: https://build.fhir.org/ig/HL7/davinci-ra/index.html

• Final content deadline 12/5
• HTA-62 and HTA-63 approved
  • HTA endorsed URI for CMS-HCC: http://terminology.hl7.org/CodeSystem/cmshcc
  • HTA endorsed URI for CMS RxHCC: http://terminology.hl7.org/CodeSystem/cmsrxhcc
• Update to the Risk Adjustment Coding Gap Report profile 

Final content deadline Dec 5- final checklist - for content balloting

HL7 Review session 12/3 - QA Report for final issues

HTA Request for external code identifier/ Rx Drug HCC- Approved

HTA endorsed URI for CMS RxHCC: Can be used for other use cases- Will have an endorsed HTA endorsed URI

IG Changes:

-Coding Gap Report

Measure Group- Left as optional

Removed- improvement notation now 0:0

Population is now 0:0

Measure score and stratifier- has been removed

Pre-connectathon kick off: January 6th 3pm- 4pm ET during this call

Now that HTA has approved do we need to talk to CMS? Yan - No

HTA- HL& terminology authority- Brent-They set up however who populates the mappings.

Linda-CMS should be informed that HL7 has defined this code and they can use it in the future.

Brent-Can I do a code look up- no

Someone has to populate that.

Brent agrees to communicate to CMS

Update removed change note from manual  all change notes can into the published version- Linda agrees.

QA report page

one error- one warning- We removed the change nodes from manual and have to update Hira artifacts to reflect the removal- Rob will update.

We can have more discussion next week  Bill agrees

Also final check and read through  for errors

Review or feedback from group:  Please read IG

If you find an issue you can log it ahead of the ballot. you can link your tracker so that we don't loose it.

Brent What happens once ballot is closed

The owners are the resolution.  We can do block vote for proposed changes

For each has to be voted they go to CQI for approval or changes or disagreement and another solution  Has to be resolved before we publish. Does not mean its final just published.

Resolve ballot comments then we can work planning how to do any requirement gatherings for the next phase.

Does PDEX have two trackers? 

Linda; first IG went out without Payer to payer- However the payers are going with it to include a future statement to follow the implementation,

We can start the work not in the IG but collect examples of reports and documents can be in the next version.

Do we want to publish V1 the publish 2nd version separately?

Yan: I believe we do have to do V1 first not together.

Brent can we go to ballot in Sep on the 2nd version?

Yan- once we get ballot feedback back on the 10 th we will see the results.

Then the comments - then evaluate. We will have a sense of how much time we need to resolve to get to the 2nd version

Cancel the 23rd/ 30

We have to prioritize- next meeting.  Yan will put the list together and have bulk data discussion next meeting.

Pre- Connectathon kick off Jan 6 during this call

Connectathon and track lead resources ( add link)

     Track Lead Resources

any further questions:  How does Quorum work on balloting:

Ballot cycle page shows Quorum requirements not sure about total numbers of voters but the percentage is to be matched.

STU ballot no quorum requirement only 60 % of approval.

Comment only ballot lower requirement- There is no approval rate.

https://confluence.hl7.org/display/HE/HL7+Essentials

Yan- Those planning to vote and enter comments - Credentials for confluence, request and account, works for JIRA and confluence.

https://confluence.hl7.org/

Yan- We can ask Vanessa to help us set up a dashboard- to show all issues and way to visually track

Instructions for voting JIRA

If you notice an error send email to Yan or Linda