Donating EHR and cybersecurity technology to physicians: the Stark exceptions and anti-kickback safe harbors, explained
Four provisions, 42 CFR 411.357(w) and (bb) and 1001.952(y) and (jj), let hospitals and others donate EHR and cybersecurity technology. They share most conditions, but differ on later payments, cost shifting and signed writings, which shapes how a donation program is budgeted and papered.
Four provisions, two laws
A hospital or health system that gives community physicians electronic health record software, or helps them pay for security tools, is giving them something of value. Two federal fraud and abuse laws apply to that. The physician self-referral law (often called Stark) is administered by CMS, and its regulatory exceptions for these donations are 42 CFR 411.357(w) for EHR items and services and 411.357(bb) for cybersecurity technology [1]. The federal anti-kickback statute is administered by the HHS Office of Inspector General (OIG), and its matching safe harbors are 42 CFR 1001.952(y) and 1001.952(jj) [2]. The four texts look alike but are not identical. This page sets out who may give and receive, the conditions in each, where the two laws differ, and what that means for the budget and paperwork of a donation program.
Where the rules came from and their status
CMS’s final rule “Modernizing and Clarifying the Physician Self-Referral Regulations” and OIG’s final rule revising the anti-kickback safe harbors were both published on December 2, 2020 (85 FR 77492 and 85 FR 77684) and took effect on January 19, 2021, with one unrelated CMS amendment effective January 1, 2022 [4] [5]. CMS’s rule created the cybersecurity exception and amended the EHR exception [4]. Both agencies removed the sunset that had applied to the EHR provisions, which CMS had earlier extended to December 31, 2021, and both dropped the bar on donating replacement or equivalent technology [4] [5]. As checked on November 14, 2026, the eCFR text, current to November 12, 2026, carries no expiry date in any of the four paragraphs [1] [2].
Who may give and who may receive
Under Stark, the EHR exception protects items and services provided to a physician by an entity, as defined in 411.351, that is not a laboratory company [1]. Under the anti-kickback safe harbor, the donor may be an individual or entity, other than a laboratory company, that provides services covered by a federal health care program and submits claims to it, or that is made up of such individuals or entities, or a health plan; the recipient is any individual or entity engaged in the delivery of health care [2]. The safe harbor’s text therefore names donors and recipients that the Stark exception does not: health plans as donors, and recipients other than physicians.
The EHR conditions both laws share
Both provisions cover nonmonetary remuneration in the form of software or information technology and training services, including cybersecurity software and services, that is necessary and used predominantly to create, maintain, transmit, receive or protect electronic health records [1] [2]. Both then require:
- Interoperable software. The software must be interoperable when provided, and is deemed interoperable if, on the date it is provided, it is certified by an ONC-authorized certifying body to the then-applicable criteria in 45 CFR part 170 [1] [2].
- A 15 percent contribution. The recipient pays 15 percent of the donor’s cost before receiving an initial or replacement donation, and the donor and related parties may not finance it or lend the money [1] [2].
- No conditioning by the recipient. The recipient may not make receipt of the items a condition of doing business with the donor [1] [2].
- Selection not based on referrals. Eligibility and the amount or nature of what is given may not directly take into account the volume or value of referrals; both texts list the same seven bases that are deemed acceptable, including total prescriptions written, practice size, hours practiced, overall use of automated technology, medical staff membership and uncompensated care [1] [2].
- A signed written agreement that specifies the items and services, the donor’s cost and the recipient’s contribution, and covers all EHR items and services the donor provides; separate agreements can meet this by cross-reference or by a centrally maintained master list that preserves the history of agreements [1] [2].
- Use for any patient. For items usable for any patient regardless of payer, the donor may not restrict that use [1] [2].
- No staffing of the recipient’s office, and no use primarily for personal business or business unrelated to the practice [1] [2].
Where the two EHR texts differ
Three differences matter for a donor’s finance and contracting teams. First, timing of later payments: Stark requires the physician to pay 15 percent for items received after the initial or replacement donation “at reasonable intervals” [1], while the safe harbor says the contribution for updates need not be paid in advance [2]. OIG explained in 2020 that it kept the contribution for updates but stopped requiring it in advance [5]. Second, cost shifting: the safe harbor requires that the donor not shift the costs of the items or services to any federal health care program [2]; the Stark exception has no such condition [1]. In 2020 CMS noted that there is no cost-shifting prohibition in its EHR exception, declined to add one to the cybersecurity exception, and said Medicare payment rules address inappropriate cost-shifting through other mechanisms [4]. Third, the master list: Stark says it “must” be maintained to preserve the historical record, the safe harbor says it “should” [1] [2]. The definitions of interoperable and cybersecurity use the same words in both [2] [3].
The cybersecurity provisions
The standalone cybersecurity provisions protect technology and services necessary and used predominantly to implement, maintain or reestablish cybersecurity, and in both, “technology” means any software or other types of information technology and “cybersecurity” means protecting information by preventing, detecting and responding to cyberattacks [1] [2] [3]. Neither requires a recipient contribution [1] [2]. Both bar selecting recipients in a way that directly takes into account the volume or value of referrals, and both bar the recipient from making the donation a condition of doing business [1] [2]. The written-record conditions differ. Stark requires only that the arrangement be documented in writing [1]. The safe harbor requires a general description of the technology and services and the amount of any recipient contribution, set out in writing and signed by the parties, and adds that the donor may not condition the donation on future referrals or shift its costs to a federal health care program [2].
Hardware is where the preambles matter. CMS stated that its final definition of technology does not preclude hardware, provided the hardware is necessary and used predominantly for cybersecurity, and that standalone cybersecurity hardware falls under 411.357(bb) rather than the EHR exception [4]. OIG likewise said its definition includes certain hardware, but expected multifunctional hardware such as servers, drives and wiring to fail the predominant-use test in most cases [5].
What this means for a donation program
A hospital or health system donor usually looks for an arrangement that fits both laws, so the stricter wording on each point sets the floor: a signed writing for cybersecurity donations, no cost shifting for either kind, and a master list that keeps history. That reading is ours, and counsel should confirm it for any specific arrangement. Because Stark’s 15 percent for later items is due at reasonable intervals and the safe harbor allows it after an update, billing for updates needs a schedule that both texts can accept. The written agreement must state the donor’s cost [1] [2], so the donor’s procurement contract with its software supplier needs to produce a per-recipient cost figure. Software is deemed interoperable if it is certified on the date it is provided [1] [2], so a donor that rolls out to practices over many months may want to recheck certification status at each go-live; that is our suggestion, not a condition in the text.
This page describes the regulatory text; it is not legal advice, and whether a particular arrangement fits an exception or safe harbor depends on its facts.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.