DCP directory grievance: selected source excerpts
These excerpts distinguish a complaint, an outward reply and a later request for handling records. They are not complete original documents or findings that the complaint was substantiated.
November 15, 2023: directory grievance
David Medeiros / ABI Resources submitted an email with the subject:
11.15.2023 Formal Grievance and Complaint Regarding the Concealment of Public Information: Medicaid ABI Waiver Program Directory of Providers.
The saved outgoing print lists an attachment. The attachment's complete contents and any agency review are not established by that print alone.
Source: saved outgoing email print, page 1; SHA-256 38e251c40ff37b286807998bd5e2f5349aa906fe00771082e6ef621f5bf78b9f. Native parent metadata separately records November 15, 2023 at 12:44:22 UTC.
November 20, 2023: DCP Complaints replied
The saved DCP reply says:
We are recommending that you contact the Office of the CT Ombudsman.
The native reply headers connect it to the November 15 grievance. This establishes a response. The selected reply does not state an intake control, assigned investigator, completed transfer, investigation, closure or disposition reason.
Source: saved DCP reply print, page 1; SHA-256 37db2a2f570a54e6b54743d1005d8664a8e86a21cefb198cc9c30ee3d771cc79. Native reply metadata records November 20, 2023 at 12:31:27 UTC.
Return to the dated timeline entry (Early Warning Record, November 20, 2023: Agency reply). A link is navigation only.
A separate records request had a response sequence
DCP acknowledged R000354-102024 / MuckRock 174585 in October 2024, initially stated it held no responsive records, then supplied emails in January 2025 and stated completion. Both answers belong in the record. The selected produced emails concern other 2024 matters; they do not establish the directory grievance's disposition.
November 10, 2026: request for the grievance's handling records
David's later records request asks DCP for:
- The complaint's intake or tracking entry, control number, handler and status.
- Associated correspondence and action history, including review, referral, transfer, closure or disposition and the stated reason.
- The retained grievance and attachment, and any link to a different case.
Sent Items shows the request was sent on November 10, 2026 at 08:42:16 UTC. A Microsoft notice received at 08:42:23 UTC reports completed delivery to the DCP recipient but no delivery notification from the destination server. A separate delivery notice concerns only the sender's copy. These transport records alone do not supply DCP's own intake date or grievance outcome. Read the later acknowledgment below separately.
Source: retained provider representations of the request, Sent Items time filter and transport notices; capture SHA-256 5b08604223614d1d2b7a63a9d7f0e75ceae22b504795689d5da999d2525912e9. Record reading reviewed November 16, 2026. A response is not a merits finding, and a records request is not proof that a record was withheld.
Return to the dated timeline entry (Early Warning Record, November 10, 2026: Report sent). A link is navigation only.
November 16, 2026: FOI acknowledgment states November 10 receipt
R000445 request scope: UNCONFIRMED.
An acknowledgment signed by the DCP FOI Records Center arrived November 16, 2026 at 16:58:35 UTC. It assigns control R000445-111626 and states:
received your Freedom of Information Act request on 11/10/2026.
This letter does not constitute a denial of your request.
The message says records gathering and exemption review are pending. It supplies no records, completion date or grievance disposition. It does not repeat the subject or scope of the request, so its specific match to the directory-grievance handling request remains unconfirmed. Its general statement about open cases does not identify the status of this grievance.
A separate welcome message arrived one second earlier. Account creation and portal instructions do not establish that David registered himself or received the requested records. The portal and access links are withheld from this excerpt.
Source: retained acknowledgment body, SHA-256 1660d9846c90d75df4df4ead78873e40c6d8ecd87c17e61dafdb0906dbb1ff37; provider-message capture SHA-256 f38d74b1c9b4852221818bf4cab2899159d54adb748823051c5eaf2f0dad27c1. Selected receipt statement begins at body character 201; the not-denial statement begins at character 342. A source hash preserves the captured representation; it does not decide the request's scope or merits.
Return to the dated timeline entry (Early Warning Record, November 16, 2026: Receipt). A link is navigation only.
Read the DCP handling question · Dated warning record · Petition rights and the record
Back to the Early Warning Record entry · Privacy-cleaned source reading prepared November 17, 2026. Private contact details and details of people who receive services are left out. A reply or receipt shows an office got a report; it is not proof anyone investigated.