Key takeaways
- For a provider, information blocking is a practice it knows is unreasonable and likely to interfere with access to, exchange or use of electronic health information.
- Exceptions exist for preventing harm, privacy, security, infeasibility and health IT performance, among others, but each has conditions you must meet and document.
- Disincentives for providers run through Medicare programs, including MIPS and the Shared Savings Program.
- Blanket holds on results, fax-only policies and slow handoffs to other providers are the habits most worth reviewing.
A different rule from HIPAA
HIPAA tells you when you may share patient information and gives patients a right to copies. The information blocking rules, which come from the 21st Century Cures Act, push from the other direction: they discourage practices that get in the way of electronic health information moving to patients and to others who are entitled to it.
The regulation defines information blocking as a practice that is likely to interfere with access, exchange or use of electronic health information, unless the practice is required by law or covered by an exception[1]. For a health care provider there is an extra element: the provider must know that the practice is unreasonable and likely to interfere[1]. That knowledge standard is narrower than the one for software developers, but it is not a safe harbor for long-standing habits nobody has questioned.
The practical point for a medical or dental office is simple. If a policy slows down or prevents a patient, another provider or an app from getting electronic information, someone should be able to explain why it is reasonable, and ideally which exception it relies on.
Where front office habits run into the rule
Information blocking sounds like a technology issue, but many of the riskiest practices are workflow choices made at the front desk or in the records room. These are the ones to review first.
| Request | Habit worth reviewing | Lower-risk approach |
|---|---|---|
| Patient wants results in the portal | Hold every result until a physician has called the patient | Release by default; hold only under a documented exception for that patient |
| New provider asks for the chart | Fax only, after a phone call to confirm | Send electronically through your EHR's exchange or direct messaging when available |
| Patient wants records in an app | Refuse because the app is unfamiliar | Explain risks if you wish, then follow the patient's choice unless an exception applies |
| Request arrives by a channel you dislike | Insist on a specific form or in-person visit | Accept any clear request and help complete what you need |
| Another practice asks for a shared patient's notes | Wait until the end of the month batch | Respond in the normal course of business |
None of these habits is automatically information blocking. Each one becomes a problem when it is applied as a blanket rule with no reason that would stand up if a patient or another provider complained. The fix is usually to keep the habit as an option for specific cases and remove it as the default.
The exceptions, in plain terms
The rule includes exceptions for practices that do not fulfill a request, grouped together in one subpart of the regulation. They cover preventing harm, privacy, security, infeasibility, health IT performance and protecting care access[2]. Other exceptions deal with the procedures for fulfilling requests and with participation in the national exchange framework.
- Preventing harm: for practices that reasonably protect a patient or another person from harm. Expect to document the clinical reasoning, not just a general worry.
- Privacy: for practices that protect patient privacy, such as honoring a patient's request not to share certain information, or meeting a HIPAA or state requirement.
- Security: for practices tied to a security risk, applied consistently and based on your security policies.
- Infeasibility: when you genuinely cannot fulfill a request, for example because of an uncontrollable event, with a written response explaining why.
- Health IT performance: for reasonable maintenance and downtime of systems, kept as short as you can.
Each exception has conditions, and the burden is on the practice to meet them. Write down which exception a policy relies on and why, and review that note when the policy changes. An exception you cannot document is very hard to claim later.
What happens to providers found to block
For health care providers, the consequences run through federal programs rather than direct fines. Under the disincentives regulation, a MIPS eligible clinician found to have committed information blocking is treated as not a meaningful EHR user for MIPS, and Shared Savings Program ACOs, participants and providers can be removed from, or denied approval to participate in, the program for at least a year[3]. Hospitals face a parallel consequence in their own Medicare program[3].
For a small practice that reports to MIPS, losing credit for that category affects a Medicare payment adjustment for a full year. For a practice in an ACO, removal can mean losing shared savings and relationships it took years to build. Those stakes are high enough to justify an hour reviewing your release policies.
Results in the portal: the hardest call
Releasing test results and notes to patients as soon as they are available is where clinicians feel the rule most. Patients are now used to seeing their information online: 65% of individuals were offered and accessed their online medical records or portal in 2024, up from 25% in 2014[4]. Almost every office-based physician uses an EHR, with 91% on a certified system in 2024[5], so the technical ability to release is rarely the obstacle.
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[4]
Show the data
| Item | Value |
|---|---|
| 2014 | 25% |
| 2024 | 65% |
The cost shows up in the inbox. 70% of medical groups reported an increase in patient portal message volume in 2024[6]. Faster release often means more questions before the physician has called. That is a staffing and workflow problem to solve, not a reason for a blanket delay. Practices that cope well usually prepare short explanation templates for common results, set clear expectations about when a clinician will follow up, and give the front desk a script for anxious callers.
Script for a caller who has seen a result first: I can see that your result is in your chart. I am not able to interpret it, but I have flagged your call for the clinical team, and someone will contact you by the time we promised. If you feel unwell now, please tell me so we can get you help straight away.
Apps, other providers and the front desk
Two kinds of request cause most hesitation at the desk: a patient who wants records sent to a consumer app, and another provider who wants a chart quickly. In both cases the instinct to slow down feels responsible. Under the information blocking rules, slowing down needs a reason.
For apps, it is reasonable to tell a patient, in plain words, that once information leaves your system the app's own privacy policy applies and HIPAA may not. What you should avoid is turning that warning into a refusal or a delay. Write a short standard message that staff can send, then process the request.
For other providers, the main risk is batching and channel rules. If your EHR can send a record electronically, a policy that requires faxing after a phone call adds delay without adding safety. Agree internally on what normal course of business means for outgoing records, such as same day or next business day, and track requests that miss it.
- Name one person who owns the release policy, usually the practice manager or privacy officer.
- Give clinicians a simple way to request a patient-specific hold and record the reason.
- Review missed outgoing requests at the monthly staff meeting.
A one-hour policy review
List your release rules
Write down every rule that delays or limits release of electronic information: result holds, note holds, record transfer methods, app requests.
Ask why for each
For each rule, record the reason. If the reason is that we have always done it this way, mark it for change.
Match to an exception
For rules you keep, note which exception applies and the conditions you meet. Keep holds patient-specific wherever possible.
Check your EHR settings
Confirm what your system actually does by default for results, notes and outgoing records, and whether staff can override it.
Update scripts
Give the front desk wording for result questions and for requests to send records to apps or other providers.
Diary a review
Revisit the list when you change EHR settings or when federal rules change.
Patient access requests still follow the HIPAA timeline, which allows up to 30 days[7]. Information blocking does not replace that clock, but a practice that routinely takes the full 30 days for an electronic record it could send in minutes should ask whether that delay is reasonable.
Example: rewriting a results hold
Example (fictional): A four-physician internal medicine practice holds all lab results from the portal for seven days so physicians can call first. After a review, the practice changes the default to immediate release for routine labs, keeps a short hold for a defined list of sensitive results where a physician documents that release could cause harm for that patient, and adds explanation templates for the ten most common lab panels.
Portal messages rise for the first month, then settle as patients learn that a clinician will follow up within the stated window. The privacy officer files the new policy with the reasoning for the sensitive-results list, so the practice can show why each hold exists.
Frequently asked questions
Does information blocking apply to small practices?
Yes. The rules apply to health care providers generally, not only to large systems. The consequences run through federal programs such as MIPS and the Shared Savings Program.
Can we still wait for a physician to call before releasing results?
A blanket hold on every result is hard to justify. Holds tied to a documented, patient-specific reason under an exception, such as preventing harm, are on firmer ground.
Is information blocking the same as a HIPAA access violation?
No. They are separate rules enforced in different ways, although one delay can raise both. HIPAA access has a 30-day limit; information blocking asks whether a practice unreasonably interferes with electronic information.
Does a patient's request to keep something private count as blocking?
Not if you follow the privacy exception's conditions. Honoring a patient's documented wishes is one of the situations the exceptions are designed for.
References
Legal Information Institute, Cornell Law School (current). 45 CFR § 171.103 - Information blocking (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR Part 171 Subpart B - Exceptions that involve not fulfilling requests to access, exchange, or use electronic health information (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 171.1001 - Disincentives for health care providers (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024 (Data Brief No. 77) (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2025). Ensuring accurate coding and billing for patient portal messages as e-visits (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.524 - Access of individuals to protected health information (opens in a new tab) ↑