AMCA’s bankruptcy showed the labs would pay for their collector’s breach

A collections vendor holding data on millions of lab patients disclosed a breach in June 2019 and filed for bankruptcy on June 17, citing notification and remediation costs. The cost, and the regulators’ attention, moved to its clients.

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

A collections vendor holding data on millions of lab patients disclosed a breach in June 2019 and filed for bankruptcy on June 17, citing notification and remediation costs. The cost, and the regulators’ attention, moved to its clients.

  1. The week On June 3, 2019, Quest Diagnostics filed a Form 8-K with the Securities and Exchange Commission about a breach at a company it used to collect unpaid bills.
  2. What the client sent: data that did not need to travel The two laboratories described different data sets.
  3. What the vendor could afford: the balance sheet as a control The attorneys general who settled with AMCA in March 2021 set out what happened to the vendor.
  4. What the contract could enforce: notice, audit and termination The timeline in the filings and the settlement shows a long gap between the intrusion and the clients’ knowledge of it.
  5. What stayed with the client: the duty that does not transfer Whatever the contract said, some costs stayed with the clients.
  6. One collector, many clients: the aggregation problem The AMCA case had a feature that a single client’s vendor review can miss.
  7. Where the intrusion began: the payment page Both laboratories’ filings located the unauthorized activity on AMCA’s web payment page.
  8. Patients who never chose the vendor The people whose data AMCA held had a relationship with a laboratory, through a doctor’s order, and in some cases with a collection agency only because a small bill went unpaid.
  9. Disclosing on the vendor’s numbers Both laboratories had to say something publicly before they had the facts.
  10. The record a client should hold for each collector The four costs and the aggregation problem point to a short file a covered entity can keep for every collections or billing vendor, and update at each renewal.
  11. The strongest objection: the clients did what the rules required The objection to this reading is that the laboratories were victims.
  12. How it applies by kind of organization Laboratories and diagnostic companies.
  13. With hindsight The states’ case against the vendor ended with its payment suspended because of its financial condition.

The week

On June 3, 2019, Quest Diagnostics filed a Form 8-K with the Securities and Exchange Commission about a breach at a company it used to collect unpaid bills. American Medical Collection Agency (AMCA), a billing collections vendor, had notified Quest and Optum360, Quest’s revenue cycle management provider, on May 14, 2019, of potential unauthorized activity on AMCA’s web payment page. AMCA told them that between August 1, 2018 and March 30, 2019, an unauthorized user had access to an AMCA system holding information AMCA had received from various entities, including Quest, and information AMCA collected itself. The information included financial data such as credit card numbers and bank account information, medical information, and other personal information such as Social Security numbers. As of May 31, 2019, AMCA believed the system held information on about 11.9 million Quest patients.

Quest said it had not been able to verify what AMCA told it, and that its laboratory test results had not been provided to AMCA. It said it had suspended sending collection requests to AMCA, notified affected health plans, and would make sure notice went to regulators and others as federal and state law required. It disclosed that it had insurance for certain potential liabilities and costs, “limited in amount and subject to a deductible.”

The next day, June 4, 2019, LabCorp furnished its own 8-K, “in response to questions it has received.” It had been notified by Retrieval-Masters Creditors Bureau, Inc., doing business as AMCA, about unauthorized activity on AMCA’s web payment page over the same period. LabCorp said it had referred about 7.7 million consumers to AMCA whose data was stored in the affected system. That data could include name, date of birth, address, phone, date of service, provider and balance information, plus any credit card or bank account information that consumers had given AMCA to pay their balances. LabCorp said it had provided no ordered test, laboratory results or diagnostic information to AMCA, and that AMCA had advised that Social Security numbers and insurance identification were not stored for LabCorp consumers.

AMCA had told LabCorp it was sending notices to about 200,000 LabCorp consumers whose card or bank information may have been accessed, offering them identity protection and credit monitoring for 24 months, but had not yet given LabCorp a list of the affected consumers. LabCorp said it had stopped sending new collection requests to AMCA and stopped AMCA from working on pending ones. It said it was working closely with AMCA to obtain more information and would take additional steps as appropriate once more was known.

The attorneys general who later investigated recorded that on June 3, 2019, AMCA gave notice to many states and began notifying more than 7 million affected individuals, with an offer of two years of free credit monitoring. They also recorded that the stolen information included, in some instances, names of medical tests and diagnostic codes, and that AMCA had failed to detect the intrusion despite warnings from banks that processed its payments.

The AMCA breach can be filed under vendor risk, and that label is correct but too broad to be useful. What the first week of June 2019 showed, and what followed confirmed, is narrower and more concrete. A collections vendor held sensitive data for several large health care organizations at once. When it was breached, it could not pay for the consequences. On June 17, 2019, it filed for bankruptcy, citing the costs of notification and remediation. The costs did not disappear. They moved to its clients, whose patients’ data it had held.

For a health system or laboratory, that makes the vendor’s balance sheet a security control. A business associate agreement that promises notification, credit monitoring and indemnity is only worth what the vendor can pay when the bill arrives. A vendor that cannot pay leaves the covered entity to absorb the work, the cost and the regulatory attention, and the covered entity’s own duties under HIPAA do not shrink because the breach happened elsewhere.

We set out four kinds of cost that came back to the clients, each controlled by a different decision the client made before the breach: what data it sent, what the vendor could afford, what the contract could actually enforce, and what stayed with the client whatever the contract said. We then look at a fifth issue the case exposed, the aggregation of many clients’ data in one vendor, and at three practical matters: the payment page where the intrusion began, the patients who received letters from a company they had not chosen, and the problem of disclosing on a vendor’s numbers. We describe the record a client should keep for each such vendor, take the strongest objection to this reading, and set out how it applies to different kinds of health care organization.

What the client sent: data that did not need to travel

The two laboratories described different data sets. Quest’s filing said AMCA’s affected system held financial information, medical information and other personal information including Social Security numbers, though it also said Quest’s test results were not provided to AMCA. LabCorp’s filing said the data it sent was demographic and billing information: name, date of birth, address, phone, date of service, provider and balance. AMCA had told LabCorp that Social Security numbers and insurance identification were not stored for LabCorp consumers. The attorneys general later said the stolen information included Social Security numbers, payment card information and, in some instances, names of medical tests and diagnostic codes.

Those differences matter well beyond the laboratories’ legal departments. Every field a client sends to a collector is a field that may have to be notified on, monitored for and defended in an investigation. A collector needs enough to identify a debtor, contact them and match payments to accounts. Whether it needs a Social Security number, a diagnostic code or a test name to do that is a question the client can answer before signing the contract. If the answer is no, the field should not leave.

The second source of data is the one clients do not control directly. Quest’s filing notes that AMCA’s system held information AMCA received from its clients and “information that AMCA collected itself.” LabCorp’s filing says that card and bank account details were provided by consumers to AMCA when they paid. The collector gathers new sensitive data in the course of the work: payment details, updated contact information, notes of calls. That data is created on the client’s behalf and about the client’s patients, and when it is stolen, the client’s name is attached to it.

So data minimization for a collections relationship has two parts. The first is what the client sends, which it can cut to what the work needs. The second is what the vendor collects and keeps, which the client can only shape through the contract: how payment data is handled, whether it is stored at all after a payment is processed, how long account files are kept after a balance is closed, and what is deleted when a client ends the relationship. In 2026, the multistate settlement with LabCorp described this balance directly, requiring the company to minimize the sharing of data with vendors “while balancing certain needs of debt collectors to meet their legal obligations.”

A health system can test its own position quickly. It can pull the file layout it sends to each collection agency and mark, field by field, which ones the collector uses. Fields that no one can explain are candidates for removal. The exercise costs little and reduces the size of every future breach at that vendor.

What the vendor could afford: the balance sheet as a control

The attorneys general who settled with AMCA in March 2021 set out what happened to the vendor. On June 17, 2019, “as a result of the costs associated with providing notification and remediating the breach,” AMCA filed for bankruptcy. The states took part in the bankruptcy proceedings through the attorneys general of Indiana and Texas. The bankruptcy court eventually let AMCA settle with the states, and on December 9, 2020, AMCA filed for dismissal of the bankruptcy. The settlement included a $21 million payment to the states, suspended because of AMCA’s financial condition unless the company broke certain terms.

The vendor that held data on millions of patients filed for bankruptcy, citing the cost of telling them and remediating the breach. That is the central economic fact of the case. A business associate agreement may allocate notification costs and indemnity to the party at fault. Those clauses assume the party at fault will exist and be solvent when the costs fall due. AMCA’s bankruptcy filing in the same month as the first public disclosures shows how quickly that assumption can fail for a small vendor.

Quest’s 8-K pointed to the other half of the problem. Quest disclosed that it had insurance for certain potential liabilities and costs related to the incident, but that the coverage was “limited in amount and subject to a deductible.” The large client’s own insurance was finite. The small vendor’s resources were exhausted. Between them was a gap that someone had to fill.

For a procurement team, this turns vendor financial review into part of security due diligence. The question is whether the vendor is financially sound enough to deliver the service and also whether it could fund a breach response proportionate to the data it will hold. That depends on the number of records, the sensitivity of the fields, the number of clients whose data sits in the same systems, and the vendor’s own insurance. A collector holding records for millions of patients across several large clients carries a breach exposure that may be far larger than anything it could pay.

A rough sizing is enough to start. A client can estimate the number of its own patients whose records a vendor holds, add a judgment about other clients’ records in the same environment, and ask what notification, call center support and credit monitoring for that population would cost. Set against the vendor’s insurance limits and size, the comparison shows whether the vendor could carry the response. Where the answer is plainly no, the client knows before signing that the cost of any serious breach will come back to it, and can decide on that basis how much data to send and how closely to watch. The practical responses are familiar from other parts of procurement. A client can require cyber liability insurance with limits that bear some relation to the data held, name itself as an additional insured where the policy allows, and ask for evidence of coverage at each renewal as well as at signing. It can ask for financial statements and consider whether a vendor with thin margins and concentrated exposure is the right home for its patients’ data. It can also accept that for some small vendors no contract term will make the vendor able to pay, and plan instead to fund the response itself. A plan that says, in advance, that the health system will pay for notification of its own patients if a small vendor cannot, and has budgeted or insured for that, is more honest than an indemnity clause against a vendor that would not survive invoking it.

What the contract could enforce: notice, audit and termination

The timeline in the filings and the settlement shows a long gap between the intrusion and the clients’ knowledge of it. AMCA told Quest and Optum360 that unauthorized access ran from August 1, 2018 to March 30, 2019. It notified them on May 14, 2019. The attorneys general later said that AMCA had “failed to detect the intrusion, despite warnings from banks that processed its payments.”

HIPAA sets a floor for the vendor’s side of that gap. Under 45 CFR 164.410, a business associate must notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery. A breach counts as discovered on the first day it is known to the business associate, or would have been known by exercising reasonable diligence, and knowledge of any employee, officer or other agent other than the person committing the breach counts as the business associate’s knowledge. The “reasonable diligence” language matters in a case where, according to the states, warnings from payment processors had gone unheeded.

A contract can set a shorter clock and a lower trigger. It can require the vendor to tell the client of suspected security incidents, as well as confirmed breaches, within a period measured in hours or days. It can require the vendor to tell the client when a payment processor, bank or law enforcement agency raises a concern about the vendor’s systems. It can require the vendor to name a contact for security events and keep that contact current. These terms would not have prevented the AMCA intrusion. Each would have shortened the time during which the clients’ patients were exposed without the clients knowing.

Audit rights are the second contract tool. The AMCA settlement required the company to create an information security program with an incident response plan, employ a qualified chief information security officer and hire a third-party assessor. The LabCorp settlement in 2026 required LabCorp to require debt collectors to perform assessments and audits, to enforce cybersecurity standards through contracts and to keep an inventory of its contracts. Those terms describe what regulators expected a client to have demanded of a collector. A client can ask, before signing, whether the vendor has a named security leader, a written program and a recent independent assessment, and can make each a condition of the relationship.

Termination is the third. Both laboratories stopped sending new work to AMCA once notified, and LabCorp stopped AMCA working on pending accounts. That is the right immediate step, but it does not retrieve the data. A termination clause should say what happens to the client’s data when the relationship ends: return or certified destruction, within a stated period, with evidence. The 2026 settlement listed “the right of termination for non-compliance” among the requirements for debt collector contracts. A right to terminate is more useful when the client has also secured the right to get its data back or see it destroyed.

What stayed with the client: the duty that does not transfer

Whatever the contract said, some costs stayed with the clients. Quest’s 8-K said it had notified affected health plans and would make sure notice went to regulators and others as law required. The laboratories, not AMCA, were likely the names their patients knew. Both laboratories made securities filings, and both stopped sending work to AMCA. Those were costs of being the covered entity.

The 2026 Michigan announcement of the LabCorp settlement put the principle in direct terms. “While the data breach occurred at AMCA, the data involved was the sensitive data of Labcorp’s patients,” it said. “Companies can contract with vendors freely and delegate authority; however, data security is a non-delegable duty.” It described the settlement as upholding “the premise that HIPAA-covered entities have a duty to protect personal and protected health information and oversee vendors entrusted with that information.”

That language describes what a client keeps after outsourcing. It can hand a vendor the work of collecting a debt. It cannot hand over the responsibility for the patient’s information that went with the debt. Each of the four costs we describe ends there. Data the client chose to send, a vendor the client chose despite its finances, contract terms the client did or did not negotiate: each is a decision for which the client remains accountable.

For a health system, this means vendor oversight is a continuing obligation, not a signing ceremony. The LabCorp settlement terms illustrate what that oversight looks like to regulators: an incident response plan that includes internal reporting of vendor security events, a vendor risk management program with a dedicated team, tools to evaluate vendors, and verification of vendor compliance. Each of those is a function the client runs on its own side, with its own staff, whatever the vendor does.

The internal reporting point deserves emphasis. A vendor’s notice of a security event may arrive at whoever manages the vendor relationship, which for a collector may be the revenue cycle or patient accounts office, not the security or privacy office. If that office does not recognize the notice for what it is, or does not know whom to tell, the client loses time it cannot recover. The 2026 settlement’s requirement for an incident response plan that “includes internal reporting of vendor security events” addresses exactly this gap. A client can test it by asking each office that manages a vendor relationship what it would do if the vendor called tomorrow to report a breach, and checking that the answer reaches the privacy officer and the security team the same day.

One collector, many clients: the aggregation problem

The AMCA case had a feature that a single client’s vendor review can miss. AMCA specialized, according to the 2021 settlement announcement, in small-balance medical debt collection primarily for laboratories and medical testing facilities. Quest’s filing said AMCA’s affected system held information AMCA had received “from various entities.” LabCorp’s filing called AMCA “an external collection agency used by LabCorp and other healthcare companies.” One vendor held records for several large clients in one environment.

From each client’s point of view, AMCA was one vendor among many, holding a slice of its patients’ data. From an attacker’s point of view, AMCA held the combined data of all its clients. The size of the prize, and so the attacker’s interest, was set by the total, not by any single client’s share. A client assessing the vendor against its own data volume would underestimate the vendor’s attractiveness as a target.

The 2026 settlement with LabCorp addressed this directly. Among the specific requirements for debt collectors as “a specialized subset of vendors,” it listed segmenting the data that debt collectors aggregate for multiple clients. Segmentation does not stop a breach. It limits what one intrusion can reach. A client can ask whether its data is logically or physically separated from other clients’ data, whether access controls stop one client’s accounts from being reached through another’s, and whether a breach of one client’s environment would be visible to the vendor in time to protect the others.

Aggregation also affects the scale of the eventual response. The two laboratories’ filings described 11.9 million and 7.7 million people respectively. The 2021 multistate announcement said the breach potentially exposed the information of up to 21 million people in the United States. The 2026 announcement put the figure at over 27.5 million, including 10.2 million LabCorp patients. The published figures rose over time. A client that relies on a vendor’s early count of affected people, for its own disclosures or its own budgeting, should expect the count to move.

Where the intrusion began: the payment page

Both laboratories’ filings located the unauthorized activity on AMCA’s web payment page. That detail tells a client where to look first in any collections vendor. A payment page is internet-facing by design, takes payment card and bank account details from members of the public, and connects to the account records needed to match a payment to a debt. It is the vendor’s front door and the place where new sensitive data enters the vendor’s systems.

The attorneys general recorded that banks processing AMCA’s payments had warned it before the intrusion came to light. Card networks and acquiring banks may see patterns of fraud on cards used at a particular merchant and trace them back to a common point of purchase. A merchant that receives such a warning has an early signal that its payment flow may be compromised. The states’ account is that AMCA did not act on the warnings in time.

For a client, two questions follow. The first is whether the vendor’s payment page is in scope for the vendor’s own security testing and monitoring, and whether the client can see the results. The second is whether the vendor is contractually bound to tell the client when a bank, card network or payment processor raises a concern. Such warnings can arrive well before any confirmed breach, and they are exactly the kind of suspected incident a client should want to hear about.

There is also an architectural choice. A client can ask whether the vendor’s payment page handles card data itself or hands it to a separate payment processor, so that card numbers never reach the vendor’s own systems. Where card data does not pass through the vendor, the vendor holds less of the data that does the greatest harm when stolen, and a compromise of its page yields less. A client can ask which design its vendor uses.

Patients who never chose the vendor

The people whose data AMCA held had a relationship with a laboratory, through a doctor’s order, and in some cases with a collection agency only because a small bill went unpaid. Notification letters came from a company many recipients may not have recognized. That creates a customer experience problem with security consequences. Patients who receive an unfamiliar breach letter may doubt it is genuine, and criminals can imitate breach letters to harvest information. Patients who call their laboratory or their doctor to ask may find staff who know nothing of the vendor.

For a covered entity, the response plan for a vendor breach should include its own patient-facing communications, even where the vendor sends the formal notice. A client’s own website and call center may become the first point of contact for patients trying to understand a letter from a vendor. Front-line staff need a short script, a way to confirm whether a caller is in the affected population, and a route for questions they cannot answer.

There is a further fairness point. The people affected were, by definition, patients with an unpaid medical bill sent to collection. Some may have been under financial strain. A breach that exposes their payment details adds to that strain. Health systems that care about how patients experience billing have reason to include the security of their collections vendors in that concern, not leave it to procurement alone.

Disclosing on the vendor’s numbers

Both laboratories had to say something publicly before they had the facts. Quest wrote that it had “not yet received detailed or complete information from AMCA” and had “not been able to verify the accuracy of the information received from AMCA.” LabCorp wrote that AMCA “has not yet provided LabCorp a list of the affected LabCorp consumers or more specific information about them.” Each gave a figure for the number of patients whose data was in the affected system, based on AMCA’s account or on its own referral records.

This is a position any covered entity can find itself in when a vendor is breached. The vendor controls the forensic evidence. The client controls its own records of what it sent. The client’s disclosure to investors, regulators, health plans and patients has to rest on both, and the vendor’s side may be incomplete, late or wrong. In AMCA’s case, the published count of people potentially affected moved from the laboratories’ early figures to over 27.5 million by 2026.

Two practices reduce the risk of disclosing on a vendor’s word. The first is knowing, from the client’s own records, exactly which patients and fields were sent to each vendor, and when. LabCorp’s figure of 7.7 million consumers referred to AMCA came from its own side, from its referral records. Even that figure was not final: the 2026 announcement counted 10.2 million LabCorp patients. The second is a contract right to the vendor’s forensic findings, or a right to appoint the client’s own investigator, so that the client is not limited to the vendor’s summary. Statements based on the vendor’s account should say so, as both laboratories’ filings did.

The record a client should hold for each collector

The four costs and the aggregation problem point to a short file a covered entity can keep for every collections or billing vendor, and update at each renewal. It is the file a regulator investigating a vendor breach would ask the client to produce, and the file the client’s own executives would want on the day a vendor calls with bad news.

The file would list the fields sent to the vendor, the reason each is needed, and the date the list was last reviewed. It would describe what the vendor collects itself, including payment data, and how the vendor’s payment page handles card numbers. It would record the vendor’s cyber insurance limits, with evidence of coverage and its date, and a note of the client’s own view of whether the vendor could fund a response for the number of records it holds. It would show the business associate agreement and any security addendum, with the notice period for suspected incidents, the audit and assessment rights, and the return or destruction terms.

It would hold the latest assessment of the vendor, whether a questionnaire, an independent report or the client’s own review, with its findings and their status. It would name the vendor’s security contact and the client’s owner for the relationship. It would note whether the vendor holds other clients’ data in the same environment and how it is separated. And it would hold the client’s own count of patients whose data has been sent to the vendor, by year, so that a disclosure could rest on the client’s numbers as well as the vendor’s.

None of the entries requires new technology. Several require someone in the client organization to ask questions a procurement process may not ask by default. The 2026 settlement with LabCorp, with its requirements for contract inventories, verification of vendor compliance and assessments of debt collectors, describes a version of this file in regulatory language.

The strongest objection: the clients did what the rules required

The objection to this reading is that the laboratories were victims. They used a licensed collection agency for a lawful purpose. Their relationships with the vendor were governed by contract. They acted quickly when notified, stopped sending work, filed public disclosures and notified health plans. A vendor’s failure to detect an intrusion, despite warnings from its own banks, was the vendor’s failure.

We agree that the vendor’s failures were primary, and the 2021 settlement placed obligations on AMCA itself for that reason. But the objection proves less than it seems to. We read HIPAA’s structure as assuming that covered entities choose and oversee their business associates, and a business associate agreement as a legal minimum rather than a description of adequate oversight. The 2026 settlement shows that regulators, at least in this multistate investigation, expected more than the minimum: data minimization, vendor risk management with verification, specific controls for collectors and incident plans that include vendor events. Settlements are negotiated and do not establish what the law requires of every organization, and organizations should check with counsel on their own obligations. But they show what a coalition of state regulators thought a large covered entity should have had in place.

A second objection is that no client can audit every vendor deeply, and that a small collections agency is a low-priority vendor in a large health system’s portfolio. We accept that vendor programs have limited resources, which is why tiering matters. We think tiering that puts collectors low on the list may rest mainly on the service’s operational importance. AMCA’s case suggests tiering should also weigh the data the vendor holds, the number of other clients whose data it holds alongside, and its ability to pay for a breach. On those measures, a collector can belong near the top.

A third objection is about cost. Tighter contracts, insurance requirements and assessments raise the price of collection services and may exclude small vendors from the market. That is likely true. The AMCA case shows the other side of the ledger: a small vendor’s breach can impose costs on its clients that dwarf any savings from choosing it.

A fourth objection is that insurance solves the problem. If the client carries its own cyber coverage, a vendor’s insolvency matters less. Quest’s filing answers this in part: its coverage was limited in amount and subject to a deductible. Insurance shifts some cost, but it does not notify patients, answer regulators or restore trust, and a claim may raise questions from the insurer about the client’s own vendor oversight. We would treat insurance as one line in the plan for a vendor breach, alongside data minimization and contract terms, and not as a substitute for them.

How it applies by kind of organization

Laboratories and diagnostic companies. The 2021 announcement described AMCA as specializing in small-balance medical debt collection primarily for laboratories and medical testing facilities. Their collection volumes make collectors a significant data relationship even when each balance is small. The two laboratories in this case were also public companies, so a vendor breach became a securities disclosure question as well.

Hospitals and health systems. A health system may use several collection agencies, early-out billing vendors and payment processors. Each holds a slice of patient financial data. The aggregation point applies twice: each vendor may hold many clients’ data, and the health system may have spread its own patients across many vendors. An inventory of every party that receives patient billing data, with the fields each receives, is the starting point.

Physician practices and ambulatory networks. Smaller practices may rely on a billing company that in turn uses collectors, so the practice’s patients’ data may pass to a vendor the practice never contracted with directly. A practice can ask its billing company for the list of downstream vendors that receive its patients’ data and the agreements in place.

Revenue cycle intermediaries. Quest’s filing named Optum360, its revenue cycle management provider, alongside Quest as a recipient of AMCA’s notice. Where a revenue cycle company sits between the provider and the collector, the chain of agreements, notice and oversight gets longer. Each link should know who it must tell, and how fast, when the link below it reports an incident.

Health plans. Quest notified affected health plans. A plan whose members’ data was held by a provider’s vendor may have its own obligations and its own members asking questions. Plans can ask their contracted providers how they oversee the vendors that handle members’ data, and include notification of vendor incidents in their provider agreements. A plan that learns of a provider’s vendor breach from the provider, rather than from its members, is better placed to answer them.

With hindsight

The states’ case against the vendor ended with its payment suspended because of its financial condition. On March 11, 2021, a coalition of 41 attorneys general announced a settlement with Retrieval-Masters Creditors Bureau, the debt collection agency that did business as AMCA. It included a $21 million payment to the states, suspended because of the company’s financial condition unless it violated certain terms of the settlement. The company and its principals agreed to create and maintain an information security program with an incident response plan, employ a qualified chief information security officer, hire a third-party assessor, cooperate with the states’ investigations and keep evidence. It was barred from transferring, selling or using the personal information it had collected except as required by law. The announcement said AMCA had filed for bankruptcy on June 17, 2019, because of the costs of notification and remediation, and had filed for dismissal of the bankruptcy on December 9, 2020.

The states then turned to a client. On September 29, 2026, the Michigan attorney general announced a $2.3 million multistate settlement with LabCorp over the AMCA breach, saying data security is a non-delegable duty and that HIPAA-covered entities must oversee the vendors entrusted with protected health information. LabCorp agreed to pay $2,287,455 to the states and to requirements on vendor management: an incident response plan that includes internal reporting of vendor security events, minimized sharing of data with vendors, an expanded vendor risk management program with a dedicated team and verification of compliance, specific requirements for debt collectors including contract inventories, contractual security standards, data segmentation, assessments and audits and a right of termination, and a third-party assessment focused on vendor risk. The announcement said LabCorp had separately agreed to a $35 million settlement in the related class action, which remained ongoing against other AMCA client covered entities, and put the total potentially exposed at over 27.5 million people.

Federal rules moved toward the same expectation but had not arrived as of our check. On January 6, 2025, HHS published a proposed rule to strengthen the HIPAA Security Rule. It would require regulated entities to obtain written verification, at least once every 12 months, that each business associate has deployed the required technical safeguards, supported by a written analysis by a qualified person and a certification by someone with authority to act for the business associate. It would also require business associates to report activation of their contingency plans within 24 hours. A Federal Register search on November 14, 2026, for documents affecting 45 CFR part 164 published since the proposal found no final rule, only a January 14, 2026, document on tribal consultation on proposed modifications to the HIPAA Privacy Rule. The proposal’s verification requirement remains a proposal.

What held up from June 2019 was the economic lesson: the vendor could not pay, and its clients carried the consequences. The 2026 settlement turned that lesson into enforcement terms aimed at the client. In our reading, its list of requirements describes the oversight a covered entity would need to have had in place before June 2019 to limit what happened: less data sent, vendors verified, collectors segmented, vendor incidents reported internally, and a right to walk away. Other AMCA clients remained defendants in the class action as of the September 2026 announcement.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • AMCA
  • business associates
  • vendor risk
  • HIPAA
  • medical debt collection