Medical Claim Address Change Trace
Put the events in your payer registration and submissions into date order.
Medical billing records
US$11View skill
Medical Refund Duplicate Payment Evidence
Find possible duplicate entries in your payer payments and refunds.
A downloadable skill for your AI agent.
Your result
Possible duplicate settlement paths.
Source references, missing information, and questions to review stay with the findings.
How to use it
Add the skill to your AI
Open your download and follow the start guide. Use an AI agent that can load skill files and run the included tools.
Provide your records
Payer payments and refunds. Confirm the case and period you want to check.
Ask for the report
Copy the request below into your agent. Add the files and any task details it needs.
Review and save
Check the findings against the original records. Choose where to save the report and follow up on open questions.
Example request
Use the Medical Refund Duplicate Payment Evidence skill. Review the attached records: payer payments and refunds. Prepare this result: possible duplicate settlement paths. Include a source reference for each finding. List missing information and questions that need my review. Ask me to confirm the scope and where to save the report before you start.
What it checks
It groups records with matching values. You review the proposed groups before deciding whether they describe the same event.
What you provide
Payer payments and refunds.
Details it records
- Original payment
- Refund
- Second payment path
Read the full task logic
For this task, keep one review row for each claim + settlement signature. Record original payment, refund, and second payment path. Keep the source location beside each value.
Track the payer's exact request and response. Separate original claims, corrections, appeals, receipts, adjustments, and refunds.
Use supplied fee schedules and deadline sources. Do not generate medical justification or change clinical coding.
A repeated signature is a candidate duplicate. Legitimate repeat events can have the same content. Do not delete, merge, or accuse a party automatically.
Example result
This synthetic example shows the included check in use. Your agent uses its findings to complete your task report.
What you provide
Synthetic example records
| Sample record | original payment: signature-A |
|---|---|
| Sample record | original payment: signature-A |
What comes back
A difference needs review
- These records contain matching values. Check whether they describe separate events.
This result comes from the checking tool in your download.
Read the source records
These are synthetic records from the bundled example.
- source-r1 · records/r1
{"id": "r1", "key": "claim + settlement signature / SYNTHETIC-001", "value": {"original payment": "signature-A"}} - source-r2 · records/r2
{"id": "r2", "key": "claim + settlement signature / SYNTHETIC-001", "value": {"original payment": "signature-A"}}
Checked values
- records: 2; distinct values: 1
Run this example
After purchase, extract the ZIP. Run these commands from the skill folder. Use a new output folder.
python3 scripts/checks.py
python3 scripts/audit.py assets/example.json \
--files-root assets/sample-files --output-dir example-resultExpected exit code: 1. Code 0 means no helper finding. Code 1 means a finding or review item. Code 2 means incomplete or invalid input.
The check uses the records you supply. Review each finding against the original documents.
What is saved
Ask your agent to save the completed task report in a folder you choose. The report template includes the result, source references, missing information, and next actions.
- A readable check report
- The local checking tool can save its findings as report.md.
- A data copy
- The same check can be saved as report.json for use in other tools. A local audit database is optional.
Tonotes does not receive your work documents through this website. Documents you share with an AI service follow that service's storage settings.
Your download
US$11 includes one skill in a ZIP with 18 files. You receive the instructions and tools to run the task with your own records.
- A start guide to help you set up the skill.
- Task instructions that tell your AI what to check.
- Checking tools with worked examples.
- A report template with space for evidence and next actions.
Setup and file details
Use an agent that supports SKILL.md instructions and Python 3.10 or later with SQLite. Your AI-agent service is separate.
- Start guide: 1 file
- START-HERE.md explains setup and the expected example result.
- Agent instructions: 1 file
- SKILL.md defines this task and its completion checks.
- Task references: 4 files
- The task guide, input contract, tools guide, and research notes.
- Python tools: 4 files
- Check records, convert CSV input, and run the local checks.
- Examples and templates: 8 files
- The input schema, synthetic cases, expected report, and report template.
Collect the records
Start with payer payments and refunds. Confirm the case, period, and source versions before the review.
Extract the task fields
Use claim ID, payer, service date, appeal version to keep records distinct. The agent records the original value, an exact quote, and the source location.
Find repeated records
Group exact matching values and report duplicate candidates. Run the Python helper on the structured records. Check each finding against its source.
Complete the report
Prepare the task result: possible duplicate settlement paths. Include missing evidence, unresolved questions, and the next action for each open item.
Eight synthetic cases check the tool locally. Live-agent accuracy on real documents has not been tested.