# Check a records-department contact directory Canonical page: https://agents.paretoid.com/workflows/check-a-records-department-contact-directory/ Category: Client Service Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Compare facility-specific routing details with supplied official public pages. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Compare facility-specific routing details with supplied official public pages. Why it matters: Sending a request to the wrong facility or department can delay collection. A dated, source-linked directory helps staff verify routing before any patient-related information is sent. ## Sources and evidence - pain: [Pain evidence: I’m terrible at subpoenas/medical records](https://www.reddit.com/r/paralegal/comments/1vbyw80/im_terrible_at_subpoenasmedical_records/) I’m terrible at subpoenas/medical records, 2026-07-31, older. Comments describe confusion between hospital groups and specific facilities and recommend maintaining the correct department/address in a shared spreadsheet. Bad firm or am I not built for this industry?, 2026-07-05, says there is no universal directory and the writer feels they are guessing. - pain: [Pain evidence: Bad firm or am I not built for this industry?](https://www.reddit.com/r/paralegal/comments/1uo0pi5/bad_firm_or_am_i_not_built_for_this_industry/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: Microsoft Lists](https://support.microsoft.com/en-us/sharepoint/lists/create-a-list-from-the-lists-app) Microsoft Lists supports structured lists with text/date fields and views. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Staff confirms a routing change or directory review is due 1. compare public official provider instructions with the directory 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested - No universal provider-directory export exists. A page can document a patient channel without authorizing third-party legal requests. Missing named facility/scope blocks a verified routing claim. Access and setup: - No universal provider-directory export exists. A page can document a patient channel without authorizing third-party legal requests. Missing named facility/scope blocks a verified routing claim. ### 1. Capture a named provider’s public instructions Tool: Browser, public Mayo Clinic site Location: Medical records and imaging request > Release of information Open the approved Mayo Clinic medical-records URL, save the public page or print to PDF with capture timestamp, and capture the Release of information section. For other facilities, use their own official allowlisted page. Do not open a patient portal or enter patient data. Expected output: Source page with named department, channels and facility scope Next step: Compare with the existing directory in a local workbook. Check before continuing: Do not substitute amendment-request, billing or general registration contacts for records-release routing; a shared parent brand is not facility coverage. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.mayoclinic.org/patient-visitor-guide/medical-records ### 2. Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Location: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Official heading → facility_name/department; explicitly displayed public channel → public_request_channel; URL → approved_public_source_url. Staff assigns public_provider_id and last_verified_date only after checking the page; preserve its stated geographic scope. Existing directory rows come from the authorized saved directory, not a claimed export. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed directory.csv; source-pages.txt; source-pages/; manifest.txt; evidence-map.csv Next step: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check before continuing: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.mayoclinic.org/patient-visitor-guide/medical-records ### 3. Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Location: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Next step: Paste the exact prompt in the next step. Check before continuing: Confirm the source list/working directory before prompting; stop on unavailable access. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html ### 4. Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Location: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. Prompt: ```text Using only the supplied official public page captures and directory rows, propose corrections to facility_name, department and public_request_channel. Return provider ID, existing value, proposed value, source ID/section, capture date, facility-scope evidence and uncertainty. Keep distinct facilities separate. Do not infer a legal request route from a patient-only route, send a request, disclose patient data or edit the directory. Missing or conflicting scope means verify with the provider before use. ``` Expected output: proposed-directory-updates.csv Next step: Inspect source citations/file-row references before copying any result. Check before continuing: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 5. Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Location: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to proposed-directory-updates.csv. Directory owner verifies exact facility and request type before accepting a row; any later patient-related request needs its own authorized recipient and content. Expected output: Source-checked proposed-directory-updates.csv Next step: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check before continuing: Acceptance case (proposed, not run): Two facilities share a health-system name but only one is explicitly covered: retain two rows and mark the second unverified. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.mayoclinic.org/patient-visitor-guide/medical-records ### 6. Approve the internal next action Tool: Responsible human owner Location: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Directory owner verifies exact facility and request type before accepting a row; any later patient-related request needs its own authorized recipient and content. Expected output: Approved internal review record or explicit blocked status Next step: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check before continuing: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://www.mayoclinic.org/patient-visitor-guide/medical-records ## What you will get Approved research assistant/browser with public-read access; proposed-directory-updates.csv stays separate from the live directory. ## Human review and limits Staff verify destination before sending any patient-related request; never trust directory freshness alone. Test two facilities in the same health system. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema directory.csv: public_provider_id, facility_name, department, approved_public_source_url, public_request_channel, last_verified_date. source-pages list contains official public URLs only. Synthetic example input: ```text FAC1 and FAC2 share a parent health system but have distinct records pages → retain two rows; do not copy FAC1 routing into FAC2 without direct evidence. ``` Expected synthetic output: ```text FAC1 and FAC2 share a parent health system but have distinct records pages → retain two rows; do not copy FAC1 routing into FAC2 without direct evidence. ``` Failure check: Staff verify destination before sending any patient-related request; never trust directory freshness alone. Test two facilities in the same health system. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/a07-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/a07/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/a07/README.txt) — Required inputs, file use, review steps and limits - [Directory blank CSV](https://agents.paretoid.com/assets/starter-kits/a07/directory-template.csv) — Blank input headers for directory.csv - [Directory synthetic example](https://agents.paretoid.com/assets/starter-kits/a07/directory-example.csv) — Synthetic test records for directory.csv - [Source pages template](https://agents.paretoid.com/assets/starter-kits/a07/source-pages-template.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Source pages example](https://agents.paretoid.com/assets/starter-kits/a07/source-pages-example.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Facility page fixtures](https://agents.paretoid.com/assets/starter-kits/a07/facility-page-fixtures.txt) — Required policy or native-input preparation aid; synthetic when marked example - [Synthetic example expected results](https://agents.paretoid.com/assets/starter-kits/a07/expected-results.txt) — Compare a pilot result with the planted exceptions - [Native input scaffold: directory.csv](https://agents.paretoid.com/assets/starter-kits/a07/native-directory-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: source-pages.txt](https://agents.paretoid.com/assets/starter-kits/a07/native-source-pages-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: manifest.txt](https://agents.paretoid.com/assets/starter-kits/a07/native-manifest-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: evidence-map.csv](https://agents.paretoid.com/assets/starter-kits/a07/native-evidence-map-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input mapping and source requirements](https://agents.paretoid.com/assets/starter-kits/a07/NATIVE-INPUT-MAPPING.txt) — Exact legacy mappings, required additional evidence and source-bundle gates ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Check only the official public provider pages supplied against this records-department directory. Record exact facility name, relevant department, permitted request channels and source URL/date. Do not substitute a parent hospital for a named facility. Flag contradictions or pages requiring login. Produce proposed changes, not live edits or requests. INPUTS directory.csv: public_provider_id, facility_name, department, approved_public_source_url, public_request_channel, last_verified_date. source-pages list contains official public URLs only. OUTPUT Approved research assistant/browser with public-read access; proposed-directory-updates.csv stays separate from the live directory. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.