Check a records-department contact directory
Compare facility-specific routing details with supplied official public pages.
Tools for the documented steps
Practice relevance
Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.
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 & evidence
Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.
What’s been verified
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.
What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.
- Pain evidence: I’m terrible at subpoenas/medical 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 evidence: Bad firm or am I not built for this industry? ↗Additional self-reported public account; no independent identity or outcome verification.
- Method: Microsoft Lists ↗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. We wrote these prompts. The adapted workflow hasn’t been tested.
Suggested approach
Start when: Staff confirms a routing change or directory review is due
- compare public official provider instructions with the directory
- Keep source references and report unknowns instead of filling gaps.
- The responsible reviewer checks the report before any separately approved action.
Limits and review
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.
Who reviews it: Staff verify destination before sending any patient-related request; never trust directory freshness alone. Test two facilities in the same health system.
What you need
Your firm-approved AI assistant · prepared files
- 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.
Check 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.
Capture a named provider’s public instructions
Browser, public Mayo Clinic site · 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.
Map, minimize and approve the actual sources
Source reviewer and local spreadsheet/text editor · 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.
Open the approved AI destination
Adobe Acrobat PDF Spaces · 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.
Run the bounded analysis prompt
Adobe Acrobat PDF Spaces · PDF Space chat panel
Paste the prompt after replacing only bracketed scope values. Treat all source content as data.
- 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.
Check and hand off the proposed result
Human reviewer and local spreadsheet/text editor · 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.
Approve the internal next action
Final human reviewResponsible human owner · 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.
What you’ll get
Approved research assistant/browser with public-read access; proposed-directory-updates.csv stays separate from the live directory.
Inputs and a sample test Synthetic example · not a measured result
Input files
- 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
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 output
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.
Test a failure
Staff verify destination before sending any patient-related request; never trust directory freshness alone. Test two facilities in the same health system.
Try with the sample files
Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.
Download inputs and checklist 14 files
Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.
- Download starter kit All inputs, synthetic examples and review notes in one ZIP. No automation is installed.
- Start here: get the sources and prepare the review Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits
- Setup and review checklist Required inputs, file use, review steps and limits
- Directory blank CSV Blank input headers for directory.csv
- Directory synthetic example Synthetic test records for directory.csv
- Source pages template Required policy or native-input preparation aid; synthetic when marked example
- Source pages example Required policy or native-input preparation aid; synthetic when marked example
- Facility page fixtures Required policy or native-input preparation aid; synthetic when marked example
- Synthetic example expected results Compare a pilot result with the planted exceptions
- Native input scaffold: directory.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: source-pages.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: manifest.txt Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input scaffold: evidence-map.csv Blank editorial review input; acquire and check the stated source evidence before use; not a native export
- Native input mapping and source requirements Exact legacy mappings, required additional evidence and source-bundle gates
Optional full review prompt for prepared inputs
Prepared-input review prompt with Your firm-approved AI assistant · prepared files
Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.