2023-01-23 National Directory Meeting

Greg Meyer

Joseph Shook 

2023-01-09 National Directory Meeting

2023-01-12 National Directory Meeting

Project Page: National Healthcare Directory

Project Scope Statement: National Healthcare Directory PSS

Implementation Guides:

• CI Build: http://build.fhir.org/ig/HL7/fhir-us-ndh/branches/master/index.html
  • Note: 3 IGs have been combined into a single IG
• Balloted Versions:
  • http://hl7.org/fhir/us/directory-query/2022Sep/
  • http://hl7.org/fhir/us/directory-exchange/2022Sep/
  • http://hl7.org/fhir/us/directory-attestation/2022Sep/

Connectathon: 2023- 01 FAST National Directory of Healthcare & Da Vinci Plan Net

Zulip Channel: https://chat.fhir.org/#narrow/stream/283066-united-states.2Fnational.20directory

Predecessor work that this effort builds upon:

• • VHDir Implementation Guide
  • ONC Healthcare Directory initiative
  • Da Vinci PDex Plan Net Implementation Guide

Sept 2022 Ballot Cycle Milestones

Tentative: May 2023 Ballot Cycle Milestones

CMS Advancing Interoperability and Improving Prior Authorization Processes Proposed Rule (CMS-0057-P)

• Federal Register (officially published 12/13/22)
• Fact Sheet
• Comment period closes 3/13/2023

This proposed regulation cover areas like Patient Access API, Payer to Payer Exchange, Handling Prior Authorization, etc.

Administrative Simplification: Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard Proposed Rule (CMS-0053-P)

• Federal Register (published on 12/21/22)
• Comments due 3/21/23

This is the long awaited attachments rule from the Division of National Standards. It contains follow on requirements in the Accountable Care Act that mandated that CMS establish a standard for exchange of attachments compatible with HIPAA transactions. 

Track report out from Connectathon (Ming)

Questions, discussions re: meeting

LN: Scenario Step 3 Query Bulk Data endpoint from Connectathon - RD: tools that can go into query, was used back in September connectathon. 

TZ: Since this is now a consolidated project, should we review scope? Might need concise, clearer scope description. RD: scope is updated. Details behind the scope likely needs more clarity. 

FHIR-38606 - Move base profiles to separate IG

• From before we consolidated IGs.
• RD: will retract the vote. Proposed disposition - not persuasive. Noting we agreed to combine 3 IGs into 1.
• Description: Defined the base resources in a well defined section of the guide.
• Grouping: ready for vote

FHIR-38546 PractitionerRole.code versus PractitionerRole.specialty

• Came from pdex - we did the same thing as pdex because US Core 3.1.1 treated it in a way we couldn't use
  • US Core defined valuesets - limited differently
  • We are not pulling from US Core - therefore have the liberty of changing; ticket is pointing out specific values they want to see in the valuesets
  • MB: tasked with creating a ticket noting that the valuesets do not support social services
  • Plan Net represents payers - described use case and require valuesets 
  • Ours needed to be extensible
• Proposed disposition - persuasive with modification
• Change impact: compatible, substantive
• Description: value sets were inherited from Plan Net. The ND has a need to expand the scope of both .code and .specialty value sets beyond that defined in either US core or Plan Net. We will change the binding of both value sets to extensible and expand the value sets based on feedback during the next ballot cycle. 
• Grouping: Ready for vote
• LN: Good work for National Direct group - could build out the extensible valueset; need to open for other use cases
  • MB: agrees; LN and MB will work on this
• Timeline - submit ballot comment against the guide re: need for expansion 
• TZ: once we put as extensible and give to implementers, is there accountability re: their ability to add new code values, will there be review to look for overlap? semantic interoperability will be assured?  RD: if there is a value that already describes semantically what you're trying to achieve, you have to use it. Reviewed by THO. 

FHIR-38522 3855 Duplication of Code System across IGs. Same code systems exits in multiple IGs by the same author

• Resolution: Persuasive with modification
• Description: we are combining the 3 IGs into 1 and the base profile definitions will indicate the value sets and code system for each of the required/must support elements. Additionally, profiles in the new IG will all be based on the base profiles and therefore avoid the problem with multiple IG and independent references to value sets in each
• Change impact - not substantive
• Grouping: ready for vote

FHIR-38362 - Introduction language should be tailored for this IG

• Resolution: persuasive with modification
• Description: since we are combining the 3 IGs into 1 the descriptions (including technical descriptions) will be updated to accurately reflect the overall approach to the ND and each section (e.g., attestation, verification) will add additional description information as well as specific use cases and examples. 
• Change category: clarification
• Change impact: non-substantive
• Grouping: ready for vote

FHIR-38361

• Relates to FHIR-38362
• Resolution: persuasive with modification
• Change category: Clarification
• Change impact: non-substantive
• Grouping: ready for vote

FHIR-38359

• Relates to FHIR-38362
• Resolution: persuasive with modification
• Change category: Clarification
• Change impact: non-substantive
• Grouping: ready for vote