Free account 2:30Documents index and filters
Every document in the case in 1 list. Search, group and filter it, and open any record straight to its pages.
The complete guide for litigation teams
Bates numbering gives every page in a production a unique, sequential identifier, such as PLTF-000412. Once a page is produced, its number never changes.
Not by name. Medrecords AI stamps Bates numbers in 1 pass.
Bates numbering is the practice of giving every page in a document production a unique, sequential identifier, usually a party prefix plus a zero-padded number such as PLTF-000412, stamped in the lower right margin. Lawyers, experts and courts cite that number to point at 1 exact page, so once a page is produced its number never changes.
A hospital production can run to 4,000 pages of flowsheets, orders and nursing notes that look alike. Without a unique number on each page, "the nursing note from the 14th" can mean 6 different pages, and nobody in the deposition can prove which one the witness was holding.
For attorneys, paralegals, legal nurse consultants and litigation support staff who produce or receive medical records. You walk away with a stamp format, a production workflow, load-file basics and 4 templates you can paste into your own file.
A Bates number is an address. It names 1 page in 1 production, and it keeps naming that page for the life of the case. Page numbers restart in every document and shift when someone re-sorts a PDF. A Bates number does not move. That is the whole point of the system, and every rule in this guide exists to protect it.
The name comes from Edwin G. Bates, whose hand stamp printed a number on a sheet of paper and advanced to the next number by itself. The Henry Ford museum, which holds a Bates numbering machine made between 1919 and 1925, describes its mechanism as an improvement patented by Bates in 1891. Law offices ran those stamps over paper productions for most of the 20th century. Software does the stamping now, but the idea has not changed: 1 page, 1 number, forever.
People use 4 terms loosely. They mean different things, and the difference shows up when a deficiency letter lands.
Who uses the number? Everyone downstream. The deposition taker says "I'm showing you PLTF-000412." The expert lists "materials reviewed: DEF-000001 to DEF-002318." The medical chronology cites the page for every entry. The judge reading a motion to compel reads "the gap between DEF-000430 and DEF-000442 is not explained." Each of those sentences fails if the numbers drift.
Medical records are crowded at the edges. Fax headers run across the top, flowsheet columns run to the right margin, and signature blocks sit at the bottom right, exactly where the stamp wants to go. Here is a produced page with every element that matters, pinned.
The stamp goes in the lower right margin, clear of content; the legend goes elsewhere; the provider's own marks stay visible.
Placement conventions are strong but not universal. The SEC wants the number in the lower right corner of each image. Many ESI protocols say "lower right, not obscuring any content." If yours says nothing, use the lower right and write the choice down so the next production matches.
Our rule for medical records: before stamping a batch, scale every page to about 95% and add a white footer band. It costs nothing, and it ends the argument about whether a stamp covered the 21:52 on a signature line. A stamp over a time entry turns a routine page into an authenticity dispute.
There is no national standard for the format. There are strong conventions, and the federal agencies that receive the most productions have written theirs down. The DOJ Antitrust Division's specification is the clearest: numbers must be unique, sequential across the entire production, "of a consistent length, include leading zeros," and carry no more than 3 segments, for example a company identifier, a custodian segment and a page counter.
Keep it short, fixed width and boring. Every clever format choice becomes a load-file problem later.
| Element | Convention | Example | What goes wrong |
|---|---|---|---|
| Party prefix | 2 to 6 letters naming the producing party or the case | PLTF, DEF, HOSP | 2 parties pick the same prefix, and 1 number points to 2 pages |
| Custodian or source segment | Optional middle segment for the custodian, provider or volume | PLTF-ORTHO-000213 | Added halfway through the case, so early and late pages sort differently |
| Volume | Usually carried in the load file and the media label, not the number | Volume PLTF001 | Volume baked into the number, then restarted per volume |
| Separator | Hyphen is the safest choice. The SEC accepts hyphens and the _ character; the DOJ specification bars the _ character | - | Spaces, slashes or the load-file delimiter inside the number break the import |
| Padding | Fixed width with leading zeros, 6 to 8 digits | 000412 | Unpadded numbers sort as 1, 10, 100, 2 in a file browser |
| Family range | Parent document first, attachments follow in sequence | BEGATTACH PLTF-000500, ENDATTACH PLTF-000515 | Attachments numbered in a separate run, so the family cannot be rebuilt |
| Native file | 1 number for the whole file, on a slip sheet and in the file name | PLTF-000473.xlsx | A 40-tab spreadsheet printed to 900 pages and stamped page by page |
| Late insert | Suffix on the page before it, used sparingly | PLTF-000412.001 | Renumbering the whole set to make room, which breaks every earlier citation |
Ranges are written first page to last page: PLTF-000100 to PLTF-000245. Some teams shorten that to PLTF-000100-245. Pick 1 style and keep it in every letter, log and index. A range must equal its page count: 000100 to 000245 is 146 pages, and if the PDF has 145, something is missing or doubled.
Here is something that surprises new paralegals: the text of Federal Rule of Civil Procedure 34 never uses the word "Bates." No federal rule makes you stamp pages. Bates numbering is required by ESI protocols, stipulated orders, local rules, agency specifications and the plain need to cite a page. The rules below are what sits underneath it.
| Rule | What it says | Why it touches Bates |
|---|---|---|
| FRCP 34(b)(1)(C) | A request "may specify the form or forms" in which electronically stored information is to be produced. | Ask for images with Bates numbers and load files in the request itself, not after. |
| FRCP 34(b)(2)(A) | The response is due in writing within 30 days after service. | Stamping, QC and the load file all have to fit inside that window, or you negotiate more time. |
| FRCP 34(b)(2)(C) | "An objection must state whether any responsive materials are being withheld on the basis of that objection." | Withheld pages should be visible in the range as slip sheets, not silent gaps. |
| FRCP 34(b)(2)(E) | Produce documents as kept in the usual course of business or organized and labeled to the requests; produce ESI in the form ordinarily maintained or a reasonably usable form; no duty to produce the same ESI in more than 1 form. | Bates-stamped images with a load file are the most common "reasonably usable" form. |
| FRCP 26(f)(3)(C) | The discovery plan must address ESI issues, "including the form or forms in which it should be produced." | The Rule 26(f) conference is where the Bates format belongs. |
| FRCP 26(b)(5)(A) | A party withholding privileged material must expressly make the claim and describe what it withheld. | The privilege log cites the Bates number of each slip sheet. |
| FRCP 26(b)(5)(B) | After notice of a privilege claim on produced material, the receiver must return, sequester or destroy it. | A clawback notice identifies pages by Bates number. Without numbers there is nothing precise to claw back. |
| FRE 502(d) | A federal court may order that disclosure connected with the case does not waive privilege in any other federal or state proceeding. | Ask for a 502(d) order before the first production. |
| 45 CFR 164.512(e)(1)(v) | A qualified protective order limits use of PHI to the litigation and requires return or destruction at the end. | It usually sets the confidentiality legend stamped next to the Bates number. |
2 advisory committee sentences from the 2006 amendments to Rule 34 explain why a stamped TIFF alone is not always enough.
"If the responding party ordinarily maintains the information it is producing in a way that makes it searchable by electronic means, the information should not be produced in a form that removes or significantly degrades this feature."
That is why stamped images travel with extracted text and a load file. A flat, unsearchable PDF of an EHR export, stamped and nothing else, invites a motion. The same note adds that a "reasonably usable form" does not let a party convert ESI into a form "that makes it more difficult or burdensome for the requesting party to use the information efficiently."
The Sedona Conference says the same thing in its own words. Principle 12 of The Sedona Principles, Third Edition (October 2017): production "should be made in the form or forms in which it is ordinarily maintained or that is reasonably usable given the nature of the electronically stored information and the proportional needs of the case."
For medical records specifically, HIPAA adds a layer. Under 45 CFR 164.512(e), a covered entity can disclose records in response to a subpoena or discovery request when, among other routes, the party seeking them has sought a qualified protective order. The order usually dictates the legend tiers and who may see which ranges. State rules differ on privilege logs, confidentiality designations and whether a party must produce records it obtained by authorization, so check your jurisdiction.
Our view: put the Bates format, the legend wording, the load-file fields and a 502(d) order in the ESI protocol before anyone produces anything. Every one of them is cheap to agree on in month 1 and expensive to fight about in month 9.
Stamping is step 4 of 6. Most Bates disasters come from doing it at step 2, before the set is final. Here is the order we recommend, then the same order on a dated hypothetical.
Asks for all medical records for 2 years before the crash. Specifies TIFF images, Bates numbers, DAT and OPT load files.
Response due 04/014 provider sets saved as received: ED 212 pages, orthopedic clinic 148, physical therapy 96, imaging center 22 plus 1 DICOM study.
Hashes recorded6 orthopedic pages share a hash with other orthopedic pages. 2 near-duplicate progress notes differ in the plan section and both stay.
Method disclosed in cover letter2 pages of the client's handwritten notes to counsel sit inside the PT packet. Withheld; 2 slip sheets hold their place.
PLTF-000401 to PLTF-000402PLTF-000001 to PLTF-000473, legend CONFIDENTIAL on every page, DICOM study as a native with 1 slip sheet.
473 numbersPLTF-000187: the stamp covers the last column of a vitals flowsheet. Footer band added, set restamped. Safe only because nothing had been produced yet.
Fixed before productionCover letter, range index, privilege log citing the 2 slip sheets, DAT and OPT files, TIFFs and extracted text.
5 days before deadlineThe PT clinic sends 14 more pages for visits missing from the first set. Supplemental production continues the sequence.
PLTF-000474 to PLTF-000487The only restamp in this timeline happens before anything leaves the office. After production, the numbers are fixed.
Download this guide as a worksheet (CSV), with Done and Notes columns.
0 of 12 checked
A modern production is 4 things on 1 volume: page images, extracted text, native files, and load files that tie them together. The load files are how a review platform knows that PLTF-000213 to PLTF-000217 is 1 document and that PLTF-000218 is the first page of the next one. If you receive productions and have never opened a DAT file in a text editor, do it once. It demystifies the whole thing.
The SEC Data Delivery Standards (revised August 2026) are a good public reference. They call for black and white images as "300 DPI Group IV single-page TIFF files," color as JPEG, a unique Bates-number file name for every image, and no more than 2,000 image files per folder. They also say PDFs are not an acceptable format for images in that structured production. Your ESI protocol may say otherwise; many state-court medical record productions go out as stamped searchable PDFs.
The OPT (or LOG) file has 1 line per page image and 7 comma-separated fields: ImageID, VolumeLabel, ImageFilePath, DocumentBreak, FolderBreak, BoxBreak, PageCount. A "Y" in the fourth field marks the first page of a new document. Here is what the start of the hypothetical orthopedic set looks like.
| ImageID | Volume | Image path | Doc break | Folder | Box | Pages |
|---|---|---|---|---|---|---|
| PLTF-000213 | PLTF001 | IMAGES\001\PLTF-000213.TIF | Y | 5 | ||
| PLTF-000214 | PLTF001 | IMAGES\001\PLTF-000214.TIF | ||||
| PLTF-000215 | PLTF001 | IMAGES\001\PLTF-000215.TIF | ||||
| PLTF-000216 | PLTF001 | IMAGES\001\PLTF-000216.TIF | ||||
| PLTF-000217 | PLTF001 | IMAGES\001\PLTF-000217.TIF | ||||
| PLTF-000218 | PLTF001 | IMAGES\001\PLTF-000218.TIF | Y | 2 | ||
| PLTF-000219 | PLTF001 | IMAGES\001\PLTF-000219.TIF | ||||
| PLTF-000221 | PLTF001 | IMAGES\001\PLTF-000221.TIF | Y | 1 |
The DAT file holds 1 row per document with a header row of field names. In the Concordance default format the SEC describes, the field separator is ASCII character 020 and every value is wrapped in the thorn character, ASCII 254. Date, time and time zone go in separate fields. The Bates fields carry different names in different specifications, so match the one in your protocol.
| Field | Also called | What it holds | Named in |
|---|---|---|---|
| BEGBATES | FIRSTBATES, BEGDOC# | First Bates number of the document, prefix included | FTC guide; SEC; DOJ |
| ENDBATES | LASTBATES, ENDDOC# | Last Bates number of the document | FTC guide; SEC; DOJ |
| BEGATTACH | Start of FAMILYRANGE | First Bates number of the parent and attachment family | SEC; DOJ (as FAMILYRANGE) |
| ENDATTACH | End of FAMILYRANGE | Last Bates number of the last attachment. The SEC requires BEGATTACH and ENDATTACH as 2 separate fields | SEC |
| PARENT_BATES | PARENTID | First Bates number of the parent, filled in child records | SEC; DOJ |
| CUSTODIAN | ALL CUSTODIANS | Whose files it came from. For records, the provider or records custodian | SEC; DOJ |
| HASHMD5 / HASHSHA | MD5, SHA1 | File hash used for deduplication and to prove a native was not changed | DOJ |
| NUMPAGES | PAGECOUNT | Page count. Should equal ENDBATES minus BEGBATES plus 1 | DOJ |
| TEXTPATH / OCRPATH | Path to the document-level text file, named for the first Bates number | SEC | |
| NATIVELINK | LINK | Path to the native file, named for the first Bates number | SEC |
The DOJ Antitrust Division specification also asks for a sample production of 500 to 1,000 records before the real one, so load problems surface early. That is a good habit on any large production, including a hospital's. The FTC Bureau of Competition Production Guide lists BEGBATES and ENDBATES as the field names and 300 DPI Group IV TIFF for black and white images.
Some records do not survive being turned into pages. A billing spreadsheet loses its formulas. An audio file of a 911 call has no pages. A DICOM imaging study is hundreds of slices plus metadata. An EHR audit trail export is a table meant to be sorted and filtered, not read on paper (see the EHR audit trail guide). For these, the usual answer is a native file with 1 Bates number, a slip sheet in the image set and a hash in the load file.
The agencies differ in the details, which is a reminder to read your own protocol. The SEC wants Excel spreadsheets to have "a placeholder image named by the Bates number of the file." The DOJ specification says the Bates range for a spreadsheet "should be a single number" and that the placeholder must show at least the BEGDOC#, file name and file path. And the SEC says native productions made without load files, with prior approval, "should not be Bates numbered" at all.
Natives get 1 number and a hash. The hash is what proves, 2 years later, that the file nobody could stamp was never changed.
A tip for exhibits from natives: cite the native's Bates number plus a locator, such as "PLTF-000473, series 4, image 112" for a DICOM study or "DEF-001920, row 3,418" for an audit log. Agree the locator style with the other side before depositions. If you want to know what AI can and cannot do with a native imaging study, the DICOM guide covers it.
Medical records break the tidy ESI model in 3 ways. They arrive from many custodians, each with its own page numbering, fax headers and certification. They arrive late and in pieces, so supplemental productions are the norm. And they are full of near-duplicates, the same note printed on different days, which can be the most important pages in the case.
That produces 2 practical rules. First, when you stamp incoming records for internal use, leave the producing party's numbers visible and track both. Your internal prefix should never replace theirs. Second, keep a Bates-range log per provider from day 1. It becomes the index for the cover letter, the materials-reviewed list for your expert and the check against every citation in the chronology. If you are still gathering the records, how to get medical records for a lawsuit covers requests, authorizations and subpoenas.
The ledger is boring, which is the point. If opposing counsel writes "your production is missing pages," you answer with arithmetic, not a search.
Start it the day the first records arrive. 1 row per provider set per production. Keep it in the case file and attach it to every cover letter.
BATES-RANGE LOG Case: [CAPTION] Producing party: [PARTY] Prefix: [PREFIX] Separator: [-] Width: [6] digits Legend: [WORDING] Prod # | Date sent | Provider / custodian | Dates of service | Bates start | Bates end | Pages | Natives | Withheld (slip sheets) | Notes -------|------------|----------------------|-----------------------|---------------|---------------|-------|---------|------------------------|------ [1] | [MM/DD/YY] | [PROVIDER] | [MM/DD/YY]-[MM/DD/YY] | [PREFIX-000001] | [PREFIX-000212] | [212] | [0] | [none] | [Custodian cert received MM/DD] [1] | [MM/DD/YY] | [PROVIDER] | [MM/DD/YY]-[MM/DD/YY] | [ ] | [ ] | [ ] | [ ] | [Bates nos. + reason] | [Exact dupes removed: N, by MD5] [2] | [MM/DD/YY] | [PROVIDER, supplement] | [ ] | [continues] | [ ] | [ ] | [ ] | [ ] | [Why late; what it adds] CHECKS FOR EACH ROW [ ] End minus start plus 1 = pages + natives [ ] Start = previous end + 1 [ ] Provider's own page marks and fax headers visible [ ] Unstamped original saved at: [PATH] [ ] Other side's Bates numbers (if any) recorded in Notes
Send it with every production and every supplement. It fixes what went out, in what form, under which numbers.
[FIRM LETTERHEAD]
[DATE]
VIA [SECURE FILE TRANSFER / OVERNIGHT]
[OPPOSING COUNSEL NAME]
[FIRM]
[ADDRESS]
Re: [CAPTION], [CASE NO.]
[PARTY]'s Production [NUMBER] in response to [REQUEST SET AND NUMBERS]
Counsel:
Enclosed is [PARTY]'s Production [NUMBER], Bates numbered [PREFIX-START] through [PREFIX-END] ([TOTAL] numbers). The production is designated [LEGEND] under the [Stipulated / Qualified] Protective Order entered [DATE].
Form: [single-page Group IV TIFF with document-level text / searchable PDF], with [DAT and OPT] load files. Native files are named by Bates number and represented by slip sheets in the image set.
Index:
[PREFIX-000001] to [PREFIX-000212] [PROVIDER] records, [DATES OF SERVICE]
[PREFIX-000213] to [PREFIX-000354] [PROVIDER] records, [DATES OF SERVICE]
[PREFIX-000473] [PROVIDER] [DICOM study / spreadsheet], native, MD5 [HASH]
Withheld: [N] pages withheld as [privileged / work product], represented by slip sheets at [BATES NUMBERS] and listed on the enclosed privilege log.
Duplicates: Exact duplicates, identified by [MD5] hash, were not produced. No near-duplicate or differing versions were removed.
This production [does / does not] complete [PARTY]'s response to Request Nos. [ ]. [PARTY] will supplement as additional records are received, continuing the Bates sequence.
[SIGNATURE BLOCK]
Enclosures: [MEDIA / LINK], privilege log, Bates-range log
1 slip sheet per withheld page, or 1 per native file. It carries the Bates number so the range has no silent gaps.
[PREFIX-000401] [DOCUMENT WITHHELD] Reason: [Attorney-client privilege / Work product / Produced in native format] Privilege log entry: [NUMBER] -- or, for a native file -- [PREFIX-000473] PRODUCED IN NATIVE FORMAT File name: [PREFIX-000473].[EXT] Original file name: [NAME] Custodian: [PROVIDER] MD5: [HASH] [CONFIDENTIALITY LEGEND]
A deposition transcript that reads "this page here" is hard to check on appeal. One that reads "PLTF-000412" can be checked by anyone with the production. Cite the page, every time, in every document that leaves the office.
| Where | Example citation | House rule |
|---|---|---|
| Medical chronology | 02/03/2026 21:40, ED nursing note, neck pain 8/10 (PLTF-000412) | Every entry cites a page. No page, no entry. |
| Deposition question | "I'm showing you what has been marked Exhibit 7, PLTF-000412. Is that your signature?" | Read the Bates number into the record. |
| Expert report | Materials reviewed: PLTF-000001 to PLTF-000487; DEF-000001 to DEF-002318 | List ranges, not "all records produced." |
| Motion or brief | Operative report, DEF-000501 to 000506, at DEF-000503 | Range, then pin cite. |
| Deficiency letter | The gap between DEF-000430 and DEF-000442 is not explained by a slip sheet or log entry | Name the numbers on both sides of the gap. |
| Clawback notice | Producing party claims privilege over DEF-000877 to DEF-000879 | Exact numbers only. |
In medical cases it always does. The plaintiff produces the orthopedic chart obtained by authorization; the defense produces the same chart obtained by subpoena, with different numbers and sometimes different contents. Pick 1 set as canonical for citations, usually the most complete one, and keep a table that maps the other set's numbers to it. That table is built by a person, page by page, and it is where the interesting findings live.
The partial match and the missing page are the 2 rows that matter. A mapping table exists to find them.
The step-by-step method for this comparison, including how to handle addenda and differing versions, is in reconciling a defense record production. Treat a partial match as a question, not a conclusion. An addendum can be a proper late entry. It can also be something else, and that is for the reviewer and the experts to work out.
Ranked by how much damage each does once a production is out the door, based on what the rules above make hard to undo.
Every deposition exhibit, expert list and chronology entry now points at the wrong page. Fix: never renumber. Replace with an overlay and a letter mapping old numbers to new.
2 people stamping with overlapping start numbers, or a prefix reused across parties. Fix: 1 person owns the sequence and the log.
A covered time, dose or signature invites an authenticity fight. Fix: shrink the page and stamp in a footer band.
A skipped number with no slip sheet reads as a hidden page. Fix: slip sheets for every withheld page, and a QC pass on the OPT file.
Removing a "duplicate" that differs by 1 addendum destroys the comparison that proves alteration. Fix: cull exact hash matches only.
A chronology that cites PDF page 88 in 1 entry and DEF-000412 in the next cannot be checked. Fix: 1 citation system per work product.
The range and the page count stop agreeing, and every later check fails. Fix: number every imaged page.
AI ediscovery is older than most people think. Technology assisted review (TAR), also called predictive coding, trains a classifier on attorney decisions and ranks documents by likely relevance. In February 2012, Magistrate Judge Andrew Peck approved its use in Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012).
"This judicial opinion now recognizes that computer-assisted review is an acceptable way to search for relevant ESI in appropriate cases."
3 years later, in Rio Tinto v. Vale, 306 F.R.D. 125 (S.D.N.Y. 2015), the same judge wrote that it is now black letter law that courts will permit a producing party that wants to use TAR for document review to do so. Sedona Principle 11 points the same way: a responding party may meet its obligations "by using technology and processes, such as sampling, searching, or the use of selection criteria."
TAR sorts documents. It does not number pages, and it does not care much whether a page is stamped. The newer wave of legal AI tools does care. Generative AI built on a large language model (LLM) now drafts chronologies, deposition summaries and record summaries from the produced pages. An AI medical chronology is only usable in litigation if every line carries a page-level citation a person can click and check. And that citation is only stable if the page numbers are.
Mechanical work you can verify against a page.
Every one of these has shown up in real record sets.
The last failure is the one that ends careers. In Mata v. Avianca, 678 F. Supp. 3d 443 (S.D.N.Y. 2023), lawyers filed a brief citing court decisions that did not exist, generated by ChatGPT, and were sanctioned $5,000 under Rule 11. A fabricated case citation and a fabricated Bates citation are the same failure: a reference nobody checked. The fix is also the same. Check every cited Bates number against the range log before anything is filed or sent. A citation to PLTF-000999 in a production that ends at PLTF-000487 should never survive QC.
If the model reads the set before it is stamped, it cites PDF page numbers. Then someone dedupes, re-sorts and stamps, and every citation drifts. 500 chronology entries now point at the wrong page, and nobody notices until a witness is handed the wrong exhibit. Our rule: freeze the set, stamp it, then run the AI. When a supplement arrives, stamp it in sequence and add it, rather than re-running the whole set in a new order.
0 of 10 checked
A starting draft for the form-of-production section. Adapt it to your court's model order; some courts publish one.
[__]. Bates Numbering. (a) Each page of each document produced in image form shall bear a unique Bates number, burned into the image in the lower right corner without obscuring any content, in the format [PREFIX]-[NNNNNN] (fixed width, leading zeros, no spaces). (b) Each party shall use a unique prefix. Numbering shall be sequential within and across productions and shall not restart. Once produced, a Bates number shall not be reassigned. (c) Documents withheld in full on a claim of privilege shall be represented by a slip sheet bearing the Bates number and the words "Withheld: [Privilege]," and shall be listed on the privilege log by Bates number. (d) Files produced in native form shall be named by their Bates number, represented by a slip sheet in the image set, and accompanied in the load file by their [MD5/SHA-1] hash. (e) Load files shall include at least: BEGBATES, ENDBATES, BEGATTACH, ENDATTACH, CUSTODIAN, NUMPAGES, [HASH], TEXTPATH and NATIVELINK. Image cross-reference files shall be in [OPT] format. (f) Confidentiality designations under the Protective Order shall be stamped on each page [lower left / bottom center]. (g) Any chronology, summary or index a party serves or files that cites produced documents, whether prepared by a person or with the help of software, shall cite by Bates number. (h) The parties request entry of an order under Federal Rule of Evidence 502(d).
More on accuracy thresholds and what courts expect is in is AI accurate enough for court, and on the privacy side, HIPAA compliant AI medical record review. The short version for AI medical record review: the model drafts, a person checks every cite against the page, and the signature on the work product belongs to the person.
Everything above stands without this chapter. This part is ours, and you should read it as a vendor describing its own product.
Medrecords AI is medical record review software. Bates numbering and stamping applies sequential numbers and confidentiality legends across the uploaded file in 1 pass. You set the prefix, start number and padding. The numbers stay stable through deduplication, re-sorting and export, so a page keeps its number for the life of the file.
The chronology cites the source page of the uploaded file on every line, and each cite links to that page. When the file is stamped, the citations speak Bates. OCR routes each page to the right engine for typed text, handwriting or tables, and flags low-confidence pages for a person to read. Hyperlinked exports keep the links to the source pages.
Pricing, if it helps the decision: Self-Service bills 10 cents a deduplicated page, down to 5 cents at volume, duplicates free; Enterprise On-Prem is an annual license. Details are on the pricing page, and the security page covers the controls.
Book a demo, 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 document in the case in 1 list. Search, group and filter it, and open any record straight to its pages.
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:30Every record the case documents mention that the file does not contain, grouped by provider, with the page that mentions it.
This guide was written by Medrecords AI from primary sources, read in September 2026. Rule text is quoted from the versions published by the Legal Information Institute. Agency specifications are quoted from the documents the agencies publish. Hypotheticals, including every Bates number, date and page count in them, are invented and labeled. Nothing here is legal advice, and local rules, standing orders and ESI protocols control.
| Source | What it supports |
|---|---|
| The Henry Ford, Bates numbering machine, 1919 to 1925 | Edwin G. Bates's improvement patented in 1891 |
| Fed. R. Civ. P. 34 and advisory committee notes | 30-day response, form of production, withheld-material statement, 2006 note on searchability |
| Fed. R. Civ. P. 26 | Privilege claims (b)(5)(A), clawback (b)(5)(B), discovery plan (f)(3) |
| Fed. R. Evid. 502 | 502(d) non-waiver orders |
| 45 CFR 164.512(e) | Qualified protective orders for PHI in litigation |
| SEC Data Delivery Standards, rev. August 2026 | 300 DPI Group IV TIFF, lower right endorsement, OPT 7-field format, DAT delimiters, 2,000 files per folder, BEGATTACH and ENDATTACH, native placeholders |
| DOJ Antitrust Division, Standard Specifications for Production of ESI | 3-segment limit, fixed width with leading zeros, spreadsheet single number, privilege placeholders, hash fields, sample production |
| FTC Bureau of Competition Production Guide | BEGBATES and ENDBATES fields, 300 DPI Group IV TIFF |
| The Sedona Principles, Third Edition (2017) | Principles 11 and 12 |
| Da Silva Moore v. Publicis Groupe, 287 F.R.D. 182 (S.D.N.Y. 2012) | First judicial approval of technology assisted review |
| Rio Tinto PLC v. Vale S.A., 306 F.R.D. 125 (S.D.N.Y. 2015) | TAR use by a producing party is black letter law |
| Mata v. Avianca, Inc., 678 F. Supp. 3d 443 (S.D.N.Y. 2023) | Rule 11 sanction for fabricated AI citations |
Product facts in chapter 12 are what Medrecords AI publishes on its own product pages. Related guides: medical record organization, deduplicating medical records and a verified chronology from scanned records.