Free account 2:30Missing records detection
Every record the case documents mention that the file does not contain, grouped by provider, with the page that mentions it.
How to spot them, prove them and preserve the evidence
Altered records are chart entries changed after the fact in a way that hides the original. A labeled, dated and signed late entry that leaves the original readable is not.
A later change that hides the original entry. Medrecords AI flags them.
Altered medical records are chart entries changed after the fact in a way that hides the original: backdated notes, overwritten text, inserted or removed pages, or additions made without a late-entry label. A late entry or addendum that is labeled, dated, timed, signed and leaves the original readable is not alteration. In litigation, alteration can support spoliation sanctions, an adverse inference or, in some states, punitive damages.
A medical chart is allowed to change. Nurses add late entries, physicians write addenda, and coders ask for corrections, and all of it is proper when the change is labeled, dated, signed and leaves the original readable. An altered record is the other kind of change: the one built to make the chart look as if it always said the new thing.
For plaintiff and defense attorneys, paralegals and legal nurse consultants who suspect a chart changed after the fact. You walk away with the rules, the red flags, a version comparison worksheet and a preservation letter.
The question in these disputes is rarely whether the chart changed. It is whether the change was disclosed. Every entry at a Medicare-participating hospital is measured against 1 sentence:
"All patient medical record entries must be legible, complete, dated, timed, and authenticated in written or electronic form by the person responsible for providing or evaluating the service provided, consistent with hospital policies and procedures."
"Dated" and "timed" mean the moment the entry was written, which is not always the moment of care. Late entries live in that gap, and so do alterations. The same section also requires the hospital to "ensure that unauthorized individuals cannot gain access to or alter patient records" (42 CFR 482.24(b)(3)). The word "alter" is in the regulation itself.
AHIMA, the health information management profession's body, uses "amendment" as the umbrella term and splits it into kinds. The definitions below follow its 2012 toolkit.
| Change | What a proper one looks like | When it becomes a problem |
|---|---|---|
| Late entry | Labeled "late entry", dated and timed when written, names the time of the event it describes, signed | Written to look contemporaneous, or created after the outcome, a claim or a records request without saying so |
| Addendum | Attached to the original note, separately dated, timed and signed, states why it was added | Adds self-serving detail days or weeks later, after the bad outcome was known |
| Correction | Original readable (a single line through on paper, a version history in the EHR), reason stated, initialed and dated | Original obliterated with white-out, scribbled over, overwritten or deleted |
| Retraction | Wrong-patient or erroneous entry hidden from routine view, prior version retained, annotation visible to clinicians | Used to remove an accurate entry that hurts the provider |
| Alteration | None. There is no proper form | Backdating, page substitution, inserted pages, removed entries, rewritten vital signs, new text under an old signature time |
Every changed entry you find can be run through 4 questions. Is it labeled as a change? Is it dated and timed when it was written? Does it name its author? Is the original still readable? A change that passes all 4 can still be weak or self-serving, and a jury can weigh that. A change that fails any 1 is where alteration arguments start.
No single federal statute defines "altered medical record" for civil litigation. What exists is a stack of rules written for certification, payment, privacy and licensing that together describe a proper change. Experts measure against this stack, and so should you.
| Source | What it requires | Why a litigator uses it |
|---|---|---|
| Hospital Conditions of Participation, 42 CFR 482.24 | Entries legible, complete, dated, timed and authenticated; records protected from unauthorized alteration; record completed within 30 days of discharge; retained at least 5 years | The baseline for any Medicare-participating hospital. A note signed 45 days after discharge is a completion problem under (c)(4)(viii), whatever else it is |
| Medicare Program Integrity Manual, chapter 3, 3.3.2.5 | Services are expected to be documented when rendered; the date and author of any amendment, correction or delayed entry should be identifiable, and the change "clearly and permanently denoted" | CMS's own statement of how a delayed entry must look, current as revised in 2024 |
| Medicare Program Integrity Manual, chapter 4, 4.7.4 | Fraud contractors evaluate records for alterations and ignore undated or unsigned margin notes | A federal agency's working list of alteration signs, quoted below |
| HIPAA right to amend, 45 CFR 164.526 | Patient may request an amendment; covered entity acts within 60 days (1 extension of 30); an accepted amendment is appended or linked, not written over | Even a change the patient asks for is added beside the original, never in place of it |
| AHIMA, Amendments in the EHR Toolkit (2012) | Lock notes after final signature; control who can reopen them; the original entry "should be viewable" with date, time, author and reason for the change | The professional standard health information managers apply, and the source of the definitions in chapter 1 |
| Facility policy | Sets the late-entry window, who may amend, when notes lock, how retractions work | The policy in force on the date of care is the yardstick for "late". Ask for it by date |
| State licensing and criminal law | Varies. California makes fraudulent alteration unprofessional conduct for physicians and a misdemeanor for anyone (chapter 9) | Tells you whether the conduct carries consequences outside the civil case |
The chapter 4 manual entry is the closest thing to an official checklist, and it is short enough to quote whole:
"The UPIC shall evaluate the medical record for evidence of alterations including, but not limited to, obliterated sections, missing pages, inserted pages, white out, and excessive late entries. The UPIC shall not consider undated or unsigned entries handwritten in the margin of a document."
Notice what the list includes: "excessive late entries". Late entries are legitimate. A pattern of them is not something CMS ignores, and neither should you.
Definitions are easier to hold onto with a real-looking note in front of you. Below is the same nursing progress note as it appears in 3 places in a hypothetical file. Chapter 6 walks the full case; this chapter is about reading the note itself.
The addendum is proper in form and weak in substance. The third column is the problem: new facts, the old signature time, and no label.
Version 1 is a clean contemporaneous note, created 25 minutes after the event and signed 6 minutes later. It holds 2 facts that hurt the hospital: the bed alarm was off, and the last rounding was at 23:00.
The addendum passes the 4-question test. It is labeled, timed when written, names the window it covers, is signed, and leaves version 1 intact. Its weakness is timing and content: written 2 days later, after the CT, it adds exactly the 2 facts that would answer the fall-risk case. A jury can weigh that. Nobody can call it concealment, because it announced itself.
Column 3 is the one that should stop you. The header still says signed at 02:41, but 2 sentences now contradict version 1 and nothing on the page says a change was made. Before you call it alteration, rule out the print view: some EHRs print only the current revision under the original signature line, with the edit tracked in the history. That still breaks the rule that the original stays viewable, but it is a different problem from a forged page. Only the metadata in chapter 8 tells the 2 apart.
Most reviewers never see an original chart. They see a PDF of a printout, or a scan of a fax of a copy. That limits what can be seen on the page, and it is worth being honest about which signs survive that chain and which need the original paper or the EHR metadata.
| Sign | How it shows in a PDF | Common innocent explanation | What settles it | Needs metadata or original? |
|---|---|---|---|---|
| Different ink, pen pressure or handwriting inside 1 entry | Often lost in a black and white scan; sometimes visible as stroke weight | A 2nd clinician co-signing, a pen running out | Paper original examined by a forensic document examiner | Original |
| Text squeezed into margins, between lines or above the signature | Visible | A labeled correction written where there was room | Whether it is dated, timed and initialed; CMS ignores unsigned margin notes | No |
| White-out, obliteration, overwriting | Partly visible as blotches or overprinted characters | Almost none for clinical content; proper corrections leave the original readable | Paper original, sometimes under oblique or infrared light | Original |
| Different font, header, footer or template on pages of the same note | Visible | Printed from a different module, or the print template changed between productions | Print dates in footers; print events in the audit trail | Partly |
| Late entry or addendum written long after the event, or after the outcome | Visible when labeled | Busy shift, dictation backlog | Facility late-entry policy; the author's usual pattern | No |
| A note timed before the event it describes, or entries running backward | Visible in a sorted chronology | Device clock drift, a wrong time typed, a late entry without a label | Create and modify times in the audit trail | Yes |
| Page "3 of 7" with no page 4, a Bates gap, extra pages in a later production | Visible | Copying or scanning error, a new document type added | A written request for the named page; page counts compared across productions | No |
| Vital signs that disagree across flowsheet, narrative and monitor strip | Visible | Device values validated later; a manual recheck entered separately | Monitor data; flowsheet filed times versus value times | Yes |
| Signature or authentication time after discharge | Visible in the signature block | Batch signing; physician catching up on deficiencies | Whether it breaches the 30-day completion rule; what changed before signing | Partly |
| Copy-forward text carrying a stale fact | Visible across notes | Routine copy-forward (chapter 5) | Whether the stale fact appears only near the event | No |
| 2 versions of 1 note across productions | Visible if you compare | Pre-suit copy printed before the note was signed; different print view | Revision history and print log | Yes |
A PDF is enough to raise it
A PDF cannot settle it
No single sign proves alteration. A late signature on 1 note in a 2,000-page chart is noise. Late signatures on the 3 notes about the hour before the injury, and on nothing else that shift, deserve a closer look.
A modern EHR note is assembled more than written. That fact produces a steady stream of false alarms in altered-records review, and it also gives real alterations somewhere to hide.
Fewer than 1 word in 5 of a typical note was typed fresh for that note. Identical text across days is the norm, not a sign of tampering.
The study covered 1 academic medical center, so shares will differ elsewhere. The direction will not: a reviewer who flags every repeated sentence will drown.
| Lookalike | What it looks like in the record | How to tell it from alteration |
|---|---|---|
| Copy-forward | Whole paragraphs identical from day to day, including facts that stopped being true ("drain in place" after removal) | Stale facts repeat on many days in both directions. An alteration tends to change the note nearest the event and nothing else |
| Imported data | Vitals, labs and medication lists that update themselves inside a note | A reprint can show newer values than the original print. Compare import timestamps, not narrative |
| Templates and smart phrases | Normal findings documented in the same words for every patient | Default normals are a documentation quality issue, not a change after the fact. See charting by exception |
| Ambient AI scribe drafts | A note drafted by software from the recorded visit, then edited by the clinician before signing | Edits before signature are normal. The question is whether the draft and the edit history are retained, and in which system |
| Dictation and transcription | A report dated days after the visit | AHIMA does not treat a dictated report typed outside the facility's time frame as a late entry. Check dictation and transcription times |
| Pended notes | A pre-suit copy shows a shorter note than the final version | The pre-suit copy may have been printed before signing. The print time versus the sign time settles it |
With an ambient AI scribe, there may be a recording or transcript, a machine draft and a signed note. The differences between them are pre-signature edits, which are ordinary, though AHIMA says those should be tracked too. If the case turns on what was said in the room, the draft and transcript may be the best contemporaneous evidence, and they may sit in a vendor system with its own retention clock. Our view: name the scribe's drafts, transcripts and retention settings in the preservation letter. Default retention varies, which is the reason to ask early.
Fall risk score documented as high. Bed alarm and hourly rounding ordered.
Nursing assessment, PL 000598Hourly rounding flowsheet: pt asleep, bed alarm on.
Rounding flowsheet, PL 000610The flowsheet in Production A has no rows between 23:00 and 02:15.
PL 000610 to PL 000611Progress note created 02:35, signed 02:41: bed alarm found off, last rounding 23:00.
Progress note #88121, PL 000644Acute subdural hematoma. Transfer to ICU.
Radiology report, PL 000702Labeled late entry: rounding at 00:00 and 01:00, pt asleep. Written 2 days after the fall and after the CT.
Addendum, PL 000645Request for the complete chart under the patient's HIPAA authorization.
Firm correspondence log1,284 pages, stamped PL 000001 to PL 001284 on receipt. File hashed and stored unaltered.
Intake logNames note #88121, the rounding flowsheet, versions, access history and bed alarm data.
Firm correspondence log1,391 pages. Note #88121 reads differently under the original 02:41 signature. The flowsheet now shows rows at 00:00 and 01:00. The addendum does not appear.
DEF 000668, DEF 000702The 2 productions disagree about the hour before the fall, and only the earlier one was obtained before anyone expected a claim.
Production A is stamped PL on receipt, logged and saved untouched with a SHA-256 hash. Production B later gets its own prefix and log line. The 2 sets are never merged before comparison, because deduplication would treat the 2 versions of note #88121 as near-duplicates and might drop 1. A medical chronology of Production A sorted by event time shows the rounding gap at once, and that gap becomes the case theory. The labeled addendum goes on the red-flag list as "settled by the page": a question for the late-entry policy and the deposition, not for a forensic expert.
Comparing the 2 productions note by note (chapter 7) produces 3 differences:
Each difference maps to a metadata request: the audit trail and every saved revision of note #88121 and the rounding flowsheet, the retraction history, the release log for Production A, and the bed alarm's own event log. Chapter 8 shows what that might return. At this point the file proves that 2 productions disagree about the hour before the fall. It does not prove who changed what, when or why, and it does not prove intent, which in federal court separates a curative measure from an adverse inference (chapter 9).
Version comparison is slow, careful work, and it is still mostly done by people. Here is the sequence that holds up when a reviewer is later asked, under oath, how they found the difference.
Use 1 worksheet per disputed note. Fill it from the PDFs only; leave the metadata rows blank until the audit trail and revision history arrive.
VERSION COMPARISON WORKSHEET
Matter: [CASE NAME / FILE NO.] Reviewer: [NAME] Date: [DATE]
DOCUMENT
Type / title: [e.g. Nursing progress note]
Note or order ID: [ID if printed, else "none shown"]
Author (as printed): [NAME, ROLE]
Event the note covers: [DATE TIME]
VERSIONS FOUND
Version A: Production [A] Bates [PL 000000] received [DATE]
Created [DATE TIME] Signed [DATE TIME] Print date in footer [DATE]
Version B: Production [B] Bates [DEF 000000] received [DATE]
Created [DATE TIME] Signed [DATE TIME] Print date in footer [DATE]
Other: [Addendum / late entry / retraction notice, with Bates]
DIFFERENCES (1 line each)
# Type (format / content) Version A text Version B text Cites
1 [content] "[exact words]" "[exact words]" [PL / DEF]
2 [format] [header, font, footer] [header, font, footer] [PL / DEF]
4-QUESTION TEST FOR EACH CHANGE
Labeled as a change? [Y / N]
Dated and timed when made? [Y / N]
Author identified? [Y / N]
Original still readable? [Y / N]
INNOCENT EXPLANATIONS TO RULE OUT
[ ] Printed before signature (pended note)
[ ] Different print view or template
[ ] Current-revision-only print of a tracked edit
[ ] Imported values refreshed on reprint
[ ] Copy-forward from another date
METADATA NEEDED (fill when received)
Audit trail rows for this ID: [requested DATE / received DATE / Bates]
Revision history (all versions): [requested / received]
Print / release log: [requested / received]
STATUS
[ ] Settled by the page [ ] Needs metadata [ ] Refer to expert
Summary (2 sentences, with cites):
[TEXT]
A PDF can tell you that 2 versions disagree. It cannot tell you when the text was typed, who typed it, or what the note said in between. Those answers live in system data that a standard records release does not include. AHIMA says it plainly: audit trails are part of the metadata and are discoverable for use in litigation.
| Question | Where the answer lives | Ask for |
|---|---|---|
| When was this text typed, as opposed to signed? | EHR audit trail | Create, modify, sign and addend events for the named note IDs, with user, role, timestamp and time zone, workstation |
| What did the note say before? | Revision or version history | The full text of every saved version of each named note, including superseded ones |
| What was hidden? | Retraction and deletion records | A list of retracted or "entered in error" items for the encounter, with their text and the reason code |
| What version went out, and when? | Release-of-information and print logs | Print and release events for the chart, with the date of each production |
| When were flowsheet values entered? | Flowsheet audit | Value time and filed time for each row in the disputed window |
| What did the devices record? | Standalone systems | Bed alarm, nurse call, telemetry, fetal monitoring, infusion pump and anesthesia logs, in native form |
| Who looked after the event? | Access log | View events by users outside the care team, including risk management, after the adverse event |
Here is what a filtered audit trail for the chapter 6 hypothetical might return. Real exports carry dozens of columns and thousands of rows; event names and codes differ by vendor and installation, which is why you ask for a data dictionary with the export.
| Timestamp | User | Action | Object | Workstation |
|---|---|---|---|---|
| 2025-03-14 02:35:12 | RN A | Create | Progress note #88121 | MS4-WS12 |
| 2025-03-14 02:41:07 | RN A | Sign | Progress note #88121 | MS4-WS12 |
| 2025-03-14 09:52:40 | MD B | View | Progress note #88121 | ICU-WS03 |
| 2025-03-16 15:02:18 | RN A | File rows 00:00, 01:00 | Rounding flowsheet 03/14 | MS4-WS07 |
| 2025-03-16 15:05:44 | RN A | Addend (late entry) | Progress note #88121 | MS4-WS07 |
| 2025-03-16 15:21:09 | Risk mgmt user | View | Progress note #88121 | ADM-WS22 |
| 2025-04-04 08:31:55 | HIM user | Print (release) | Full chart, encounter | HIM-WS02 |
| 2025-06-19 10:14:33 | RN A | Modify (revision 2) | Progress note #88121 | MS4-WS07 |
| 2025-06-19 10:15:02 | RN A | Sign | Progress note #88121 | MS4-WS07 |
Read in order, the rows sharpen the story without finishing it. The 00:00 and 01:00 flowsheet rows were filed 2 days late, 3 minutes before the addendum, which explains DEF 000668. The modify event on 19 June explains DEF 000702 and puts the change after the preservation letter. What the log cannot say is why. That is for RN A, the records custodian and an informatics expert who can explain what "Modify" means in this installation.
An audit trail export is a spreadsheet problem before it is an AI problem. Filter to the note IDs, sort by timestamp, and highlight events after the adverse event and after notice of the claim. A general-purpose large language model can help write filter formulas or explain vendor event codes, but only inside a tool covered by a business associate agreement, and every row it summarizes has to be checked against the raw export. A model that summarizes 40,000 rows will sometimes invent a row that is not there. The full request and reading method is in the EHR audit trail guide.
Ask in the first discovery request, before the deposition. When the author testifies the note was written at 02:41, you want the log already in hand. Name the note IDs, run the date range from admission to the latest production, and ask for native or CSV format with a data dictionary. A narrow request is harder to resist on burden.
Spoliation is the destruction, alteration or failure to preserve evidence when litigation is pending or reasonably foreseeable. For a hospital the duty can attach before suit: a serious adverse event, a risk review, a law firm's records request or a preservation letter can each show foreseeability. When it attached is for the court, under the law of the jurisdiction.
In federal court, lost electronically stored information is governed by FRCP 37(e), rewritten in the 2015 amendments. The rule applies when ESI that should have been preserved is lost because a party failed to take reasonable steps, and it cannot be restored or replaced through additional discovery. It then sets 2 tiers:
"(2) only upon finding that the party acted with the intent to deprive another party of the information's use in the litigation may: (A) presume that the lost information was unfavorable to the party; (B) instruct the jury that it may or must presume the information was unfavorable to the party; or (C) dismiss the action or enter a default judgment."
Below that tier, under (e)(1), a court that finds prejudice may order only "measures no greater than necessary to cure the prejudice". The 2015 committee note adds that the rule "does not call for perfection": reasonable steps suffice. 3 practical consequences follow for altered-records cases:
Most medical malpractice cases are in state court, and state spoliation law differs on at least 3 points: when the duty to preserve arises, what level of fault supports an adverse inference instruction, and whether spoliation is only a sanctions issue or also a separate tort. Some states recognize an independent tort for intentional spoliation; many do not. Check your jurisdiction before you plead or brief it.
Ohio is the clearest example of how seriously a state court can treat deliberate alteration by a physician. In Moskovitz v. Mt. Sinai Medical Center, 69 Ohio St.3d 638 (1994), the Ohio Supreme Court held:
"An intentional alteration, falsification or destruction of medical records by a doctor, to avoid liability for his or her medical negligence, is sufficient to show actual malice, and punitive damages may be awarded whether or not the act of altering, falsifying or destroying records directly causes compensable harm."
The court also recognized that "a cause of action exists in tort for interference with or destruction of evidence". It reinstated punitive damages against the physician, with a remittitur of $2 million from the jury's $3 million punitive award, leaving $1 million. That is 1 state's law from 1994. It shows the ceiling of the risk, not the norm everywhere.
| Law | What it covers | Consequence |
|---|---|---|
| California Penal Code 471.5 | Anyone who alters or modifies a medical record, or creates a false one, with fraudulent intent | Misdemeanor |
| California Business and Professions Code 2262 | Physicians and podiatrists who alter a record or create a false one with fraudulent intent | Unprofessional conduct, plus a $500 civil penalty per violation |
| 18 USC 1035 | Knowingly and willfully falsifying or covering up a material fact, or using a false document, in a matter involving a health care benefit program, in connection with delivery of or payment for care | Up to 5 years in prison, a fine, or both |
| 18 USC 1519 | Knowingly altering, destroying or falsifying a record to impede a federal investigation or matter | Up to 20 years in prison, a fine, or both |
Other states have their own rules. None of these are remedies a civil litigant controls, but they explain why a clinician asked about a changed note at deposition may be advised not to answer.
Suspicion is cheap and accusations are expensive. The path below runs from the cheapest step that can settle the question to the most expensive. Whether to take each step is a decision for counsel.
Each step costs more than the one before. Most suspected alterations end at step 2 or 3, and that is a good outcome: it means the file is cleaner than you feared.
A preservation letter puts the provider on notice. It also tells the provider which notes you care about. Many plaintiff lawyers get a complete pre-suit copy under the patient's HIPAA right of access first, then send the letter the same week. We think that order is right: a baseline obtained after the letter is worth less. The routes are in how to get medical records for a lawsuit. For defense counsel and risk managers, the mirror image: once a claim is foreseeable, lock the chart, suspend purges and document the hold.
A starting draft for counsel to adapt. Names the categories most often lost. Adjust to your jurisdiction and your facts.
[FIRM LETTERHEAD]
[DATE]
VIA [EMAIL AND CERTIFIED MAIL]
[Custodian of Records / Risk Management / General Counsel]
[FACILITY NAME AND ADDRESS]
Re: Preservation of evidence
Patient: [NAME], DOB [DATE], MRN [IF KNOWN]
Dates of care: [ADMISSION DATE] through [DISCHARGE DATE]
Dear [NAME]:
This firm represents [CLIENT] regarding care provided at [FACILITY]
during the dates above. We anticipate litigation. We ask that you
preserve, and suspend any routine deletion, purge, overwrite or log
rotation of, the following, from [ADMISSION DATE] to the present:
1. The complete electronic health record for the encounter in native
format, including every saved version of every note, order,
flowsheet row and addendum, and the revision history of each.
2. Audit trails and access logs for the chart: create, view, modify,
sign, addend, retract, delete, print and release events, with
user, role, timestamp and time zone, and workstation, plus the
data dictionary for event codes.
3. Retracted, "entered in error", deleted or hidden entries, with
their original text and reason codes.
4. Release-of-information and print logs showing each production of
this record and its date.
5. Specifically, and without limiting the above:
[NOTE TYPE, DATE, TIME, NOTE ID IF KNOWN]
[FLOWSHEET NAME, DATE RANGE]
6. Data from systems outside the EHR: [bed and chair alarms, nurse
call, telemetry, fetal monitoring, infusion pumps, anesthesia
records, glucometers], in native form.
7. Ambient documentation or scribe data, if used: audio, transcripts,
machine drafts and edit history, and the vendor's retention
settings.
8. Imaging in DICOM format, in addition to reports.
9. Paging, secure messaging and nurse call logs for [UNITS, SHIFTS].
10. Staffing and assignment records for [UNITS, SHIFTS].
11. Policies in force on the dates of care on documentation, late
entries, addenda, corrections, retractions and record locking.
12. Paper originals of any handwritten or downtime records, not
copies, so ink and paper can be examined.
Please confirm in writing within [NUMBER] days that a hold is in
place and identify the person responsible for it. This letter does
not waive any right to seek additional evidence.
Sincerely,
[ATTORNEY NAME]
[BAR NUMBER, CONTACT DETAILS]
Download this guide as a worksheet (CSV), with Done and Notes columns.
0 of 10 checked
Altered-records work has 2 halves. The first half is finding: reading every page, noticing the late-entry label on page 645 and the near-identical note on page 702, and putting entries in order by when they were written. The second half is judging: deciding whether a change hid something, and why. AI tools are good at a large part of the first half and should not be trusted with the second.
In litigation, a flag you cannot trace to a page is worthless. A flagged late entry helps only if you can open both versions. Grounded, page-level citations make that 1 click; the human-in-the-loop reviewer decides addendum or alteration. The court side makes the point sharply. In Mata v. Avianca, Inc. (S.D.N.Y. 2023), lawyers were sanctioned under Rule 11 after filing a brief with case citations a chatbot had fabricated. The same duty to verify applies to a chronology an expert relies on, or to a spoliation motion that quotes a note. Check every cited line at the page before it goes into a filing.
The market for AI document review and technology assisted review is crowded, and agentic AI tools now promise to run whole review workflows. For altered-records work, rank the requirements in this order:
Every flag, date and quote opens the source page. No citation, no use.
A business associate agreement before any record is uploaded. Consumer chatbots without one are out.
An independent security report, and a written commitment that your records do not train the model.
The tool must not silently deduplicate 2 versions of the same note into 1.
A log of who uploaded, viewed and edited what, so you can answer chain-of-custody questions about your own work.
Output that says "near-duplicate, differs in 2 lines", not "altered". The verdict stays with people.
For the wider question of how AI review compares to a person on accuracy, see is AI accurate enough for court and HIPAA-compliant AI medical record review.
Medrecords AI is medical record review software. You upload the records; it drafts a cited chronology and flags, every line linked to its source page. On a chart where alteration is a question, it flags these signals in the uploaded record, each cited to its page:
Flags are signals, not verdicts. A near-duplicate that differs may be a pended note, a print view difference or a real alteration, and the software cannot tell which. A human decides.
What it does not do: it does not read EHR system exports or access history, so it cannot tell you when text was typed. It does not build a page-by-page map between 2 productions; chapter 7 describes how a person does that. It does not judge intent, decide whether spoliation occurred, give legal advice, or retrieve records from providers. It works on the files you upload, under SOC 2 and HIPAA with a signed BAA (see security and HIPAA). Self-Service bills 10 cents a deduplicated page, down to 5 cents at volume, duplicates free; Enterprise On-Prem is an annual license.
Book a demo on a chart you have questions about, then run your first case free on us. Every line comes back cited to its source page. You review, you revise, you sign.
Scheduling only. No records move from a public page.
3 short guides from our help center, recorded on a demo case. They play inside the app: sign in or create a free account, and the video opens at the chapter you picked. First case is free on us.
Free account 2:30Every record the case documents mention that the file does not contain, grouped by provider, with the page that mentions it.
Free account 2:35Every medical event on its date, in order, tied to the page it came from. Filter it, search it and export it as PDF or Word.
Free account 2:12Ask a question in your own words. The answer comes back with numbered links, and each one opens the page it came from.
Rules and statutes were checked against primary sources in September 2026, and quoted text is verbatim. AHIMA's toolkit is paraphrased except for 1 short phrase. Everything in the case example in chapters 3, 6 and 8 is hypothetical. Product facts come from this site's product pages. Nothing here is legal or medical advice.
Related guides: EHR audit trails in medical malpractice, reconciling a defense record production, how to get medical records for a lawsuit, and medical malpractice record review.
Related guide: Medical chart audit: how to run one that holds up