Capability template for operations and process improvement
Records request preparation check
When a request for copies of records arrives, the records officer gets a checklist: what the request asks for, what the supplied authorization documents say, who the copies would go to, each set against the practice's own release procedure, with every gap listed. A person decides what, if anything, is released.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
The records officer opens a request knowing, in one page, what has been asked for, what the paperwork behind it actually says, and what is still missing. Where the request and a document disagree, both wordings sit side by side. Where the practice's own procedure asks for something the request does not carry, the gap is named, with the person who resolves it.
The response date appears exactly as counsel or privacy staff confirmed it. If no one has confirmed one, the page says so and asks. Nothing on the page is a decision to release, to refuse or to wait. Verifying who the requester is, and whether that person holds authority, stays with the records officer. What may be disclosed stays with privacy staff or counsel.
Who starts the work, and when
The records officer, or the health information clerk who opens the practice's records requests, starts it when a request for copies arrives and again when new paperwork comes in. The practice manager owns the release procedure the check follows.
What they supply
- The request, entered as one row: who is asking, in what role, for which patient, which records, which dates, to be sent to whom and how.
- The documents that came with it, one row each: who signed, in what role, when, what the document names, whether it is signed, how many pages arrived and how many it says it has.
- The practice's release procedure, written as numbered checks the practice already applies.
- The practice's authority records for that patient: people it already holds on file, and in what role.
- The response date, confirmed by counsel or privacy staff, with who confirmed it and when.
- Today's date.
Nothing connects to the practice's records system, and the records themselves are never supplied. No one is asked for a password or a login code.
What comes out
One checklist in a fixed order: the request as stated, the response date as supplied, the request set against each document, each check in the practice's procedure, the gaps and open questions numbered with an owner for each, anything to look at twice, and anything that could not be assessed. Every section is always present, so an empty list reads as checked and never as forgotten.
The checklist sends nothing, releases nothing and changes no record. It ends by saying so.
An invented example
Illustrative example with invented data. An invented family-medicine practice, on Monday 16 November 2026. The practice, the people (Renata, the records officer; Odile, who leads privacy; Counsel Q, who confirmed the response date) and the patient and requesters (Patient A, Person B, Person E, Patient F) are all invented. The inputs come first, in full, then the checklist.
What the records officer supplied
The records officer's message
It's Monday 2026-11-16. A request for copies came in on Thursday. Here is the request, the two documents that came with it, our release procedure, our authority records and the response date Counsel Q confirmed. What is missing?
Response date, as supplied by Counsel Q: 2026-12-14, confirmed by Counsel Q on 2026-11-13.
The request: request.csv
Request ID,Received on,Requester,Requester role as stated,Patient,Records requested as stated,Date range as stated,Recipient as stated,Delivery as stated
R-0412,2026-11-12,Person B,Daughter of the patient,Patient A,Visit notes and lab results,2023-01-01 to 2026-10-31,Person B,Secure download link
The documents: documents.csv
Document ID,Document type,Signed by,Signer role as stated,Signed on,Patient named,Records named,Date range named,Recipient named,Expires,Signature present,Pages supplied,Pages stated
D1,Authorization form,Person B,Daughter,2026-11-10,Patient A,Visit notes,2024-01-01 to 2026-10-31,Person B,2027-11-10,yes,2,3
D2,Representative document,Person E,Representative,2026-11-11,Patient A,,,,,unclear,1,1
The practice's release procedure: release-procedure.csv
Check ID,Requirement,Applies to,Field,Test,Owner
P1,The authorization form is signed,Authorization form,Signature present,equals: yes,Records officer
P2,The form carries a signing date,Authorization form,Signed on,filled,Records officer
P3,The form has not expired,Authorization form,Expires,not before as-of date,Records officer
P4,Every page of the form arrived,Authorization form,Pages supplied,matches: Pages stated,Records officer
P5,The signer is on the patient's authority record,Authorization form,Signed by,listed in authority records,Records officer
P6,The form names a recipient,Authorization form,Recipient named,filled,Records officer
P7,A representative document is signed,Representative document,Signature present,equals: yes,Records officer
P8,The representative is on the patient's authority record,Representative document,Signed by,listed in authority records,Records officer
P9,Delivery is by an approved method,request,Delivery as stated,equals: Secure download link | Postal mail,Records officer
The authority records: authority.csv
Patient,Person,Role on record,Recorded on
Patient A,Person B,Emergency contact,2024-06-02
Patient F,Person E,Parent,2025-01-20
What came back
The checklist below is what the template's rules produce from the inputs above, worked through by hand for this page. The template was tried once on an earlier form of these inputs in Claude on 10 November 2026. That run found that D2's Expires cell, which then read "none", is not a date, so the rules set the whole row aside; the cell is now blank, and the changed example and instructions have not been run again. The record is in the trial.
RECORDS REQUEST PREPARATION CHECK, request R-0412, as of Monday, 2026-11-16
Outcome: complete
Coverage: The request file "request.csv" holds 1 request. The documents
file "documents.csv" has 2 rows; 2 assessed; 0 could not be assessed.
The authority records "authority.csv" have 2 rows, 1 about this patient.
The procedure "release-procedure.csv" has 9 checks; 9 run; 0 could not
be assessed. Comparisons: 8 (Same 3, Differs 2, Blank in document 3,
Blank in request 0). Check results: 9 (Met 5, Differs 2, Gap 2). Gaps
and open questions: 9.
Inputs: as-of date 2026-11-16, stated in the message; release procedure
and authority records as supplied by the person running this check;
response date as supplied by Counsel Q. Nothing below decides what may be disclosed.
1. The request as stated
Request ID: R-0412
Received on: 2026-11-12
Requester: Person B
Requester role as stated: Daughter of the patient
Patient: Patient A
Records requested as stated: Visit notes and lab results
Date range as stated: 2023-01-01 to 2026-10-31
Recipient as stated: Person B
Delivery as stated: Secure download link
2. Response date as supplied
Response date: 2026-12-14. Confirmed by Counsel Q on 2026-11-13.
Copied as supplied; no date or period is worked out here.
3. The request set against each document
D1 (Authorization form), Patient: Same. Request: "Patient A".
Document: "Patient A".
D1 (Authorization form), Records: Differs. Request: "Visit notes and
lab results". Document: "Visit notes".
D1 (Authorization form), Date range: Differs. Request: "2023-01-01 to
2026-10-31". Document: "2024-01-01 to 2026-10-31".
D1 (Authorization form), Recipient: Same. Request: "Person B".
Document: "Person B".
D2 (Representative document), Patient: Same. Request: "Patient A".
Document: "Patient A".
D2 (Representative document), Records: Blank in document. Request:
"Visit notes and lab results". Document: "(blank)".
D2 (Representative document), Date range: Blank in document. Request:
"2023-01-01 to 2026-10-31". Document: "(blank)".
D2 (Representative document), Recipient: Blank in document. Request:
"Person B". Document: "(blank)".
4. The practice's release procedure
P1, The authorization form is signed. Applies to Authorization form.
D1: Met (Signature present: "yes").
P2, The form carries a signing date. Applies to Authorization form.
D1: Met (Signed on: "2026-11-10").
P3, The form has not expired. Applies to Authorization form.
D1: Met (Expires: "2027-11-10").
P4, Every page of the form arrived. Applies to Authorization form.
D1: Differs (Pages supplied: "2"; compared with "3").
P5, The signer is on the patient's authority record. Applies to
Authorization form.
D1: Differs (Signed by: "Person B"; stated role "Daughter", on
record: "Emergency contact").
P6, The form names a recipient. Applies to Authorization form.
D1: Met (Recipient named: "Person B").
P7, A representative document is signed. Applies to Representative
document.
D2: Gap (Signature present: "unclear").
P8, The representative is on the patient's authority record. Applies
to Representative document.
D2: Gap (Signed by: "Person E"; not on record for this patient).
P9, Delivery is by an approved method. Applies to request.
Request: Met (Delivery as stated: "Secure download link").
5. Gaps and open questions
G1. Comparison: D1, Records: the request says "Visit notes and lab
results"; the document says "Visit notes". Owner: privacy staff or
counsel.
G2. Comparison: D1, Date range: the request says "2023-01-01 to
2026-10-31"; the document says "2024-01-01 to 2026-10-31". Owner:
privacy staff or counsel.
G3. Comparison: D2, Records: the document is blank; the request says
"Visit notes and lab results". Owner: privacy staff or counsel.
G4. Comparison: D2, Date range: the document is blank; the request
says "2023-01-01 to 2026-10-31". Owner: privacy staff or counsel.
G5. Comparison: D2, Recipient: the document is blank; the request
says "Person B". Owner: privacy staff or counsel.
G6. Check P4, D1: Pages supplied "2"; compared with "3". Owner:
Records officer.
G7. Check P5, D1: Person B is on record for Patient A as "Emergency
contact"; the stated role is "Daughter". Owner: Records officer.
G8. Check P7, D2: Signature present reads "unclear". Owner: Records
officer.
G9. Check P8, D2: Person E is not on record for Patient A. Owner:
Records officer.
6. Check these
None
7. Could not assess
None
Nothing was sent, released or changed. A person contacts the requester.
The records officer verifies identity and authority; privacy staff or
counsel decide what may be disclosed. The response date is the one
counsel or privacy staff confirmed, copied as supplied.
A note on what the checklist leaves alone: it does not say whether the first document is enough, whether the second is genuine, or what the practice may send. Person E is on record only for Patient F, and the checklist treats that as no record for Patient A. Those calls belong to the records officer and to privacy staff or counsel.
Where it fits
- Healthcare: a medical practice that takes requests for copies of patient records and wants each one prepared the same way.
- Operations and process improvement: a release routine that lives in one person's habits becomes a procedure anyone covering the desk can follow.
- Compliance, risk and privacy: the practice can show what was checked, what was missing and who was asked, for every request.
- Established businesses: a practice with a long-serving records officer and a release routine that works until they are away.
What has to change for your company
The release procedure is yours. The template carries no list of what an authorization must contain, no view of who may ask for what, and no response period. Write your procedure as numbered checks, each tied to a field the template reads, and name who owns each one. Keep your authority records current, because the template trusts them and nothing else. Match the column names to your own request log.
Several rules are our editorial choices for the records officer to confirm or change: names are compared after ignoring letter case and spacing, and nothing closer; a difference in wording is shown, never reconciled; a blank cell is a gap; a familiar name or email address on a request counts for nothing unless the authority records hold it; and one request is checked per run. The complete list is in the template.
Use it only in an AI product your practice has approved for patient information.
What has been checked
Fully Powered AI wrote this capability template from its own map of the work. It was editorially reviewed on 10 November 2026. The checklist shown in the example was worked through by hand from the template's rules. It was tried once on its invented example in Claude on 10 November 2026; that run found one cell of the example that broke the template's own rule about unreadable dates, and left several rules open. The cell and the instructions were changed afterwards and have not been run again; the record is published with the example. It has not been tested in a medical practice, and no privacy officer or counsel has reviewed its rules. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your practice means running it on requests your records officer has already worked, with the cases written in advance: a request wider than its authorization, an authorization with a page missing, a signer who is known to the practice only as an emergency contact, a request with no confirmed response date. The records officer compares every line with their own file. Pilot acceptance-test preparation sets those cases up. Provider credentialing tracker is a separate routine for a clinician's licences and enrolments; this one handles a single request for copies.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: