Checklist: information blocking compliance for certified health IT developers and HINs/HIEs
Fourteen steps for the actors OIG can fine up to $1 million per violation: confirming actor status, the knows-or-should-know standard, building the exceptions into how requests, fees, licenses and downtime are handled, and the developer attestation.
Who can be fined, and on what standard
The information blocking rules in 45 CFR part 171 apply to health care providers, health IT developers of certified health IT, and health information networks and exchanges [1]. For developers, networks and exchanges, a practice is information blocking if it is likely to interfere with access, exchange or use of electronic health information and the actor knows, or should know, that it is, unless the practice is required by law or meets an exception [1]. HHS’s Office of Inspector General may impose a civil money penalty of up to $1,000,000 per violation on these actors [2]. Its rule took effect for these penalties on September 1, 2023, and OIG said it would not penalize conduct before that date [3]. Health care providers face disincentives from other agencies instead; this checklist does not cover them.
As checked on November 14, 2026, the eCFR shows no change to part 171 after January 15, 2025 [1]. ONC proposed deregulatory changes on December 29, 2025 that included addressing reported misuse of the information blocking definitions and exceptions [6]. Its final rule of October 28, 2026, effective December 28, 2026 except for three amendments effective January 1, 2027, lists parts 170 and 172 as the parts it amends [7]. Check the current text before relying on any step.
Using the steps
Steps 1 to 4 set the scope; steps 5 to 12 build the exceptions into everyday work; steps 13 and 14 cover the developer attestation and enforcement. A practice is covered by an exception only if the actor meets all of its requirements and conditions at all relevant times, under sections 171.200, 171.300 and 171.400 [1], so the steps below include keeping the records each exception asks for. ONC notes that the exceptions are voluntary, and that a practice that meets none of them is not automatically information blocking: it is assessed case by case [5]. Where a step is our suggestion, it says so. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. This page explains the rules; it is not legal advice.
Moraph’s teams help organizations with work like this. See our solutions.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
General counsel
Section 171.102 defines a health IT developer of certified health IT as one that has at least one certified Health IT Module at the time of the practice in question, and a health information network or exchange as one that determines, controls or has discretion to administer requirements, policies or agreements for access, exchange or use of electronic health information among more than two unaffiliated parties for treatment, payment or health care operations [1].
Data governance lead
Section 171.102 defines electronic health information as electronic protected health information to the extent it would be in a designated record set, whether or not the records are held by or for a HIPAA covered entity, excluding psychotherapy notes and information compiled for legal proceedings [1]. The map is our suggestion.
Interoperability product lead, with legal
Section 171.102 defines a practice as an act or omission, and section 171.103(a) covers any practice likely to interfere [1]. The structured review is our suggestion.
CISO
Section 171.203 requires the practice to be directly related to safeguarding electronic health information, tailored to the specific risk and implemented in a consistent and non-discriminatory manner. A written organizational policy must respond to assessed risks, align with consensus-based standards or best practice guidance and set objective timeframes for handling incidents; without one, the actor must determine in each case that the practice is necessary to mitigate the risk and that no reasonable and appropriate alternative is less likely to interfere [1].
Privacy officer
Section 171.202(b) covers a precondition required by law that has not been met, such as a missing consent: the practice must be tailored, consistent and either follow written policies or be documented case by case, and the actor must make reasonable efforts to help the individual provide a valid consent. Section 171.202(c) gives developers not covered by HIPAA their own sub-exception [1].
Customer support lead
Section 171.204(a) lists the infeasibility conditions, including uncontrollable events, inability to segment data, exhaustion of the manner exception and infeasibility under the circumstances, which needs a contemporaneous written record of the listed factors. Section 171.204(b) sets the ten-business-day written response [1].
Interoperability product lead
Section 171.301(a) requires fulfilling a request in any manner requested unless the actor is technically unable or cannot reach agreeable terms. Section 171.301(b) then requires, in order, certified technology the requestor specifies, published federal or ANSI-accredited content and transport standards the requestor specifies, or an agreed alternative machine-readable format, without unnecessary delay [1].
Pricing and contracts lead
Section 171.302(a) requires fees based on objective, verifiable criteria applied uniformly, reasonably related to costs and reasonably allocated, and bars fees based on whether the requestor is a competitor or on the value the requestor derives. Section 171.302(b) excludes, among others, any fee based in any part on an individual’s electronic access to their own information [1].
Contracts lead
Section 171.303(a) sets both deadlines, and section 171.303(b) sets conditions on the scope of rights, reasonable and nondiscriminatory royalties and other terms [1].
Site reliability engineering lead
Section 171.205(a) requires downtime for maintenance to last no longer than necessary, be applied consistently and, for developers, networks and exchanges, be consistent with existing service level agreements or, for unplanned downtime, agreed to by the customer. Section 171.205(b) sets similar conditions for action against a third-party application that is harming performance [1].
Interoperability product lead
Section 171.403 requires that both actor and requestor are part of TEFCA, that the requestor can use TEFCA for the request, that the request is not made through the standards in 45 CFR 170.215, and that any fees and licenses meet sections 171.302 and 171.303 [1].
Regulatory affairs, with an authorized representative capable of binding the developer (named in the rule)
Section 170.401 makes not engaging in information blocking a Condition of Certification from April 5, 2021, and section 170.406 requires the developer or an authorized representative capable of binding it to attest to compliance semiannually [4]. Keeping the evidence behind each attestation is our suggestion.
General counsel
OIG describes its process from complaint through investigation, a chance to discuss findings, a demand letter and appeal, and lists five enforcement priorities: patient harm, impact on a provider’s ability to care for patients, long duration, financial loss to federal health care programs or others, and actual knowledge [3] [8]. Section 1003.1420 has OIG consider the number of patients and providers affected and the number of days the blocking persisted [2]. Complaints can reach OIG through ONC’s portal or the OIG Hotline [8]. Naming a contact and keeping records retrievable are our suggestions.
Spotted an error? Tell us and we will check it and correct the checklist where needed.