Health IT Developers: Information Blocking Deadline Postponed

Updated: Mar 4

Health and Human Services’ (HHS) Office of the National Coordinator for Health IT (ONC) released an interim final rule postponing the November 2nd deadline until April 5th, 2021 when Compliance Requirements start for Conditions of Certification:

  • Information Blocking Assurances: Health IT developers must provide assurances that they will not engage in prohibited Information Blocking.

  • APIs: We covered API Conditions of Certification in a previous blog: Basically, you need to provide complete documentation, reasonable open access, and publication of fees for your existing API.

Information Blocking

EHR vendors (health IT developers) are prohibited from blocking access, exchange, or use of Electronic Health Information (EHI). Eventually (Q3 of 2022), this will extend to include the full HIPAA definition of ePHI. For the April deadline, Information Blocking is limited to US Core Data for Interoperability Version 1 (USCDIv1) and that’s good news for vendors because USCDIv1 is basically the familiar Common Clinical Dataset with a couple of new Data Classes and Data Elements (noted in the table, below):