A record request can arrive by fax, email, portal, or mail, from an attorney, insurer, court, provider, or relative. The request is not the hard part. Proving who asked, what they may receive, what you sent, and when you closed the matter is.
Without one log, each request becomes a private project: copies leave from separate inboxes, deadlines live in calendars, redactions have no reviewer.
Sort requests by authority, not urgency
Urgency is easy to fake. A caller who says "this is for a court case" may have no legal process. Start with the requester category and its authority question:
- Client or personal representative: access rights under HIPAA and state law.
- Attorney: authorization, court order, or subpoena.
- Insurer: payment contract or client authorization.
- Court: subpoena, order, or warrant with specific terms.
- Another provider: treatment or care coordination need.
- Relative without authority: a public request, not an automatic disclosure.
The category tells intake which proof to request and stops a story from replacing a document.
Verify authority before you copy
Match the requester to the proof
For an attorney, read the authorization: who signed it, what it covers, which provider may release, and when it expires. Firm stationery is not authority. For a personal representative, confirm the power of attorney or guardianship order. For an insurer, check the member authorization and payment scope. For another provider, confirm the treatment relationship and minimum information needed.
If the client is the requester, verify identity first, especially when the email address is unknown.
Watch for expired or narrow authorizations
An expired authorization does not become valid because records are old. A request for "all records" does not override a date limit. Read the scope and write it in the log before pulling the file.
When authority is unclear, do not release. Ask in writing for the missing document and set a follow-up date.
Keep one log with closure evidence
The log should work for someone who was not involved. Keep it in an approved system with access limited to privacy and operations roles; a shared inbox is not a log.
| Field | What it proves |
|---|---|
| Request number | One identifier for every document |
| Requester and organization | Who asked and in what role |
| Authority | Authorization, order, subpoena, or contract |
| Scope | Dates, record types, and exclusions |
| Received and due dates | Response clock and deadline |
| Decision | Release, partial release, denial, or clarification |
| Pages and fee | Volume released and copy charge |
| Delivery method | How records left the agency |
| Reviewer | Who approved the release |
| Closed date and notes | Why and when the item ended |
One row per request. Link source documents instead of pasting clinical detail.
Apply minimum necessary and redaction
Run a redaction pass
Redact information outside the authorized scope and information about other people who are not the subject of the request. Common examples include a relative's phone number in a care note, a former spouse's comments, or another client's name in a scheduling message.
Check headers, footers, attachments, scanned page backs, and metadata. A black box over text on one PDF page does not protect an attachment. Work from a copy and keep the redaction key with the request record.
Minimum necessary does not permit withholding treatment information the requester is entitled to receive. Apply the standard your privacy officer and counsel approved, and document the judgment.
Escalate subpoenas and court orders to counsel
A subpoena is a legal demand, not a copy request. Do not decide alone whether it is valid, properly served, or should be objected to. Route it to counsel or the privacy officer the same day, preserve the envelope and service records, and note the deadline.
The same applies to a court order beyond the client's authorization, a law enforcement request, or a confidentiality instruction. Counsel may direct a limited release, a motion to quash, or notice to the client. Log the escalation and the next owner.
Manage deadlines and secure delivery
Calendar the due date
Enter both dates in the log and compliance calendar. Set reminders ahead of the deadline. HIPAA generally gives a covered entity 30 days to act on an access request, with a possible extension, but state law, contracts, and court deadlines can be shorter. Confirm the rule with counsel.
Document any clarification request and response. Do not let a pending answer hide the deadline.
Send only through approved channels
Use the secure portal, encrypted email, or tracked delivery the agency approved. Confirm the recipient before sending. Do not text records, use personal email, or copy anyone outside the authorization. Record the delivery receipt.
For a client access request, the closure checklist helps at discharge. The evidence review covers the trail, and the compliance service describes how support stays inside disclosure boundaries.
Deny clearly and close the loop
A denial should state what was requested, what was not released, the reason, and the next step. "We cannot release the full file without a valid authorization for these dates" is clearer than "request denied." Include a contact and decision date.
Some denials require a specific notice or review. Have counsel or the privacy officer approve the template. Keep the letter with the log and authority document.
Close the row only when records were sent, a denial was issued, or the requester withdrew. "Waiting" is not closure.
Work an example, then measure the log
A worked request
An attorney asks for a former client's entire file. The attachment is a client-signed authorization naming the attorney and limiting the request to visit notes and billing records from March through June. Intake logs the request, verifies the signature, and confirms the dates. The reviewer releases in-scope notes and invoices, redacts a neighbor's phone number, and denies the rest because the authorization does not cover it. Records go through the portal, the fee invoice is recorded, and the row closes with the reviewer's name.
The example is ordinary. The log does not depend on memory.
Metrics and failure modes
Track requests closed by the due date, releases corrected afterward, denials for insufficient authority, and time to decision. Review quarterly for missing authority, redaction misses, and releases without a named reviewer.
Common failures include an authorization never linked to the log, a subpoena treated as a copy request, and a closure note that says only "sent." For retention, the National Archives guidance is a general reference; the HHS Privacy Rule and Security Rule set the federal frame.
If record requests are scattered across inboxes, start with one numbered log and one reviewer. Contact us to map the intake, authority check, and closure steps for your agency.

