Information blocking is a practice that is likely to interfere with access, exchange, or use of electronic health information, except as required by law or covered by an exception in subparts B, C, or D of 45 CFR part 171 [12]. If a health IT developer of certified health IT, a health information network, or a health information exchange conducts the practice, the actor knows, or should know, that it is likely to interfere [12]. If a health care provider conducts it, the provider knows that the practice is unreasonable and is likely to interfere [12]. The actors are health care providers, health IT developers of certified health IT, and health information networks or exchanges [1]. A behavioral health program is in that set when it is a health care provider. It is not in that set merely because it uses software.
Who enforces, and against whom
Enforcement is split. ASTP/ONC reviews claims of possible information blocking against health IT developers of certified health IT that may be a nonconformity under the certification program [2]. The HHS Office of Inspector General has authority to investigate claims across providers, health information networks and exchanges, and developers of certified health IT [2].
Civil monetary penalties apply to health IT developers of certified health IT and to health information networks and exchanges. The Cures Act authorizes penalties of up to $1 million per violation for those actors, and OIG’s penalty provisions for information blocking took effect on September 1, 2023 [2, 3]. Those penalties do not apply to a health care provider in its role as a provider. They can apply if the provider also meets the definition of a developer of certified health IT or of a network or exchange [3].
For certain health care providers, a separate final rule establishes disincentives after OIG determines the provider committed information blocking. That rule, 89 FR 54662, is effective July 31, 2024, and the disincentives apply to providers who are also Medicare-enrolled providers or suppliers under the Medicare Promoting Interoperability Program, the Promoting Interoperability category of the Merit-based Incentive Payment System, and the Medicare Shared Savings Program [4]. It is not a penalty that reaches every behavioral health program.
The 2022 change expanded the data, and it did not start the rule
OIG’s 2023 penalty rule states that on and after October 6, 2022, electronic health information for the information blocking definition is not limited to the information identified by the data elements represented in the USCDI standard [3]. The current definition in 45 CFR 171.102 is electronic protected health information to the extent it would be included in a designated record set, regardless of whether the group of records is used or maintained by or for a covered entity, excluding psychotherapy notes and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding [1].
Exceptions that matter for Part 2 records
An actor does not have to fulfill every request. The privacy exception in 45 CFR 171.202 has more than one sub-exception [5]. Its precondition sub-exception applies when federal or state law requires a precondition, such as a consent, that has not been satisfied [5]. The practice must be tailored to that precondition and implemented in a consistent and non-discriminatory manner [5]. It must also conform to the actor’s written policies and procedures, which specify the criteria used to decide when the precondition would be satisfied and, as applicable, the steps the actor will take to satisfy it, and which the actor implements, including training on those policies, or the practice must be documented case by case with the criteria used, any criteria that were not met, and why [5]. If the precondition depends on a consent or authorization and the actor has received a version that does not satisfy every element the law requires, the actor must use reasonable efforts within its control to give the individual a form that satisfies those elements, or other reasonable assistance to satisfy them, and must not improperly encourage or induce the individual to withhold the consent or authorization [5]. When the actor’s operations are subject to multiple laws with inconsistent preconditions, the actor’s privacy policies and procedures and its actions are deemed to satisfy those policy and consent-assistance requirements if the actor has adopted uniform privacy policies and procedures that address the more restrictive preconditions [5]. The security exception in 45 CFR 171.203 applies when the practice is directly related to safeguarding the confidentiality, integrity, and availability of electronic health information, is tailored to the specific security risk being addressed, and is implemented in a consistent and non-discriminatory manner, and when it also meets either the organizational-policy condition or the case-by-case condition [6]. If the practice implements an organizational security policy, that policy must be in writing; have been prepared on the basis of, and be directly responsive to, security risks identified and assessed by or on behalf of the actor; align with one or more applicable consensus-based standards or best-practice guidance; and provide objective timeframes and other parameters for identifying, responding to, and addressing security incidents [6]. If the practice does not implement an organizational security policy, the actor must have made a determination in each case, based on the particularized facts and circumstances, that the practice is necessary to mitigate the security risk to electronic health information, and that there are no reasonable and appropriate alternatives to the practice that address the security risk and are less likely to interfere with access, exchange, or use [6].
The infeasibility exception at 45 CFR 171.204 includes a segmentation condition [7]. It applies when the actor cannot fulfill the request because it cannot unambiguously segment the requested electronic health information from electronic health information that applicable law does not permit to be made available, or that may be withheld in accordance with § 171.201, § 171.202, or § 171.206 [7]. If the actor does not fulfill the request for a reason in that section, it must, within ten business days of receiving the request, tell the requestor in writing why the request is infeasible [7]. That condition is part of the regulation. It is not a grace period that expires when a program has had time to install an interface.
USCDI, by the version that added the element
USCDI Version 1 includes the Clinical Notes data class, with note types such as consultation note, discharge summary, history and physical, and progress note [9]. USCDI Version 2, published July 2021, adds SDOH Assessment, described as a structured evaluation of risk for any social-determinants domain such as food, housing, or transportation security, and SDOH Interventions, described as a service offered to a patient to address identified social-determinant concerns, problems, or diagnoses [8]. Later versions added more classes. Do not treat a slide that names several version numbers at once as proof that each version added the same elements.
FHIR Release 4 is the exchange standard many of these APIs use. Supporting Release 4 is a technical choice. It is not, by itself, a certification or a finding that a program has met information blocking rules.
Part 2 consent after 2024
Part 2 restricts use and disclosure of a record that would identify a patient as having or having had a substance use disorder, either directly, by reference to publicly available information, or through verification of that identification by another person when a federally assisted substance use disorder program obtained the substance use disorder information after March 20, 1972, or a federally assisted alcohol use disorder or substance use disorder program obtained the alcohol use disorder information after May 13, 1974, for the purpose of treating a substance use disorder, making a diagnosis for that treatment, or making a referral for that treatment [11]. It also restricts using that information, whether or not it is recorded, to initiate or substantiate criminal charges against the patient or to conduct a criminal investigation of the patient [11]. Information obtained before the pertinent date is covered when a part 2 program maintains it after that date as part of an ongoing treatment episode that extends past that date [11]. Since the 2024 rule, one written consent can cover all future uses and disclosures for treatment, payment, and health care operations [10]. Until the patient revokes that consent in writing, a Part 2 program, covered entity, or business associate may use and disclose the records for treatment, payment, and health care operations as the HIPAA regulations permit [10]. When records are disclosed for those activities to a covered entity or business associate, that recipient may redisclose them as HIPAA allows, except for uses and disclosures in civil, criminal, administrative, and legislative proceedings against the patient [10].
A Part 2 program, covered entity, or business associate that receives records under that single consent is not required to segregate or segment the records [11]. Older instructions that every receiving system must keep Part 2 data in a separate store, and must log that every access followed a consent directive, overstate the rule.
A FHIR Consent resource can record a directive. The regulation that decides whether a disclosure is permitted is 42 CFR Part 2, not the presence of a Consent resource in an API response [10, 11].
Sources
- 45 CFR 171.102, Information blocking definitions, eCFR, HHS. Accessed September 28, 2026.
- Information blocking, ASTP/ONC. Accessed September 28, 2026.
- Grants, Contracts, and Other Agreements: Fraud and Abuse; Information Blocking (88 FR 42820), HHS Office of Inspector General, Federal Register. Accessed September 28, 2026.
- 21st Century Cures Act: Establishment of Disincentives for Health Care Providers That Have Committed Information Blocking (89 FR 54662), HHS, Federal Register. Accessed September 28, 2026.
- 45 CFR 171.202, Privacy exception, eCFR, HHS. Accessed September 28, 2026.
- 45 CFR 171.203, Security exception, eCFR, HHS. Accessed September 28, 2026.
- 45 CFR 171.204, Infeasibility exception, eCFR, HHS. Accessed September 28, 2026.
- USCDI Version 2 (July 2021), ASTP/ONC, Interoperability Standards Platform. Accessed September 28, 2026.
- USCDI public export, ASTP/ONC, Interoperability Standards Platform. Accessed September 28, 2026.
- 42 CFR 2.33, Uses and disclosures permitted with written consent, eCFR, HHS. Accessed September 28, 2026.
- 42 CFR 2.12, Applicability, eCFR, HHS. Accessed September 28, 2026.
- 45 CFR 171.103, Information blocking, eCFR, HHS. Accessed September 29, 2026.