What is information blocking?

Information blocking is a practice by a health care provider, a developer of certified health IT, or a health information network that is likely to interfere with access, exchange or use of electronic health information, unless it is required by law or fits a regulatory exception. The 21st Century Cures Act prohibits it, and HHS enforces it with penalties of up to $1 million per violation for developers and networks.

The regulatory definition is in 45 CFR 171.103. To count as information blocking, a practice, meaning an act or an omission, must not be required by law, must not be covered by an exception, must be done by a regulated actor, must involve electronic health information (EHI), must be done with the required knowledge, and must be likely to interfere with access, exchange or use of EHI. Interfere means to prevent, materially discourage or otherwise inhibit.

Who and what it covers

  • Actors: health care providers; health IT developers of certified health IT; and health information networks and exchanges. Developers and networks are liable if they know or should know a practice is likely to interfere. Providers are liable if they know it is unreasonable and likely to interfere.
  • EHI: electronic protected health information to the extent it would be in a HIPAA designated record set, except psychotherapy notes and information compiled for legal proceedings. This applies whether or not a HIPAA covered entity holds it.

Exceptions

As of ASTP's February 2026 review, ten exceptions are in effect: Preventing Harm, Privacy, Security, Infeasibility, Health IT Performance, Protecting Care Access, Manner, Fees, Licensing and TEFCA Manner. Each is voluntary. Meeting one gives certainty; missing one does not automatically make a practice information blocking, since practices are judged case by case. The HTI-5 proposed rule includes further revisions, so check the current text of Part 171.

Penalties

Developers of certified health IT and networks face civil monetary penalties of up to $1 million per violation, in effect since September 1, 2023, and developers also risk certification action. Providers face appropriate disincentives under a rule effective July 31, 2024. The rules operate separately from HIPAA, and the HIPAA right of access still applies.

Examples ASTP calls likely interference

  • A patient portal that can send EHI to a third party, with that capability switched off.
  • A FHIR API for patient access whose service base URL the actor refuses to publish.
  • Refusing to register a patient-access app, which in practice prevents its use.
  • Taking several days to respond when same-day access in the requested manner is possible.

For a product team, this shapes contracts and roadmaps: fees, app registration terms and disabled export features can all raise information blocking questions as well as commercial ones.