Cottage Health’s $3 million settlement tied a HIPAA evaluation to a server change
OCR’s February 2019 Cottage Health settlement traced two breaches to server changes, one by a contractor and one after a troubleshooting ticket. Read together, its findings put the HIPAA security evaluation inside the change process, not the annual calendar.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
OCR’s February 2019 Cottage Health settlement traced two breaches to server changes, one by a contractor and one after a troubleshooting ticket. Read together, its findings put the HIPAA security evaluation inside the change process, not the annual calendar.
- The week On February 7, 2019, the HHS Office for Civil Rights (OCR) announced that Cottage Health had agreed to pay $3 million to OCR and to adopt a corrective action plan to settle potential violations of the HIPAA Rules.
- Two accounts of the same failures OCR published the press release on February 7, 2019, and the release pointed readers to the resolution agreement and corrective action plan on OCR’s website.
- The change as the hazard The Security Rule’s evaluation standard, at 45 CFR 164.308(a)(8), requires a covered entity or business associate to perform a periodic technical and nontechnical evaluation, “based initially upon the standards implemented under this rule and, subsequently, in response to environmental or operational changes affecting the security of electronic protected health information.”
- Who touched the server The first breach was caused by a contractor, on the agreement’s account.
- The inventory beneath the risk analysis The corrective action plan’s first obligation was an enterprise-wide risk analysis, and the plan specified what it had to contain.
- The corrective plan as an operating model Corrective action plans are imposed after an investigation, but their content is public, and an organization can read one as a specification.
- What a record year signaled The release presented the Cottage settlement as the end of a record year, and the numbers were real as OCR reported them: 10 settlements and one summary judgment in 2018, together totaling $28.7 million, against a previous record of $23.5 million in 2016.
- With hindsight The money side of the announcement was the first to shift.
The week
On February 7, 2019, the HHS Office for Civil Rights (OCR) announced that Cottage Health had agreed to pay $3 million to OCR and to adopt a corrective action plan to settle potential violations of the HIPAA Rules. Cottage Health operates four hospitals in California: Santa Barbara Cottage Hospital, Santa Ynez Cottage Hospital, Goleta Valley Cottage Hospital and Cottage Rehabilitation Hospital. OCR used the announcement to close out its 2018 enforcement year, which it described as an all-time record. In 2018, OCR said, it settled 10 cases and was granted summary judgment in a case before an Administrative Law Judge, together totaling $28.7 million. The release said that total surpassed the previous record of $23.5 million, from 2016, by 22 percent, and it noted a $16 million settlement with Anthem, Inc., which OCR called the single largest individual HIPAA settlement in history.
The Cottage agreement itself had been signed in December 2018. The resolution agreement carries a Cottage Health signature dated December 11, 2018 and an OCR Pacific Region signature dated December 12, 2018, and it required payment of the $3 million on or before January 30, 2019. The release called it OCR’s final settlement of the year.
The case rested on two breach reports. According to the resolution agreement, OCR received notifications from Cottage Health on December 2, 2013 and December 1, 2015, affecting approximately 33,349 and 11,608 individuals respectively. OCR opened its investigation on December 26, 2013. On July 2, 2014, Cottage Health updated the number of individuals affected by the first breach to 50,917. The press release described the two breaches together as affecting over 62,500 individuals.
The two documents describe the causes in different words. The press release said the first breach arose when ePHI on a Cottage Health server was accessible from the internet, and that OCR’s investigation determined that security configuration settings of the Windows operating system permitted access to files containing ePHI without requiring a username and password. The release does not mention a contractor. The resolution agreement said the first breach arose from the removal of electronic security protections from one of Cottage Health’s servers by a Cottage Health contractor. As a result, the agreement said, patient names, addresses, dates of birth, diagnoses and conditions, lab results and other treatment information were available to anyone outside Cottage Health with access to its server and the ability to download files without a username and password. For the second breach, the press release said a server was misconfigured following an IT response to a troubleshooting ticket. The agreement said the second breach traced back to an employee activating the wrong website on a SQL server, which left the ePHI of 11,608 individuals, including Social Security numbers, accessible on the internet. The agreement does not mention a troubleshooting ticket.
OCR alleged four failures. Cottage Health had not conducted an accurate and thorough analysis of the potential risks and vulnerabilities to its ePHI. It had not implemented security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. It had not performed a technical evaluation in response to its contractor installing the Windows operating system. And it had not obtained satisfactory assurances, in the form of a written business associate agreement, from a particular contractor that maintained ePHI on its behalf. The press release worded the third failure more generally, as a failure to perform periodic technical and non-technical evaluations in response to environmental or operational changes affecting the security of ePHI. The agreement states that it is not an admission, concession, or evidence of liability by Cottage Health.
The corrective action plan set a three-year compliance term. It required an enterprise-wide risk analysis built on a complete inventory of the ePHI Cottage Health maintained, naming servers, laptops, mobile devices, diagnostic equipment, copy machines and security monitoring devices. It also required a risk management plan, a written process to regularly evaluate environmental or operational changes that affect the security of ePHI, revised policies and procedures, training, immediate reports to HHS when Cottage Health determined that a workforce member had failed to comply with its HIPAA policies or the HIPAA Rules, and annual reports. The major deliverables went to HHS for review and approval.
The Cottage Health settlement arrived wrapped in a headline about money. OCR announced it as the last entry in a record enforcement year, and the release opened with the year’s $28.7 million total before it reached the hospital system at all. The documents behind the headline tell a narrower and more useful story. Neither the press release nor the resolution agreement describes an outside attacker breaking in. As the two documents describe them, both breaches began with something the organization’s own contractor or staff did to a server. The agreement says a contractor removed security protections from one server. For the other, the release says a server was misconfigured following an IT response to a troubleshooting ticket, and the agreement says an employee activated the wrong website on a SQL server.
Our argument is that the Cottage findings move the HIPAA security evaluation out of the annual compliance calendar and into the change process. The Security Rule had always asked covered entities to evaluate their safeguards in response to environmental or operational changes. OCR’s third allegation applied that clause to a single, ordinary event: a contractor installing an operating system. For a hospital technology leader, the useful test is whether every change to a system that holds patient data leaves evidence that someone checked its security effect, and whether that evidence could be produced years later for an investigator.
The analysis has six parts. The first five are about controls; the last is about what the enforcement numbers did and did not signal.
- Two accounts of the same failures: what the press release and the resolution agreement each say, and why the differences matter to an incident review.
- The change as the hazard: how the evaluation standard reaches individual changes, including break-fix work.
- Who touched the server: contractors, business associate agreements and the gap between the two.
- The inventory beneath the risk analysis: why the corrective plan asked for every place ePHI lives, down to copy machines.
- The corrective plan as an operating model: reading the plan as a specification an organization can adopt before OCR asks.
- What a record year signaled: the economics of the 2018 total, and what it told a board.
Two accounts of the same failures
OCR published the press release on February 7, 2019, and the release pointed readers to the resolution agreement and corrective action plan on OCR’s website. The press release is the public summary. The resolution agreement, with the corrective action plan attached, is the binding text that both parties signed. They agree on the outcome and list the same four failures, though the release words the evaluation failure more generally, and they describe the two breaches in different language, and the differences are instructive.
The first breach
The press release frames the first breach as a configuration state. It says OCR’s investigation determined that security configuration settings of the Windows operating system permitted access to files containing ePHI without requiring a username and password, and that as a result the data was available to anyone with access to Cottage Health’s server. It does not mention a contractor. The resolution agreement frames the same breach as an action. It says the breach arose from the removal of electronic security protections from one of Cottage Health’s servers by a Cottage Health contractor. The third allegation then ties the failure to a specific moment: Cottage Health failed to perform a technical evaluation in response to its contractor installing Windows.
Read together, the documents suggest a sequence, though neither sets it out in one place. The agreement says a contractor removed electronic security protections from a server, and separately alleges that no technical evaluation followed a contractor’s installation of Windows. The release says files containing ePHI could be reached without a username and password. Neither document says in so many words that the installation and the removal of protections were the same event. The documents do not say what the server was for, how long the files were reachable or how the exposure was found, and we do not fill those gaps.
The second breach
The second breach involves the organization’s own people rather than a contractor. The press release says a server was misconfigured following an IT response to a troubleshooting ticket. The agreement says the breach traced back to an employee activating the wrong website on a SQL server. The release does not mention the employee, and the agreement does not mention the ticket. On either account, the cause was an action taken inside the organization, and the agreement says the result was that the ePHI of 11,608 individuals, including Social Security numbers, was accessible on the internet.
Why the wording matters
An incident review that records the first breach as a misconfiguration and the second as human error would be accurate and would miss what joins them. As the documents describe them, both causes were changes made by the organization’s own contractor or staff. Neither document describes an adversary defeating a control; in each case a protection was absent after the change. The release’s framing points a reader toward configuration standards. The agreement’s framing points toward change control. In our view the agreement’s framing is the more useful for an organization reviewing its own exposure, because it names the moment at which the failure could have been caught.
The counts also moved. The first breach was reported in December 2013 as affecting approximately 33,349 individuals and was updated in July 2014 to 50,917. Cottage Health’s initial count was revised upward after the investigation opened. A count that rises after an investigation opens may widen the notification work, enlarge the eventual matter and change the public figure that attaches to the organization’s name. The 2019 release used a figure of over 62,500 individuals for the two breaches together.
What the documents leave out
The public record is also notable for what it does not contain. Neither document says how either exposure was discovered, whether by Cottage Health’s own monitoring, by a patient, by a third party or by chance. Neither says how long the files were reachable, or whether anyone outside the organization actually retrieved them. The agreement describes the data as available to anyone with access to the server and the ability to download files without a username and password, which is a statement about exposure, not about access.
Those gaps matter for an organization writing its own incident records. An investigator reading a hospital’s file years later may look for the same facts the Cottage documents omit: the discovery path, the exposure window, the evidence of access or the absence of it, and the change that caused the exposure. A post-incident review that records all four, with the change ticket attached, gives the organization its own account to set beside the regulator’s summary.
Finally, the dates. The first notification reached OCR in December 2013, the investigation opened later that month, the second notification arrived in December 2015, and the agreement was signed in December 2018. The agreement resolved both, under two OCR transaction numbers. The case shows that a breach reported while an earlier investigation is still open can end up resolved in the same agreement as the first.
The change as the hazard
The Security Rule’s evaluation standard, at 45 CFR 164.308(a)(8), requires a covered entity or business associate to perform a periodic technical and nontechnical evaluation, “based initially upon the standards implemented under this rule and, subsequently, in response to environmental or operational changes affecting the security of electronic protected health information.” The evaluation establishes the extent to which the organization’s security policies and procedures meet the rule’s requirements.
Two readings of one clause
The standard can be read as calendar-driven: an evaluation done periodically, perhaps once a year, with changes feeding into the next cycle. Or it can be read as event-driven: changes that affect the security of ePHI trigger an evaluation of their own. The Cottage agreement takes the second reading for at least one class of change. Its third allegation does not say Cottage Health failed to perform a periodic evaluation. It says Cottage Health failed to perform a technical evaluation in response to its contractor installing Windows. The installation was the trigger, and the missing evaluation was the violation alleged.
The corrective action plan carries the same reading forward. Section V.A.5 requires Cottage Health to review its risk analysis annually and also to promptly update it in response to environmental or operational changes affecting the security of ePHI, and then to reassess whether its security measures are sufficient. Section V.C requires a written process to regularly evaluate any environmental or operational changes that affect the security of ePHI, submitted to HHS for approval. Neither section defines which changes count. The plan leaves that to the process Cottage Health had to write.
Where the evidence would live
For an organization that runs a formal change process, the event-driven reading has a direct consequence. The evidence of evaluation belongs in the change record. A change ticket for a system that holds ePHI would, under this reading, carry a record that someone considered the security effect of the change, what they concluded, and how the result was checked after the change was made. A separate annual assessment can summarize those records. It cannot substitute for them, because the annual assessment does not exist at the moment the change is made.
None of the Cottage documents prescribes a format for such evidence. What follows is our suggestion, not a requirement. A workable minimum has four fields on every change to an in-scope system: whether the system holds or reaches ePHI; what security-relevant settings the change touches, such as authentication, network exposure or file sharing; who reviewed that assessment; and what post-change check confirmed the result. A change that touches none of those settings can say so in a line. A change that touches them gets a proportionate review.
Break-fix work
The second Cottage breach followed a troubleshooting ticket. A clinical system that is down needs to come back, and requiring advance review of every action taken during an outage would delay that. In our judgment, advance review of each troubleshooting step is not a realistic control. The control that fits is verification after the fact. A troubleshooting ticket for a server that holds ePHI would close only after someone confirmed that the server’s exposure matched its intended state: which services answer, from where, and with what authentication.
That verification can be automated. An external scan of the organization’s internet-facing address space, compared against an expected list of services, could show a website that had been activated on a database server. So would an internal configuration check against a baseline. The tooling is secondary. What matters is that the troubleshooting ticket cannot be closed until the check has run and its result is attached.
Standard changes and templates
A change process that pre-approves routine changes, such as installing an operating system from a standard image, moves the security review from the individual change to the template. The Cottage agreement ties its evaluation allegation to a contractor’s installation of Windows. If installations are done from a hardened image with authentication requirements already set, the evaluation happened when the image was approved, and the change record need only show that the approved image was used. If a contractor builds a server by hand, the pre-approval does not apply, and the change needs its own review. A change process that cannot tell the two apart will treat both as routine.
Technical and nontechnical evaluation
The standard asks for a technical and a nontechnical evaluation. The two Cottage breaches show why both halves are needed. A technical evaluation of the first change would have asked whether the server still required authentication after the installation. A nontechnical evaluation would have asked who was allowed to install operating systems on servers holding ePHI, under what instructions and with what review. The second breach raises the nontechnical question more sharply: the agreement says an employee activated the wrong website on a SQL server. Whether that employee had a procedure to follow, and whether the procedure said anything about exposure, is a process question that no scan answers.
Operational changes are not limited to systems. A new contractor, a reorganized support team, an outsourced help desk or a new remote access route each changes who can alter a server and how. Under the event-driven reading, each of those is a candidate trigger for evaluation, because each changes the conditions under which the next server change will be made. The change process for systems and the review of operational changes to the organization are, for this purpose, two halves of one control.
Who touched the server
The first breach was caused by a contractor, on the agreement’s account. The fourth allegation concerns a contractor too: Cottage Health failed to obtain satisfactory assurances, in the form of a written business associate agreement, that a particular contractor would appropriately safeguard ePHI the contractor maintained on Cottage Health’s behalf. The agreement does not say whether the contractor in the fourth allegation was the same one that installed Windows. Readers should not assume it was. The two allegations are distinct, and together they cover two different ways an outside party can create risk: by changing the systems, and by holding the data.
What the rule requires of business associates
Under 45 CFR 164.308(b)(1), a covered entity may permit a business associate to create, receive, maintain or transmit ePHI on its behalf only if it obtains satisfactory assurances, in accordance with 45 CFR 164.314(a), that the business associate will appropriately safeguard the information. The fourth allegation applied that standard to a contractor that maintained ePHI. The obligation runs to the covered entity: the hospital must obtain the assurance before the contractor holds the data.
Whether a contractor that installs software on a server holding ePHI, without otherwise maintaining the data, is a business associate is a question of fact and law that organizations should take to counsel. The Cottage documents do not answer it. They do show that OCR examined both kinds of contractor relationship in one investigation, and that a gap in either can become an allegation.
Joining the contract register to the access register
The practical control is to connect two records that sit in different departments. Contracts, including business associate agreements, are tracked by procurement, legal or compliance. Administrative access to servers is granted by IT. A contractor can receive administrative credentials on a server holding ePHI without anyone checking the contract register. Our suggestion is to make the check a precondition of the grant: no contractor account with administrative rights on an in-scope system without a recorded decision on whether a business associate agreement is required, and, where it is, a reference to the signed agreement.
The same join serves the change process. If contractor accounts are identifiable as such, changes made under them can be routed to review automatically, and a change made by a contractor outside an approved window becomes visible. On the agreement’s account, the first Cottage breach arose from a contractor’s change to a server holding ePHI. A process that flagged that combination could have prompted the evaluation the third allegation says was missing.
Assurance that reflects what the contractor does
A business associate agreement is a promise. It does not show that the contractor’s technicians follow the hospital’s build standards when they work on the hospital’s servers. For contractors who change systems, the stronger assurance is operational: they use the hospital’s change process, its approved images and its post-change checks, and their work appears in the hospital’s change records like that of any internal team. Whether that is written into the contract or simply enforced through access, it puts contractor changes inside the evidence trail that an evaluation would rely on.
The end of an engagement
Contractor relationships end, and the end is a change too. Accounts that remain active after an engagement closes, scheduled tasks the contractor created, remote access tools left installed and configuration the contractor alone understood all persist after the contract register says the work is done. An offboarding step that removes access, reviews the systems the contractor changed and confirms their configuration against the baseline closes the loop that the access grant opened. The Cottage documents do not address offboarding; we include it because the same join between the contract register and the access register serves both ends of the relationship.
The inventory beneath the risk analysis
The corrective action plan’s first obligation was an enterprise-wide risk analysis, and the plan specified what it had to contain. Section V.A.1 required a complete inventory of all ePHI maintained by Cottage Health, including but not limited to ePHI stored on servers, laptops, mobile devices, diagnostic equipment, copy machines and security monitoring devices. Cottage Health had to submit the risk analysis to HHS within 180 days of the effective date, and HHS would approve it or require revisions until it was approved.
Why the list reaches copiers
The list in V.A.1 is broader than the systems a hospital’s data center team would name first. The plan does not explain why each class is named, and we do not add technical claims about the devices. Its effect is to put each class inside the risk analysis on the plan’s own terms. In a hospital where clinical engineering services diagnostic equipment, a print vendor maintains copiers and physical security runs monitoring devices, changes to those devices may never pass through central IT’s change process. The inventory requirement brings them into view.
The inventory as the scope of the change process
The connection to the first two parts of this analysis is direct. A change process can only flag changes to systems that it knows hold ePHI. If the inventory says a server holds no ePHI, a change to it goes through as routine. If a diagnostic device is missing from the inventory, a vendor’s service visit that changes its network settings is not a change to an in-scope system at all, as far as the records show. The risk analysis and the change process depend on the same list, and the quality of the list sets the reach of both.
For that reason we would build the ePHI inventory as a property of each configuration item in whatever system of record IT already uses for changes, rather than as a separate spreadsheet maintained for the risk analysis. A configuration item that holds or can reach ePHI carries that tag. A change to a tagged item triggers the evaluation fields. A new item cannot be put into service without the tag being set one way or the other. The risk analysis then reads from the same source as the change process, and the two cannot drift apart.
Finding what the inventory missed
An inventory compiled from records will miss things that were never recorded. The second Cottage breach involved a website that, on the agreement’s account, should not have been activated. A discovery process that looks for services and data stores the inventory does not list is the check on the inventory itself. Network scans, data discovery tools and reviews of cloud accounts all serve that purpose. When they find something, the finding is both a possible exposure and an inventory defect, and it should be corrected in both places.
One analysis across several hospitals
The agreement was entered into by Cottage Health on behalf of itself and the health care providers under its common ownership or control that had been designated as a single affiliated covered entity under the Privacy Rule, 45 CFR 164.105(b). The plan accordingly called for an enterprise-wide risk analysis and an enterprise-wide risk management plan. For a hospital system made up of several licensed facilities, that structure has an operational meaning. Failures found in one investigation were resolved through obligations that bound every member of the affiliated covered entity, and the inventory had to span every member.
An enterprise-wide inventory also needs owners. Each configuration item that holds ePHI should have a named owner, by role, who approves changes to it and answers for its entry in the risk analysis. Ownership is what turns the inventory from a list into a control: a change to an item without its owner’s approval is visible as an exception, and an item with no owner is visible as a gap.
The corrective plan as an operating model
Corrective action plans are imposed after an investigation, but their content is public, and an organization can read one as a specification. The Cottage plan is a sequence of deliverables, each built on the one before and each reviewed by HHS.
The sequence
The plan runs in order. First, the risk analysis, built on the inventory, submitted within 180 days of the effective date. HHS would respond within 90 days of receiving it, and Cottage Health would have 60 days to revise in response to any required changes, repeating until approval. Second, a risk management plan, submitted within 90 days of HHS’s final approval of the risk analysis, with the same review cycle, and formally adopted within 60 days of approval. Third, the written process for evaluating environmental and operational changes, submitted within 60 days of the risk management plan’s approval. Fourth, written policies and procedures, provided within 150 days of the risk management plan’s approval and implemented within 90 days of their own approval. Fifth, training, augmented within 60 days of the policies’ approval and repeated annually. Then an implementation report within 120 days of the training program’s approval, and annual reports for each of the three reporting periods.
The order is the point of reading the plan as a model. The inventory comes before the analysis, the analysis before the management plan, the management plan before the change process, and the change process before the policies that describe it. An organization that writes policies first and inventories last will produce documents that do not match its systems. The Cottage plan forces the opposite order.
Minimum content
Section V.F sets the minimum content of the policies. On the Security Rule side, it lists the administrative safeguards with all required and addressable implementation specifications, information system activity review, information access management, business associate contracts and other arrangements, encryption and decryption, audit controls and transmission security. On the Privacy Rule side, it lists uses and disclosures, disclosures to business associates, safeguards and changes to policies and procedures. The list is a useful cross-check for any hospital reviewing its own policy set: each item maps to a specific regulatory citation in the plan.
Certification and access
Section V.E requires the policies to be distributed to every workforce member with access to PHI, and to new workforce members within 30 days of starting. Each must sign a certification that they have read, understand and will abide by the policies. The plan then adds a hard control: Cottage Health shall not provide access to PHI to any workforce member who has not signed the certification. That ties policy acknowledgment to access provisioning, the same kind of join between records that the contractor section above recommends.
Reportable events and attestations
Two features of the plan change how an organization behaves during the compliance term. Section V.H requires Cottage Health, when it determines after investigation that a workforce member failed to comply with its HIPAA policies or the HIPAA Rules, to report the event to HHS immediately, with a description of the facts, the persons involved and the actions taken. Section VI requires the implementation report to include attestations signed by an owner or officer, including an attestation that the signer has reviewed the report, made a reasonable inquiry and believes it is accurate and truthful. During the term, workforce failures the organization confirms internally go to the regulator, and a named officer stands behind the reports.
Adopting the model without the agreement
An organization that has never been under a corrective action plan can still adopt its structure: an inventory-based risk analysis, a risk management plan that flows from it, a written change evaluation process, policies that follow those documents, training that follows the policies, and a periodic report to its board signed by an accountable officer. Doing so voluntarily does not bind it to report to HHS. It does produce the evidence an investigator would ask for, in the order an investigator would expect to see it.
Where the change process fits in the sequence
The position of the change evaluation process in the Cottage plan deserves attention. It comes after the risk analysis and the risk management plan, and before the policies and training. That order implies that the change process should be designed from the risks the analysis identified, and that the policies should then describe the process as designed, not the other way round. It also implies that training should teach staff and contractors how the change process works for systems holding ePHI, including the post-change checks. A training module that covers HIPAA in general terms but says nothing about how a server change is evaluated would leave the people the agreement links to the two Cottage breaches, a contractor and an employee, without the instruction that bore directly on the outcome.
Finally, the plan’s reporting obligations give the change process a measurable output. An organization adopting the model can report to its board, each period, the number of changes to in-scope systems, the share with completed evaluation fields, the post-change checks that found a problem and the inventory defects found by discovery. Those figures describe the control in operation, which is what the annual reports under a corrective action plan exist to show.
What a record year signaled
The release presented the Cottage settlement as the end of a record year, and the numbers were real as OCR reported them: 10 settlements and one summary judgment in 2018, together totaling $28.7 million, against a previous record of $23.5 million in 2016. The Anthem settlement alone was $16 million. A board reading the release in February 2019 might have taken the total as a sign that HIPAA enforcement was becoming more expensive across the board. The documents support a narrower reading.
What the totals measure
An annual enforcement total adds up a small number of resolved cases. One large settlement can move it more than all the others together. The total says something about the cases OCR closed that year, and little about the probability or the cost of an investigation for any particular hospital. The Cottage figure, $3 million, was the result of a negotiated resolution. Neither the release nor the agreement explains how it was set, and we do not attempt to.
The cost the headline leaves out
The resolution amount is a single payment. The corrective action plan is a program of work with a three-year compliance term, with every major deliverable submitted to HHS for approval, annual reports, officer attestations and immediate reporting of workforce violations. The agreement also leaves out of the six-year limitations period for civil money penalties the time from its effective date until any termination for breach, plus one year, so the government’s ability to pursue the covered conduct is preserved if the agreement is breached. For a hospital system, the cost of the plan, in staff time, outside help and management attention, is part of the price of the settlement, even though no release states it.
The lag
The events behind the Cottage settlement were reported in 2013 and 2015. The settlement was signed in December 2018 and announced in February 2019. A board that budgets for regulatory exposure in the year a breach occurs may find that the regulatory resolution arrives under different management, after systems have been replaced and staff have moved on. That is a reason to keep incident and change records long enough, and organized well enough, to answer questions about events that leadership may no longer remember.
What carried over
The four allegations against Cottage Health were not new requirements. Risk analysis, risk management, evaluation and business associate assurances were all in the Security Rule before 2018. What the settlement added was a public illustration of how OCR connected an ordinary change to the evaluation standard and to the risk analysis. That illustration is the part of the February 2019 announcement that we would bring to a hospital’s technology leadership today. The dollar total was a fact about OCR’s year. The change-driven reading of the evaluation standard showed how OCR’s investigators had read the rule in at least one case.
Reading enforcement releases as a control map
Each allegation in the Cottage agreement carries a citation. The risk analysis failure cites 45 CFR 164.308(a)(1)(ii)(A). The risk management failure cites 164.308(a)(1)(ii)(B). The missing evaluation cites 164.308(a)(8). The missing business associate assurance cites 164.308(b) and 164.502(e). An organization can use that list as a test of its own records: for each citation, the document or record that would show compliance, the date it was last updated, and the owner who would explain it. Where the answer to any of those is missing, the gap is of the kind OCR described at Cottage Health, whatever the dollar figure attached to that year’s enforcement.
With hindsight
The money side of the announcement was the first to shift. On April 30, 2019, HHS published a notification of enforcement discretion in the Federal Register. Since 2009 its rules had applied a $1.5 million annual limit to all four culpability tiers of HIPAA civil money penalties. After further review by its Office of the General Counsel, HHS said the better reading of the HITECH Act was different annual limits for each tier: $25,000 for no knowledge, $100,000 for reasonable cause, $250,000 for corrected willful neglect and $1.5 million for uncorrected willful neglect, adjusted for inflation, until further notice. The notice set annual limits for civil money penalties; it did not mention resolution agreements such as the one Cottage Health signed.
Congress then gave evidence of sustained practice a formal role. Public Law 116-321, approved January 5, 2021, requires the Secretary, when making determinations relating to fines, the length and extent of audits, or remedies otherwise agreed to by the Secretary, to consider whether a covered entity or business associate has adequately demonstrated that it had recognized security practices in place for not less than the previous 12 months. Recognized security practices include NIST standards and guidance and the approaches promulgated under section 405(d) of the Cybersecurity Act of 2015. The law also says that nothing in it gives the Secretary authority to increase fines because of a lack of compliance with those practices. For a hospital, the practical effect is that a year of records showing those practices at work became something the Secretary must consider in an investigation’s outcome.
OCR kept returning to risk analysis. On March 21, 2025, it announced a settlement with Health Fitness Corporation, a business associate, as the fifth enforcement action in its Risk Analysis Initiative, which it said was created to focus select investigations on compliance with the Security Rule’s risk analysis provision. According to the release, a software misconfiguration on a server made ePHI discoverable on the internet by web crawlers beginning approximately in August 2015, and Health Fitness reported the breaches to OCR between October 15, 2018 and January 25, 2019. OCR said its investigation determined that Health Fitness had failed to conduct an accurate and thorough risk analysis until January 19, 2024. Health Fitness paid $227,816 and agreed to a corrective action plan that OCR will monitor for two years. That plan included implementing a process for evaluating environmental and operational changes that affect the security of ePHI, an obligation that matches the heading of section V.C of the Cottage plan.
HHS also proposed to write the change-driven reading into the rule. On January 6, 2025, it published a proposed rule to strengthen the Security Rule (90 FR 898), with comments due March 7, 2025. The proposal would require a written technical and nontechnical evaluation within a reasonable period of time before making a change to the regulated entity’s environment or operations, and it lists the adoption of new technology assets and the upgrading, updating or patching of technology assets among such changes. It would also require a written technology asset inventory and network map, reviewed at least once every 12 months and when the environment or operations change; a new configuration management standard with security baselines; written verification from business associates, at least once every 12 months, that they have deployed required technical safeguards; and the removal of the distinction between required and addressable implementation specifications, making all of them required with specific, limited exceptions.
As checked on November 15, 2026, the most recent Unified Agenda entry for the rule on reginfo.gov, in the edition the site labels 2026 (publication ID 202510), listed it under long-term actions with final action projected for July 2027; that date is HHS’s projection, not a commitment. The current eCFR text of 45 CFR 164.308(a)(8), as checked the same day, still requires evaluation “in response to environmental or operational changes” and does not contain the proposed before-the-change language. The rule text OCR applied to Cottage Health in 2018 remains in force, and the proposal shows the direction HHS proposed to take it.
Spotted an error? Tell us and we will check it and correct the article where needed.