www.healthit.gov Open in urlscan Pro
2406:da00:ff00::36ad:f03e  Public Scan

Form analysis
4 forms found in the DOM

GET https://www.healthit.gov/buzz-blog/

<form method="get" id="search" action="https://www.healthit.gov/buzz-blog/" data-module-dynamic="mobile-search">
  <label for="s" class="show-for-sr">Search Form</label>
  <!-- <input type="submit" id="searchsubmit" class="search-button" value="Search"> -->
  <input title="Search Text" type="text" id="s" name="s" class="search-box" placeholder="Search">
  <input type="submit" style="display: none">
  <button type="submit" class="search-button">
    <span class="hide">Search</span>
    <span class="sprite -search-icon">
      <svg version="1.1" id="Glyph" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 32 32" style="enable-background:new 0 0 32 32;" xml:space="preserve">
        <style type="text/css">
          .st0 {
            fill: #FFFFFF;
          }
        </style>
        <path id="XMLID_223_" class="st0" d="M27.4,24.6l-5.1-5.1c1-1.6,1.7-3.5,1.7-5.5c0-5.5-4.5-10-10-10S4,8.5,4,14s4.5,10,10,10
	c2,0,3.9-0.6,5.5-1.7l5.1,5.1c0.8,0.8,2,0.8,2.8,0C28.2,26.6,28.2,25.4,27.4,24.6z M7,14c0-3.9,3.1-7,7-7s7,3.1,7,7s-3.1,7-7,7
	S7,17.9,7,14z"></path>
      </svg>
    </span>
  </button>
</form>

GET https://www.healthit.gov/buzz-blog

<form action="https://www.healthit.gov/buzz-blog" class="selectbox-nav" method="get"><label class="screen-reader-text" for="cat">Categories</label><select name="cat" id="cat" class="postform">
    <option value="-1">Categories</option>
    <option class="level-0" value="510">Consumer Engagement</option>
    <option class="level-0" value="66">Electronic Health &amp; Medical Records</option>
    <option class="level-0" value="76">From the ONC Desk</option>
    <option class="level-0" value="1011">Health Data</option>
    <option class="level-0" value="355">Health Information Exchange</option>
    <option class="level-0" value="75">Health Innovation</option>
    <option class="level-0" value="966">Health IT Certification</option>
    <option class="level-0" value="996">Health IT Implementation</option>
    <option class="level-0" value="776">Health IT Safety</option>
    <option class="level-0" value="1426">Information Blocking</option>
    <option class="level-0" value="906">Interoperability</option>
    <option class="level-0" value="1061">Precision Medicine</option>
    <option class="level-0" value="1101">Usability</option>
  </select>
  <button type="submit">GO</button>
</form>

GET

<form class="selectbox-nav" method="get" data-module-dynamic="selectbox-nav">
  <label class="screen-reader-text" for="archive-dropdown">View archives by selecting a month and year from the dropdown and clicking the go button</label>
  <select id="archive-dropdown" name="archive-dropdown" role="navigation">
    <option value="">Select Month</option>
    <option value="https://www.healthit.gov/buzz-blog/2022/10"> October 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/09"> September 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/08"> August 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/07"> July 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/06"> June 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/05"> May 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/04"> April 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/03"> March 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/02"> February 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2022/01"> January 2022 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/12"> December 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/11"> November 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/10"> October 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/09"> September 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/08"> August 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/07"> July 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/06"> June 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/05"> May 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/04"> April 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/03"> March 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/02"> February 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2021/01"> January 2021 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/12"> December 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/11"> November 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/10"> October 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/09"> September 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/07"> July 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/06"> June 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/05"> May 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/04"> April 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/03"> March 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/02"> February 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2020/01"> January 2020 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/12"> December 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/11"> November 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/10"> October 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/09"> September 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/08"> August 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/07"> July 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/04"> April 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/02"> February 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2019/01"> January 2019 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/11"> November 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/10"> October 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/09"> September 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/08"> August 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/07"> July 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/06"> June 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/05"> May 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/04"> April 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/03"> March 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2018/01"> January 2018 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/11"> November 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/10"> October 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/09"> September 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/08"> August 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/07"> July 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/06"> June 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/05"> May 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/04"> April 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/03"> March 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2017/01"> January 2017 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/12"> December 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/11"> November 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/10"> October 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/09"> September 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/08"> August 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/07"> July 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/06"> June 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/05"> May 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/04"> April 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/03"> March 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/02"> February 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2016/01"> January 2016 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/12"> December 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/11"> November 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/10"> October 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/09"> September 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/08"> August 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/07"> July 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/05"> May 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/04"> April 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/02"> February 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2015/01"> January 2015 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/12"> December 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/11"> November 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/10"> October 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/09"> September 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/08"> August 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/07"> July 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/06"> June 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/05"> May 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/04"> April 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/03"> March 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/02"> February 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2014/01"> January 2014 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/12"> December 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/11"> November 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/10"> October 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/09"> September 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/08"> August 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/07"> July 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/06"> June 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/05"> May 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/04"> April 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/03"> March 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/02"> February 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2013/01"> January 2013 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/12"> December 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/11"> November 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/10"> October 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/09"> September 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/08"> August 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/07"> July 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/06"> June 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/05"> May 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/04"> April 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/03"> March 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/02"> February 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2012/01"> January 2012 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/12"> December 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/11"> November 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/10"> October 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/09"> September 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/08"> August 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/07"> July 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/06"> June 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/05"> May 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/04"> April 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/03"> March 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/02"> February 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2011/01"> January 2011 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/12"> December 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/11"> November 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/10"> October 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/09"> September 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/08"> August 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/07"> July 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/06"> June 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/05"> May 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/04"> April 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/03"> March 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/02"> February 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2010/01"> January 2010 </option>
    <option value="https://www.healthit.gov/buzz-blog/2009/12"> December 2009 </option>
    <option value="https://www.healthit.gov/buzz-blog/2009/11"> November 2009 </option>
  </select>
  <button type="submit">GO</button>
</form>

POST https://cloud.connect.hhs.gov/Form_Processing

<form action="https://cloud.connect.hhs.gov/Form_Processing" id="get-updates-buzz-form" method="post" accept-charset="UTF-8">
  <label for="subscribe_email" class="show-for-sr">Enter email address</label>
  <input id="subscribe_email" type="email" name="email" placeholder="Enter email address" required="">
  <input name="form" type="hidden" value="Newsletter">
  <input name="Preferences" type="hidden" value="">
  <input name="Subscriptions" type="hidden" value="ONC Health IT News">
  <input id="ONC Health IT News" name="listIds" type="hidden" value="ONC Health IT News">
  <input type="submit" value="Subscribe">
</form>

Text Content

Skip to Content


HEALTH IT BUZZ

Visit HealthIT.gov
 * Connect with ONC on LinkedIn
 * Follow ONC on Twitter
 * Check ONC's YouTube Channel

Search Form Search
Visit HealthIT.gov
 * Connect with ONC on LinkedIn
 * Follow ONC on Twitter
 * Check ONC's YouTube Channel

   
 * Health IT Buzz
 * Information Blocking
 * Information Blocking: Eight Regulatory Reminders for October 6th

Information Blocking


INFORMATION BLOCKING: EIGHT REGULATORY REMINDERS FOR OCTOBER 6TH

Steven Posnack | September 30, 2022

 * 

Share
Share
Share via Email

On October 6, 2022, we reach the end of the more than two-year glide path laid
out for the information blocking regulations. Moving forward, expect to see
periodic, experience-driven regulatory updates as well as continued work on
education, outreach, and oversight, including the establishment of disincentives
for health care providers. There may also be the possibility of information
blocking advisory opinions if Congress grants the Secretary such authority.

This blog post covers a few information blocking (IB) reminders, including the
significance of October 6, 2022. To help “IB actors” and the community as a
whole, we’ve launched a new, dedicated information blocking webpage that
contains links to everything from basic regulatory information, fact sheets,
frequently asked questions, and blog posts like this. I’d especially like to
call your attention to two upcoming virtual office hours that our team is
holding on October 6th and October 27th – click here for more information.


REMINDER #1 – THE INFORMATION BLOCKING DEFINITION’S LIMITATION ON THE SCOPE OF
ELECTRONIC HEALTH INFORMATION (EHI) IS LIFTED AS OF OCTOBER 6, 2022.

As of October 6, 2022, EHI as it was defined under the information blocking
regulations will be applicable to practices associated with its access,
exchange, and use. The main difference between October 5th and October 6th is
that the definition of “information blocking” in 45 CFR 171.103 no longer limits
what’s considered EHI to the data elements represented in the United States Core
Data for Interoperability version 1 (USCDI v1).

Since the 21st Century Cures Act (Cures Act) became law in late 2016 and we
completed our major rulemaking activities in 2020, we have sought to make sure
that IB actors had ample time to evaluate and revise their practices related to
EHI and making it available for access, exchange, and use. This includes
delaying the information blocking regulations applicability date by almost a
year by first setting a November 2, 2020 applicability date, then extending that
date to April 5, 2021. Additionally, we limited the scope of EHI for another 18
months from the applicability date via the information blocking definition (45
CFR 171.103) and the Content and Manner Exception (45 CFR 171.301).

While the facts and circumstances that an IB actor may face with respect to the
scope of EHI has changed, an IB actor’s approach to meeting an information
blocking exception generally remains the same as it was when the information
blocking regulations became applicable on April 5, 2021.


REMINDER #2 – IB ACTORS’ PRACTICES INCLUDE ACTS AND OMISSIONS.

While short and sweet, it’s particularly important to keep this point in mind.
Even though technology related practices may come up as a top-of-mind example,
information blocking practices are inclusive of but not solely limited to them.
Other acts (e.g., contract negotiations and terms) and omissions could prevent,
materially discourage, or otherwise inhibit the access, exchange, and use of
EHI. As an example of an omission, many states legally require reporting of
certain diseases and conditions to detect outbreaks and reduce the spread of
disease. Should an actor that is required to comply with such a law fail to
report, the failure could be an interference with access, exchange, or use of
EHI under the information blocking regulations (please see applicable FAQ).


REMINDER #3 – THE INFORMATION BLOCKING REGULATIONS’ EXCEPTIONS ARE NOT SOLELY
“ONE SIZE FITS ALL” AND ADDRESS THE FACTS AND CIRCUMSTANCES OF THE SITUATION AT
HAND.

The Cures Act required the Secretary to identify reasonable and necessary
activities that do not constitute information blocking. The information blocking
regulations, including the exceptions, implement this statutory direction. The
exceptions are designed to address the fact that not all actors are similarly
situated, such as hospitals that participate in the CMS Promoting
Interoperability Program and laboratories or other health care providers that
may not have adopted certified health IT. The Infeasibility Exception is a good
example in that it’s applicable to a specific IB actor’s circumstances at the
time access, exchange, or use of EHI may be in question. What’s infeasible for
an IB actor in October 2022, may not be a year later.


We identified eight exceptions in 45 CFR part 171 subparts B and C that
recognize the complexity and heterogeneity of health care delivery across the
country. We encourage everyone, especially IB actors, to become familiar with
each of the exceptions and the contexts in which they can be met.


REMINDER #4 – NOT ALL HEALTH INFORMATION THAT’S ELECTRONIC IS EHI UNDER THE
REGULATORY DEFINITION. AND IF SUCH INFORMATION IS NOT EHI, THEN IT’S NOT COVERED
BY THE INFORMATION BLOCKING REGULATIONS.

The good news is that the EHI definition as of October 6th is something with
which most IB actors have had 20 years of familiarity – the Designated Record
Set (DRS) as defined under the Health Insurance Portability and Accountability
Act (HIPAA) Privacy Rule. Because nearly all IB actors are HIPAA-covered
entities or business associates, the DRS is a keystone shared between the
information blocking regulations and HIPAA Privacy Rule. To put it simply, the
same electronic protected health information (ePHI) that an individual has a
right to access (and request an amendment to) under the HIPAA Privacy Rule is
the same ePHI that IB actors can’t “block.”


Importantly, the information blocking regulations apply not only to practices
associated with individuals seeking access to their own EHI, but also an IB
actor’s practices associated with its business-to-business (B2B) relationships
such as those to support treatment, payment, and health care operations.

An IB actor’s existing efforts to meet HIPAA Privacy Rule requirements puts them
on solid ground when it comes to understanding what EHI is, where it may reside,
and whether and how complicated it may be to make it available for access,
exchange, or use for purposes of the information blocking regulations. For
health care providers, in particular larger enterprises, we recognize that
what’s included within your DRS may be spread out across different systems
(certified or not). However, it’s important to remember that your ongoing
efforts to meet HIPAA Privacy Rule requirements drives what’s considered EHI.
One point that we’ve emphasized to health care providers is that “the ePHI in
your DRS constitutes your EHI” for the purposes of the information blocking
regulations. Within the bounds of the definition, the HIPAA Privacy Rule allows
for each HIPAA covered entity to scope their DRS in a way that meets their
business needs. This means it’s entirely possible, for example, for hospital A
to have a slightly different DRS than hospital B.



REMINDER #5 – HOW IB ACTORS MAKE EHI AVAILABLE FOR ACCESS, EXCHANGE, AND USE CAN
AND WILL VARY BASED ON WHO THE IB ACTOR IS, THEIR TECHNOLOGICAL SOPHISTICATION,
AND WHO IT IS THAT IS SEEKING TO ACCESS, EXCHANGE OR USE AN IB ACTOR’S EHI.

The information blocking regulations do not require IB actors to adopt or use
certain technologies or platforms. IB actors may use “patient portals,” other
web interfaces, application programming interfaces (APIs), and a multitude of
technologies and platforms to make EHI available for access, exchange, or use.
The information blocking regulations focus on practices that are likely to
interfere with, prevent, or materially discourage access, exchange, or use of
EHI. For example, while the information blocking regulations don’t prescribe
specific technologies, how IB actors design, implement, use, or limit
technologies in relation to the access, exchange, or use of EHI could implicate
the information blocking regulations.


REMINDER #6 – INFORMATION BLOCKING IS ABOUT “THE DATA” (I.E., EHI) REGARDLESS OF
WHETHER ONC-CERTIFIED HEALTH IT IS INVOLVED.

As we’ve stated before and in the reminder above, the Cures Act’s information
blocking provision applies to the access, exchange, and use of EHI no matter
what technology is used by IB actors. A common misconception we’ve heard with
respect to the information blocking regulations is that they’re dependent on
health IT that is certified through the ONC Health IT Certification Program. To
the contrary, there are only limited connections between the information
blocking regulations and ONC’s certification regulations.

First, the Cures Act authorized information blocking penalties against
developers and offerors of certified health IT. However, we often remind
stakeholders that developers and offerors of certified health IT are subject to
information blocking for all of their practices involving EHI, including those
related to non-ONC-certified health IT. Thus, it’s entirely possible for a
developer of certified health IT to have engaged in information blocking without
its practice being connected to any ONC-certified health IT.

Second, only a subset of IB actors – in fact, a subset of health care providers
– are the ones who directly use ONC-certified health IT. Health information
networks/health information exchanges as well as health care providers covered
by the information blocking regulations (such as laboratories, pharmacies, renal
dialysis facilities, blood centers) may be unlikely to have or use ONC-certified
health IT for a variety of reasons. Again, this reinforces the point for health
care providers that the information blocking regulations do not focus just on
your EHI practices with ONC-certified health IT.

Third, we’d highlight two exceptions that consider the technology available to
an actor. As part of the “alternative manner” condition of the Content and
Manner Exception, priority is given to making EHI available for access,
exchange, or use with certified health IT. Additionally, the type of technology
available to an actor would be a consideration under the “infeasible under the
circumstances” condition of the Infeasibility Exception, including whether the
EHI could have been made available under the Content and Manner Exception.


REMINDER #7 – USE OF CERTAIN INFORMATION BLOCKING EXCEPTIONS BY ACTORS WILL
PROVIDE CLEAR NOTIFICATION TO REQUESTORS WHETHER THEIR REQUEST TO ACCESS,
EXCHANGE, OR USE EHI IS DELAYED OR DENIED.

While certain information blocking exceptions simply need to be met (“followed”)
by an IB actor in order for them to receive the benefit of the exception (e.g.,
Health IT Performance Exception) there are three exceptions that require an IB
actor to explain to the other party seeking to access, exchange, or use EHI why
a request for access, exchange, or use is not fulfilled.

 * The Licensing Exception – The information blocking regulations accommodate
   that in certain cases, a license to access, exchange, or use EHI may be
   necessary for certain interoperability elements to be used. In such
   instances, upon “receiving a request to license an interoperability element
   for the access, exchange, or use of electronic health information, the actor
   must – (1) Begin license negotiations with the requestor within 10 business
   days from receipt of the request; and (2) Negotiate a license with the
   requestor, subject to the licensing conditions in paragraph (b) of this
   section, within 30 business days from receipt of the request.” Accordingly,
   these dates set boundary conditions for another party to monitor insofar as
   they are exceeded, which would remove an IB actor’s ability to meet this
   exception and could increase the likelihood that information blocking
   practices had occurred.
 * The Infeasibility Exception – If an IB actor seeks to meet this exception,
   “the actor must, within ten business days of receipt of a request, provide to
   the requestor in writing the reason(s) why the request is infeasible.” As a
   result, any engagement with an IB actor that leads to the IB actor claiming
   to have met the Infeasibility Exception will generate a written response to
   the requestor as to the reason(s) why. At that point, the requestor could
   determine they wish to submit an information blocking claim to ONC. (Please
   see our Information Blocking FAQs for more information about how any claim of
   information blocking would be evaluated.)
 * The Content and Manner Exception – This exception first recognizes that two
   parties are free to reach agreement, on their own terms, with respect to a
   request for access, exchange, and use of EHI. However, if no agreement can be
   reached, the Content and Manner Exception provides a specific set of steps
   for an IB actor to follow with respect to the requestor with whom it
   interacts. Ultimately, if an IB actor cannot meet the Content and Manner
   Exception, it may turn to the Infeasibility Exception, which per the bullet
   above, will result in a written response stating the reasons why the IB actor
   was unable to provide for the access, exchange, or use of EHI.


REMINDER #8 – INFORMATION BLOCKING CLAIMS ARE CONFIDENTIAL AND RESTRICTED FROM
PUBLIC DISCLOSURE.

The Cures Act prohibits ONC from disclosing information blocking claims or
information that could reasonably be used to identify the source of the
information, except as may be necessary to carry out the purpose of the
information blocking statue (e.g., sharing with HHS Office of Inspector General
(OIG)), and exempts these claims and information from mandatory disclosure under
the Freedom of Information Act (FOIA). Once received, information blocking
claims go through a review process and are shared with the OIG, which is
responsible for conducting investigations and determining whether information
blocking occurred.

Remember, information blocking is more than just an individual’s access to EHI
issue, it could involve a practice between a hospital and clinician practice,
two hospitals, a doctor and a lab, a developer of certified health IT and a
health information network, or a practice involving other actors and entities.
If you believe that information blocking has occurred, please submit a claim via
our web portal.

With your feedback we can best assess the frequency, types, and nature of the
difficulties experienced with respect to the access, exchange, and use of EHI.
This feedback may also help us assess whether any regulatory changes could be
needed or where additional education and outreach on specific topics would help
better explain the information blocking regulations. If you’d like to keep tabs
on trends in the claims of information blocking ONC receives, we update
information blocking stats on a monthly basis.




CATEGORIES

 * Consumer Engagement
 * Electronic Health & Medical Records
 * From the ONC Desk
 * Health Data
 * Health Information Exchange
 * Health Innovation
 * Health IT Certification
 * Health IT Implementation
 * Health IT Safety
 * Information Blocking
 * Interoperability
 * Precision Medicine
 * Usability


CATEGORIES

Categories Categories Consumer Engagement Electronic Health & Medical Records
From the ONC Desk Health Data Health Information Exchange Health Innovation
Health IT Certification Health IT Implementation Health IT Safety Information
Blocking Interoperability Precision Medicine Usability GO


ARCHIVES

View archives by selecting a month and year from the dropdown and clicking the
go button Select Month October 2022 September 2022 August 2022 July 2022 June
2022 May 2022 April 2022 March 2022 February 2022 January 2022 December 2021
November 2021 October 2021 September 2021 August 2021 July 2021 June 2021 May
2021 April 2021 March 2021 February 2021 January 2021 December 2020 November
2020 October 2020 September 2020 July 2020 June 2020 May 2020 April 2020 March
2020 February 2020 January 2020 December 2019 November 2019 October 2019
September 2019 August 2019 July 2019 April 2019 February 2019 January 2019
November 2018 October 2018 September 2018 August 2018 July 2018 June 2018 May
2018 April 2018 March 2018 January 2018 November 2017 October 2017 September
2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 January 2017
December 2016 November 2016 October 2016 September 2016 August 2016 July 2016
June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December
2015 November 2015 October 2015 September 2015 August 2015 July 2015 May 2015
April 2015 February 2015 January 2015 December 2014 November 2014 October 2014
September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014
February 2014 January 2014 December 2013 November 2013 October 2013 September
2013 August 2013 July 2013 June 2013 May 2013 April 2013 March 2013 February
2013 January 2013 December 2012 November 2012 October 2012 September 2012 August
2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 January
2012 December 2011 November 2011 October 2011 September 2011 August 2011 July
2011 June 2011 May 2011 April 2011 March 2011 February 2011 January 2011
December 2010 November 2010 October 2010 September 2010 August 2010 July 2010
June 2010 May 2010 April 2010 March 2010 February 2010 January 2010 December
2009 November 2009 GO


RSS FEED

Sign up to receive content updates to your My Yahoo!, Newsgator, Bloglines, and
other news readers.

Subscribe


GET UPDATES

Please submit your email address to receive alerts when new posts are published
on the Health IT Buzz Blog

Enter email address
Visit HealthIT.gov
HHS Vulnerability Disclosure Policy
 * Connect with ONC on LinkedIn
 * Follow ONC on Twitter
 * Check ONC's YouTube Channel