Warnings and Answers

What this case is about. David Medeiros runs ABI Resources LLC, a provider in Connecticut's Medicaid Acquired Brain Injury (ABI) waiver. He has a traumatic brain injury. Since May 2015 he has warned Connecticut's Department of Social Services (DSS) in writing that waiver participants were being steered to certain providers instead of choosing freely. Later he raised service access, payment checks and retaliation. These are his reports, not findings. DSS said it reviewed the 2015 concerns, and in 2023 it sent his referral concerns to its Special Investigations unit; no final decision has been found. From 2022 his reports reached HHS-OIG, DOJ, GAO and CMS. Most answers were receipts, referrals or closures. A CMS fraud contractor reviewed his concerns and closed the review in May 2026. DSS suspended ABI from new clients in 2019; David disputes the reason. In a November 10, 2026 reply to David's records request, DSS attached an export of its contractor GT Independence's provider directory, which lists ABI's enrollment as ACTIVE, effective March 25, 2026 and expiring March 25, 2028; the listing does not show whether or when the 2019 suspension ended, and it does not settle the dispute or any payment question. Records show $97,882.76 in denied or unclear claims; no loss is established. He proposes safeguards such as a public provider list, random-order referrals and independent payment checks. The records show he warned before several 2024-2026 federal actions, not that he caused them.

David Medeiros warned Connecticut and federal offices about the Medicaid Acquired Brain Injury (ABI) Waiver Program for years. This page shows what those offices did next: their dated replies and decisions, who knew before each decision, how they answered his disability accommodation requests, what his records requests produced, what happened to David and his agency afterward, and the safeguards he proposes so it cannot happen again.

How to read this page: a thank-you, a read receipt or a forwarded email shows that an office received a report. It is not proof that anyone investigated. A closure or dismissal is a decision by that office, not a court ruling. Complaints are David’s reports, not findings. Dates in calendar order do not show cause. Every quote and number on this page was checked word for word against the original email, letter, law or record on November 14, 2026 (231 checks, all passed). Most originals are kept privately because they also contain other people’s details; privacy-cleaned copies of 38 of them, including agency decision letters, are now public. Lines added on November 15, 2026 were copied from the original records named in each line’s source. Lines added on November 16, 2026 were checked the same way. People who receive services are never named.
  1. Proof and gaps: what the records show and what is still missing
  2. What CMS did with the warnings
  3. What each agency actually decided
  4. CHRO’s two findings on the August 7, 2024 meeting: both sides
  5. Who knew what before each decision
  6. Accommodation requests and answers
  7. Disability Rights Connecticut: a request for advocacy (2023-2024)
  8. Records requested, produced and still missing
  9. What happened to David and ABI, and what the money records show
  10. Permanent Protection: six safeguards (David's proposal)
  11. From Connecticut to the nation: how far the warnings traveled
  12. Official findings already public
  13. Latest steps (November 14, 2026)
  14. Corrections to older pages

Proof and gaps: what the records show and what is still missing

"David's account" is his side. A receipt shows an office got a report; it is not proof anyone investigated. "After" means calendar order, not cause.

1. Did David warn DSS early, and what did DSS say?

2. What happened during the 2018 Mindscape transition?

3. Why was ABI suspended from new clients in 2019, and when did it end?

4. What did federal offices do with his reports?

5. Were disability accommodations given?

6. What do the money records show?

7. Did his warnings lead to national action?

All source records: privacy-cleaned copies. Safeguards that would close these gaps: Permanent Protection and the Remedy Ledger.

March 5, 2026: one FBI recipient rejected

A retained provider-rendered notice received at 19:41:57 UTC reports 550 #5.1.0 Address rejected. for the FBI recipient of the report timestamped 19:41:39 UTC. Retained message fields put the Governor's office in To and the FBI address in Bcc; the normalized export display is qualified in the reading copy.

This explains the existing BOUNCED:1 label for that recipient and message. It does not show why delivery failed, decide the allegations, or negate the separate July 25, 2025 receipt and August 11, 2025 response. Any accepted resend and evidence inventory remain unknown here. DSS and CMS replies in the thread do not establish FBI acceptance.

Read the retained notice excerpt and its limits · Read the matching machine record

Is Connecticut's ABI waiver head count real? A count check

What Connecticut has published

  1. 571 people on the two ABI waivers: ABI I, 379; ABI II, 192. The count is as of October 28, 2019.Source: Connecticut Office of Legislative Research, report 2019-R-0114.
  2. "Over 550 enrollees" on the ABI waivers.Source: DSS, "HUSKY Health Eligibility Basics", presented to the Medical Assistance Program Oversight Council on November 9, 2023.
  3. Federal limits in the waiver applications DSS posted:
    • ABI II: up to 315 people in its first year (December 2024 to November 2025) and 349 in its second year (December 2025 to November 2026).
    • ABI I: up to 228 people in 2027, in the renewal draft DSS posted for public comment in August 2026.
    Source: DSS, Medicaid Waiver Applications page (Table B-3-a in each application).

About "516"

An AI search summary said DSS reports 516 active ABI waiver participants. This archive has not found a Connecticut record that states that number.

The open question

Connecticut has not published proof that every person it counts and bills for is:

  • alive;
  • eligible for Medicaid, including citizenship or qualified immigration status;
  • living in the community, not in a hospital or nursing home, while waiver services are billed.

Records that would answer it

  • The yearly CMS-372 reports for each ABI waiver (people served and dollars spent).
  • DSS's checks of waiver participants against death records and other eligibility data.
  • Checks for waiver services billed while a person was in a hospital or nursing home.
  • The electronic visit verification (EVV) records for home visits.

This is a question, not a finding.

Related CMS record: October 30, 2025 HCBS settings plan determination and its limits

Connected Records Across This Archive (13)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

FOIA request pages (1)

Early Warning Record (11)

Livewire (1)

PDF files with their exact SHA-256: PDF File Index.

Original complaint behind the HHS referral: DOJ's retained complaint 301882-TRG supplies the reported content and original production reference. It does not establish which HHS office accepted the referral, its receiving control, accepted exhibits or resulting handling.

What CMS did with the warnings

Oldest first. A thank-you, a read receipt or a promise to escalate is not proof of action.

Still open: appeals on CMS requests 111920237002, 112020247009 and 022720267093. No decision letter found.

CMS gave two different answers about request 010220247006. David appealed this CMS records request on January 9, 2024, and CMS acknowledged the appeal on January 11, 2024. On July 14, 2025, Sybil Anderson of CMS’s Office of Strategic Operations and Regulatory Affairs (OSORA) wrote: “Your case is still processing.” Four days later, on July 18, 2025, the CMS records office wrote: “Please, be advised that this request was closed on 08/07/24.” The same July 18 email gives the same closing date for request 122620237029, which Ms. Anderson had also called “still processing” on July 14. No August 7, 2024 closing letter from CMS was found in David’s mailbox. These are CMS’s own words; they do not show which answer is right or why they differ. Source: CMS emails of January 11, 2024, July 14, 2025 and July 18, 2025

Related CMS record: October 30, 2025 HCBS settings plan determination and its limits

Connected Records Across This Archive (3)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

FOIA request pages (3)

PDF files with their exact SHA-256: PDF File Index.

What each agency actually decided

Receipt = we got it. Referral = sent elsewhere. Final = done. Most are not rulings on whether David's reports are true. Where an office did rule, the line says so.

CHRO’s two findings on the August 7, 2024 meeting: both sides

On August 7, 2024, David went to a Providers Council meeting run by the Brain Injury Alliance of Connecticut (BIAC). The Department of Consumer Protection (DCP) gave a presentation. David asked to record the meeting as a disability accommodation; he has a brain injury. On October 28, 2024 he filed two complaints with the Connecticut Commission on Human Rights and Opportunities (CHRO): one against BIAC and one against DCP. CHRO ruled against him in both. Each finding is shown below with David’s account and the other side’s account, as CHRO wrote them down. A CHRO finding is CHRO’s decision, not a court ruling. Witnesses are named by job title only.

1. BIAC case, No. 2510184 (finding dated January 13, 2026)

2. DCP case, No. 2510183 (finding dated January 22, 2026)

The August 7 recording dispute: where the accounts differ

Reopening: on the December 9, 2026 agenda, not decided

Source: CHRO final findings and notices (January 13 and 22, 2026); CHRO emails and notices (January 28, October 7 and November 5, 2026); draft Commission minutes (October 14, 2026); David’s sent comments (December 29, 2025). Privacy-cleaned extracts: CHRO final findings, January 13 and 22, 2026.

Who knew what before each decision

Each item: David's earlier report, proof the office got it, who decided, the reason they gave, and what followed. Calendar order is not cause. Complaints are David's reports, not findings.

Nov 6, 2018 - DSS - Warning email.

Oct 10, 2019 - DSS - New clients suspended.

Sep 28, 2023 - DSS - Limit on messages.

May 29, 2024 - CHRO - Complaint against DSS dismissed.

Jan 13 and 22, 2026 - CHRO - Complaints against BIAC and DCP dismissed.

Related: November 2018 on the Early Warning Record · October 2019 suspension · Rights and the Record · Three DSS emails side by side (December 1 and 5, 2022; received September 28, 2023)

Connected Records Across This Archive (2)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

Early Warning Record (2)

PDF files with their exact SHA-256: PDF File Index.

Accommodation requests and answers

David has a traumatic brain injury. He asks offices to work with him in writing, by email. "No answer found yet" is not a refusal.

Connected Records Across This Archive (1)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

Livewire (1)

PDF files with their exact SHA-256: PDF File Index.

Disability Rights Connecticut: a request for advocacy (2023-2024)

Disability Rights Connecticut (DRCT) is Connecticut’s protection and advocacy agency for people with disabilities. The Administration for Community Living (ACL), part of HHS, funds the protection and advocacy agencies, including a program for people with traumatic brain injury (acl.gov/programs/pa-programs). This is the record of David’s written request to DRCT and DRCT’s answers, as found in his mailbox. DRCT’s emails carry a confidentiality notice, so only short quotes are shown.

The other side: DRCT did respond. It confirmed receipt the same day, sent the request to its Board, and said it was investigating. It also said early on that it was unlikely to be able to take on the issues. Nothing here shows what DRCT decided, or that it did anything wrong.

Records requested, produced and still missing

Each request is a dated record of what David asked for. The answer is separate evidence. "No records" means that office says its search found none. It does not show the records never existed.

DateAgencyAsked forWhat came backAppeal
Dec 6, 2021CT DSSABI waiver, MFP, personal care recordsReceived; part sent Oct 6, 2022, rest promisedNone
Nov 15, 2022CMSMember counts; one named providerNo records; ask the StateNone
Mar 28, 2023CMSABI waiver and MFPRecords: 261 pagesNone
Apr 4, 2023CMSMoney Follows the PersonRecords: 211 pagesNone
Apr 27, 2023CMSABI waiver programsReferred to paid research dataNone
Sep 26, 2023CMSFederal ABI waiver and MFP moneyAsked which staff to search; closedNone
Nov 20, 2023CMSBehavior analystsNo recordsPending since Mar 1, 2024
Dec 21, 2023CMSHis own CMS requestsRecords: list of 51 requestsNone
Dec 21, 2023CMSStopped companion-service approvalsCMS says closed; no letter found"still processing" in Jul 2025
Jan 6, 2024CMSRecords on an HHS civil-rights complaintNo recordsNo decision found
Sep 3, 2024CMSABI waiver program recordsNo records; ask the StateNone
Nov 5, 2024U.S. LaborMedicaid services, two provider numbersTwo interim letters, then final letter Jan 8, 2025None found
Nov 20, 2024CMSABI waiver provider numbersNo recordsPending; "update" Jun 10, 2026
Feb 27, 2026CMSOne named providerNo recordsPending since Apr 28, 2026
Feb 27, 2026CMSCare management, ABI Waivers I and IIPaid research data; ask the StateAppeal emailed Nov 14, 2026

In all: 79 CMS control numbers, Nov 15, 2022 to Apr 27, 2026.

All requests by number: FOIA records.

What happened to David and ABI, and what the money records show

"After" means calendar order only. It does not prove cause.

Counted from the records in hand, up to Oct 27, 2026. Denied and unpaid in those records. Not called "lost" or "owed."

DSS records reply, November 10, 2026: provider directory lists ABI Resources as ACTIVE

What this is: GT Independence’s online provider directory, as attached by DSS to its records reply. It is not a list made by DSS. GT Independence checks provider credentials for DSS under contract.

  • Date - November 10, 2026, 8:44 AM Eastern (sent 13:44:15 UTC).
  • Source office - Connecticut Department of Social Services, FOIA office (FOIA.DSS@ct.gov). Signed by Kelly Bartomioli, Paralegal Specialist, Communications & Legislative Management, Privacy Officer & FOIA Officer. Also sent to the DSS Commissioner’s office and the Connecticut Freedom of Information Commission; copied to two DSS staff, including Christine Weston.
  • Control number - None is stated in the reply. It answers David’s February 27, 2026 request and his November 7, 2026 follow-up about the “DSS Medicaid ABI Waiver Provider Master List.”
  • What it shows - DSS wrote that the information “is publicly available” on GT Independence’s online provider directory, and attached two exports of that directory filtered to the ABI I and II waiver (158 providers; file date November 8, 2026). ABI Resources LLC is entry “9 of 158”: Enrollment ACTIVE; Effective Date Mar 25, 2026; Expires Mar 25, 2028 (PDF page 21; spreadsheet data row 9). The same entry lists 10 ABI waiver services, each marked “Effective Jul 29, 2025” (PDF page 20). DSS wrote: “The Department considers this request to have been fulfilled.” It also wrote that the directory “may not reflect recent changes within the last month.”
  • What it does not show - ABI’s status in earlier years, or whether or when the October 2019 new-client suspension ended. Any payment, claim decision or the $97,882.76 question. NPI or EIN numbers, ownership disclosure forms or enrollment history: David asked for these, and the two files do not contain them (the spreadsheet’s “Owner Name” for ABI says “Not Provided”). Any DSS finding about the dispute. The 2028 date is a stated expiration date, not proof of status on any later day.
  • Related records - GT Independence’s credentialing letter dated March 12, 2026, and Connecticut Medicaid’s re-enrollment approval dated March 25, 2026, whose provider agreement runs March 25, 2026 to March 25, 2028 — the same dates as the directory entry (see “Approved” above).

    Related: March 9, 2020: Connecticut Medicaid approves ABI Resources’ re-enrollment · Free choice of care provider

    Related Allied records: DSS contract 12DSS5101AS: Allied's written duty to keep the ABI waiver provider directory, and when a provider may be removed · September 2018 and February 28, 2020: ABI's answer to Allied's draft audit, and Allied's re-credentialing letter · June 1-2, 2020: "Again / Allied Community Resources ABI Program Provider Directory" and the DSS reply

  • Exhibit files - PDF excerpt (an added cover page plus original pages 1, 20 and 21) and spreadsheet header and row 9. Withheld: ABI’s office street address and ZIP+4, one email address, the GTI number and the AVRS provider number. The other 157 providers are not shown.
  • SHA-256, full originals - PDF “GTI Provider Directory.ABI.pdf” (375 pages, 1,952,009 bytes): 40f771dc6248b04418e3d71a035d4274294121754f8b112d52bdc1a87fdcfa5a; spreadsheet “ABI.Providers-2026-11-8.csv” (158 providers, 305,452 bytes): 300d445ca71e7684085e7e7aac172b7e96f39e5406290a1bf4c5b2eeef3ee4aa.
  • SHA-256, excerpt files - PDF excerpt (115,927 bytes): e8ee3be88588c293bb2b1bbe380cd0f97d9fde8cbd05b39e2b5d29eb6fbe1a8f; spreadsheet row (2,767 bytes): 62f9e88df7cf57c02a9aace23813f105cb4b406b67abf6ebaaee60a47154ea30.

Independent public-records archive. Verify independently. A filing is not a finding.

David has a traumatic brain injury. Accommodation requests: /warnings-and-answers/#accommodations.

These are David's reports. No offense is proved here.

July 22, 2025: the IC3 report described Medicaid and payroll consequences

David's retained IC3 submitted-form print, dated July 22, 2025, describes the disputed Google Ads charges as a threat to ABI Resources' Medicaid operations. The narrative says the reported loss jeopardized payroll and support for disabled clients, and asks the FBI to coordinate with the FDIC, DOJ, HHS and Secret Service.

This is a documented statement of what David reported. The form does not establish the alleged theft, the amount ultimately owed, the cause of any service disruption, or that those agencies actually coordinated. Supporting documents being described or offered is also different from an accepted attachment inventory.

The saved form marks itself as an update to an earlier IC3 submission. A separately retained form for that earlier submission prints June 26, 2025; the July 22 narrative also gives a conflicting July 22 date for the earlier filing. That date conflict remains unresolved.

The relationship between these saved forms and the separately numbered I2507081647058791 complaint is unverified. The July 25 FBI receipt and August 11 financial-scope statement remain separate documented records; neither identifies the exact July 22 narrative or accepted attachments. FBI/IC3's issued control-to-version mapping and receiving-file inventory would resolve that connection.

Source: retained 11-page IC3 Complaint Submitted print. Literal Date Filed: 7/22/2025 11:00:06 AM EST. EST is the printed label; no UTC conversion is assumed. SHA256: abcfa95b37a2bcdb111af5e842592e0aacadfe8b2edc26fbee45977ce7f22fc0.

Exact words (physical page 5): "The stolen funds directly compromised federally supported disability services." The word "stolen" is the filer's characterization. This excerpt verifies reported content, not the underlying allegation or acceptance by an investigator.

Independent public-records archive. Verify independently. A filing is not a finding.

November 15, 2026: what was reported and what is still unanswered

All times are Eastern time. Source: David’s sent emails and the replies in his mailbox.

The earlier Google record these requests rely on:

Still unanswered: FBI New Haven, Google and the FTC. None of these has said what it found.

Update, November 16–18, 2026: NCUA answered. On November 16, NCUA’s Office of Inspector General replied that questions about the Consumer Assistance Center’s decision or process go to NCUA’s Ombudsman. On November 17, the Consumer Assistance Center wrote that the concerns “do not appear to involve a federal law or regulation for which the NCUA is the primary regulator,” that it was closing its file, and that it was forwarding the correspondence to the Connecticut Attorney General. On November 18, the Ombudsman answered David’s two November 15 emails: cases 00254194 and 00254526 “were considered duplicative and administratively closed”; because the matters involve a business account, the case belonged with the state Attorney General; and the Ombudsman “considers this matter closed.” These are NCUA’s statements about its authority and its handling, not findings about the disputed charges. The Ombudsman dates the closure of case 00254192 to October 17, 2025. Whether the Attorney General’s office received the forwarded correspondence is not shown in these emails. Source: NCUA emails of November 16, 17 and 18, 2026 (addresses and phone numbers withheld)

November 15, 2026 (continued): requests for federal review

One more DOJ acknowledgment: record 868850-WNS, received November 16, 2026 at 10:43:32 UTC (5:43:32 a.m. Eastern). It is one more retained acknowledgment, not a finding; these totals are not independent complaints. How these acknowledgments differ from DOJ’s 46 CLOSED headers · source notes.

Later that day David sent many more requests. Each one asked a federal office to review how one named official, office or contractor handled his reports. Each is a request, not a finding. None of them shows that anyone named did something wrong. Officials are named with the title in their own work emails or official pages; where no title was found, only the office is given. CHRO is the Connecticut Commission on Human Rights and Opportunities, FOIC the Connecticut Freedom of Information Commission, and DSS the Connecticut Department of Social Services. All times are Eastern time.

Proof levels. DOJ confirmation email: DOJ emailed a record number. Confirmation page: the office’s website showed a “submitted” page and gave no number. Sent; delivery notice: the receiving mail server reported delivery. Sent: the email left David’s mailbox and no delivery notice came back. None of these shows that anyone read or acted on a request.

U.S. Department of Justice, Civil Rights Division

Disability reports on DOJ’s civil rights form, one per person. The time is when DOJ’s confirmation email arrived. A record number shows DOJ received a report; it does not show that DOJ opened an investigation. Record 868451-GFL, about the FBI, is in Latest steps.

HHS Office of Inspector General hotline

The hotline gives no case numbers. Its page said: “You have successfully submitted your complaint.”

CMS Medicaid Integrity Program (email)

Outlook reported that each email was relayed to the CMS mail server, but CMS’s server sent no delivery notice. So the proof level is “sent”.

Five Medicaid contractors (asked for review; nothing is proven against them)

Other federal offices

DOJ sent 35 confirmation emails on November 15, 2026: 868451-GFL (see Latest steps), the 33 records above, and 868558-RJT. The other offices give no numbers. When this list was checked on November 16, 2026, ACL had answered one of them on November 16, 2026 (see the DRCT record); no other office had answered. Automatic receipts are not answers. Waiting for the other answers. Source: DOJ confirmation emails; confirmation pages saved on November 15, 2026; David’s sent emails and their relay or delivery notices; titles from each official’s own emails or official pages.

Connected Records Across This Archive (7)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

FOIA request pages (2)

Early Warning Record (3)

Rights and the Record (1)

PDF files (1)

  • PDF: dss-gt-directory-excerpt-abi.pdf (links to this PDF; same file SHA-256, starts e8ee3be88588c293)

PDF files with their exact SHA-256: PDF File Index.

Permanent Protection: six safeguards (David's proposal)

This is David's proposal, not a finding. It adds detail to the Remedy Ledger, where all 7 requests still show "STATUS_UNKNOWN", and to the Impact Ledger. Each safeguard gives the problem, the change, who can make it, proof it was done, and a test. Connecticut's 2027 session runs January 6 to June 9, 2027.

1. A public list of every provider (Remedy Ledger FMR-R-001)

2. Real choice, in random order (FMR-R-002)

3. Protective services for adults 18-59

4. Independent checks of payments

5. Every fraud report gets a traceable answer (FMR-R-006)

6. Protection for people who report

Related CMS record: October 30, 2025 HCBS settings plan determination and its limits

From Connecticut to the nation: how far the warnings traveled

Oldest first. "After" means calendar order, not cause. Complaints are David's reports, not findings. Labels: David warned before this (no record ties them); his report reached the office involved (a receipt or reply); records link his report to this action (a referral, forward or review notice).

Earlier federal warnings on personal care

David's warnings and who got them

Federal reviews of Connecticut

Federal steps on his own report

Later national actions

For each of these: David warned before this.

The strongest statement the records support today

David warned Connecticut's Medicaid agency in writing about provider-choice steering in May 2015, years before the 2024-2026 federal actions above. His reports reached HHS-OIG, DOJ, GAO and CMS, and in 2026 CMS's fraud contractor reviewed his concerns, then closed the review in May 2026. No record yet shows his reports caused a national action, and federal offices warned about personal care fraud before him.

Records that would make it stronger

Full timeline: Early Warning Record.

Connected Records Across This Archive (1)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

Early Warning Record (1)

PDF files with their exact SHA-256: PDF File Index.

DOJ's released record for 301882-TRG retains David's June 5, 2023 allegations about DSS favoritism, ignored reports and unfair solicitation involving the ABI Waiver and Money Follows the Person programs. DOJ's June 8 response said it was referring that complaint to HHS. These are reported allegations and a stated referral, not agency findings. The HHS receiving control, accepted exhibits and resulting handling remain unknown. Read the complaint text DOJ retained and its source reference.

Official findings already public

These are official findings about Connecticut’s systems. They do not name ABI Resources and are not findings about David’s reports.

Related CMS record: October 30, 2025 HCBS settings plan determination and its limits

Records connected November 16, 2026

Read three distinct records together: DSS’s written provider-selection policy; David Medeiros’s retained DOJ complaint and DOJ’s stated HHS referral; and the payer record resolving the 177-line May 2022 matching gap. They establish a written standard, an attributed report and referral, and a specific payer adjudication record. Individual implementation of choice, HHS’s accepted referral contents and handling, and bank settlement still require separate evidence.

Each card below was checked against the original record. Each one shows the exact words, what the record does not show, and the records it connects to. A filing is not a finding.

March 20, 2025: Attorney General's office writes that it forwarded David's CCCI complaint for review

On March 20, 2025, the Connecticut Attorney General's office answered David's complaint about Connecticut Community Care (CCCI), the ABI waiver care-management agency. It wrote: "I have forwarded this email to the chief of our Government Fraud Section for review." The reply came from the office's main email address at 4:54 PM Eastern, the same afternoon David sent his complaint. Its signature reads "AG CAU1" and "Intern." It gave no case number.

David's complaint was titled "Request for Investigation – Medicaid Fraud, Whistleblower Retaliation, and Illegal Kickbacks Involving CCC Connecticut Community Care." These are David's allegations. A complaint is not a finding.

The reply also suggested a complaint to the State Auditors of Public Accounts. The next morning, March 21, 2025, the Auditors' whistleblower office wrote: "Please consider this email as confirmation that your submission has been received." Its email carries a copy of David's March 20 email to the Attorney General. David's own copy shows he sent it only to the Attorney General. The record does not show who sent it to the Auditors.

What the review found is not known. David wrote to the office again on October 8 and October 27, 2025. He asked whether his complaint had been referred, and asked for any referral records. No written answer was found in his mailbox (searched through November 16, 2026). A separate reply on October 2, 2025 was about a different complaint, about bank charges. It does not decide the CCCI complaint.

  • Exact words - “I have forwarded this email to the chief of our Government Fraud Section for review.” — Office of the Attorney General, State of Connecticut (reply from the office's main mailbox; signature lines "AG CAU1" and "Intern"), March 20, 2025.
  • Exact words - “You may also wish to file a complaint with the Auditors of Public Accounts” — Office of the Attorney General, State of Connecticut (same reply), March 20, 2025.
  • Exact words - “Please consider this email as confirmation that your submission has been received.” — Auditors of Public Accounts, State of Connecticut (WB Complaints mailbox; no person named), March 21, 2025.
  • Exact words - “Request for Investigation – Medicaid Fraud, Whistleblower Retaliation, and Illegal Kickbacks Involving CCC Connecticut Community Care” — David Medeiros, ABI Resources (subject line of his complaint; his allegation), March 20, 2025.
  • Exact words - “What you have described is a banking fraud issue that this office cannot assist you with.” — Thomas Martin, Forensic Fraud Examiner, Office of the Attorney General (separate banking complaint), October 2, 2025.
  • Exact words - “I am missing a nexus between the recent unauthorized banking transactions through the Charter Oak Federal Credit Union and your prior complaints about the Medicaid ABI Waiver program.” — Thomas Martin, Forensic Fraud Examiner, Office of the Attorney General (separate banking complaint), October 2, 2025.
  • Record numbers - FBI IC3 complaint I2507081647058791 (subject line of the separate October 2, 2025 banking reply; already public at /warnings-and-answers/#nov-15-2026)
  • What it does not show - That the chief of the Government Fraud Section received, read or reviewed the complaint. The reply is the office's statement that it forwarded it. Who the chief was. The reply does not name the chief. An investigation, a referral to any other agency, or any finding about CCCI or anyone else. A case or tracking number. The reply gave none. Who sent the complaint to the Auditors of Public Accounts, or what the Auditors did with it. A written outcome. None from the Attorney General's office about this complaint was found in David's mailbox (mail copy searched through November 12, 2026; live search through November 16, 2026). That is a search result, not proof that no outcome exists. Any answer to David's October 8 and October 27, 2025 follow-ups, including his request for referral records. None was found. Anything about the March 20 complaint in the October 2, 2025 banking reply. That reply does not mention it and does not decide it. Whether CCCI did what David alleges.
  • Counter-evidence and other side - The office did answer in writing, the same afternoon. This is not a case of no response. On October 2, 2025, the office's Forensic Fraud Examiner reviewed David's separate bank-charges complaint. He wrote that he was "missing a nexus" between the bank charges and David's "prior complaints about the Medicaid ABI Waiver program." He added: "Without direct involvement of state funds, the False Claims Act does not apply." That is his view of the banking complaint. It is not a ruling on the CCCI complaint. The October 2 reply pointed David to another office: the Connecticut Department of Banking, for a complaint about the credit union.
  • Connected records - Read the March 20, 2025 reply, privacy-cleaned copy; What each agency actually decided; Earlier report on the same subject: April 14, 2021, "CCCI - Steering clients" (to DSS); Earlier: August 2022 request to CCCI for an internal investigation; Earlier: December 1, 2022 report to the DSS Commissioner's office; Where David took his concerns (the Attorney General's office from October 2023); The separate banking matter (Charter Oak, IC3) and what is still unanswered; Proof and gaps (question 6: the money records); Permanent Protection, safeguard 5: every fraud report gets a traceable answer (David's proposal)

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, March 20, 2025: Referral). A link is navigation only.

November 2022: David's HHS-OIG complaint text and the agency records that followed

On November 29, 2022, the HHS Office of Inspector General (HHS-OIG) Hotline confirmed that David had submitted a healthcare-fraud complaint. In the same minute, David saved a copy of the form's review page. It lists the allegation type "Kickbacks," the program "Medicaid," and "ABI Waiver Program l and ll as well as MFP program." It names a 24-page attachment. The receipt confirms a submission only. Beyond the words "Healthcare Fraud," it shows no topic, attachment or case number.

The 24-page narrative is dated November 28, 2022. David wrote that he was "unsure" whether it was fraud. He listed what "may appear to be" patient steering, unfair competition, and kickbacks or inducements for Medicaid referrals. He wrote that DSS care management appeared to send Medicaid referrals to one provider, The Supported Living Group LLC, instead of using the approved provider list. These are David's allegations, not findings.

Two weeks earlier, on November 15, 2022, David asked CMS under the Freedom of Information Act how many people were in the ABI Waiver and Money Follows the Person programs, and how many that provider served (control number 111520227061). CMS answered over about 14 months: a receipt letter dated November 22, 2022; a "no records" letter on November 8, 2023; emails on November 20, 2023 saying the information is kept at the State level; and, on January 25, 2024, a copy of the 2022 request itself, released in answer to a later request (010920247054).

DSS also answered. On December 1, 2022, David emailed the DSS Commissioner's office in similar words. DSS met with him on December 8 and, on December 9, asked for specific examples it could research. No HHS-OIG intake number, reviewer or outcome has been found. No finding by any office on these allegations has been found.

  • Exact words - “Other: ABI Waiver Program l and ll as well as MFP program” — David Medeiros, ABI Resources (his entry in the HHS-OIG form's Program type field), November 29, 2022.
  • Exact words - “I am unsure if this is indeed fraudulent activity or if people are using loopholes to achieve personal financial gain; however, it does appear to be wrong for many reasons.” — David Medeiros, ABI Resources (complaint narrative 'Connecticut Medicaid Fraud November 29 2022.pdf', body dated November 28, 2022), November 28, 2022.
  • Exact words - “Corruption of medical decision-making, patient steering, unfair competition, monopolization efforts, kickbacks, or inducements for Medicaid Referrals.” — David Medeiros, ABI Resources (complaint narrative, under the heading '3. How: What may appear to be;'), November 28, 2022.
  • Exact words - “CT DSS care management appears to be funneling Medicaid Referrals to the Supported Living Group LLC exclusively and not using the CT DSS Medicaid approved agency provider list.” — David Medeiros, ABI Resources (complaint narrative, item 3f; his allegation), November 28, 2022.
  • Exact words - “You have successfully submitted your complaint.” — HHS Office of Inspector General Hotline (automatic receipt from no-reply@oig.hhs.gov), November 29, 2022. Open the record
  • Exact words - “The Hotline will not be able to confirm receipt of your complaint or respond to any inquiries about action taken on your complaint.” — HHS Office of Inspector General Hotline (automatic receipt), November 29, 2022. Open the record
  • Exact words - “Would the Connecticut Department of Social Services, DSS, please provide information in reference to Medicaid programs ABI Waiver programs I and II, and the MFP, Money Follows the Person program?” — David Medeiros (request text in CMS's copy of his FOIA request, control 111520227061, 'submitted November 15, 2022 01:35:07pm ET'), November 15, 2022.
  • Exact words - “Within your correspondence, you requested records relating to <Insert description of the request>.” — Emmett Nicholson, Director, Division of FOIA Analysis - C, Freedom of Information Group, CMS (no-records letter for control 111520227061), November 8, 2023. Open the record
  • Exact words - “we were unable to locate any records responsive to your request.” — Emmett Nicholson, Director, Division of FOIA Analysis - C, CMS (same letter), November 8, 2023. Open the record
  • Exact words - “I have been informed that the detailed information you are seeking is kept at the State level, not with CMS.” — Catherine Grochowski, Senior FOIA Analyst, Freedom of Information Group, CMS, November 20, 2023. Open the record
  • Exact words - “We are releasing those documents to you in their entirety, without deletions.” — Emmett Nicholson, Director, Division of FOIA Analysis - C, CMS (letter dated 1/25/2024 on control 010920247054), January 25, 2024. Open the record
  • Record numbers - 111520227061; 010920247054
  • What it does not show - Which file HHS-OIG accepted. The form names the attachment, but the receipt lists no attachment. Two saved copies of the narrative have the same text but different file bytes (one made November 29, 2022, one December 8, 2022). An HHS-OIG intake or case number, who reviewed the complaint, or what HHS-OIG did with it. Any finding by HHS-OIG, CMS, DSS or another office that the conduct David described happened. A filing is not a finding. That the narrative itself went to CMS or the FTC in November 2022. No email copy was found in David's mailbox. CMS's November 2022 record is a records request, not a complaint. The first FTC report receipt found is dated July 11, 2023 (already public). That DSS received the narrative text. The December 1, 2022 email to DSS had no attachment. That CMS's "no records" letter or its January 25, 2024 letter answered the HHS-OIG complaint. They answer David's records requests to CMS. What happened inside CMS between the November 22, 2022 receipt letter and the November 8, 2023 answer.
  • Counter-evidence and other side - David's own narrative says he was "unsure" it was fraud, and it frames each point as what "may appear to be." HHS-OIG's form says "not every submission results in an investigation." Its receipt says "you may not be contacted by an investigator but that does not mean your complaint is not being investigated." David's November 15, 2022 request to CMS was written as a request to DSS ("Would the Connecticut Department of Social Services, DSS, please provide information..."). CMS later wrote that the information is kept at the State level, not with CMS. CMS's November 8, 2023 letter says it found no responsive records "After a careful search of the Centers for Medicare & Medicaid Services (CMS) files." On December 9, 2022, DSS ABI waiver program manager Amy Dumont wrote "I am not sure the accuracy of this." about one example David gave, and asked for specific examples to research (already public).
  • Connected records - Early Warning Record: November 29, 2022 entry; HHS-OIG receipt of November 29, 2022 (privacy-cleaned copy); CMS records request 111520227061 (November 15, 2022) and CMS answers; CMS emails of November 20, 2023 on case 111520227061; David's January 14, 2024 CMS appeal listing 111520227061; CMS letter of January 25, 2024 on request 010920247054; December 1-9, 2022: emails to DSS and the DSS replies; August 2018: provider-list concerns; May 2015: first written warning to DSS and the DSS reply; July 2023: FTC report receipt and other federal records; FTC 161825278: the complaint text, the later FOIA search answer, and the missing handling records; Records still missing; Early Warning Record: December 1, 2022; National questions this record raises; Proposed safeguards

Independent public-records archive. Verify independently. A filing is not a finding.

February 5, 2024: Senator Blumenthal's office writes, "I reviewed the materials and spoke to DSS"

On February 5, 2024, Kasandra Navarro of U.S. Senator Richard Blumenthal's office emailed David: "I reviewed the materials and spoke to DSS." DSS is the Connecticut Department of Social Services, which runs the Medicaid ABI waiver program. She added: "They are working to get you the information you requested."

She wrote that the office would "let them take it from here as they are best equipped to help with your request." The email was sent at 9:55 AM Eastern and signed "Best, Kasandra." It answers David's email of February 4, 2024. On January 19, 2024, she had introduced herself as "Senator Blumenthal’s Health Legislative Assistant" and asked David to reattach the documents he sent in November 2023.

The reply does not say which DSS person she spoke to, when, or what was said. It does not say which of David's requests "the information you requested" means. It does not show that DSS later sent that information. No later written reply from the senator's office was found in David's mailbox.

No DSS record of this contact was found in the DSS records checked. That does not prove DSS has none. DSS's full search details and release lists are not available.

  • Exact words - “I reviewed the materials and spoke to DSS.” — Kasandra Navarro, Health Legislative Assistant, Office of U.S. Senator Richard Blumenthal (title from her January 19, 2024 email; this email is signed "Best, Kasandra"), February 5, 2024. Open the record
  • Exact words - “They are working to get you the information you requested.” — Kasandra Navarro, Health Legislative Assistant, Office of U.S. Senator Richard Blumenthal, February 5, 2024. Open the record
  • Exact words - “I know you are in touch with their staff so we will let them take it from here as they are best equipped to help with your request.” — Kasandra Navarro, Health Legislative Assistant, Office of U.S. Senator Richard Blumenthal, February 5, 2024. Open the record
  • Exact words - “My name is Kasandra Navarro and I am Senator Blumenthal’s Health Legislative Assistant.” — Kasandra Navarro, Office of U.S. Senator Richard Blumenthal (signature: "Legislative Assistant, U.S. Senator Richard Blumenthal"), January 19, 2024. Open the record
  • Exact words - “Would you mind reattaching the documents you shared?” — Kasandra Navarro, Office of U.S. Senator Richard Blumenthal, January 19, 2024. Open the record
  • Exact words - “I cannot guarantee that our office will be able to assist in this matter but I am happy to take a closer look.” — Kasandra Navarro, Office of U.S. Senator Richard Blumenthal, January 19, 2024. Open the record
  • What it does not show - Which DSS person or office she spoke to, on what date, how, or what was said. What "the materials" were. Her reply answers David's February 4, 2024 email, which had attachments; it does not list what she read. Which request "the information you requested" means. DSS's own chart of February 20, 2024 lists 59 of David's records requests; 37 are marked "Pending." That DSS later sent the information. That Senator Blumenthal personally read anything. The emails are from his staff. A DSS record of the contact. None was found in the DSS records checked. These were DSS's November 21, 2023 release (it came before this exchange), its February 20, 2024 request chart and its November 10, 2026 provider-directory reply. A text search of the saved FOIA collections for her name and the senator's email domain also found none (PDFs and images were not searched). This is not proof that DSS has no record. Any review, investigation or finding about DSS. A staff contact is not a finding.
  • Counter-evidence and other side - The senator's office did act on David's emails. On January 19, 2024 it asked for his documents. On February 5, 2024 its staff member wrote that she reviewed the materials and spoke to DSS. Later opinion articles on this site say the office "failed to act" or "failed to escalate." This reply shows staff review and a contact with DSS. It does not show what followed. On January 19, 2024, the office said it could not "guarantee" it would be able to assist. The office gave its own reason for leaving the request with DSS: DSS was "best equipped to help with your request."
  • Connected records - January 19, 2024: the same office asks David to reattach his documents (privacy-cleaned copy); Early Warning Record, January 19, 2024; Who knew what before each decision; Records requested, produced and still missing; Proof and gaps; Rights and the Record; February 5, 2024: the reply itself (privacy-cleaned copy)

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, February 5, 2024: Agency reply). A link is navigation only.

U.S. Labor Department wage cases 1891753 and 2001329 for The Supported Living Group (DOL data checked Nov 16, 2026)

The U.S. Department of Labor's public enforcement data lists two concluded Wage and Hour Division (WHD) cases for The Supported Living Group, LLC (SLG). DOL lists SLG, a Connecticut company, under the industry “Home Health Care Services”. Case 1891753 (Plainville, CT) records $17,181.51 in overtime back wages agreed to pay, for findings from November 16, 2017 to November 15, 2019. Case 2001329 (Danielson, CT) records $22,480.96 in overtime back wages agreed to pay, for findings from March 11, 2023 to March 10, 2025. Both rows show $0.00 in civil money penalties. Source: DOL's official WHD enforcement file dated November 9, 2026. Both rows were checked byte for byte against DOL's live file on November 16, 2026.

These are DOL's own records, not David's allegations. In both rows, all of the back wages are overtime. Minimum-wage back wages are $0.00, and Section 14(c) violations are 0. David's November 1, 2024 report to WHD described a different issue. He reported that SLG paid Medicaid members in its employment services a stipend below minimum wage, without a Section 14(c) certificate. DOL's public data does not show that either case looked at that issue.

How the records connect. On November 7, 2024, a WHD regional enforcement coordinator wrote that David's information about SLG had been forwarded to WHD's Hartford District Office. On November 8, 2024, the Hartford District Director wrote that the information “will be considered for investigation based on the priorities and resources of the WHD.” Case 2001329's findings period (March 11, 2023 to March 10, 2025) includes those dates. DOL lists that case at the same Danielson street address that David's report gave as SLG's main office. DOL's record does not say what started the case.

In a separate records (FOIA) request filed November 5, 2024, David asked WHD for wage records on NPI 1962278119. The federal NPI registry lists that number for The Supported Living Group, LLC. On November 25, 2024, WHD wrote that, as agency policy, it does not tell FOIA requesters whether an investigation started because of a complaint. It asked him for specific WHD case numbers from its public enforcement database. David had already written on November 4, 2024 that he did not have case numbers. On January 8, 2025, WHD closed the request, writing that it had not received the additional information it asked for. Cases 1891753 and 2001329 are WHD case numbers of the kind that letter asked for.

  • Exact words - “The dataset contains all concluded WHD compliance actions since FY 2005.” — U.S. Department of Labor, Wage and Hour Division - official description of the WHD Enforcement dataset (dataset 10362), June 4, 2026.
  • Exact words - “Findings Start Date and Findings End Date are not equal to Case Open Date and Case Close Date, which are not included in the dataset.” — U.S. Department of Labor, Wage and Hour Division - official description of the WHD Enforcement dataset, June 4, 2026.
  • Exact words - “BW Agreed to under FLSA (Fair Labor Standards Act) Overtime” — U.S. Department of Labor, Wage and Hour Division - official definition of column flsa_ot_bw_atp_amt, June 4, 2026.
  • Exact words - “As promised, I am confirming that all information you provided to me regarding the above identified firm has been forwarded to the Hartford District Office.” — Nancy M. DiPietro, Regional Enforcement Coordinator (FLSA, FMLA, CL, Section 14c & Other Acts), Wage and Hour Division, U.S. Department of Labor, November 7, 2024. Open the record
  • Exact words - “I have received and reviewed the information you provided, and it will be considered for investigation based on the priorities and resources of the WHD.” — Don Epifano, District Director, Hartford District Office, Wage and Hour Division, U.S. Department of Labor, November 8, 2024. Open the record
  • Exact words - “The primary concern is that Medicaid consumers engaged by SLG are being misclassified as “participants” or “stipend recipients” rather than employees” — David Medeiros, ABI Resources - his allegation in his complaint to WHD, November 1, 2024. Open the record
  • Exact words - “I appreciate your suggestion to identify specific case IDs; however, I currently do not have these numbers.” — David Medeiros, ABI Resources - his reply to WHD's Branch of Document Management (sent through MuckRock), November 4, 2024. Open the record
  • Exact words - “please identify the specific case identification number(s) sought and narrow the records to the Compliance Action Report (CAR) and the case narrative.” — Branch of Document Management, Wage and Hour Division, U.S. Department of Labor (through MuckRock), November 4, 2024. Open the record
  • Exact words - “as a matter of agency policy, the Wage and Hour Division (WHD) does not disclose complaints or specify whether particular investigations were initiated as a result of a complaint to third party FOIA requesters.” — Barbara Coldwell, Government Information Specialist, Wage and Hour Division, U.S. Department of Labor (first interim letter, FOIA 2025-F-01586), November 25, 2024.
  • Exact words - “Wage and Hour Division investigation case file numbers can be found in the enforcement database link provided above.” — Barbara Coldwell, Government Information Specialist, Wage and Hour Division, U.S. Department of Labor (first interim letter, FOIA 2025-F-01586), November 25, 2024.
  • Exact words - “The agency has not received additional information requested from you in our letter dated November 25, 2024.” — Michael A. Leiterman, Chief, Branch of Document Management, Wage and Hour Division, U.S. Department of Labor (final letter, FOIA 2025-F-01586), January 8, 2025.
  • Record numbers - WHD case 1891753; WHD case 2001329; DOL FOIA 2025-F-01586; NPI 1962278119
  • What it does not show - What started either case. DOL's public data has no complainant, referral or intake field. WHD also told David that, as agency policy, it does not tell FOIA requesters whether an investigation began because of a complaint. That David's November 2024 report led to case 2001329, or that WHD examined the stipends paid to Medicaid members. The two records share a company name, a Danielson address and overlapping dates. That is not proof of a link. Who the workers were or what jobs they did. The public rows name no workers. When either case was opened or closed, or which WHD office handled it. DOL says findings dates are not case open or close dates. Whether SLG paid the back wages, or whether anything is still owed. “Agreed to pay” is DOL's term. It is not a payment record. Any money owed to David or ABI Resources. Neither row names ABI Resources or David. Any Medicaid billing, fraud or Section 14(c) finding. Any link between the older case (findings 2017 to 2019) and David's reports. Whether WHD opened an investigation based on David's referral. No later WHD message about the referral was found in David's mailbox (live search Nov 16, 2026; the newest DOL message found is dated March 31, 2025 and is about a different complaint).
  • Counter-evidence and other side - Both DOL rows record only overtime back wages. Minimum-wage back wages are $0.00 and Section 14(c) violations are 0. David's report was about pay below minimum wage and a missing 14(c) certificate. The record does not rule out that case 2001329 was about ordinary staff overtime, unrelated to David's report. WHD's November 8, 2024 letter said only that the information “will be considered for investigation based on the priorities and resources of the WHD.” It did not say an investigation would open. WHD closed David's FOIA request 2025-F-01586 on January 8, 2025, writing: “The agency has not received additional information requested from you in our letter dated November 25, 2024.” Case 1891753's findings period ended November 15, 2019, almost five years before David's November 2024 report.
  • Connected records - WHD letters and David's SLG complaint, Oct 22 - Nov 8, 2024 (privacy-cleaned); Early Warning Record: October 22 - November 8, 2024; What each agency decided (Nov 8, 2024 Wage and Hour line); Nov 4, 2024: WHD asked for case numbers; Nov 4, 2024: David wrote he did not have case numbers; David's Nov 5, 2024 FOIA request to DOL (NPI 1962278119); Nov 15, 2026: David asked DOL's Inspector General to review WHD's handling (a request, not a finding); March 31, 2025: DOL Civil Rights Center declined further action on a separate complaint (CRC No. 25-CT-003); Records still needed

Independent public-records archive. Verify independently. A filing is not a finding.

March 31, 2025: DOL Civil Rights Center declined further action on David’s complaint about WHD records access and communications

On November 25, 2024, David complained to the U.S. Department of Labor’s Civil Rights Center (CRC) about the Wage and Hour Division’s handling of his records request, requested accessible communications and alleged whistleblower-protection violations. These are David’s allegations, not established violations. CRC’s March 31, 2025 email expressly refers to his complaint below and reproduces that November 25 complaint, establishing which correspondence it answered.

The retained CRC letter, reference 25-CT-003 and dated March 31, 2025, says the matter falls outside the laws CRC enforces and does not meet its investigation criteria; CRC therefore cannot take further action. The letter lists general criteria, but does not specify which one the complaint failed. This is a CRC scope/criteria decision, not a decision on whether the underlying wage allegation is true.

Keep the three tracks separate. DOL CRC is the Labor Department’s Civil Rights Center. DOJ’s Civil Rights Division is a different office. WHD’s November 7–8, 2024 forwarding and receipt/review of David’s SLG wage report are a separate record. The CRC attachment’s list of WHD resources does not show that CRC transferred this complaint, that WHD accepted a referral or that either WHD enforcement case arose from David’s report. WHD intake-to-case association, selection and disposition records remain the deciding missing records.

Source qualification: the PDF attachment retrieved from the retained March 31 email matches the reviewed CRC No. 25-CT-003 letter byte for byte. This binds the reviewed letter to the retained reply; it does not authenticate the original email transmission or establish the underlying allegations.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, March 31, 2025: Decision). A link is navigation only.

Nov 11, 2024: the FCC logged each emailed copy of David's email-access complaint as a request, with automatic replies

The FCC's consumer complaints mailbox sent eight automatic replies to David's November 11, 2024 complaint, one for each copy that David copied to it. Each reply carries a hidden "View ticket" link to a numbered request in the FCC's Consumer Complaint Center (consumercomplaints.fcc.gov), so each copy was logged as a request; the request numbers are withheld here. Each reply also ends with a different bracketed reference code. The visible text says the address is not monitored, and that a ticket number is emailed once a complaint is submitted on the FCC's online form. No such form-ticket email and no later FCC answer were found in David's mailbox.

What David reported. On Sunday, November 10, 2024, David emailed the same records request to eight Connecticut “.FOIA@ct.gov” addresses. Seven bounced within seconds: the Governor, State Library, Office of Governmental Accountability, Attorney General, OPM, DSS and CHRO addresses. The eighth, DAS.FOIA@ct.gov, was delivered. Each bounce notice says the address “isn't listed in the domain's directory” and that “it might not exist.” On November 11, 2024, David sent a “Formal Complaint” about these bounces to Connecticut and federal offices, with a copy to the FCC.

Delivery to the FCC, address by address. consumercomplaints@fcc.gov: Microsoft reported each of the eight copies as handed off (“Relayed”). The FCC system then answered each copy, and the email headers tie each reply to one copy. dro@fcc.gov (the FCC Disability Rights Office): at 10:19 AM Eastern, David forwarded one copy, and Microsoft reported it relayed. On November 12, 2024, that mailbox sent a notice that the message “was deleted without being read.” The notice does not show who deleted it or why.

Other addresses on the November 11 complaint. Connecticut's mail server reported delivery to the Governor's, the Attorney General's and the DAS Commissioner's addresses, and to State Chief Information Officer Mark Raymond. Copies to foic@ct.gov and DAS.SMO@ct.gov bounced with the same “isn't listed” notice. GAO FraudNet, the HHS Office for Civil Rights and CISA got “Relayed” notices only. HHS sent automatic replies, and CISA sent one “deleted without being read” notice. No notice of any kind was found for crt@usdoj.gov.

  • Exact words - “Hello. You have reached an e-mail address which is not monitored by the FCC’s Consumer Help Center.” — FCC Consumer Help Center, Consumer and Governmental Affairs Bureau (automatic reply from consumercomplaints@fcc.gov), November 11, 2024.
  • Exact words - “Once you submit the form, you will receive an email with the ticket number associated with your complaint and information about what to expect from the process.” — FCC Consumer Help Center, Consumer and Governmental Affairs Bureau (same automatic reply), November 11, 2024.
  • Exact words - “was deleted without being read on Tuesday, November 12, 2024 4:14:41 PM (UTC-05:00) Eastern Time (US & Canada).” — FCC Disability Rights Office mailbox (dro@fcc.gov), automatic Outlook notice, November 12, 2024. Open the record
  • Exact words - “Each attempt has met with immediate rejection messages due to domain mail protection protocols” — David Medeiros, Founder, ABI Resources - his complaint (his description), November 11, 2024.
  • Exact words - “Your message was rejected by the recipient's domain because the recipient's email address isn't listed in the domain's directory. It might be misspelled or it might not exist.” — Microsoft Outlook.com mail system (postmaster@outlook.com), bounce notice for CSL.FOIA@ct.gov, November 10, 2024. Open the record
  • Exact words - “Directory based edge blocking is enabled for the recipient's organization and the recipient wasn't found in their directory.” — Microsoft Outlook.com mail system, same bounce notice (note for email administrators), November 10, 2024. Open the record
  • Exact words - “Delivery to these recipients or groups is complete, but no delivery notification was sent by the destination server” — Microsoft Outlook.com mail system (postmaster@outlook.com), "Relayed" notice for consumercomplaints@fcc.gov, November 11, 2024.
  • Exact words - “Compliance with the FOIA is important, and can confirm that we are adhering to its requirements.” — Sandra Arenas, Associate Attorney General / Chief of the Division of Consumer and Constituent Affairs, Connecticut Office of the Attorney General, November 15, 2024. Open the record
  • What it does not show - What the FCC did with the eight requests. No later FCC answer was found, and no ticket email for a complaint filed on the FCC's online form was found. That the eight bracketed codes are FCC complaint numbers. They are reference codes printed at the end of the automatic replies; the request numbers sit separately in the hidden "View ticket" links. That any person at the FCC read the complaint or its seven PDF attachments. Who or what deleted the Disability Rights Office copy, or why. Any FCC decision or finding. That Connecticut blocked David's email address. The bounce notices say the addresses were not found in the state's mail directory. Whether the seven bounced FOIA addresses ever worked. David's mailbox has no earlier delivered email to any of them. Delivery to crt@usdoj.gov. No delivery, relay or bounce notice was found for it on any of the eight copies. Inbox delivery at GAO FraudNet, HHS and CISA. A “Relayed” notice only shows Microsoft handed the message off.
  • Counter-evidence and other side - The bounce notices give the reason: the address “isn't listed in the domain's directory. It might be misspelled or it might not exist.” They do not say David's address was blocked. Connecticut accepted David's email at working addresses at the same time. DAS.FOIA@ct.gov was delivered on November 10, 2024. On November 11, 2024, David's FOIA email to foi@ct.gov (the FOI Commission) was delivered, and so were his complaint copies to four other ct.gov addresses. David's mailbox shows years of working email with DSS's FOIA office at foia.dss@ct.gov: 203 emails sent to it (December 6, 2021 to November 9, 2026) with no bounce notice, and 135 emails received from it. The DSS address that bounced on November 10, 2024 was written DSS.FOIA@ct.gov. David's mailbox also shows 193 emails sent to the FOI Commission at foi@ct.gov (October 28, 2023 to November 7, 2026) with no bounce notice. The November 11 complaint copy addressed to foic@ct.gov bounced. OPM.FOIA@ct.gov had already bounced once before, on September 3, 2024, with the same “isn't listed” reason. The Connecticut Attorney General's office answered the complaint on November 15, 2024: “Compliance with the FOIA is important, and can confirm that we are adhering to its requirements.”
  • Connected records - What each agency decided: the Nov 11-12, 2024 FCC line; Accommodation requests and answers; Nov 15, 2026: David asked the FCC Inspector General to review the Disability Rights Office's handling (a request, not a finding); Separate track: FCC records request FOIA-2025-000150 and appeal FOIA-2025-000358-A; Nov 10, 2024 request to DAS.FOIA@ct.gov (delivered); Nov 10, 2024 request to DSS.FOIA@ct.gov (bounced); David's article quoting all seven bounce notices; Right to petition; Communication access (ADA)

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, November 11, 2024: Receipt). A link is navigation only.

April 30, 2025: State Auditors' DSS audit, and the 2021 law on contractor records

On April 30, 2025, Connecticut's Auditors of Public Accounts released their audit of the Department of Social Services (DSS) for the fiscal years ended June 30, 2022 and 2023. The State Auditors are John C. Geragosian and Craig A. Miner. The report lists 25 recommendations, 19 of them repeated from the previous audit. Their release email led with $9,623,410 in Medicaid revenue losses DSS did not report. These were federal payments a CMS review disallowed because DSS's own Medicaid claims to the federal government missed the filing deadline.

Two findings concern contractors and public records. Finding 6 says DSS did not make sure it and its contractors regularly reconciled cash advances paid to access agencies, which provide care management for Medicaid waiver recipients, and to a fiscal intermediary. These advances are money owed back to DSS. For fiscal year 2023 they were $10,831,123 to the fiscal intermediary and $1,234,365 to access agencies. Finding 24 says DSS fulfilled one public-records request 702 calendar days after receiving it, and kept no log of such requests until June 2023. DSS agreed with both findings and described fixes.

A 2021 law, Public Act 21-145, approved July 7, 2021, created routes to contractor-held information starting October 1, 2021. Section 2, now C.G.S. 4e-72, says State contracts entered into, renewed or amended on or after that date must let the agency get contract data from the contractor on demand, at no extra cost. Section 3 added to C.G.S. 2-90(c) that the Auditors may examine relevant information held by an agency's private contractors, provided on demand at no cost. Section 12 extended the ethics rules in C.G.S. 1-86e to employees of State consultants and independent contractors.

What these records do not show: the audit does not name ABI Resources, David, the ABI waiver or any provider, and it does not measure payments owed to providers. No record was found showing that DSS or the Auditors used the 2021 data rights for any ABI-related contract. Those rights belong to the agency and the Auditors. The public's route is a records request under the Freedom of Information Act; C.G.S. 1-206 sets the denial and appeal steps.

  • Exact words - “Our examination of the records of the Department of Social Services disclosed the following 25 recommendations, of which 19 were repeated from the previous audit.” — State Auditors, Auditors of Public Accounts (audit of DSS, FY2022-2023), April 30, 2025. Official source
  • Exact words - “Noteworthy findings include that DSS did not report $9,623,410 in Medicaid revenue losses for noncompliance with Medicaid timely filing requirements.” — State Auditors John C. Geragosian and Craig A. Miner (release email from Reports@ctauditors.gov), April 30, 2025.
  • Exact words - “A Centers for Medicare and Medicaid Services review disallowed $9,080,577 in federal reimbursements for the quarter ended September 30, 2021, and $542,833 for the quarter ended December 31, 2021.” — State Auditors (Finding 2, Condition), April 30, 2025. Official source
  • Exact words - “DSS did not ensure that it and its contractors performed regular reconciliations of operating and processing advances and uncollectible rejected claims during the audited period.” — State Auditors (Finding 6, Condition), April 30, 2025. Official source
  • Exact words - “DSS provided $10,831,123 in cash advances to the fiscal intermediary and $1,234,365 to access agencies for fiscal year 2023.” — State Auditors (Finding 6, Context), April 30, 2025. Official source
  • Exact words - “The Department, its fiscal intermediary, and third-party contractor have completed several reconciliations since the initial reporting of this finding.” — Department of Social Services (agency response to Finding 6, printed in the audit), April 30, 2025. Official source
  • Exact words - “DSS provided public records in response to a freedom of information (FOI) request 702 calendar days after receiving the request.” — State Auditors (Finding 24, Condition), April 30, 2025. Official source
  • Exact words - “Our review of FOI requests for fiscal years 2022 and 2023 disclosed that DSS had no log to track these requests until June 2023.” — State Auditors (Finding 24, Condition), April 30, 2025. Official source
  • Exact words - “shall contain a provision authorizing the state contracting agency to access any data concerning such contract that is in the possession or control of the contractor upon demand” — Connecticut General Statutes section 4e-72 (P.A. 21-145, S. 2), October 1, 2021. Official source
  • Exact words - “such information shall be provided upon demand in a format prescribed by the auditors at no cost to the auditors or the department, commission, board or court” — Connecticut General Statutes section 2-90(c) (P.A. 21-145, S. 3), October 1, 2021. Official source
  • Exact words - “AN ACT IMPLEMENTING THE RECOMMENDATIONS OF THE AUDITORS OF PUBLIC ACCOUNTS.” — Public Act 21-145 (Substitute Senate Bill No. 1071), title; approved July 7, 2021, July 7, 2021. Official source
  • Exact words - “No person hired by the state as a consultant or independent contractor, and no person employed by such consultant or independent contractor, shall” — Connecticut General Statutes section 1-86e(a) (amended by P.A. 21-145, S. 12), October 1, 2021. Official source
  • Exact words - “may appeal therefrom to the Freedom of Information Commission, by filing a notice of appeal with said commission.” — Connecticut General Statutes section 1-206(b)(1) (current text), November 16, 2026. Official source
  • Record numbers - Auditors' report 1179 (ctauditors.gov/r/1179.pdf); Findings 2, 6 and 24; Public Act 21-145 (Substitute Senate Bill No. 1071); C.G.S. 4e-72; C.G.S. 2-90(c) and (h); C.G.S. 1-86e; C.G.S. 1-206
  • What it does not show - The audit does not mention ABI Resources, David Medeiros, the ABI waiver, brain injury or any provider by name. A search of the full report text found none of these words. Finding 6 does not name the access agencies or the fiscal intermediary. It is about advances to them in fiscal years 2022 and 2023 that are owed back to DSS. It says nothing about advances to providers such as ABI Resources, and it does not measure claims or invoices owed to providers. Finding 2's late-filing losses are DSS's own claims to the federal government. They are not claims by providers such as ABI Resources, and they do not concern denials of provider claims. Finding 24 does not name the requester. Its dates do not match David's December 6, 2021 records request to DSS: on July 26, 2022, DSS wrote that it was still "checking with staff to determine if there are any responsive documents available." The audit's list of the areas it covered does not mention Medicaid waiver services or provider claim payments. Public Act 21-145 does not show that DSS or the Auditors ever asked any contractor for ABI-related data, or what any contractor produced. No such demand was found in the records checked. Section 4e-72 reaches only contracts "entered into, renewed or amended on or after October 1, 2021." Which ABI-related contracts meet that test is not shown. These sections give access to the contracting agency and to the Auditors. They do not give members of the public direct access to contractor records, and C.G.S. 2-90(h) keeps confidentiality rules in place for the Auditors. Section 1-86e lists specific prohibited acts. Working for, or being paid by, a State contractor is not a violation by itself. No record found shows a violation by anyone. No finding in this audit is about David's reports. His 2023 complaints to the Auditors' office are a separate, already-public record.
  • Counter-evidence and other side - DSS agreed with Findings 6 and 24 and described fixes: several reconciliations completed since the finding was first reported, a tracking process, a full-time staff person for the FOI inbox, and the GovQA platform. On Finding 2, DSS agreed only in part on data breaches. It said not every improper disclosure on its log was a breach. The audit reports that six of the prior audit's 27 recommendations were implemented or otherwise resolved. Earlier State audit findings about ABI waiver applications, and their 2023 RESOLVED status, are already public on the Official findings section.
  • Connected records - Official findings already public: earlier State audits and federal reviews; Records requested and still missing; David's December 6, 2021 records request to DSS; DSS replies on the December 6, 2021 request; November 2023: David's emails with the State Auditors' office; Statute summaries; Proposed safeguards

Independent public-records archive. Verify independently. A filing is not a finding.

Nov 10, 2026: Gainwell's answer on May 8-14, 2022 claims matches the July 28, 2026 remittance

On November 10, 2026, Gainwell Technologies, Connecticut Medicaid's fiscal agent, answered ABI's November 6 records request about services dated May 8-14, 2022. Gainwell wrote that its search found 20 claims, received July 23, 2026, with a paid date of July 28, 2026 for $0. The July 28, 2026 remittance matches: 20 claims made up of 200 service lines, all denied, $52,223.01 billed, $0.00 allowed, $0.00 paid.

Every one of the 200 lines carries two payer codes: 0512 ("CLAIM EXCEEDS TIMELY FILING LIMIT.") and 4021 (a benefit-plan reason). Ten lines also carry 4990 ("BENEFIT PLAN RESTRICTION FOR PROCEDURE CODE"). All 20 claim numbers carry the date code Gainwell named, 26204, which is July 23, 2026. The remittance is dated July 28, 2026; its data file shows a "Paid Date" of July 25, 2026 on every line.

Sandata, the visit-verification (EVV) contractor, wrote on November 8 and 10, 2026 that the invoices for that week were created in May 2022 but first exported on July 23, 2026, and that it found no record of rejected claims or system errors. The export history saved from ABI's Sandata billing account on November 5, 2026 shows the same: these 200 lines appear in one export only, on July 23, 2026. Neither record says why the invoices were not exported sooner. Sandata wrote that any reason it could give "would be conjecture."

These 200 lines are already counted inside the site's 353-line, $97,882.76 review of denied or unclear lines. Do not add them again. The billed amount is not a proven loss or an amount owed. The same remittance paid 79 other claims. A deposit equal to its $212,110.22 net payment, from the State DSS, posted to ABI's bank on July 29, 2026.

  • Exact words - “shows 20 claims with an ICN Julian date of 26204 -7/23/26 (Date received by Gainwell) with a paid date of 7/28/26 for ($0).” — Debbie Hockla-Kaba, Senior Professional Customer Support, CT Medical Assistance Program, Gainwell Technologies, November 10, 2026.
  • Exact words - “There were no other claims processed by Gainwell Technologies for this date range of service.” — Debbie Hockla-Kaba, Senior Professional Customer Support, CT Medical Assistance Program, Gainwell Technologies, November 10, 2026.
  • Exact words - “CLAIM EXCEEDS TIMELY FILING LIMIT.” — Connecticut interChange MMIS remittance advice, EOB code 0512 (EOB code descriptions page), July 28, 2026.
  • Exact words - “The procedure billed is not a covered service under the client’s benefit plan.” — Connecticut interChange MMIS remittance advice, EOB code 4021 (EOB code descriptions page), July 28, 2026.
  • Exact words - “The first time the invoices were exported was on 07/23/26.” — Sandata Support - General (Sandata, EVV contractor; no individual named), November 8, 2026.
  • Exact words - “there is no history or record of claims rejecting or system errors from that time inasmuch as what we can parse from 4 years ago.” — Sandata Support - General (Sandata, EVV contractor), November 8, 2026.
  • Exact words - “I queried the account and saw that the invoices that were exported on 7/23/2026 but created back in May of 2022 were never exported prior to 7/23/2026.” — Sandata Support - General (Sandata, EVV contractor), November 10, 2026.
  • Exact words - “It does appear as if invoices were created and then were not subsequently exported for whatever reason.” — Sandata Support - General (Sandata, EVV contractor), November 10, 2026.
  • Record numbers - Sandata / HHAeXchange support case 00578340 (opened Nov 6, 2026)
  • What it does not show - Why the May 2022 invoices were not exported until July 23, 2026. Sandata wrote that any reason it could give "would be conjecture." Whether any claim for these dates was sent and rejected before July 23, 2026 by another route. David asked Gainwell about front-end rejects; Gainwell's reply speaks only of claims "processed." Whether a late-filing exception could apply, or whether the 4021 benefit-plan reason was correct. The final outcome. No later payment, adjustment or replacement of these lines appears in the six remittances held from August 11 to October 27, 2026. Later records are not held. A loss or an amount owed. $52,223.01 is the billed amount on denied lines. That any person or office did something wrong. A denial code is the payer's stated reason, not a finding about anyone. The 2026 provider approvals on this site do not decide eligibility for services in 2022.
  • Counter-evidence and other side - Sandata (Nov 8 and 10, 2026): the invoices were created in May 2022, were never exported before July 23, 2026, and Sandata found no record of rejected claims or system errors. The export history saved from ABI's Sandata billing account on Nov 5, 2026 (1,230 export files, Jan 4, 2017 to Nov 3, 2026) shows the 200 lines in one export only: July 23, 2026, sent by ABI's billing account to the DSS claims system. The same July 28, 2026 remittance paid 79 claims. A deposit equal to its $212,110.22 net payment, described as 'ST OF CONN D.S.S', posted to ABI's bank on July 29, 2026. The match is by amount, date and payer name; the remittance prints no trace number. The 200 selected lines show $0.00 paid.
  • Connected records - March 2026 approvals and the separate 28-service 2026 group; What the money records show (353-line review); Proof and gaps; Spring 2024 lines denied on the same July 28, 2026 remittance

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, November 10, 2026: Agency reply). A link is navigation only.

Correction: DSS's $100,000 advance of July 2025 was taken back in full by Sep 23, 2025

DSS took back all of the $100,000 advance it gave ABI in July 2025. Five Medicaid remittances, dated July 29, August 12, August 26, September 9 and September 23, 2025, each took back $20,000.00. The September 23, 2025 remittance shows the advance balance as $0.00. The Warnings and Answers page listed the records of full recovery as still missing; they have now been found and checked.

On July 16, 2025, Christine Weston, Director of Community Options at DSS, wrote that DSS had authorized a one-time $100,000 advance and would set up a recoupment "at $20,000 per cycle." ABI's bank statement shows a $100,000.00 deposit from "ST OF CONN D.S.S" on Friday, July 18, 2025.

The money came back out of ABI's regular Medicaid payments, not as bank withdrawals. Each remittance lists the advance with an original amount of $100,000.00 and $20,000.00 "RECOUPED THIS CYCLE", and pays that much less. The balance went $80,000.00, $60,000.00, $40,000.00, $20,000.00, then $0.00. The bank received each reduced payment one day later: $108,715.54 (Jul 30), $106,672.21 (Aug 13), $101,314.05 (Aug 27), $99,866.33 (Sep 10) and $100,581.33 (Sep 24). A December 23, 2025 remittance still shows $100,000.00 as the 2025 total for this kind of recovery.

This corrects the money record; it is not a new claim. The advance and its recovery are separate from the denied claims and do not change those totals. The records do not show any signed agreement for the advance, and they do not show that any other disputed claim was paid.

  • Exact words - “DSS has authorized a one-time advance of $100,000 today and the funds will deposit on Friday morning.” — Christine Weston, Director of Community Options, Connecticut Department of Social Services, July 16, 2025.
  • Exact words - “We will set up a recoupment to begin the second cycle in July at $20,000 per cycle.” — Christine Weston, Director of Community Options, Connecticut Department of Social Services, July 16, 2025.
  • Exact words - “We continue to explore your request for a stabilizing advance to cover payroll obligations.” — Christine Weston, Director of Community Options, Connecticut Department of Social Services, July 10, 2025.
  • Exact words - “I confirm receipt of your email and understand the terms regarding the July recoupment cycle.” — David Medeiros, ABI Resources, July 17, 2025.
  • Exact words - “I appreciate the Department's responsiveness during this critical time.” — David Medeiros, ABI Resources, July 17, 2025.
  • Exact words - “RECOUPED THIS CYCLE” — Connecticut interChange MMIS remittance advice, Financial Transactions page, Accounts Receivable column heading, September 23, 2025.
  • What it does not show - Any signed agreement or other written terms for the advance. DSS's July 16, 2025 email is the only statement of terms found. Two secure DSS messages of July 15-16, 2025 could not be read in the saved mail copy. What reason code 8409, printed beside the advance on each remittance, means. These pages do not define it. That any disputed or denied claim was paid. The advance and its recovery are separate from the denied claims on this site. Any loss or gain from the advance itself: $100,000.00 was paid in and $100,000.00 was taken back. Why ABI needed the advance. ABI's July 8, 2025 request is described here only as a request for emergency help.
  • Counter-evidence and other side - DSS acted on ABI's request quickly: ABI wrote on July 8, 2025; DSS answered the same day, asked questions on July 9 and for documents on July 10, authorized the advance on July 16, and the money arrived July 18. David wrote to DSS on July 17, 2025: "I appreciate the Department's responsiveness during this critical time." The recovery followed the plan DSS stated in writing on July 16, 2025 ($20,000 per cycle, starting in July). No recovery beyond $100,000.00 appears: the December 23, 2025 remittance shows $100,000.00 as the year's total.
  • Connected records - What the money records show; Corrections to older pages

Independent public-records archive. Verify independently. A filing is not a finding.

July 4, 2025 parade report to Willimantic Police: what David reported and what WPD wrote back

On July 5, 2025, David emailed an incident report about the July 4 "Boom Box Parade" to the Willimantic Police Department (WPD) and to the Windham mayor's address, and forwarded it to Chief Fabian Silva. David reported that a police officer told him he would be arrested if he did not move, and he asked WPD to keep all video. On July 8, Chief Silva wrote that WPD was "currently reviewing" the report.

A WPD letter dated July 11, 2025, signed by Lieutenant Matthew Solak, says David's emails and voicemails were investigated as a civilian complaint. It says he reviewed the body-worn camera video, found no evidence of misconduct by any WPD officer, and that the complaints were "determined to be unfounded." On August 4, 2025, WPD wrote that the department adopted these conclusions and that no documents showed a referral to any outside oversight body.

Under David's records request FOI 25-31, WPD listed four videos, a three-page incident report, a two-page CAD report, emails, and radio and phone recordings. WPD sent the four videos through Motorola's CLOUD-SHARE service on August 4 and September 3, 2025, and again on October 8, 2026, when it also sent an audit trail for each video. WPD said it would send the documents after payment, and it did not grant David's fee-waiver request. WPD's $134 request is a different request: its August 21, 2025 letter under FOI 25-33 priced 268 pages of personnel records about one officer. It is not the price of the July 4 documents or of bank case 25-00005222.

On July 24, 2025, David sent the July 4 complaint to the U.S. Justice Department's Civil Rights Division, the HHS Office for Civil Rights, and the U.S. Office of Special Counsel. Each email cited WPD's July 11 letter. The WPD case that WPD sent to the Secret Service is a different matter: case 25-00005222, David's June 26, 2025 report about disputed Google Ads charges.

  • Exact words - “You will be arrested if you don’t move now.” — David Medeiros, his July 5, 2025 incident report to WPD (his account of what an officer told him), July 5, 2025.
  • Exact words - “Preserve all video/audio/bodycam footage, officer logs, internal communication, and parade correspondence related to this event.” — David Medeiros, his July 5, 2025 incident report to WPD, July 5, 2025.
  • Exact words - “Your email/fax has been received, and we are currently reviewing the details of the incident you reported.” — Fabian Silva, Chief of Police, Willimantic Police Department, email, July 8, 2025.
  • Exact words - “your communications with Chief Silva have been investigated as a civilian complaint” — Lieutenant Matthew Solak, Willimantic Police Department, letter, July 11, 2025.
  • Exact words - “I have carefully reviewed the Body Worn Camera (BWC) video associated with this incident and have found no evidence of malfeasance, misfeasance, or misconduct by any Willimantic Police Officers.” — Lieutenant Matthew Solak, Willimantic Police Department, letter, July 11, 2025.
  • Exact words - “Your complaints have been determined to be unfounded, and no further action is required on your part.” — Lieutenant Matthew Solak, Willimantic Police Department, letter, July 11, 2025.
  • Exact words - “We have four videos and one, three page police Incident report. We also have a two page CAD report.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter on FOI 25-31, August 4, 2025.
  • Exact words - “the Letter to you by Lt Solak is the review that was conducted of this matter and summarizes his conclusions which has been adopted by our Department.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter on FOI 25-31, August 4, 2025.
  • Exact words - “There are no documents indicating this matter was referred to any external oversight bodies.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter on FOI 25-31, August 4, 2025.
  • Exact words - “I resent the four videos we have from the July 4, 2025 incident.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter on FOIA 25-31, October 8, 2026.
  • Exact words - “Lieutenant Matthew Solak has retired from this department, and his letter speaks for itself.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter on FOIA 25-31, October 8, 2026.
  • Exact words - “I am following up with you regarding case number 25-00005222, dated 06/26/2025.” — Willimantic Police Department, email from a WPD officer about the separate bank case, October 28, 2026.
  • Exact words - “I have found 268 pages of records responsive to your request.” — Samuel P. Browning, FOIA Officer, Willimantic Police Department, letter re FOI 25-33, August 21, 2025.
  • Record numbers - FOI 25-31 - WPD records request for the July 4, 2025 records (made July 8, 2025); FOI 25-33 and FOI 25-36 - later WPD request numbers in the same exchange; DI-25-000310, DI-25-000325, DI-25-000379 - earlier Office of Special Counsel files that David's July 24, 2025 update named; 25-00005222 - WPD case for David's June 26, 2025 report about disputed Google Ads charges; a separate matter, not the July 4 report
  • What it does not show - What happened at the parade. This card shows what each side wrote; it does not say anyone broke a law or a rule. A case, incident or CAD number for the July 4 report. WPD's letters say an incident report and a CAD report exist but give no number. Whether David paid for, or received, the incident report, CAD report, emails or audio recordings WPD offered. Whether the shared videos opened or played for David. How long anyone watched the videos, or which recordings mattered to the review. The audit trail logs views inside WPD's video system only. When or how Lt. Solak's July 11 letter reached David. On July 17, 2025, David wrote that he had "received no written acknowledgment of any internal action or external referral"; his July 24, 2025 emails cite the letter. Any referral of the July 4 matter by WPD to another agency. WPD wrote that no documents show one. Any decision by the Justice Department, HHS or the Office of Special Counsel on the July 4 complaint. Any link between the July 4 report and WPD case 25-00005222 or the Secret Service referral of that case. What the videos show. The videos are not published or described here.
  • Counter-evidence and other side - WPD's July 11, 2025 letter found "no evidence of malfeasance, misfeasance, or misconduct" and called the complaints "unfounded." WPD's August 4, 2025 letter says the department adopted those conclusions. WPD's audit trail, sent to David on October 8, 2026, logs views of the recordings by Chief Silva on July 7, 2025 and by Lt. Solak on July 10, 2025, before the July 11 letter. Each viewed the same two of the four recordings in that log. WPD sent the four videos on August 4 and September 3, 2025 and on October 8, 2026 (share notices in David's mailbox and the audit trail). An August 29, 2025 share was followed the same day by a WPD email asking David to disregard that link. The audit trail lists two "Downloaded" entries for the share's recipient address (David's email, withheld here) on August 5, 2025. That same day David wrote to WPD that the CLOUD-SHARE delivery method was "inaccessible." The log does not show whether a download finished. David's August 5 and August 22, 2025 emails to the address police@willimanticct.org bounced; the bounce says "the recipient's domain does not exist." WPD's FOIA officer was also addressed on both emails.
  • Connected records - FOI 25-31 emails between David and WPD's FOIA officer, July 8 to October 29, 2025; FOI 25-33 and 25-36 reply thread with WPD; What each agency decided; David's reports list, including the separate WPD bank case 25-00005222; Timeline entries for July 2025; State-agency record FMR-ST-016, Willimantic Police Department; WPD letter of July 11, 2025 (image; ABI office address withheld); WPD records status: what is held, what was priced, and what FOIC answered

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, July 5, 2025: Report sent). A link is navigation only.

WPD records: what is held, what was priced, and what FOIC answered

Updated November 16, 2026. This status note distinguishes retained files, agency statements, requester claims and unresolved records.

The most important distinction

A recording export labeled FOIA 25-31 is held locally. Its retained inventory lists six video streams across four recording events. That is a recording component, not proof that every requested record was delivered. Playback, complete incident coverage and full fulfillment remain unverified.

The $134 demand concerned a different record set: WPD's August 21, 2025 FOI 25-33 letter identified 268 pages of personnel-related material concerning Officer/Sgt. Nixon and required a check before electronic delivery. The one-page fee letter is not the 268-page production. It is not identified as the price of the separate bank investigation report 25-5222.

What remains unresolved: the issued July 4 incident/CAD documents and operational report number; the payment/waiver and matching documentary production for 25-33; complete 25-36 production; and the separate bank investigation file 25-5222/25-00005222 and receiving USSS packet. An FOIA request number is not an incident number.

What the fee records say

The quoted totals differ by date and scope:

  • August 21, 2025: 268 pages/$134 under FOI 25-33.
  • August 28, 2025: 364 pages/$182, including additional awards/citations/articles/press releases and Motorola-related documents.
  • August 29, 2025: 268 pages/$134 or 337 total pages/$168.50. These totals are not cumulative charges.
  • September 29, 2026: Browning again conditioned documentary delivery on payment.

Actual payment, an approved waiver and complete delivery of those sets remain unverified in the records checked. WPD's August 28 and September 4, 2025 letters say David already had a copy of Lt. Solak's letter. The July 4 record card now links a retained signed Solak complaint-disposition letter, and WPD’s August 4 letter says the department adopted his conclusions. David's July 24, 2025 emails cite that letter; the exact date and method of its delivery are not shown. Complete fulfillment of the records requests remains unverified.

Read the FOI 25-31 correspondence and FOI 25-33 reply thread.

What FOIC answered

David maintains that his September 4, 2025 email filed the appeal.

On October 27, 2025, Russell Blair, FOIC Director of Education & Communications, said he believed that email had unintentionally not been logged as a complaint because it looked like police correspondence and lacked information needed to open a case. He asked for a refreshed police request and the attached form or the same information by email, including agency correspondence.

On October 28, 2025, FOIC Secretary Mikia Gray acknowledged receipt of the appeal, stated a 25-page limit for emailed appeals/complaints, and directed mail or hand delivery if David still wished to submit it.

Verified: receipt and the agency's stated intake conditions. Unverified: an assigned FIC docket number, accepted filing date, hearing, merits ruling or closure. These exchanges do not decide legal timeliness, the validity of the 25-page condition, accommodation compliance, motive or liability. Fifty-four elapsed days between September 4 and October 28 are not themselves a finding that an agency was legally 54 days overdue. A requester-proposed placeholder is not an issued docket number.

Read the preserved FOIC correspondence and qualified historical commentary. The dated status above governs the current summary; statements in historical requester commentary remain attributed assertions.

Why these records belong together

The sequence lets readers check what was requested, what WPD offered, what is actually held, how FOIC responded, and what document would decide the remaining question. It preserves both the access concerns and the agency's explanation. It does not infer deliberate obstruction from an incomplete record.

The next deciding records are WPD's request-specific payment/production manifest and FOIC's intake/register/docket or disposition record matched to the actual submissions.

See the state-agency record, warnings and answers, and rights and the record. These events relate to records access and accommodation; no violation is declared here.

Source notes

These notes identify the original records behind the summary. They do not release held recordings or private files.

  • WPD fee letter, August 21, 2025, FOI 25-33: Samuel P. Browning’s signed, one-page letter identifies 268 personnel-related pages and requests a $134 check before electronic delivery. Original control: ABI_036891. Original SHA-256: 43c098f523e242bda728c279cdcdc441348cdd605177c85b90d6a8d72bec3081. Relevant location: page 1, first and final substantive paragraphs. The authorized page-image derivative has SHA-256 6fb98f45bd70592ecf6d9b2738b502f4bdc7c1351b8fceedbb15b823666bf705. The reply letter is not the offered production.
  • WPD scope letter, August 28, 2025: original control ABI_007070; recorded original SHA-256 prefix 266ab3322486; two pages. The inventory totals 364 pages/$182. The letter’s complaint/IA statement describes the proposed set; it does not show actual delivery. Page 1 also says David has Lt. Solak's letter.
  • WPD fee email, August 29, 2025: the office quoted 268 pages/$134 and 337 total pages/$168.50, with prepayment before PDF delivery. Read the preserved correspondence.
  • WPD letter, September 4, 2025, FOI 25-31, 25-33, 25-36: original control ABI_007533, page 1. Browning keeps the prepayment position and says WPD has "a small number of emails, and a letter from Lt. Solak of which you already have a copy." It does not show actual delivery.
  • WPD reply, September 29, 2026: the office again conditioned delivery on payment. Sent at 15:40:30 UTC; received at 15:41:17 UTC. The existing page labels the reply with its received time. Read that reply. The promise does not establish payment or actual production.
  • Retained recording inventory, FOIA 25-31: WatchGuard table of contents, control ABI_245734, SHA-256 85d2d585b88d8f9edb029968a85ef62e6bd1b163d508fd463aeab38d8063a111. Its metadata and the retained archive manifest list six MP4 streams across four recording events. This describes a locally retained export. It offers no public video download or playback/completeness certification.
  • Solak complaint-disposition letter, July 11, 2025: the current July 4 card links a retained signed letter by Lieutenant Matthew Solak; it says the complaints were determined to be unfounded. Original control ABI_081985; recorded original SHA-256 6c4eab52823989b64bd1f8164acdc01534b884d3fdd144003e3aad48b8c003e2, page 1. The public cleaned derivative reports SHA-256 9d3e3889f15ec9def2573191d22bc5363562584d7a109681d9cc0521b7228170; that is a different representation, with the ABI office address withheld. The public OCR gives July 11; the older review established July 2025 only. The letter is the agency’s conclusion, not an independent finding of what happened or proof of complete production.
  • FOIC reply, October 27, 2025: Russell Blair, Director of Education & Communications, described the September 4 email as unintentionally unlogged/incomplete and allowed either the form or the same information by email. Sent at 20:30:32 UTC; received at 20:33:01 UTC.
  • FOIC reply, October 28, 2025: Mikia Gray, Secretary, acknowledged the appeal and stated the 25-page email condition. Sent at 19:44:56 UTC; received at 19:45:04 UTC. Read both preserved agency replies. They establish the agency statements and receipt, not an issued docket or outcome.

The reviewed, minimized agency-message representations for the FOIC replies and August 29 email are preserved with SHA-256 533fc51360c2b9db311ffc3e4abe53da2eec7ab159915447eba468caceb8c57f. This digest identifies the retained representation, not original MIME bytes or an independently authenticated transport trace. Duplicate mailbox copies are not additional events.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, August 21, 2025: Background). A link is navigation only.

Spring 2024 services: April 2024 authorization interruption, July 2026 billing, July 28, 2026 denial (25 lines)

Twenty-five ABI service lines dated March 31 to April 19, 2024, billed at $6,857.34, appear in ABI's retained July 23, 2026 outbound billing file, 825 to 844 days after the services. The July 28, 2026 remittance denied all 25. Each line carries 0512 ("CLAIM EXCEEDS TIMELY FILING LIMIT.") and 4021 (a benefit-plan reason). $0.00 was paid.

In April 2024, CCCI and DSS both wrote about an IT interruption in CCCI's offices. On April 5, CCCI's XXXXXX XXXXX apologized for the delay and wrote that authorizations would be uploaded "as soon as possible." On April 8, DSS's Amy Dumont wrote that it "should be corrected this week." The same morning, David wrote that ABI could not "add or bill services" (David's account).

Gainwell's authorization history, as shown in November 2026, lists an approved authorization covering each of the 25 lines. For 24 lines ($6,661.95) the approval date shown is April 9, 10 or 23, 2024, after the service. For one line ($195.39) it is December 1, 2023. Gainwell's January 25, 2024 approval letter prints a provider agreement from January 25, 2024 to January 25, 2026, unless terminated earlier; that printed period does not by itself show unbroken enrollment or client coverage. No earlier export of these 25 lines was found among the 1,230 export files saved from ABI's Sandata billing account (January 4, 2017 to November 3, 2026).

A broader review of 198 retained remittance PDFs and 21 remittance data files (CSV), issued April 25, 2017 to October 27, 2026, found no payment, adjustment or replacement for these 25 lines. A wider check that allowed changed codes or invoices found one earlier paid weekly claim (April 23, 2024) with a service on the same date as one of these lines, under a different procedure code; no record ties that payment to any of these lines, and nothing is subtracted. These are ABI's retained copies, not the payer's full claim history. Whether any of the 25 lines was submitted or received before July 23, 2026 is not known. The records do not show who was responsible, or any loss. None of these records names GT Independence. The 25 lines are already counted in the site's 353-line, $97,882.76 review; do not add them again.

  • Exact words - “There was an IT Infrastructure interruption in CCC offices – IT is aware and proactively working on this issue.” — XXXXXX XXXXX, LMSW, MS, CBIS, Manager, Clinical Operations, ABI, PCA waiver, Connecticut Community Care (CCCI), April 5, 2024.
  • Exact words - “We apologize for the delay and PA’s will be uploaded as soon as possible.” — XXXXXX XXXXX, Manager, Clinical Operations, ABI, PCA waiver, Connecticut Community Care (CCCI), April 5, 2024.
  • Exact words - “There was an IT Infrastructure interruption in CCC offices which you are aware of and it should be corrected this week.” — Amy Dumont, Connecticut Department of Social Services (title not shown in this email), April 8, 2024.
  • Exact words - “This disruption has now resulted in our complete inability to add or bill services for the Medicaid consumers” — David Medeiros, ABI Resources (David's account), April 8, 2024.
  • Exact words - “the effective date of your Provider Enrollment Agreement is 01/25/2024, and the Provider Enrollment Agreement shall thereafter be in effect until 01/25/2026” — Connecticut Medical Assistance Program (Gainwell Technologies), re-enrollment approval letter dated 01/25/2024, January 25, 2024.
  • Exact words - “CLAIM EXCEEDS TIMELY FILING LIMIT.” — Connecticut interChange MMIS remittance advice, EOB code 0512, July 28, 2026.
  • What it does not show - Whether any of these 25 lines was submitted, or received by the payer, before July 23, 2026. The search covered ABI's retained export and remittance files, not the payer's full claim history. Whether the April 2024 IT interruption lasted past that month, or affected these lines after their authorizations were approved. Who was responsible for the delay. The billing file names ABI as sender and the DSS claims system as receiver; it does not name the person who sent it. Any role of GT Independence. No record in this chain names GT. Nothing here shows that GT caused the delay, the denials or any loss. Whether a late-filing exception applies, or whether the 4021 benefit-plan reason was correct for these clients and dates. That the approval dates shown in November 2026 are when the authorizations first became usable. The history is a current snapshot, and 21 of the lines also overlap entries marked 'Voided'. The final outcome, a loss or an amount owed. $6,857.34 is the billed amount on denied lines. Scope: the July 28, 2026 remittance denied 81 lines with 2024 service dates; this card covers 25 of them. The other 56 are not reviewed here.
  • Counter-evidence and other side - DSS wrote on April 8, 2024 that the interruption 'should be corrected this week', and 24 of the 25 lines show approval dates of April 9, 10 or 23, 2024, more than two years before the lines were billed. Billing worked for other services in the same weeks: an April 23, 2024 remittance paid 47 ABI claims for services dated March 31 to April 13, 2024. One line ($195.39, April 13, 2024) shows an approval date of December 1, 2023, before the service. The export history saved from ABI's Sandata billing account on Nov 5, 2026 (1,230 export files, Jan 4, 2017 to Nov 3, 2026) shows no export of these 25 lines before July 23, 2026; ABI's billing account is the named sender of that export.
  • Connected records - March 2026 approvals, GT's Nov 10, 2026 statement, and the separate 28-service 2026 group; What the money records show (353-line review); Proof and gaps; Gainwell's November 10, 2026 answer on the same July 28, 2026 remittance; March 2026: which approval went in which direction

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 5, 2024: Background). A link is navigation only.

May 1-7, 2022 services: all 177 saved lines appear on Gainwell's May 24, 2022 remittance, in its paid-claims section

An earlier check compared ABI's saved Sandata billing exports with 21 saved remittance data (CSV) groups. It did not find 177 service lines dated May 1-7, 2022. That gap is now closed. All 177 lines appear on Gainwell remittance (number withheld, as on the May 8-14 card), dated May 24, 2022, in the printed section titled "CMS 1500 CLAIMS PAID" (pages 2-9).

The 177 lines left ABI's Sandata billing account in one export, created May 12, 2022 (export 977: 18 claims, 177 service lines, $47,365.53 billed). The remittance lists the same 18 claims and 177 lines. Each line matches by service date, procedure code, units and billed amount. Every line shows a positive allowed amount. The allowed amounts add up to $47,365.53.

The line table prints billed and allowed amounts only. It has no paid-amount column for each line. So the paid amount for each line is unknown. It is not zero. The remittance does print a paid amount for each of the 18 claims, and a net payment of $47,365.53 for this remittance. It prints "CLAIMS DENIED" as 0. One line carries code 9991 ("BILLED UNITS HAVE BEEN CUTBACK TO CONTRACT MAXIMUM"); its allowed amount is still positive.

These 177 lines are not part of the site's 353-line, $97,882.76 review of denied or unclear lines. They are also a different group from the May 8-14, 2022 lines that Gainwell answered about on November 10, 2026. Do not add, subtract or combine these counts. A printed remittance is the payer's record of how it processed claims. It is not a bank record.

  • Exact words - “CMS 1500 CLAIMS PAID” — Connecticut interChange MMIS provider remittance advice (Gainwell Technologies, fiscal agent), section heading on pages 2-9, May 24, 2022.
  • Exact words - “TOTAL CMS 1500 CLAIMS PAID: 47,365.53” — Same remittance, page 9 (end of the paid-claims section), May 24, 2022.
  • Exact words - “BILLED UNITS HAVE BEEN CUTBACK TO CONTRACT MAXIMUM” — Same remittance, EOB code 9991 (EOB code descriptions page), May 24, 2022.
  • Record numbers - Gainwell remittance (number withheld, as on the May 8-14 card), issue date May 24, 2022; Sandata export 977 (created May 12, 2022), in the export history saved Nov 5, 2026
  • What it does not show - The paid amount for any single line. The line table has no paid column. Each line's paid amount is unknown, not zero. That the money reached ABI's bank. No bank record was checked for this card. The remittance's printed net payment is not a bank deposit. When Gainwell first received the May 12, 2022 export. No receiver acknowledgment (999 or 277CA) tied to export 977 was found in the records checked. That is not proof that none exists. That each billed line is the same as one exact EVV visit. The match is by date, code, units and amount, not by a visit ID. Any later adjustment or take-back of these 18 claims. Later remittances were not searched for this card. Why the earlier CSV check missed these lines. The likely reason is that the 21 saved CSV groups did not include this remittance, but this card does not prove that. Anything about the May 8-14, 2022 lines, the 353-line review, or any other group. That any person or office did something wrong. This card is not a finding of unpaid claims, loss, debt, theft or retaliation.
  • Counter-evidence and other side - This record cuts against any reading that the May 1-7, 2022 lines were never received or never paid. The payer printed all 177 in its paid-claims section with positive allowed amounts. The same week's work was adjudicated 12 days after export; contrast the May 8-14, 2022 lines, which were first exported on July 23, 2026 and denied (separate card). Calendar order alone does not explain why the two weeks differed.
  • Connected records - The next week, May 8-14, 2022: first exported July 2026 and denied (Gainwell answer of Nov 10, 2026); What the money records show (353-line review); Proof and gaps; Earlier Sandata/DSS exchange: March 18-25, 2019 app problem report and DSS reply (a different event, not a cause of the 2022 history); Due process: notice, decisions and review; Permanent protection: David's proposed safeguards; Investigator Hub

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, May 24, 2022: Background). A link is navigation only.

DSS's own written ABI waiver policy: the person or their legal representative selects the providers

On November 14, 2023, the Connecticut Department of Social Services (DSS) answered David's November 13, 2023 records request about the ABI waiver provider directory. Its FOIA office wrote: "Please find the attached Policy information as a portion of this request." The attachment was a 22-page document titled on each page "ABI Waiver Operational Policy Effective 7.1.16." The same document is posted on DSS's official website.

Page 18 lists the responsibilities of the individual. It says the individual or the individual's legal representative, or both, shall "Select, from a list of providers, the providers who will deliver the services specified in the service plan". They may also "Select new providers, as necessary." They shall "Notify the department if a provider is not performing satisfactorily."

Other pages set related duties. Page 7 says person-centered planning shall "Offer informed choices to the individual regarding the types and providers of services and supports that are available." It bars waiver service providers from providing care management or developing the person's service plan. Page 19 says DSS or its agent shall "Establish provider qualifications and, through its fiscal intermediary, establish and maintain a directory of providers." Page 22 lets DSS suspend or terminate a provider immediately, without notice, for a threat to a participant or fraudulent or abusive practices.

This is a written standard. It can be read next to DSS's 2015 reply on choice, David's 2018 reports that families were steered, and DSS's October 2019 restriction on ABI Resources taking new clients. Reading them together is a comparison, not proof. The policy does not show that anyone broke it, and it does not decide any one person's case.

  • Exact words - “Select, from a list of providers, the providers who will deliver the services specified in the service plan;” — DSS, ABI Waiver Operational Policy Effective 7.1.16, (NEW) Sec. 17b-260a-11(a)(2)(C), responsibilities of the individual or legal representative, July 1, 2016. Official source
  • Exact words - “The individual or the individual's legal representative, or both, shall:” — DSS, ABI Waiver Operational Policy Effective 7.1.16, Sec. 17b-260a-11(a)(2) (lead-in to the list above; PDF uses a curly apostrophe), July 1, 2016. Official source
  • Exact words - “Offer informed choices to the individual regarding the types and providers of services and supports that are available;” — DSS, ABI Waiver Operational Policy Effective 7.1.16, person-centered planning requirement (7), July 1, 2016. Official source
  • Exact words - “Prohibit providers of waiver services for the individual, or those who have an interest in or are employed by a provider of waiver services for the individual, from providing care management or participating in the development of the person-centered service plan;” — DSS, ABI Waiver Operational Policy Effective 7.1.16, person-centered planning requirement (6), July 1, 2016. Official source
  • Exact words - “Establish provider qualifications and, through its fiscal intermediary, establish and maintain a directory of providers;” — DSS, ABI Waiver Operational Policy Effective 7.1.16, Sec. 17b-260a-12(k), department responsibilities, July 1, 2016. Official source
  • Exact words - “Please find the attached Policy information as a portion of this request” — DSS FOIA office (FOIA.DSS@ct.gov), reply to David's November 13, 2023 request, November 14, 2023. Open the record
  • Record numbers - ABI Waiver Operational Policy Effective 7.1.16 (22 pages; footer: Pursuant to Conn. Gen. Stat. 17b-10); Draft regulation sections 17b-260a-1 to 17b-260a-18 (marked (NEW)); Sec. 17b-260a-11(a)(2)(C) and (G); 17b-260a-12(k); 17b-260a-18(b); FOIA email record EM-20231113-CTDSS-c7ec22
  • What it does not show - That this text was formally adopted as a regulation, is current law, or applied on any given date. The document calls itself an operational policy "Effective 7.1.16" and marks each section "(NEW)." Which version applied in each year is not shown. That any DSS worker, care manager or contractor steered anyone, or broke this policy. It is a written rule, not a finding. What happened in any one participant's case, or which list of providers a person was shown. That ABI Resources was owed any referral or client. That DSS's October 2019 restriction on ABI Resources was wrong or retaliatory. Calendar order is not proof of cause. That DSS's November 14, 2023 reply produced everything David asked for. DSS itself called it "a portion of this request." That the policy was unknown. It is posted on DSS's own website.
  • Counter-evidence and other side - The same policy gives DSS duties that cut both ways. Page 22 lets DSS suspend or terminate a provider immediately and without prior notice if it believes the provider posed a threat to a participant or engaged in fraudulent or abusive practices. Page 18 also lets a legal representative make decisions for the person, and lets DSS go to probate court if it finds a representative is not acting in the person's best interests. Page 19 assigns the provider directory to DSS through its fiscal intermediary. On June 1-2, 2020, DSS told David that ABI was listed, and a saved June 2 copy lists ABI (already live under Rights and the Record). DSS stated its own reasons for the October 2019 restriction (already live at /early-warning-record/#d-2019-10-10).
  • Connected records - May 11-18, 2015: David's report and DSS's reply on choice; November 6-7, 2018: DSS writes to David about the care managers' process, and his steering report; October 10-31, 2019: DSS restricts ABI Resources from new clients, with DSS's stated reason; Free choice of care provider (42 CFR 431.51); David's November 13, 2023 request and DSS's November 14 reply; Proposed safeguards: signed choice, a usable directory, written reasons

Independent public-records archive. Verify independently. A filing is not a finding.

Related CMS record: October 30, 2025 HCBS settings plan determination and its limits

Return to the dated timeline entry (Early Warning Record, November 14, 2023: Background). A link is navigation only.

DSS contract 19DSS2201BZ: what DSS bought from the Brain Injury Alliance of Connecticut (BIAC)

The Connecticut Department of Social Services (DSS) signed purchase-of-service contract 19DSS2201BZ with the Brain Injury Alliance of Connecticut (BIAC). It took effect July 1, 2019. The contract term, as amended in the reviewed records, was July 1, 2019 through June 30, 2026. These records do not establish an active contract in November 2026.

Among the services DSS bought, page 3 of the original contract lists "A directory of service providers and professionals" and a Providers' Council "with meetings 4-5 times per year to promote networking and information exchange between providers."

The contract also sets reporting and review. BIAC must send quarterly statistical reports within 30 calendar days of each quarter's end (page 6), and financial reports on set dates each year (page 6). Page 5 says BIAC's performance "shall be reviewed and evaluated at least annually by Department staff."

Amendment 4 (January 31, 2025) added $3,130, a one-time ARPA cost-of-living adjustment (COLA) that it says shall be paid from state account (SID) 29773. Amendment 6 (signed by BIAC and DSS on August 29, 2025; approved as to form by the Attorney General's office on September 11, 2025) extended the term to June 30, 2026 and added $188,142 for state fiscal year 2026: $108,142 from SID 16174 and $80,000 from SID 35308. Amendment 7 added another $3,130 COLA, for a maximum of $1,288,548. Amendment 7 does not name a SID.

These are signed duties. They do not show how BIAC carried them out, what directory it kept, or what DSS reviewed. Those records are still needed.

What the three state accounts are called in official state records: SID 29773 is "ARPA private Provider COLA" (OPM code table). SID 16174 is the "Human Services Infrastructure Community Action Program" (DSS program list for the legislature, March 2026; the Comptroller shortens it to "Infrastructure Community Action Program"). SID 35308 is the "Brain Injury Prevention and Service Account" (Comptroller's FY2023 budgetary report).

These are funding lines for BIAC's whole program. The contract does not price the directory, the Providers' Council or any other single duty separately. An account name alone does not show a federal Medicaid source. BIAC also had a separate $300,000 Treasury-funded contract, 23DSS2201BZ, with its own duties.

Follow the funding to the services and review records

Federal conditions need their own contract link. A4 and A5 of the 19 contract also contain Treasury and 2 C.F.R. Part 200 conditions covering reporting, procurement/conflicts, records access, applicable audits and completion certification. A4, pp33-37; A5, pp3-13. A4's printed FAIN placeholder does not identify its actual federal award. Do not substitute the separate 23-contract award number. Audit applicability depends on the relevant fiscal year and federal version.

For the separate 23DSS2201BZ contract, payment requires supporting expenditure records and DSS review and acceptance of financial reports. Original 23 contract, physical pp12-13.

Why this matters: connect the signed work to dated campaign materials, Spanish versions, workshop recordings, submitted financial reports, actual expenditure support and DSS monitoring/closeout records. These would test performance. The contracts alone establish no delivery, misuse, discrimination or loss. The conference-recording duty does not establish a right to privately record a different Providers' Council presentation. The existing 2019-June 2026 period limit, Allied-directory distinction and CHRO contrary findings still apply.

  • Exact words - “A directory of service providers and professionals;” — Contract 19DSS2201BZ (DSS and BIAC), Part I, Section A.3.b.iii, July 1, 2019. Official source
  • Exact words - “with meetings 4-5 times per year to promote networking and information exchange between providers.” — Contract 19DSS2201BZ, Part I, Section A.3.c.vi (the clause opens "A Providers' Council"; the PDF text layer shows the apostrophe as a stray symbol), July 1, 2019. Official source
  • Exact words - “The performance of the Contractor, and any applicable subcontractors, shall be reviewed and evaluated at least annually by Department staff.” — Contract 19DSS2201BZ, Part I, Section E.2 (Quality Assurance Compliance), July 1, 2019. Official source
  • Exact words - “The Contractor will submit to the Department completed quarterly statistical reports in a format provided by the Department within thirty (30) calendar days of the end of each quarterly period.” — Contract 19DSS2201BZ, Part I, Section G.1, July 1, 2019. Official source
  • Exact words - “The Contractor shall submit to the Department financial reports on the Department's requested forms on or before July 30, October 30, January 30, and March 31 of each year during the contract period.” — Contract 19DSS2201BZ, Part I, Section H.1 (dates as printed; PDF shows the apostrophe as a stray symbol), July 1, 2019. Official source
  • Exact words - “Contract Term as Amended: 7/1/2019 to 06/30/2026” — Contract 19DSS2201BZ, Amendment 6, page 1 (spacing as printed), August 29, 2025. Official source
  • Exact words - “SFY 2026 - $108,142.00 (SID 16174)” — Contract 19DSS2201BZ, Amendment 6, page 1, item 2.i, August 29, 2025. Official source
  • Exact words - “SFY 2026 - $80,000.00 (SID 35308)” — Contract 19DSS2201BZ, Amendment 6, page 1, item 2.ii (spacing as printed), August 29, 2025. Official source
  • Exact words - “Contract Term as Amended: 7/01/2019 – 6/30/2026” — Contract 19DSS2201BZ, Amendment 7, page 1 (spacing as printed), June 12, 2026. Official source
  • Exact words - “The one-time ARPA COLA payments shall be made from Special Identification Code ("SID") #29773.” — Contract 19DSS2201BZ, Amendment 4, page 1, item 1 (the PDF text layer shows the quote marks as stray symbols), January 31, 2025. Official source
  • Exact words - “ARPA private Provider COLA” — State of Connecticut, Office of Policy and Management, code table row for SID 29773, October 1, 2025. Official source
  • Exact words - “Human Services Infrastructure Community Action Program” — DSS, State-Funded Program Descriptions for the legislature's Human Services subcommittee, row for SID 16174, March 4, 2026. Official source
  • Exact words - “BRAIN INJURY PREVENTION AND SERVICE ACCOUNT” — Office of the State Comptroller, Annual Report (budgetary basis), fiscal year ended June 30, 2023, row for SID 35308 (capitals as printed), December 29, 2023. Official source
  • Record numbers - DSS contract 19DSS2201BZ (also printed 164-1BZ-TBI-01), Amendments 1-7; Core-CT SIDs 16174 and 35308 (A6); SID 29773 (A4); Separate contract 23DSS2201BZ (Treasury award SLFRP0128, $300,000)
  • What it does not show - That the contract was active in November 2026. The contract term, as amended in the reviewed records, was July 1, 2019 through June 30, 2026. These records do not establish an active contract in November 2026. The state's contract summary marks it "Expired." A renewal or new contract, if any, was not found in the reviewed records. That BIAC's contract directory is the same as the provider directory kept by Allied, DSS's fiscal intermediary. That has not been established. Which directory editions BIAC kept, what rules decided who was listed, or who could take part in the Providers' Council. That any service was or was not delivered, or how the money was spent. Budget lines are authorizations, not spending. What reports BIAC sent or what DSS's annual reviews found. None were in the reviewed records. A breach. David's 2018 reports came before this 2019 contract. That any family saw a particular directory, that ABI Resources was owed a referral, or that DSS authorized any recording restriction. That Amendment 7's $3,130 came from SID 29773. A7 does not print a SID for it.
  • Counter-evidence and other side - The contract sets targets, not results. For example, "75% of callers will speak to a specialist within one business day" (page 4) is a goal to be measured, not a reported outcome. Amendments say unmodified terms "remain in full force and effect" (A6 page 2); no amendment found removes the directory or Council duties. CHRO's findings and the contrary reasoning in the 2024 recording and accommodation dispute are already live at /warnings-and-answers/#decisions. This contract does not change them. Separate Allied directory and version evidence is already live at /rights-and-the-record/#equal.
  • Connected records - 2018: David's reports about provider lists and steering; Who knew: DSS replies and notice history; What each agency decided, including CHRO's findings; Equal treatment and the Allied directory evidence; Records requested and still missing; Investigator Hub

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, July 1, 2019: Background). A link is navigation only.

April 19, 2023: "ABI Resources will not bill for ABI waiver services that are not being provided"

On April 19, 2023, David Medeiros wrote an ABI Waiver critical incident report. He is named as reporter and as the person submitting it. On page 2 he wrote: "ABI Resources will not bill for ABI waiver services that are not being provided." The sentence follows his report that ABI day staff had been told verbally to let a participant take unsupervised walks for undefined periods. He asked the care manager for written directions.

He emailed the report that night (10:58 PM Eastern) from ABI's account to the participant's care manager at Connecticut Community Care (CCCI), with a copy to ABI's own secure mailbox.

On April 24, 2023, David attached the same report to an email to the DSS Community Options Unit: Amy Dumont (Program Manager) and Jennifer Cavallaro, with copies to Elizabeth Orejuela and Michael Slitt. The attached copy contains the same sentence. On April 26, Amy Dumont replied in the same thread that DSS had contacted the care manager and clinical staff, and that "it was determined that the client is in a safe situation and had an appropriate plan of care."

These records show what David wrote and who received it. They do not show what ABI billed or did not bill for this participant, or whether any later decision about ABI was linked to this report.

  • Exact words - “ABI Resources will not bill for ABI waiver services that are not being provided.” — David Medeiros, ABI Resources (reporter and submitter on the ABI Waiver critical incident report), April 19, 2023.
  • Exact words - “Please find a CIR attached to this email for your review.” — David Medeiros, ABI Resources, to Amy Dumont and Jennifer Cavallaro (DSS), cc Elizabeth Orejuela and Michael Slitt (DSS), April 24, 2023.
  • Exact words - “Upon receipt of the critical incident report, the Department reached out to the Care Manager and the clinical professionals on the client’s care team.” — Amy Dumont, LCSW, Program Manager, CT Department of Social Services, Community Options Unit, April 26, 2023.
  • Exact words - “it was determined that the client is in a safe situation and had an appropriate plan of care.” — Amy Dumont, LCSW, Program Manager, CT Department of Social Services, Community Options Unit, April 26, 2023.
  • Exact words - “I will also have him review with you the services that ABI resources should be providing on the clients plan.” — Amy Dumont, LCSW, Interim Director/Program Manager, CT Department of Social Services, Community Options Unit, May 23, 2023.
  • What it does not show - Billing records. No claim, Sandata visit or remittance record for this participant was checked. Whether ABI billed, or did not bill, any hours during the unsupervised walks is not shown. That anyone asked ABI to bill for services not provided. The report describes verbal instructions about unsupervised walks, as told to ABI by its staff. It does not quote an instruction to bill. The person who gave the instructions is not named in that passage. That the care manager or DSS read this sentence. The emails show the report was sent and that DSS answered about "the critical incident report." They do not show which lines anyone read. The plan DSS referred to. On May 23, 2023 David wrote that ABI had not received it. No copy is held. What was decided at the later team meeting. No meeting record is held. Any link between this report and a later decision about ABI. Calendar order is not cause. A finding about fraud, false claims or retaliation by anyone. This is David's report and DSS's account of its follow-up.
  • Counter-evidence and other side - DSS wrote on April 26, 2023 that, after contacting the care manager, the clinical professionals and the conservator, it found the participant safe with an appropriate plan of care. That is DSS's account; its notes and the plan were not reviewed. The CCCI care manager answered within a day and set up a team call; the thread shows staff of CCCI and the clinical provider replying on April 20-21, 2023. The report was not unanswered.
  • Connected records - Who knew what before each decision; What each agency actually decided; What the money records show; Proof and gaps; July 6, 2023: David's later report to DSS about an ABI waiver behaviorist (a separate report; a link to this one is not established); Right to petition; Permanent protection: David's proposed safeguards

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 19, 2023: Background). A link is navigation only.

November 2026: CMS's Northeast fraud contractor says its review closed in May 2026

SafeGuard Services LLC is the Northeast Unified Program Integrity Contractor (NE UPIC) for the Centers for Medicare & Medicaid Services (CMS). On March 25, 2026, its project coordinator Eric Bischof wrote that it had "been asked to review some of the concerns" David raised. He asked for incidents David "personally observed or were directly involved in." David answered on March 26, 2026.

On November 5, 2026, David sent Mr. Bischof records he described as firsthand. On November 9, 2026, at 3:59 PM UTC, he sent "one more" incident, from November 2018, copying CMS's Medicaid Integrity Program. These are David's submissions and his descriptions. They are not findings.

On the evening of November 9, 2026 (6:54 PM Eastern), Jeffrey D. Hartley, NE UPIC Medicaid Fraud Manager, replied, copying CMS. He wrote that the review "was completed, and no further investigative action is anticipated." He wrote that the new material "does not establish a new or independently actionable allegation." He pointed David to Connecticut DSS.

David asked for a reference number, the closing date, and the CMS office that approved the closure. On November 10, 2026, Mr. Hartley wrote that "the matter was closed in May 2026." He wrote that the CMS lead assigned at the time "has since retired from CMS." He did not give a reference number or name a CMS approver. David asked again on November 12. No answer was found through November 16, 2026.

What is still missing: the list of material the contractor actually reviewed, and any closure or CMS approval record. Those records were not given to David and were not found.

  • Exact words - “We have been asked to review some of the concerns you raise.” — Eric Bischof, Project Coordinator, UPIC Northeastern Jurisdiction, SafeGuard Services LLC, March 25, 2026.
  • Exact words - “Here is one more, separate from my November 5 email.” — David Medeiros, ABI Resources, to Eric Bischof, cc CMS Medicaid Integrity Program (his submission), November 9, 2026.
  • Exact words - “This email serves to notify you that our review of the allegations was completed, and no further investigative action is anticipated.” — Jeffrey D. Hartley, CFE, AFI, NE UPIC Medicaid Fraud Manager, SafeGuard Services LLC, November 9, 2026.
  • Exact words - “While your recent correspondence provides additional historical information, it does not establish a new or independently actionable allegation of Medicaid fraud, waste, or abuse that would warrant further investigative action by the Northeast Unified Program Integrity Contractor (NE UPIC).” — Jeffrey D. Hartley, NE UPIC Medicaid Fraud Manager, SafeGuard Services LLC, November 9, 2026.
  • Exact words - “SafeGuard Services LLC is a private company contracted by the Centers for Medicare & Medicaid Services (CMS) to perform specific Medicaid program integrity functions.” — Jeffrey D. Hartley, NE UPIC Medicaid Fraud Manager, SafeGuard Services LLC (HTML shows &amp;), November 9, 2026.
  • Exact words - “Our review of your previous complaint was completed, and the matter was closed in May 2026.” — Jeffrey D. Hartley, SafeGuard Services LLC (NE UPIC), November 10, 2026.
  • Exact words - “The CMS Business Function Lead assigned to the NE UPIC at the time of our review has since retired from CMS.” — Jeffrey D. Hartley, SafeGuard Services LLC (NE UPIC), November 10, 2026.
  • Record numbers - No NE UPIC reference number was given (asked Nov 10 and Nov 12, 2026); CMS FOIA control numbers on /warnings-and-answers/#cms are separate matters
  • Separate CMS records answer - May 13, 2026: CMS found no responsive records for the SWCAA request (control 022720267103). The shared month does not establish that the two decisions concern the same case or records.
  • What it does not show - What the contractor reviewed. No list of examined material was given or found. Which two emails the November 9 reply meant by "two additional emails." It does not name them. David sent Mr. Bischof emails on November 5 and November 9, 2026, and also sent CMS's Medicaid Integrity Program and HHS-OIG a separate email on November 5. A closure letter, a closing date more exact than "May 2026," or a CMS approval of the closure. None was given or found. That anyone told David of the May 2026 closure before November 9, 2026. No such message was found in his mailbox (native copy through Nov 12, 2026; live search through Nov 16, 2026). That the contractor found there was no fraud. It wrote that the new material did not establish a new or independently actionable allegation, and that its review was complete. What CMS itself decided. The CMS Medicaid Integrity Program was copied; no CMS reply on this was found. That David's allegations are true. They remain his allegations.
  • Counter-evidence and other side - The contractor did answer in writing, twice, within about a day, and copied CMS. It explained its limits: "We are not a federal or state regulatory agency and do not possess independent enforcement authority." In March it had written that its statement of work with CMS and federal statute limit what it can review. It wrote that the concerns were "substantially similar to concerns previously submitted to CMS and other agencies dating back to at least 2023." It named a route: Connecticut DSS, as the State Medicaid Agency, and offered to coordinate with DSS and CMS if DSS finds further review warranted.
  • Connected records - Read both replies (November 9 and 10, 2026), privacy-cleaned copy; What CMS did with the warnings (includes the Nov 9-10, 2026 line); What each agency actually decided; Records requested and still missing; November 6-7, 2018: DSS and the client transfers David described on November 9, 2026; Proposed safeguards: every fraud report gets a traceable answer

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, November 10, 2026: Background). A link is navigation only.

May 13, 2026: CMS found no responsive records for the SWCAA request

CMS's Freedom of Information Act office answered David Medeiros's request relating to Southwestern Connecticut Agency on Aging, Inc. Its two-page letter identifies the request date as February 27, 2026 and control number 022720267103. CMS stated that its search did not locate responsive records. Emmett Nicholson, Director, Division of FOIA Analysis – C, CMS Freedom of Information Group, signed the letter.

This is a request-specific federal records-search answer. It is separate from the CMS fraud contractor's statement that a prior review closed in May 2026. The shared month does not establish that the two decisions concern the same case or records.

The answer does not establish that records do not exist elsewhere, that SWCAA did anything wrong, or that David's provider-choice or payment concerns have been resolved. CMS may not hold the particular records sought, or its search may not have located them; the letter does not decide which explanation applies.

To assess the search, the deciding records are the full request as submitted and CMS's control-specific search documentation: custodians, systems, search terms, dates and results. Any later appeal determination or reopened-search record must be evaluated separately. Current appeal status remains unverified in this review.

Source: retained CMS letter dated May 13, 2026, control 022720267103, physical pages 1-2. This is a minimized summary of the retained copy, not a full transcription or a newly authenticated native attachment. The original remains private because it includes requester contact and access information.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, May 13, 2026: Agency reply · Decision). A link is navigation only.

June 10, 2026: CMS requested another provider-records search

CMS's Freedom of Information Group wrote about appeal 112020247009, concerning National Provider Identifier numbers and information about entities approved to deliver Connecticut Medicaid ABI Waiver services. Emmett Nicholson reported that CMCS had initially found no responsive records and that a no-records letter had been emailed on December 10, 2024. The email also says the Freedom of Information Group "were informed by CMCS that the requester may find information within the Connecticut Department of Social Services." He then stated that FIG had requested another thorough CMCS search and would report the results when complete.

This is a concrete request for additional search work. It is not a completed-search report or a final appeal decision. The June message does not establish current status, what Connecticut DSS held, whether the earlier search was adequate, or wrongdoing by any provider or office. Another search can be an ordinary step in reconsidering a records appeal.

CMS described the appeal as dated November 7, 2024. That wording remains attributed to the message; the date has not been silently reconciled with other records.

The deciding records are CMS's resulting search report and final appeal determination, with the custodians, systems, terms, date range and results. Those outcomes remain unknown from this message.

Source: CMS email of June 10, 2026 about appeal 112020247009, from a saved mailbox copy. It is not a newly authenticated original message file.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, June 10, 2026: Agency reply). A link is navigation only.

DCP answered the directory grievance. What action followed?

David submitted the ABI Waiver directory grievance on November 15, 2023. DCP replied November 20 recommending Ombudsman contact. That reply establishes a response; it does not document a completed transfer or disposition.

In a separate records request, DCP acknowledged R000354-102024, initially stated it held no responsive records, then supplied emails on January 7, 2025. Those selected emails concern other 2024 matters.

David sent a November 10, 2026 request for the directory grievance's intake and action history. A November 16 acknowledgment signed by DCP's FOI Records Center assigns R000445-111626 and states that DCP received an FOI request on November 10. It describes records review as pending and says it is not a denial. It does not repeat the request's subject or scope, so its specific match to the directory-handling request remains unconfirmed. This acknowledgment supplies no records or grievance outcome.

R000445 request scope: UNCONFIRMED.

This record relates to petition rights and the dated warnings. It does not establish concealment, liability or a duty to investigate every petition.

  • Exact words - “We are recommending that you contact the Office of the CT Ombudsman.” — Connecticut Department of Consumer Protection, November 20, 2023. Open the record
  • Record numbers - R000354-102024 (the separate 2024 FOI request); 174585 (the separate public FOI archive); R000445-111626 (November 16 acknowledgment of a November 10 request; request scope: UNCONFIRMED)
  • What it does not show - A completed transfer to the Ombudsman or the original grievance's disposition. That the January 7, 2025 production resolved the November 2023 directory grievance. That R000445-111626 specifically identifies the directory-grievance handling request, a final records disposition, an actual appeal deadline or a proven statutory violation.
  • Counter-evidence and other side - DCP did answer the November 2023 grievance. This is not evidence of no outward response. The separate FOI history includes acknowledgment, an initial answer and a later production; those responses must be read alongside the original grievance rather than treated as its disposition. The November 16 acknowledgment states November 10 receipt of an FOI request. The earlier unqualified agency-intake-unknown description must be read with this new record; its precise subject/scope match remains unconfirmed.
  • Connected records - Selected grievance, reply and handling-request excerpts; Separate FOI request: acknowledgment; Separate FOI request: initial answer; Separate FOI request: production; Petition rights and the record; Dated warnings and responses; DSS records reply, November 10, 2026

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, November 15, 2023: Background). A link is navigation only.

DSS contract 12DSS5101AS: Allied's written duty to keep the ABI waiver provider directory, and when a provider may be removed

Under historical DSS contract 12DSS5101AS, Allied Community Resources served as a third-party administrator for DSS's disability waiver programs, with defined provider-directory and provider-credentialing duties. DSS's own ABI waiver policy says DSS, "through its fiscal intermediary," keeps the directory of providers that participants choose from (see the DSS policy card). The contract, posted on DSS's website, spells out that duty.

The contract says Allied "shall develop and maintain an accurate Provider Directory" of all qualified providers that waiver participants may select. Allied must update it within five business days of any addition or removal, send DSS monthly updates and a full copy every quarter, and give a copy to any participant who asks.

The contract also limits removal. A provider is removed when the provider or DSS asks "for criminal or fraud reasons," or after six months of inactivity if Allied cannot reach the provider by phone or mail. Allied must notify the provider two weeks before removing it. Amendment 7 states the amended term as January 1, 2012 to June 30, 2017 and repeats the same directory terms. Its signature page shows January 25, 2017 for Allied and DSS and February 22, 2017 for the Attorney General's office. These dates are as printed on the posted copy; they have not been separately authenticated.

These historical clauses alone do not show which terms governed in 2018-2019. State reports list a later Allied contract, 18DSS7101AS (February 1, 2018 to January 31, 2025). Its signed terms and amendments were not in the records reviewed. That later contract is the missing record needed to compare these duties with David's August 2018 provider-list concerns or DSS's October 2019 restriction on ABI Resources.

Allied also credentialed providers. Amendment 7 says Allied "shall continue to credential new providers and re-credential existing providers every two years" for the ABI program and others, and "shall issue a letter to providers" when credentialing is complete. Allied's February 28, 2020 letter says ABI Resources "met all required qualifications for re-credentialing" and "will remain on the state-wide Provider Directory."

In June 2020 David wrote that ABI was again not listed for referrals. DSS replied that Allied supplied the directory and that ABI "continues to be listed." A retained Allied directory printed June 2, 2020 does list ABI Resources. Which version families and care managers actually saw is not known.

Coverage: this card is based on the posted original contract with Amendments 1-3, and Amendment 7. Amendment 7 replaces the scope of "the original contract through Amendment Six (A6)," so Amendments 4-6 exist, but they were not retrieved and their terms are not known.

  • Exact words - “The Contractor shall develop and maintain an accurate Provider Directory, listing all qualified Providers who may perform services for and are eligible for selection/employment by Waiver Participants.” — Allied Community Resources, contract 12DSS5101AS with DSS, January 1, 2012. Official source
  • Exact words - “Maintain the Provider Directory database current within five business days of Provider additions or removals;” — Allied Community Resources, contract 12DSS5101AS with DSS, January 1, 2012. Official source
  • Exact words - “the full updated Directory shall be provided on a quarterly basis to the Department and upon request to any Waiver Participant;” — Allied Community Resources, contract 12DSS5101AS with DSS, January 1, 2012. Official source
  • Exact words - “Registered Providers shall be removed from the Provider Directory when the Provider and/or the Department request the removal for criminal or fraud reasons;” — Allied Community Resources, contract 12DSS5101AS with DSS, January 1, 2012. Official source
  • Exact words - “The Contractor will send a notification to the Provider two weeks prior to removing any Provider from the Directory;” — Allied Community Resources, contract 12DSS5101AS with DSS, January 1, 2012. Official source
  • Exact words - “Contract Term as Amended: 1/1/2012 to 6/30/2017” — Allied Community Resources, contract 12DSS5101AS with DSS, Amendment 7 (signature page 19 shows Jan 25, 2017 for Allied and DSS and Feb 22, 2017 for the Attorney General's office, as printed; the June 29, 2016 date on page 1 is the earlier approval the amendment builds on), January 25, 2017. Official source
  • Exact words - “The contractor shall continue to credential new providers and re-credential existing providers every two years who wish to perform Waiver Services for the Acquired Brain Injury Program, PCA Waiver and Home Care Program for Elders.” — Allied Community Resources, contract 12DSS5101AS with DSS, Amendment 7, Section II.2.b.vi, January 25, 2017. Official source
  • Exact words - “The Contractor shall issue a letter to providers indicating that they have completed the credentialing process.” — Allied Community Resources, contract 12DSS5101AS with DSS, Amendment 7, Section II.2.b.vi, January 25, 2017. Official source
  • Exact words - “Your agency will remain on the state-wide Provider Directory which is distributed regularly to the Access Agencies.” — Allied Community Resources, Financial Management Services, re-credentialing letter to ABI Resources, February 28, 2020. Open the record
  • Exact words - “ABI Resources continues to be listed and listed within the first several pages based on numeric/alpha formatting.” — DSS (George Chamberlin), email reply to David Medeiros, subject "Provider Directory", June 2, 2020. Open the record
  • Record numbers - DSS contract 12DSS5101AS (Allied Community Resources): reviewed the posted original with Amendments 1-3, and Amendment 7. Amendments 4-6 were not retrieved.; Later Allied contract number reported by the state: 18DSS7101AS
  • What it does not show - The terms in force in 2018 or 2019. These historical clauses alone do not settle that either way. The later contract 18DSS7101AS and its amendments were not in the records reviewed. That ABI Resources was ever removed from Allied's directory, or how its listing changed. One retained edition was checked: the Allied ABI Program Provider Directory printed June 2, 2020 (85 pages) lists ABI Resources LLC under "APPROVED PROVIDERS." No other edition was reviewed for this card, and that copy does not show which version families or care managers saw. That DSS's October 2019 restriction on new clients was a directory removal. It was a separate DSS action, and calendar order is not cause. That Allied broke this contract. Contract terms describe what was expected, not what happened. Which directory any participant was shown, or what they chose. That this directory is the same list as BIAC's contract directory. They are separate contracts.
  • Counter-evidence and other side - The contract also lets household employees who work for one participant ask to be left out of the published directory, so a name missing from one printed list does not by itself show removal.
  • Connected records - DSS's written ABI waiver policy: the person or their representative selects providers; BIAC contract 19DSS2201BZ: a separate directory and Providers Council; August 14-15, 2018: David raises "ACR approved provider list - Concerns" with Allied and DSS; October 2019: DSS restricts ABI Resources from new clients (both sides); Freedom of choice in the record; Proposed safeguard: a public provider list; Proof and gaps: records still missing; February 28, 2020: Allied's re-credentialing letter ("will remain on the state-wide Provider Directory"); June 1-2, 2020: David's directory email and DSS's reply that ABI "continues to be listed"; Early Warning Record: June 1-2, 2020, with the retained June 2 directory; What happened to David and ABI; DSS records reply, November 10, 2026

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, January 1, 2012: Background). A link is navigation only.

2025-2026: What HHS-OIG and DSS wrote back: filing advice, two reprisal closures, and a separate audit review

On August 26, 2025 (10:02 PM Eastern), DSS staff attorney Michael Slitt acknowledged David's August 13, 2025 concerns. He wrote that DSS was "currently looking into the circumstances." He wrote that David was "free to relay any of your concerns" to the HHS Office of Inspector General (HHS-OIG) by filing a complaint, and named the State Auditors as another option. The email went to David only. It is advice to David. It is not a record of DSS sending anything to HHS-OIG.

HHS-OIG closed two of David's whistleblower reprisal complaints, for different stated reasons. Complaint I203262: the April 3, 2025 letter says OIG received it on March 20, 2025. The one box checked was "Standing." The letter quotes David calling ABI Resources a Connecticut Medicaid ABI Waiver provider. It then reasons from Medicare provider agreements that ABI Resources has no contract with CMS, so OIG has no jurisdiction under 41 U.S.C. § 4712. That is OIG's stated reasoning. This card does not judge it.

Complaint I248830: the April 9, 2026 letter is about a complaint David submitted on April 1, 2026. The one box checked was "Complaint Filed in Another Forum." It does not name the forum. The letter says any fraud, waste or abuse allegations "are treated separately" from reprisal and "may be forwarded" if warranted. The 2025 letter also says OIG "may refer" them. Neither letter says anything was forwarded, or what happened to the fraud allegations.

The closing emails arrived on April 3, 2025 at 10:17 AM Eastern and April 9, 2026 at 12:50 PM Eastern. Those are when the letters arrived, not when OIG received the complaints. The same records hold 15 automatic HHS-OIG Hotline receipts (November 29, 2022 to June 27, 2025: 9 Healthcare Fraud, 5 Whistleblower Retaliation, 1 Quality of Care). They say "You have successfully submitted your complaint" and print no tracking number. Six MuckRock request numbers are that platform's own numbers. Neither group is an OIG case or FOIA number. This covers the reviewed records through November 12, 2026 only. There may be other matters.

Separately, the State Auditors of Public Accounts (APA) wrote in their 2025 annual report that an HHS-OIG representative on their 2025 peer review team reviewed selected work papers for the State's 2024 Single Audit. The federal review "did not cite any audit deficiencies" and informally raised four documentation matters. The peer review was completed in August 2025. The report describes it as a review of audit work papers. It does not mention David's complaint or any provider.

What is still missing: any DSS record of sending, or deciding not to send, a referral to HHS-OIG or the Medicaid Fraud Control Unit; any OIG intake number tied to David's fraud reports; and any record of what OIG did with the fraud allegations.

  • Exact words - “The Department is currently looking into the circumstances giving rise to your communication.” — Michael Slitt, Staff Attorney, Connecticut Department of Social Services, August 26, 2025.
  • Exact words - “you are free to relay any of your concerns to the U.S. Department of Health and Human Services Office of Inspector General” — Michael Slitt, Staff Attorney, Connecticut Department of Social Services, August 26, 2025.
  • Exact words - “has completed its review of your complaint of reprisal, which we received on March 20, 2025” — Adam Layton, Assistant Special Agent in Charge, Special Investigations Branch, HHS-OIG Office of Investigations (Whistleblower Complaint No. I203262), April 3, 2025.
  • Exact words - “Complainant is not a protected whistleblower” — Adam Layton, Assistant Special Agent in Charge, Special Investigations Branch, HHS-OIG Office of Investigations (text of the "Standing" box, the only box checked; "Complaint Filed in Another Forum" is not checked), April 3, 2025.
  • Exact words - “Without an existing contractual relationship between ABI Resources and CMS, the HHS/OIG does not have jurisdiction to investigate your whistleblower reprisal complaint under 41 U.S.C. § 4712.” — Adam Layton, Assistant Special Agent in Charge, Special Investigations Branch, HHS-OIG Office of Investigations, April 3, 2025.
  • Exact words - “we may refer these allegations to the appropriate authority for any action that may be appropriate.” — Adam Layton, Assistant Special Agent in Charge, Special Investigations Branch, HHS-OIG Office of Investigations, April 3, 2025.
  • Exact words - “has completed reviewing the whistleblower reprisal complaint you submitted on April 1, 2026” — HHS Office of Inspector General, Whistleblower Reprisal Investigative Team (Whistleblower Complaint No. I248830), April 9, 2026.
  • Exact words - “Complaint Filed in Another Forum” — HHS Office of Inspector General, Whistleblower Reprisal Investigative Team (the only box checked; "Standing" and the OSC (U.S. Office of Special Counsel) "Referral" box are not checked), April 9, 2026.
  • Exact words - “Any underlying allegations of fraud, waste, or abuse that you submitted to OIG are treated separately from your reprisal allegations and may be forwarded to appropriate officials for review if warranted.” — HHS Office of Inspector General, Whistleblower Reprisal Investigative Team, April 9, 2026.
  • Exact words - “A peer review team completed our most recent peer review during August of 2025, which covered the one-year period of July 1, 2024, to June 30, 2025.” — Auditors of Public Accounts, State of Connecticut (2025 Annual Report, page 26), January 30, 2026. Official source
  • Exact words - “Our 2025 peer review team included a representative from the Department of Health and Human Services’ Office of the Inspector General, who conducted a review of select work papers supporting our 2024 Single Audit of the State of Connecticut.” — Auditors of Public Accounts, State of Connecticut (2025 Annual Report, page 26), January 30, 2026. Official source
  • Exact words - “While this federal review did not cite any audit deficiencies, the reviewer informally conveyed four matters for further consideration to our management team” — Auditors of Public Accounts, State of Connecticut (2025 Annual Report, page 26), January 30, 2026. Official source
  • Exact words - “You have successfully submitted your complaint” — HHS-OIG Hotline automatic "Confirmation Receipt" emails (15 of them, Nov 29, 2022 to June 27, 2025), November 29, 2022.
  • Record numbers - HHS-OIG Whistleblower Complaint No. I203262 (reprisal; received March 20, 2025 per the letter; closed April 3, 2025; also on OIG correspondence received March 25, 2025); HHS-OIG Whistleblower Complaint No. I248830 (reprisal; submitted April 1, 2026; closed April 9, 2026); 15 HHS-OIG Hotline confirmation receipts, Nov 29, 2022 to June 27, 2025: no tracking number printed; MuckRock request IDs 175105, 175285, 175540, 175673, 176809, 180803 (Oct 23, 2024 to Feb 1, 2025): platform numbers, not HHS-OIG control numbers; No HHS-OIG fraud-hotline or FOIA control number was found in the reviewed records (through Nov 12, 2026). That is a search result, not proof that none exists.
  • What it does not show - That DSS sent David's concerns to HHS-OIG or the Medicaid Fraud Control Unit. The August 26, 2025 email is advice to David. A separate referral that was never produced is not ruled out. What DSS found when it looked into the circumstances. This email gives no outcome. That HHS-OIG reviewed, forwarded or decided David's fraud allegations. Both letters say only that OIG "may" refer or forward them. A ruling on the facts of the reprisal claims. The 2025 letter's stated basis is standing and jurisdiction. The 2026 letter's is that the complaint was filed in another forum. Which other forum the 2026 letter meant. It does not say. That any of the 15 automatic receipts belongs to I203262 or I248830. Several are dated March 20, 2025, the same day as I203262, but a matching date does not join them. That OIG accepted any attachment, assigned an investigator, or opened an investigation from any receipt. "Successfully submitted" shows only that the form went through. That the MuckRock numbers are OIG case or FOIA numbers. That these are the only HHS-OIG matters. The reviewed records run through November 12, 2026. They do not cover David's November 15, 2026 filings, paper mail, or OIG's own systems. That the APA peer review looked at David's complaint, or cleared any provider. The report describes a review of audit work papers. No record reviewed connects it to the Auditors' March 21, 2025 whistleblower receipt. The exact day the peer review ended. The report says only "August of 2025." That David's allegations are true. They remain his allegations.
  • Counter-evidence and other side - DSS did answer in writing, about two weeks after David's August 13 email. It said it was looking into the matter and named two places to report: HHS-OIG and the State Auditors. HHS-OIG answered both reprisal complaints in writing, about two weeks (I203262) and eight days (I248830) after receipt or submission, and gave a checked reason each time. The 2025 letter explains its legal reason: no contract between ABI Resources and CMS, so no jurisdiction under 41 U.S.C. § 4712. The 2026 letter says fraud allegations are handled separately from reprisal. The APA report says the overall peer review gave the office a rating of "pass," its highest rating, and that the office began to make the documentation improvements.
  • Connected records - November 2022: David's HHS-OIG complaint text and the agency records that followed; March 20, 2025: the Attorney General's office wrote that it forwarded David's CCCI complaint for review; June 5-15, 2023: DOJ Civil Rights Division reports 301882-TRG (complaint text; referred to HHS June 8) and 301896-XPT (separate no-further-action reply, June 15); November 2026: CMS's Northeast fraud contractor says its review closed in May 2026; What each agency actually decided; Records requested and still missing; Proof and gaps; Proposed safeguards: every fraud report gets a traceable answer

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 9, 2026: Background). A link is navigation only.

February 21, 2025: HHS says it referred the records request to OIG and CMS for searches

HHS's Office of the Secretary (OS) closed its own FOIA file, 2025-00638-FOIA-OS, because its serviced components did not routinely collect or retain the requested records. Its February 21, 2025 letter states that the request was also referred to HHS-OIG and CMS to conduct searches. It says those offices would log the request and issue new tracking numbers upon receipt. OS states that it received the request on November 18, 2024; the letter does not give OIG's or CMS's receipt date.

The November 21, 2024 renumbering message separately connects former 2025-00575-FOIA-PHS to 2025-00638-FOIA-OS. MuckRock 176223 is the platform request number. The former PHS number is not printed in the February letter.

This is the originating office's statement of FOIA search routing. It does not establish a receiving OIG or CMS control, accepted attachment inventory, fraud-investigation transfer or merits decision. No reviewed record joins this request to either reprisal complaint below.

Decentralized processing could produce different component controls or correspondence delivered only through the request platform. An unmatched control is not proof that a request or investigation did not exist.

Still missing and who holds it: The deciding records are OS's outward referral envelope and manifest, matched to each component's incoming control and accepted-file inventory; any separate investigative transfer needs its own record.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, February 21, 2025: Decision · Referral). A link is navigation only.

April 3, 2025: I203262: Standing is the checked closure reason

The HHS-OIG letter says it received the reprisal complaint on March 20, 2025. Its only checked reason is Standing. It reasons from Medicare provider agreements that ABI Resources has no contract with CMS, so OIG has no jurisdiction under 41 U.S.C. § 4712. This is the agency's stated reason, not an independent legal ruling by this archive. It says non-reprisal allegations may be referred; it does not document an actual onward transfer.

This is a reprisal closure, not a determination that the underlying fraud allegations were false. The letter email arrived April 3 at 10:17 AM Eastern; that is not the complaint-receipt time. Accepted complaint files and any separate fraud handling remain UNKNOWN.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 3, 2025: Decision). A link is navigation only.

April 9, 2026: I248830: Complaint Filed in Another Forum is the checked closure reason

The HHS-OIG letter identifies a reprisal complaint submitted April 1, 2026. Its only checked reason is Complaint Filed in Another Forum. It does not name that forum. The Standing and OSC Referral boxes are not checked. It says underlying fraud, waste or abuse allegations are handled separately and may be forwarded if warranted. It does not document an actual onward transfer.

The selected forum, its case number, the accepted April 1 submission and exhibits, and separate fraud handling remain UNKNOWN. The letter email arrived April 9 at 12:50 PM Eastern; that is not the original submission or agency-receipt time. This is not a fraud-merits clearance.

Why the connection matters: The chain shows which office stated it routed a records search, which office closed each reprisal matter and which receiving records still decide the fraud-handling question. It avoids treating a FOIA control, platform number, reprisal complaint or generic Hotline receipt as the same case.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 9, 2026: Decision). A link is navigation only.

November 5, 2026: A rejected reprisal-records request and a separate Hotline/CMS report

David asked the HHS-OIG reprisal office for his accepted April 1 submission, the identity of the other forum, and the separate fraud-routing record. A mail-system rejection matched to that outgoing message reported a permitted-sender restriction at the intended mailbox. A delivery notice concerned David's own copy; the relay notice did not confirm destination delivery. This failure does not establish the fate of a separate report sent that morning to the HHS-OIG Hotline and CMS Medicaid Integrity.

In the source audit completed November 13, 2026, recipient acceptance and the accepted attachment inventory for the separate fraud report remained unproved. That historical audit does not establish the absence of a later reply or government action. This is a recipient-specific transport failure, not a decision on the allegations.

An ordinary mailbox security restriction could explain the rejection. The records do not establish intent, concealment or refusal to investigate.

The receiving office's message-matched intake/control and accepted-file inventory remain the deciding records. HHS-OIG and CMS hold those records.

Checked against retained sender records, original message-reference headers and the matching rejection body. Original headers and attachment details remain private. The source review establishes this historical transport relationship, not agency intake or the truth of the allegations.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, November 5, 2026: Report sent). A link is navigation only.

October 30, 2025: CMS says Connecticut met its HCBS settings corrective action plan, including both ABI waivers

On October 30, 2025, CMS wrote to William Halsey at the Connecticut Department of Social Services (DSS). The letter is about Connecticut's corrective action plan (CAP) "to address compliance with the home and community-based services (HCBS) regulations" at 42 CFR 441.301(c)(4)-(5). Those are the federal HCBS settings rules.

The letter lists ten Connecticut programs. Two are Acquired Brain Injury Waiver I (CT.0302) and Acquired Brain Injury Waiver II (CT.1085).

CMS wrote that it "has determined that Connecticut meets all requirements related to the development and implementation of the CAP." The letter was signed by George P. Failla, Jr., Director of CMS's Division of HCBS Operations and Oversight. It is a CMS decision, not just a State promise. CMS also wrote that it will keep giving technical assistance on the federal waiver assurances.

Limits. The letter is about the settings plan only. It does not decide David's complaints about individual provider choice, payment or retaliation. It is not about the separate October 2019 CMS program-integrity review listed under Official findings. It does not show the evidence CMS reviewed, any sample, or later monitoring.

What is still missing: the State's CAP file and the evidence CMS relied on for this determination. Those records were not found in this archive.

  • Exact words - “The Centers for Medicare & Medicaid Services (CMS) has determined that Connecticut meets all requirements related to the development and implementation of the CAP.” — George P. Failla, Jr., Director, Division of HCBS Operations and Oversight, Medicaid and CHIP Operations Group, Centers for Medicare & Medicaid Services (letter to William Halsey, Connecticut Department of Social Services), October 30, 2025. Official source
  • Exact words - “to address compliance with the home and community-based services (HCBS) regulations” — George P. Failla, Jr., Director, Division of HCBS Operations and Oversight, Medicaid and CHIP Operations Group, Centers for Medicare & Medicaid Services (letter to William Halsey, Connecticut Department of Social Services), October 30, 2025. Official source
  • Exact words - “Acquired Brain Injury Waiver I, CT.0302” — George P. Failla, Jr., Director, Division of HCBS Operations and Oversight, Medicaid and CHIP Operations Group, Centers for Medicare & Medicaid Services (letter to William Halsey, Connecticut Department of Social Services) (one of ten programs listed), October 30, 2025. Official source
  • Exact words - “Acquired Brain Injury Waiver II, CT.1085” — George P. Failla, Jr., Director, Division of HCBS Operations and Oversight, Medicaid and CHIP Operations Group, Centers for Medicare & Medicaid Services (letter to William Halsey, Connecticut Department of Social Services) (one of ten programs listed), October 30, 2025. Official source
  • Exact words - “CMS will continue to provide technical assistance as needed to your state regarding the required federal waiver assurances.” — George P. Failla, Jr., Director, Division of HCBS Operations and Oversight, Medicaid and CHIP Operations Group, Centers for Medicare & Medicaid Services (letter to William Halsey, Connecticut Department of Social Services), October 30, 2025. Official source
  • Record numbers - Waiver numbers named in the letter: ABI Waiver I CT.0302 and ABI Waiver II CT.1085 (plus CT.0140, CT.0301, CT.0437, CT.0881, CT.0426, CT.0993, CT.6053 and 1915(i) CT 22-0001); Regulation cited: 42 CFR 441.301(c)(4)-(5) (HCBS settings); The letter prints no CMS case or tracking number
  • What it does not show - Any decision on David's individual complaints about provider choice, payment or retaliation. Anything about the separate October 2019 CMS program-integrity review or its findings. This letter does not mention it. What evidence, sites or sample CMS reviewed, or what the State's CAP said. Neither is attached. How the settings rules were applied to any one provider or participant, or any monitoring after October 30, 2025. That any provider, including ABI Resources, was reviewed. No provider is named. When DSS received the letter. Only its printed date is known. That David's allegations are true or false. They remain his allegations.
  • Counter-evidence and other side - This is a favorable federal decision. CMS wrote that Connecticut met all development and implementation requirements of the settings CAP, and it named both ABI waivers. Any account saying CMS accepted no State correction would leave this out. The ordinary reading of the letter is that CMS accepted the State's settings correction within the plan's scope. Unresolved individual complaints do not, by themselves, contradict it. CMS said it will keep giving technical assistance on the federal waiver assurances.
  • Connected records - Official findings already public (includes CMS's separate October 2019 program-integrity review); What CMS did with the warnings; DSS's written provider-choice policy; What each agency actually decided; Proof and gaps; Proposed safeguards
  • Separate CMS records answer - May 13, 2026: CMS found no responsive records for the SWCAA request (control 022720267103)

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, October 30, 2025: Background). A link is navigation only.

March 9, 2020: Connecticut Medicaid approves ABI Resources' re-enrollment, a separate step from the 2019 new-client restriction

A Connecticut Medical Assistance Program letter dated March 9, 2020 says ABI Resources' "application for re-enrollment in the Connecticut Medical Assistance Program has been approved." It lists program participation for ABI effective February 24, 2020. It says the Provider Enrollment Agreement runs from March 9, 2020 to March 9, 2022, "unless terminated by either DSS or the Provider" before then.

Before this: on October 10, 2019, DSS suspended ABI Resources from the ABI Waiver/MFP provider registry for new clients, "for a minimum period of three months." Existing clients could keep their services. DSS wrote it would review the status after three months. David disputed DSS's reasons in writing.

On February 28, 2020, Allied Community Resources, the State's ABI waiver credentialing contractor, wrote that ABI met all required qualifications for re-credentialing. Allied called its letter the follow-on documentation needed to finish re-enrollment. The March 9 Medicaid approval is the later, separate written decision on that re-enrollment.

Enrollment approval is a separate process from the referral restriction. This letter does not mention the 2019 restriction. It does not show whether DSS did its promised review, or when the restriction ended.

In June 2020, David wrote to DSS that ABI was again not listed for referrals in the Allied provider directory. DSS answered that ABI "continues to be listed." That exchange is about the directory people saw, not enrollment. Which directory version families and care managers saw is still not known.

About the copy: the retained PDF's internal creation date is May 5, 2021. It also names Gainwell Technologies, the company name DSS's contractor took on October 1, 2020. So this copy appears to be a later printout of the March 9, 2020 letter. It does not show when the letter was first sent or received.

  • Exact words - “your application for re-enrollment in the Connecticut Medical Assistance Program has been approved:” — Connecticut Medical Assistance Program, Provider Assistance Center (approval letter to ABI Resources LLC), March 9, 2020.
  • Exact words - “Program Participation/Effective Date: ABI 02/24/2020” — Connecticut Medical Assistance Program, Provider Assistance Center (approval letter to ABI Resources LLC) (field label and value; the provider ID fields printed beside it are left out), March 9, 2020.
  • Exact words - “the effective date of your Provider Enrollment Agreement is 03/09/2020, and the Provider Enrollment Agreement shall thereafter be in effect until 03/09/2022, unless terminated by either DSS or the Provider prior to the stated ending date.” — Connecticut Medical Assistance Program, Provider Assistance Center (approval letter to ABI Resources LLC), March 9, 2020.
  • Record numbers - Retained approval letter Bates ABI_008480 (SHA-256 9415ed0f2ab7cd5fcfc86019e0963e2b944812dfb2b5072640881e941cb25743); Dates printed: letter March 9, 2020; ABI participation effective February 24, 2020; agreement March 9, 2020 to March 9, 2022 (re-enrollment due date March 9, 2022); The letter's provider ID numbers are left out
  • What it does not show - When the October 2019 new-client restriction ended, or whether DSS did the review it promised after three months. The approval letter does not mention the restriction. That ABI could take new clients from March 2020 on. Enrollment and referral-registry access are different things. Which directory version care managers and families received, or what provider choices they were offered. That ABI stayed enrolled without a break after March 2020. The agreement allowed earlier termination by either side. When the letter was first sent or received. The retained copy appears to be a 2021 printout. Any service authorization, claim, or payment. That anyone acted wrongly. These are separate records from separate processes. That David's allegations are true. They remain his allegations.
  • Counter-evidence and other side - This is a favorable State decision: Connecticut Medicaid approved ABI's re-enrollment within months of the October 2019 restriction. The restriction did not end ABI's Medicaid enrollment. The 2019 letter limited new clients only. It let ABI keep serving existing clients. In June 2020, DSS wrote that ABI "continues to be listed" in the directory, and a retained Allied directory printed June 2, 2020 lists ABI under Approved Providers. The ordinary explanation for the different dates is that credentialing, Medicaid enrollment and the referral directory are run as separate processes.
  • Connected records - October 10-31, 2019: DSS suspends ABI Resources from new ABI waiver / MFP clients; October 10, 2019: the DSS suspension letter (privacy-cleaned copy); February 28, 2020: Allied's re-credentialing letter; June 1-2, 2020: provider directory emails with DSS; June 1-2, 2020: the directory emails (privacy-cleaned copy); Records requested and still missing; Proof and gaps; Due process: notice, decisions and review; DSS records reply, November 10, 2026

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, March 9, 2020: Background). A link is navigation only.

April 2023: DOJ Civil Rights Division report 275528-PKR: David's referral-access complaint and DOJ's answer

All 46 of David’s reports in DOJ’s own released records, every one marked CLOSED: DOJ Civil Rights Division records table.

On April 4, 2023, David filed an online report with the U.S. Department of Justice (DOJ) Civil Rights Division. DOJ logged it as report 275528-PKR. The form names Connecticut Community Care Inc. (CCCI) and lists disability as the reason he believed people were treated this way.

In his description, David wrote that "covert referral practices by Connecticut contracted care management agencies may be restricting full access to available services for disabled Medicaid consumers" in Money Follows the Person (MFP) and the ABI Waiver. He asked for "advocacy support in investigating this matter." These are his concerns. They are not findings.

The same day, DOJ sent an automatic acknowledgment with the record number. Its standard text says the Division reads every report, and adds: "We do not have the resources to follow-up on every letter."

On April 12, 2023, DOJ answered. The email subject names the Disability Rights Section. It said DOJ had "decided not to take any further action on your complaint." It gave the reason: "We unfortunately do not have the resources to take direct action for every report." It then said: "We are not determining that your report lacks merit."

The response cited resource limits and expressly said it was not determining that the report lacked merit. It did not find the report true. DOJ said the issue "may still be actionable by others" and named the state bar and legal aid.

These pages come from DOJ's own FOIA production 24-00146-P (September 4, 2024), physical pages 285 to 291. The later June 2023 reports 301882-TRG and 301896-XPT have different numbers. Their order in time does not show they share the same packet.

What is still missing: what DOJ's reviewers looked at, any attachments DOJ accepted, and any internal notes on the review.

  • Exact words - “there are concerns that covert referral practices by Connecticut contracted care management agencies may be restricting full access to available services for disabled Medicaid consumers enrolled in programs such as the MFP Money Follows the Person Program and the ABI Waiver Program.” — David Medeiros, ABI Resources (his report description; his allegation), April 4, 2023.
  • Exact words - “we respectfully request your advocacy support in investigating this matter” — David Medeiros, ABI Resources (his report description; his allegation), April 4, 2023.
  • Exact words - “Please save your record number for tracking.” — U.S. Department of Justice, Civil Rights Division (automatic acknowledgment email, TMS ID 921359854), April 4, 2023.
  • Exact words - “We do not have the resources to follow-up on every letter.” — U.S. Department of Justice, Civil Rights Division (automatic acknowledgment email, TMS ID 921359854), April 4, 2023.
  • Exact words - “After careful review of what you submitted, we have decided not to take any further action on your complaint.” — U.S. Department of Justice, Civil Rights Division (response email, subject "Response: Your Civil Rights Division Report - 275528-PKR from the Disability Rights Section"; signed by the Division, no person named), April 12, 2023.
  • Exact words - “We unfortunately do not have the resources to take direct action for every report.” — U.S. Department of Justice, Civil Rights Division (response email, subject "Response: Your Civil Rights Division Report - 275528-PKR from the Disability Rights Section"; signed by the Division, no person named), April 12, 2023.
  • Exact words - “We are not determining that your report lacks merit.” — U.S. Department of Justice, Civil Rights Division (response email, subject "Response: Your Civil Rights Division Report - 275528-PKR from the Disability Rights Section"; signed by the Division, no person named), April 12, 2023.
  • Exact words - “Your issue may still be actionable by others” — U.S. Department of Justice, Civil Rights Division (response email, subject "Response: Your Civil Rights Division Report - 275528-PKR from the Disability Rights Section"; signed by the Division, no person named), April 12, 2023.
  • Record numbers - DOJ Civil Rights Division report 275528-PKR (received April 4, 2023; response April 12, 2023; shown as CLOSED in DOJ's record); DOJ email TMS IDs 921359854 (acknowledgment, April 4, 2023) and 924067941 (response, April 12, 2023); DOJ FOIA/Privacy Act production 24-00146-P (September 4, 2024); DOJ's record for 275528-PKR prints "RECEIVED: 10:35 a.m. April 4, 2023" and "LAST UPDATED: 4:02 p.m. April 12, 2023" (time zone not stated) and the status CLOSED; it gives no separate closing date; Source pages: DOJ FOIA production 24-00146-P (291 pages, SHA-256 3874b31abad00616ed784e66daca0935a9386e63d5681f73a882f77b3c7e4f9c), physical pages 285-291
  • What it does not show - That DOJ found the report had no merit. The response expressly disclaims that determination: "We are not determining that your report lacks merit." That David's concerns are true. They remain his concerns. What DOJ's reviewers read, or which attachments, if any, DOJ accepted. The report links to a web page; DOJ's record does not list attachments. Any internal DOJ notes, or the individual reviewers' reasons beyond the printed reply. That DOJ sent the report to another agency. The response names no agency. (The June 2023 report 301882-TRG is a separate matter with its own HHS referral notice.) Any finding about CCCI or anyone else.
  • Counter-evidence and other side - DOJ did answer in writing, eight days after the report, and said team members reviewed it. DOJ explained its reason: it receives "several thousand reports" a year and cannot act on every one. DOJ pointed David to other help: the state bar association and local legal aid offices. DOJ wrote that reports like his "can help us find issues affecting multiple people or communities."
  • Connected records - April 4, 2023 in the Early Warning Record; Evidence record EV-000142: DOJ's acknowledgment of report 275528-PKR; June 5-15, 2023: DOJ reports 301882-TRG (complaint text and June 8 HHS referral notice) and 301896-XPT (separate no-further-action reply, June 15); April 14, 2021: earlier report on CCCI to DSS; March 20, 2025: the Attorney General's office wrote that it forwarded David's CCCI complaint for review; What each agency actually decided; Proof and gaps; The right to petition; Separate November 2022 complaint narrative and agency records; Separate April 19, 2023 billing statement and DSS response; Separate November 2026 CMS contractor review and closure chronology

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, April 12, 2023: Background). A link is navigation only.

DSS contract 23DSS2201BZ: BIAC's separate $300,000 Treasury-funded contract for outreach, Spanish access, recorded training and workshops

Separate from its long-running DSS contract, the Brain Injury Alliance of Connecticut (BIAC) signed a second DSS contract, 23DSS2201BZ, for up to $300,000. Page 3 says it is supported by federal award SLFRP0128 from the U.S. Department of the Treasury (American Rescue Plan Act recovery funds). The term was January 1, 2023 through December 31, 2024. Amendment 1 extended it to June 30, 2025 with no new money.

Spanish access. BIAC must produce outreach materials in Spanish by December 31, 2023, conduct Spanish outreach during 2024, and give at least one in-person and two virtual or hybrid trainings or workshops in Spanish in 2024 (pages 4-5).

Recorded training. BIAC must host a live or hybrid professional conference in March 2023 and March 2024 and record workshops. Page 5 says the training "shall be available for viewing both live and recorded" and "Recordings shall be available for future use."

Workshops. BIAC must host free workshops for survivors and caregivers: at least three quarterly remote workshops and one in-person half-day seminar each year, and at least two workshops in Spanish (page 5). The contract also funds a statewide awareness campaign, a website rebuild, staff time, retention bonuses and equipment.

Money and reporting. The approved budget (page 12) adds to $300,000, including $140,000 for the campaign, $10,000 for Spanish outreach, $18,500 for the conference and recordings and $7,000 for survivor workshops. BIAC must keep accounts showing receipts by source, spending and balances (page 7), send quarterly Budget vs. Actual reports within 30 days of each quarter and a final fiscal report within 45 days of the contract's end (page 11), and return unspent advances within 30 days (page 12).

These are signed duties. They do not show what BIAC delivered, what it spent, or what DSS reviewed. Those records are still needed. Nothing here shows misuse of funds.

  • Exact words - “This Contract is supported in whole or in part, by federal award number SLFRP0128 awarded to the State of Connecticut by the U.S. Department of the Treasury.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section A (Overview), January 1, 2023. Official source
  • Exact words - “Produce outreach materials in Spanish by December 31, 2023.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.2, January 1, 2023. Official source
  • Exact words - “Conduct outreach activities in Spanish between January 1, 2024 and December 31, 2024.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.3, January 1, 2023. Official source
  • Exact words - “Provide a minimum of one (1) in-person and two (2) (virtual/hybrid) trainings/workshops in Spanish (January 2024 through December 2024)” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.3.a.iv, January 1, 2023. Official source
  • Exact words - “Host a live or hybrid conference in March 2023 and March 2024 and record workshops for future use;” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.5.a, January 1, 2023. Official source
  • Exact words - “The training shall be available for viewing both live and recorded. Recordings shall be available for future use.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.5.b, January 1, 2023. Official source
  • Exact words - “Provide at least three (3) quarterly remote workshops and one (1) in person half day seminar annually.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.6.b, January 1, 2023. Official source
  • Exact words - “Offer at least 2 workshops in Spanish.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section C.6.d (the clause continues "SFY 2023 and SFY 2024."), January 1, 2023. Official source
  • Exact words - “Controls must be adequate to ensure that expenditures charged to grant activities are made for allowable purposes only.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section H.D (Fiscal Control), January 1, 2023. Official source
  • Exact words - “The final fiscal report is due within 45 days following the end of the entire contract period.” — Contract 23DSS2201BZ (DSS and BIAC), Part I, Section I.1 (Financial Reporting), January 1, 2023. Official source
  • Exact words - “Contract Term as Amended: 1/1/2023 to 6/30/2025” — Contract 23DSS2201BZ, Amendment 1, page 1 (a no-cost extension; the maximum stays $300,000), August 5, 2024. Official source
  • Record numbers - DSS contract 23DSS2201BZ (BIAC), original and Amendment 1; U.S. Treasury award SLFRP0128 (Coronavirus State and Local Fiscal Recovery Funds); Public Act 22-146, section 1; Separate DSS contract 19DSS2201BZ (BIAC)
  • What it does not show - That BIAC held the Spanish trainings, conferences or workshops, or made recordings available. Those are duties, not results. How the $300,000 was spent. The budget lines are authorizations, not payments. What quarterly or final reports BIAC sent, or what DSS's reviews found. None were in the reviewed records. Misuse of funds, a breach, or money owed back. Nothing reviewed shows any of these. That the outcome targets (for example, 10% more helpline contacts) were met. They are goals. Whether the two Spanish workshop duties (Section C.3 and Section C.6) are separate events or can overlap. The contract does not say. Anything about recording at Providers' Council meetings. The recording duty here covers this contract's professional conference training. The Council is a duty under the separate contract 19DSS2201BZ.
  • Counter-evidence and other side - Amendment 1 calls the service description Part I, Section B, but in the original contract that heading is Section C. The extension still covers the original services; the mislabel is noted as printed. Amendment 1 moved only the end date. It does not expressly reschedule the dated 2023-2024 activities. CHRO's findings and the contrary reasoning in the 2024 recording and accommodation dispute are already live at /warnings-and-answers/#decisions. This contract does not change them.
  • Connected records - BIAC's main DSS contract 19DSS2201BZ: directory, Providers' Council and funding accounts; What each agency decided, including CHRO's findings; Records requested and still missing; Proof and gaps: records still missing; Investigator Hub

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, January 1, 2023: Background). A link is navigation only.

Six Paycor payroll-tax withdrawals ($49,829.11) and the six held Paycor tax-activity reports: what matches and what is unverified

ABI Resources used Paycor, a payroll company. A November 16, 2026 review selected six withdrawals from ABI's bank account, made between November 2023 and April 2026. Together they total $49,829.11.

Each withdrawal date has a matching entry in a Paycor quarterly "Tax File Client Activity Report," in the table Paycor labels "Impounds." All six reports are held. No report for these dates is missing.

For four withdrawals, the bank amount equals the report's total for that date. For the other two, the withdrawal is one part of a larger total on the report for that date; other entries on the same date make up the difference.

The six bank withdrawals themselves are documented. What is still unverified: how Paycor allocated each withdrawal to the tax payments (the allocation-to-bank-debit match, including any return or reissue), and whether a tax agency posted the money to the right account and tax period. A matching date and amount does not prove either.

This comparison does not establish additional loss, final tax nonpayment or theft; those outcomes remain unresolved. It is kept separate from the Medicaid claims and other money disputes on this site.

  • Record numbers - Paycor Tax File Client Activity Reports for Q4 2023, Q1 2024, Q4 2024, Q1 2025, Q3 2025 and Q2 2026 (held privately; not published)
  • What it does not show - That the selected Paycor funding entries were executed together as the corresponding bank debit, or what their final return, reversal, reissue and tax-application status was. That a tax agency received or applied the money to the correct account and period. The report's quarter is not proof of the tax period the money was applied to. Any loss, nonpayment, theft or wrongdoing by Paycor or anyone else. All of ABI's Paycor withdrawals. These six were selected for review. A payroll register. The reports reviewed are tax-activity summaries, not payroll registers.
  • Counter-evidence and other side - The held reports account for all six amounts: four match exactly and two are explained by other entries on the same date. On amounts, the reports support Paycor's records. A separate bank export record agrees with one of the six withdrawals (March 2025).
  • Connected records - What happened to David and ABI, and what the money records show; Proposed safeguard: independent checks of payments; Proof and gaps: records still missing; Investigator Hub

Independent public-records archive. Verify independently. A filing is not a finding.

August and September 2025: the U.S. Justice Department's Inspector General writes that it forwarded David's correspondence to the FBI Inspection Division

The U.S. Department of Justice Office of the Inspector General (DOJ-OIG) sent David two one-page letters, dated August 26, 2025 and September 25, 2025. They answer his correspondence dated August 22 and September 19, 2025. Each says OIG reviewed his complaint, found the matters "more appropriate for review by another office within the DOJ," and "forwarded your correspondence to" the FBI Inspection Division. That is DOJ-OIG's statement of what it did. Neither letter shows that the FBI received the material, gave it a number, or did anything with it. Two letters are two routing notices, not two FBI investigations.

  • Exact words - “Thank you for your correspondence dated August 22, 2025.” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), August 26, 2025.
  • Exact words - “After reviewing your complaint, we have determined the matters that you raised are more appropriate for review by another office within the DOJ.” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), August 26, 2025.
  • Exact words - “Therefore, we have forwarded your correspondence to: Federal Bureau of Investigation Inspection Division” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), August 26, 2025.
  • Exact words - “Thank you for your correspondence dated September 19, 2025.” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), September 25, 2025.
  • Exact words - “After reviewing your complaint, we have determined the matters that you raised are more appropriate for review by another office within the DOJ.” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), September 25, 2025.
  • Exact words - “Therefore, we have forwarded your correspondence to: Federal Bureau of Investigation Inspection Division” — Office of the Inspector General, Investigations Division, U.S. Department of Justice (DOJ-OIG; letter signed by the office, no person named), September 25, 2025.
  • Record numbers - DOJ-OIG letters of August 26, 2025 and September 25, 2025 (no case or control number printed)
  • What it does not show - That the FBI Inspection Division received either forwarded package. The letters say only that DOJ-OIG forwarded the correspondence; they do not show FBI receipt, an FBI control number or any FBI action. What DOJ-OIG actually sent. The two reviewed letters contain no outgoing transmittal record or attachment inventory. This is not a search of every agency file; the deciding records would be DOJ-OIG's outgoing transmittal joined to FBI Inspection Division intake records. The subject of David's August 22 and September 19 correspondence. The letters identify correspondence dates but do not describe its subject or list its attachments. This review has not independently matched the complete August 22 and September 19 submissions to these responses. Any link to David's IC3 reports comes from his later November 15, 2026 request, not from these letters. Any FBI review, investigation or finding. That these DOJ-OIG letters concern HHS-OIG complaints I203262 or I248830. They are a different office's answers to different correspondence.
  • Counter-evidence and other side - DOJ-OIG answered both times in writing, within four to six days of David's correspondence, and named where it sent it.
  • Connected records - November 15, 2026: David's later requests for review, and what is still unanswered; HHS-OIG and DSS replies (a different inspector general); Who knew what before each decision; Proof and gaps: records still missing

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, August 26, 2025: Background). A link is navigation only.

September 25, 2025: HHS Office for Civil Rights folds David's July 2025 complaint into a 2023 complaint it had closed in May 2024

All 13 of David’s HHS Office for Civil Rights complaint numbers and what OCR did with each: HHS OCR complaints table.

The U.S. Department of Health and Human Services, Office for Civil Rights (HHS-OCR) received David's complaint about the Connecticut Department of Social Services on July 31, 2025 (CU-25-633230). On September 25, 2025, a letter signed by Maqueda M. Fuller, Supervisor, Centralized Case Management Operations, says OCR decided to consolidate it into OCR Transaction Number 24-556944 and closed CU-25-633230 the same day.

The earlier matter, 01-24-556944, began with a complaint OCR received December 18, 2023. OCR's letter emailed to David on May 29, 2024 (signed by Susan M. Pezzullo Rhodes, Regional Manager) says OCR "cannot accept your complaint" because no claim of prohibited discrimination was established, and closes that case. So the 2025 complaint was folded into a matter that OCR's own letter had already closed. The letters do not say whether 24-556944 was reopened or what happens to the newer allegations. David asked OCR to confirm on September 25 and October 27, 2025; no email copy of an OCR answer was found.

October 27, 2025 — After OCR's September 25, 2025 consolidation letter, David asked OCR for the consolidation record, a list of any issues not carried over, the assigned investigator, the case status and next steps, and an accessible copy of the letter. His request does not show that the older matter was reopened or that the newer allegations received a decision on the merits.

  • Exact words - “Upon review of your allegations, OCR has decided to consolidate this complaint into OCR Transaction Number 24-556944, which you previously filed with this office.” — Maqueda M. Fuller, Supervisor, Centralized Case Management Operations (CCMO), HHS Office for Civil Rights, September 25, 2025.
  • Exact words - “Accordingly, we are closing the subject transaction, CU-25-633230, effective the date of this letter.” — Maqueda M. Fuller, Supervisor, Centralized Case Management Operations (CCMO), HHS Office for Civil Rights, September 25, 2025.
  • Exact words - “As such, we regret to inform you that the Office for Civil Rights cannot accept your complaint. Therefore, OCR is closing this matter.” — Susan M. Pezzullo Rhodes, Regional Manager, HHS Office for Civil Rights, New England Region, May 29, 2024.
  • Record numbers - CU-25-633230 (also written 25-633230; received July 31, 2025; closed September 25, 2025); 01-24-556944 (also written 24-556944; complaint received December 18, 2023; closed by the letter emailed May 29, 2024)
  • What it does not show - That OCR reopened 24-556944, or what OCR did with the July 2025 allegations after the consolidation. Any finding on the merits. The 2024 letter says OCR could not accept the complaint; the 2025 letter applies "only to the allegations in this complaint that OCR reviewed." Any OCR answer to David's September 25 and October 27, 2025 requests to confirm the consolidation and status (no email copy found).
  • Counter-evidence and other side - OCR answered in writing both times and named the person who signed. The 2025 letter came 56 days after OCR received the complaint.
  • Connected records - Selected letter excerpts: OCR letter of September 25, 2025 (CU-25-633230) · OCR determination for 01-24-556944 (no printed date; emailed May 29, 2024); January 2024: OCR closes 01-24-551819 without investigating, then folds 01-24-554014 into 01-23-551819 (earlier same pattern); All agency control numbers in one table; HHS-OIG and DSS replies (a different HHS office); Proof and gaps: records still missing

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, September 25, 2025: Background). A link is navigation only.

HHS civil rights office, January 2024: one complaint closed without investigation, a second folded into it four days later

In January 2024 the HHS Office for Civil Rights (OCR), New England Region, closed two of David's disability-discrimination complaints about Connecticut's Medicaid Acquired Brain Injury (ABI) program within four days. On January 5 it said it would not investigate complaint 01-24-551819. On January 9 it closed complaint 01-24-554014 "without further investigation" and said it had been folded into "another open complaint" numbered 01-23-551819.

January 5, 2024: OCR's letter for complaint 01-24-551819, signed by Regional Manager Susan M. Pezzullo Rhodes: "We have reviewed your complaint and have determined that OCR will not investigate your allegations. Therefore, OCR is closing this complaint with no further action, effective the date of this letter." The letter gives no reason.

January 5, 2024: The same day, David asked OCR how to appeal and sent a request to reopen the complaint. OCR's investigator pointed him to OCR's Centralized Case Management Operations. No OCR answer to the reopening request was found in David's mailbox.

January 9, 2024: OCR's letter for complaint 01-24-554014 (received November 16, 2023; it alleged disability discrimination and unfair business practices in the Connecticut Medicaid ABI program), also signed by Susan M. Pezzullo Rhodes: "In the interest of maximizing our administrative efficiency, OCR has consolidated your complaint into another open complaint you filed where OCR is reviewing similar allegations. Effective the date of this letter, OCR Transaction Number 01-24-554014 will be closed and incorporated into OCR Transaction Number 01-23-551819. Based on the foregoing, OCR is closing this case without further investigation."

What it shows: Four days after OCR wrote that it would not investigate complaint 01-24-551819 and closed it, OCR folded David's next complaint into "another open complaint" numbered 01-23-551819, a complaint it said it was "reviewing".

The same pattern appears again in September 2025, when OCR folded complaint CU 25 633230 into complaint 24 556944, whose closure letter was emailed May 29, 2024 (see the card on that consolidation).

A complaint is not a finding. These letters show what OCR did with the complaints, not whether the allegations are true.

January 9, 2024 — David asked OCR for copies of complaints 01-24-554014 and 01-23-551819, saying copies would help accommodate his comprehension. This is a request for accessible participation. It is not an agency reopening or finding.

  • Record numbers - 01-24-551819 (OCR letter of January 5, 2024: will not investigate; closed); 01-24-554014 (received November 16, 2023; closed January 9, 2024 and incorporated into 01-23-551819); 01-23-551819 (the "another open complaint" named in the January 9, 2024 letter)
  • What it does not show - Whether 01-23-551819 and 01-24-551819 are the same complaint. The two numbers differ only in the middle part, and neither letter explains the difference. HHS OCR holds the answer. Any OCR review or investigation of the allegations folded into 01-23-551819 after January 9, 2024. Why OCR decided not to investigate. The January 5 letter gives no reason.
  • Counter-evidence and other side - OCR answered both complaints in writing, and a named Regional Manager signed both letters. The January 9 letter says OCR was "reviewing similar allegations" in 01-23-551819.
  • Connected records - September 2025: OCR folds CU 25 633230 into 24 556944 (same pattern); All agency control numbers in one table

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, January 9, 2024: Decision). A link is navigation only.

Two different offices called OSC

Federal OSC means the U.S. Office of Special Counsel (osc.gov), not Connecticut’s Office of the State Comptroller (osc.ct.gov). In its saved October 21, 2024 response, the Comptroller’s office wrote: “Our office has no responsive records”. That answer covers only that office and that request. Federal OSC separately released 383 pages under FOIA-2025-314, including David’s December 4, 2024 filing. Neither response determines the merits of his allegations. A jurisdiction closure, a FOIA search result and a suggestion to contact DSS are different actions; a suggestion is not proof of forwarding or receipt.

Federal OSC identity | CT Comptroller identity | CT response, MR174576 communication 3 | Federal filing and production sources | CT suggestion, communication 8

January 24, 2024: GAO FraudNet replies under COMP-24-000645

GAO FraudNet said the matter was outside its ongoing work and suggested following up with another federal entity to avoid duplicating efforts. That entity is unnamed. GAO would retain the information for possible future work. This is a procedural reply, not proof of a merits finding, audit, investigation or actual referral.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, January 24, 2024: Agency reply). A link is navigation only.

July 2023: what David reported to the FTC, and the separate 2024 records-search answer

On July 11, 2023, David retained a ReportFraud.ftc.gov confirmation for report 161825278. The site already publishes the FTC's automated receipt. The retained form also contains his actual complaint text.

David alleged that Connecticut DSS favored certain Medicaid ABI Waiver providers, reduced consumer choice and competition, and used federal funds inefficiently. He asked the FTC to investigate DSS's allocation and use of those funds. These were his allegations and request, not findings that the conduct occurred or violated a law.

The retained form and the automated acknowledgment share the exact report number. This connects the receipt to the retained complaint representation; it does not establish a complete accepted-attachment inventory or prove what an FTC reviewer examined.

In September 2024, David separately asked the FTC for records about the Connecticut Medicaid ABI Waiver Program. On September 20, under FOIA-2024-01740, the FTC said its search began September 11 and did not identify a responsive record. This was a records-search answer, not a determination about the truth or merit of the consumer complaints.

On September 3, 2024, David wrote to the FTC FOIA office that his first message "was deleted without being read." On September 4, 2024, R. Anthony Ellis, II, Team Lead Attorney, FTC Office of the General Counsel (FOIA), replied: "Your request was not deleted in our systems and has been assigned for processing." He asked David to tell the FOIA processor if he wanted expedited treatment and to give a justification. His reply does not print FOIA-2024-01740 and does not show which systems were searched, which exhibits were accepted or whether FTC reviewed the complaint's merits. The separate numbered acknowledgment and September 20 records-search answer remain distinct records.

The acknowledgment describes a September 3 request, while the final letter describes a September 2 request. Both descriptions are preserved. The available letter does not name the searched systems, custodians, search terms or date cutoff, or say whether ReportFraud or Consumer Sentinel was searched.

Read together, these records show a documented complaint and a later records-search result that still needs its search scope explained. A difference in systems, custodians or search scope is an ordinary possible explanation. The processing/search file would decide; these records do not establish concealment, deletion, an inadequate search or a referral.

Separate report controls 174716621 (July 5, 2024 acknowledgment) and 189501332 (July 7, 2025 acknowledgment) have retained receipts, but their submitted narrative texts are NOT IN FILE in the reviewed source set. The 2025 report postdates the 2024 records search.

The next deciding records are each report's accepted submission and exhibit inventory, the FOIA processing/search file, and any report-specific access, transfer, receiving-office acceptance and disposition records. Generic sharing or future database-availability wording is not proof of those acts.

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, September 20, 2024: Report sent · Agency reply). A link is navigation only.

December 4, 2024: David's 41-page filing with the U.S. Office of Special Counsel, as it appears in OSC's own FOIA release

The U.S. Office of Special Counsel (OSC, osc.gov; a federal office, not Connecticut's Office of the State Comptroller) released 383 pages to David under FOIA request FOIA-2025-314. Release part 2, pages 57 to 97, is OSC's printout of his online "Report Government Wrongdoing (Disclosure)" form: 41 form pages, each stamped "Date Received by OSC: 12/4/2024." The form says he is a non-federal employee. Form pages 39 and 40 (release pages 95 and 96) list the files he attached, under the line "I have attached the following documents to my filing." The list has 18 file names, including his September 24, 2024 federal whistleblower report, his November 28, 2024 "Federal Representation for Justice" report and several record ZIP files.

That list shows what David named when he filed. On its own it does not show which attached files OSC kept or produced. Some of David's own reports appear elsewhere in the release (a September 2024 whistleblower report and a "Federal Representation for Justice" report in parts 1 and 2); the release does not say whether those are the same files he attached on December 4. The portal reference for this filing is DI-12042024718. OSC's receipt email the same day said a case number and contact person would follow.

  • Exact words - “This Disclosure of Information was Received by OSC on: 12/4/2024” — OSC Online Filing Portal form printout (FOIA-2025-314 release, part 2, page 97; form page 41 of 41), December 4, 2024.
  • Exact words - “I have attached the following documents to my filing:” — OSC Online Filing Portal form printout (FOIA-2025-314 release, part 2, page 95; form page 39 of 41), December 4, 2024.
  • Exact words - “If a disclosure is filed by an anonymous source, the disclosure will be referred to the Office of Inspector General in the appropriate agency.” — OSC form instructions (FOIA-2025-314 release, part 2, page 57; form page 1 of 41), December 4, 2024.
  • Record numbers - OSC portal reference DI-12042024718 (December 4, 2024); FOIA-2025-314 (OSC FOIA request, July 15, 2025; final answer December 17, 2025)
  • What it does not show - That OSC kept, opened or produced each attached file. A list of file names on the form is not the files, and the release does not match its other documents to this list. Any OSC case number, case notes, handling log or referral for this filing. The anonymous-source sentence is standard form text; David's filing was not anonymous, and no referral record follows in the release. Which, if any, of OSC's December 9, 2024 closures (DI-25-000310, DI-25-000325, DI-25-000379) covers this filing.
  • Counter-evidence and other side - OSC did produce the full 41-page form, with the attachment list, in its FOIA release. The form itself tells filers to keep their own copies of supporting documents.
  • Connected records - OSC portal receipt for DI-12042024718; FOIA-2025-314 request and OSC replies; All U.S. Office of Special Counsel FOIA threads; All agency control numbers in one table

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, December 4, 2024: Background). A link is navigation only.

January 8, 2025: the FBI administratively closes David's records request about the OSC cases (NFP-168932) because it was "not searchable" as written

On December 23, 2024, through MuckRock (request 178286), David asked the FBI for records about U.S. Office of Special Counsel cases DI-25-000310, DI-25-000325 and DI-25-000379 and two OSC portal references, and about any FBI role. The FBI numbered it NFP-168932. Its January 8, 2025 letter, signed by Michael G. Seidel, Section Chief, Record/Information Dissemination Section, says the request "is not searchable in our indices" and "is being administratively closed."

In plain words: the FBI did not search and find nothing. It said its records system is indexed by investigation subjects and could not be searched the way the request was worded, and it pointed to its FOIA help address for rewording and to an appeal to DOJ's Office of Information Policy within 90 days. The thread later shows two "Please withdraw this request" posts (February 2 and 12, 2025) and David's February 15 notice that he did not authorize withdrawal. The letter has been public on this site; this card adds the explanation.

  • Exact words - “Your request for the above referenced subject is not searchable in our indices.” — Michael G. Seidel, Section Chief, Record/Information Dissemination Section, Information Management Division, FBI, January 8, 2025. Open the record
  • Exact words - “Therefore, your request is being administratively closed.” — Michael G. Seidel, Section Chief, Record/Information Dissemination Section, Information Management Division, FBI, January 8, 2025. Open the record
  • Record numbers - MuckRock request 178286 (December 23, 2024); FBI FOIPA Request No. NFP-168932 (closed January 8, 2025)
  • What it does not show - Any FBI search result. An administrative closure is not a finding that no records exist. Whether the FBI holds any record about the OSC cases or about David's reports. Who posted the February 2025 withdrawal messages; the thread shows the posts, not who sent them.
  • Counter-evidence and other side - The FBI answered in 16 days, gave the reason, named the signer, and offered rewording help, an appeal to DOJ's Office of Information Policy, and mediation through OGIS.
  • Connected records - Full saved FOIA thread 178286 (10 messages, the letter and attachments); MuckRock request page 178286; OSC filing of December 4, 2024 in OSC's own release; All agency control numbers in one table

Independent public-records archive. Verify independently. A filing is not a finding.

Return to the dated timeline entry (Early Warning Record, January 8, 2025: Background). A link is navigation only.

Connected Records Across This Archive (47)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

FOIA request pages (20)

Early Warning Record (17)

Rights and the Record (5)

Livewire (3)

PDF files (2)

  • PDF: 2025-01-08T172341.959585 E8c5cbebcb2cecdc6ee69d44ffe237ddc57b1f6cb766b551864_Q239199_D165381570.pdf (links to this PDF)
  • PDF: 2025-02-21T094120.380490 Final_Response_Letter-_Not_An_Agency_Record.pdf (links to this PDF)

PDF files with their exact SHA-256: PDF File Index.

Latest steps (November 16, 2026)

Corrections to older pages

Older pages on this site were written before the records were checked one by one. The original pages stay online so nothing is hidden; the corrections below are added to them.

Connected Records Across This Archive (2)

Each entry below shares an exact key with this record: the same request or tracking number, the same file SHA-256, a direct link, a cited control ID, or an approved public work email. A shared key only shows that two records are connected; it is not a finding, and it does not show who did what. A filing is not a finding.

Early Warning Record (2)

PDF files with their exact SHA-256: PDF File Index.

Published November 14, 2026. Related: Early Warning Record · Rights and the Record · Investigator hub · FOIA records