In short
- Under 45 CFR 171.103, information blocking is a practice likely to interfere with access, exchange or use of electronic health information, and a developer of certified health IT is liable if it knows or should know that the practice is likely to interfere.
- ASTP has named specific API practices that can count, such as withholding FHIR service base URLs, delaying app registration, requiring security vetting of patient-chosen apps and demanding business associate agreements HIPAA does not require.
- The exceptions for privacy, security, infeasibility, fees, licensing and the rest each come with conditions, so your software has to make the compliant path possible and your team has to document why a request was limited.
Information blocking rules tell developers what their software and their business terms must not do with electronic health information (EHI). Under 45 CFR 171.103, information blocking is a practice that is likely to interfere with access, exchange or use of EHI, unless a law requires it or one of the regulatory exceptions applies. For a developer of certified health IT, the test is whether it knows, or should know, that the practice is likely to interfere. In practice, that means not hiding FHIR endpoints, not stalling app registration, not vetting the apps patients choose, not charging for a patient's electronic access and not writing license terms that shut competitors out.
This guide is for engineering and product leads at companies that build EHRs, patient portals, integration engines and the apps that sit on top of them. It covers who the rules apply to, the API practices federal guidance has flagged, the exceptions and how they affect your design. It is not legal advice. The facts come from ASTP/ONC publications and the regulation text, linked at the end.
Who do the information blocking rules apply to?
The regulation calls the regulated parties actors, and there are three kinds: health care providers, health IT developers of certified health IT, and health information networks or exchanges (HINs and HIEs). Section 171.102 defines a health IT developer of certified health IT as an individual or entity, other than a health care provider, that has at least one Health IT Module certified under the ONC Health IT Certification Program at the time of the practice in question. An HIN or HIE is an entity that determines, controls or administers an agreement or policy that enables exchange among more than two unaffiliated parties for treatment, payment or health care operations.
If your product is not certified and you are not running a network, you may not be an actor yourself. Your customers often are. A clinic that uses your portal is a health care provider, and the way your software handles a patient's request becomes the clinic's practice. If your product makes the clinic look like it is blocking information, the clinic will want to replace it.
What counts as interference?
The definitions in 171.102 are broad on purpose. Access is the ability or means necessary to make EHI available for exchange or use. Exchange is the ability for EHI to move between different technologies, systems, platforms or networks. Use is the ability for EHI, once accessed or exchanged, to be understood and acted on. To interfere with means to prevent, materially discourage or otherwise inhibit. EHI itself means electronic protected health information as HIPAA defines it, with exclusions for psychotherapy notes and information compiled for certain legal proceedings.
The knowledge standard differs by actor. Developers of certified health IT, HINs and HIEs are covered if they know or should know that a practice is likely to interfere. Health care providers are covered only if they know that the practice is unreasonable and is likely to interfere, which is a narrower test.
Which API practices have regulators called out?
ASTP's October 2024 fact sheet on API technology collects examples from rulemaking and FAQs. It stresses that the list is not exhaustive and that any practice likely to interfere can implicate the definition. The examples most relevant to software teams:
- A certified API developer withholding or restricting the public availability of the FHIR service base URLs that patients need to access their EHI.
- A health system with locally hosted certified EHR technology choosing not to publish its service base URLs automatically and giving them only to specifically approved apps.
- A certified API developer refusing to register and enable an app for production use within five business days of completing its verification of the API user's authenticity, which is a requirement of 45 CFR 170.404(b)(1)(ii).
- A developer of certified health IT requiring third-party apps to be vetted for security before patients may use them to receive EHI through technology certified to 170.315(g)(10).
- A delay in providing a patient's EHI through an API to an app the patient has authorized.
- Refusing to license or grant the rights needed to distribute apps that use an API's interoperability elements, or refusing the services needed to run those apps in production.
- Charging app developers a substantial fee to list their app unless they agree not to deploy it in other EHR developers' app stores.
- App store terms that require a competing app to grant the developer rights to its source code.
- Requiring third-party developers to sign business associate agreements with all of the EHR developer's covered entity customers, even when the work is not for the benefit of those covered entities.
- A provider demanding a HIPAA business associate agreement as a precondition when HIPAA would not require one.
The same fact sheet adds a useful clarification. Registering an app or publishing a base URL does not give the app access to any EHI on its own. The app still cannot reach a record unless the patient authenticates through an appropriate workflow, or, for a provider-facing app, it is configured to work inside the provider's infrastructure. Publishing endpoints and authorizing access to a record are separate controls, and you need both.
What does certification add for developers?
If you hold certified modules, the information blocking definition is not the only rule. The Information Blocking Condition of Certification in 45 CFR 170.401 says a developer may not take any action that constitutes information blocking. The Assurances Condition in 170.402 adds that the developer must not take any other action that may inhibit appropriate access, exchange and use of EHI, and must not interfere with a user's ability to access or use certified capabilities for any purpose within the scope of the certification. ASTP notes that a certified API developer can also implicate the condition through nonconformity with other certification program requirements.
What are the exceptions?
Exceptions give an actor certainty that a practice meeting all their conditions is not information blocking. A practice that misses an exception is not automatically information blocking either; it is judged case by case. ASTP's April 2024 fact sheet describes nine exceptions in three groups, and the current HealthIT.gov page counts ten, alongside a fact sheet for the HTI-3 rule titled Protecting Care Access. The nine in the fact sheet:
- Preventing Harm: the actor must reasonably believe the practice will substantially reduce a risk of harm, the practice must be no broader than necessary, and patients must be able to request review of an individualized determination of risk.
- Privacy: covers four situations, including a precondition such as consent that has not been met, a developer not covered by HIPAA acting for a privacy purpose, a denial allowed under 45 CFR 164.524(a)(1) and (2), and honoring a patient's request not to share.
- Security: the practice must be directly related to safeguarding EHI, tailored to specific risks, applied consistently and without discrimination, and based on a qualifying security policy or determination.
- Infeasibility: covers uncontrollable events, an inability to segment the requested EHI unambiguously, certain third-party modification requests, documented infeasibility under the circumstances and an exhausted Manner exception. The actor must answer in writing within 10 business days with the reasons.
- Health IT Performance: downtime or degraded performance for maintenance must last no longer than necessary and be applied consistently. Action against a third-party app that harms performance must also follow existing service level agreements.
- Manner: an actor that cannot fulfill a request in the manner asked, technically or on agreeable terms, may fulfill it in an alternative manner, following the exception's order of priority and the Fees and Licensing exceptions.
- Fees: fees may include a reasonable profit, but must rest on objective, uniformly applied criteria, relate reasonably to cost and not depend on whether the requester is a competitor. Fees based on an individual's electronic access to their own EHI, and fees for an EHI export through the 170.315(b)(10) capability, are excluded.
- Licensing: the actor must begin license negotiations within 10 business days of the request and negotiate a license within 30 business days, on reasonable and non-discriminatory terms.
- TEFCA Manner: added by the HTI-1 final rule, it lets an actor fulfill certain requests only through TEFCA when both parties participate, the request is not made through certified API standards, and fees and licensing meet the related exceptions.
What does that mean for the way you build?
Most exceptions depend on evidence: a written policy, a timely written response, consistent treatment of similar requesters. Software can make that evidence easy or impossible to produce. The design choices below are suggestions that follow from those conditions; ASTP does not phrase them this way.
- Publish FHIR service base URLs in a public, machine-readable list, and keep it current as customers go live.
- Build app registration as a tracked workflow with timestamps, so you can show each verified app was enabled within five business days.
- Tag sensitive data finely enough to segment it. If you cannot separate one sensitive note from the rest of a record, the only choices left are sharing too much or withholding everything.
- Put security practices in a written policy and apply them the same way to every app, including competitors' apps.
- Schedule maintenance windows, keep them short and keep a record of when and why performance was degraded.
- Apply rate limits and throttling by documented rules that do not single out particular requesters.
- Give operations staff a template and a 10-business-day clock for written infeasibility responses.
- Never charge patients, or apps they designate, for electronic access to their own record, and keep fee schedules tied to documented costs.
- Support EHI export and standards-based APIs, so an alternative manner is always available when a custom request cannot be met.
Who enforces information blocking, and what are the penalties?
Enforcement is split. ASTP can review claims against developers of certified health IT under the certification program. The HHS Office of Inspector General (OIG) can investigate claims against all actor types. ASTP's fact sheet says it shares every claim it receives through its Information Blocking Portal with OIG, without assessing the merits first, and that information identifying the person who submitted a claim is exempt from mandatory disclosure under the Freedom of Information Act.
Under 42 CFR 1003.1410, OIG may impose a civil money penalty of not more than $1,000,000 per violation, where a violation is a practice that constitutes information blocking. The September 2025 enforcement alert from OIG and ONC says those penalties apply to developers of certified health IT, entities offering certified health IT, HIEs and HINs, and that ONC can also ban a developer from the certification program and terminate certification of health IT involved in information blocking. Health care providers face disincentives through CMS programs instead. The alert lists OIG's priorities: practices that cause patient harm, impair a provider's ability to deliver care, last a long time or cause financial loss to federal health programs or other government or private entities.
The alert called stopping information blocking a top priority for the HHS Secretary. If your product touches EHI on behalf of providers, assume that the way it handles requests will be examined.
Where do privacy and security fit?
Information blocking does not override HIPAA. The Privacy and Security exceptions exist so that you can protect data and still comply, as long as your practices are written down, tailored and applied consistently. On our projects, we sign a BAA before anyone sees PHI, scope access so each clinician sees only their own patients and run a penetration test before launch. None of that conflicts with open APIs, as long as it is done the same way for everyone.
We have shipped Epic and athenahealth integrations. If you want an engineer's read on how your product handles EHI requests, talk to one of our engineers. Onix Systems has built software since 2000 with 370+ engineers, and our free five-day technical audit ends with a written report.
Sources
- HealthIT.gov: Information Blocking
- 45 CFR 171.102: Definitions (Cornell LII)
- 45 CFR 171.103: Information blocking (Cornell LII)
- ASTP: Information Blocking Reminders Related to API Technology (October 2024)
- ASTP: Information Blocking Exceptions fact sheet (April 2024)
- HealthIT.gov: OIG and ONC information blocking enforcement alert (September 2025)
- 42 CFR 1003.1410: Amount of penalties for information blocking (Cornell LII)