Every clinical term, defined inline — for the people in the room who aren't clinicians.
Medical terminology translator for legal documents: hover any diagnosis, procedure, or clinical term in a chronology, summary, or deposition digest and get a plain-language definition, cited to the same clinical source. The jargon becomes readable for the people in the room who aren't clinicians — and the record stays the record.
Orthopedic consult. Assessment: chondromalacia patellae, right knee. Conservative management continued. p.140
Chondromalacia patellae: softening and wear of the cartilage on the underside of the kneecap, which can cause pain in the front of the knee — here documented in the right knee.
One capability, every output.
This is not a glossary bolted onto the side of the product. Definitions live on the terms themselves — in chronology entries, summary reports, deposition digests, and chat answers — so wherever a clinical term surfaces, the plain-language explanation is one hover away.
"Chondromalacia patellae, right knee. Conservative management continued." p.140
Cartilage wear under the kneecap causing front-of-knee pain — documented here in the right knee, treated without surgery.
Plain language that never drifts from the record.
The danger in "translating" medical records is paraphrase that quietly changes meaning. Each definition here explains the term as used in this record and cites the same clinical source it came from, so simplification stays audit-grade: readable by a layperson, checkable by anyone.
Written for the people who decide the case.
Jurors, adjusters, clients, hearing officers — the audiences that decide outcomes rarely hold medical degrees. When the chronology or demand package explains its own terminology, the reader stays inside your document instead of reaching for a search engine and coming back with the wrong answer.
Even the simple version is cited.
A definition you can't verify is just another paraphrase. Every plain-language explanation on the platform links to the clinical source it interprets, so opposing counsel, an auditor, or your own reviewer can check the simplification against the record — the same source-linked, legally defensible standard as every other output.
See Verifiable AI CitationsFrom jargon to plain English, in place.
Three steps — no glossary to build, no second document to maintain.
Clinical terms are identified as the record is read — diagnoses, procedures, medications, and shorthand, each tied to its source page.
Each term gets a plain-language explanation matching how it is used in this file, cited to the same clinical source.
Every reader of every output gets the explanation inline — and one click back to the source page to check it.
Who reads with it.
Every team whose documents get read by non-clinicians.
Demand packages and exhibits a jury can actually read.
For law firmsAdjusters evaluate clinical files without queuing for nurse review.
For carriersCase managers and clients stay on the same page — literally.
For TPAsIME reports that referral sources and attorneys parse without callbacks.
For evaluatorsPlain-language definitions, answered.
Across the platform's outputs, not in a separate glossary: hover a clinical term in a chronology entry, a summary report, a deposition digest, or a chat answer and the definition appears inline, in context. The same coverage travels with exports, so the definitions are there when the document leaves the platform.
Each definition explains the term as it is used in this record — the same clinical source the term was extracted from — rather than a generic dictionary entry pasted in from elsewhere. The plain-language wording simplifies the vocabulary, not the facts: it never adds a claim about the patient that the record does not support.
Yes. Every definition carries the same citation discipline as the rest of the platform: it links to the clinical source where the term appears in the record, so a reviewer can click from the plain-language explanation straight back to the underlying page. If a term can't be grounded, it is flagged for review — never silently guessed.
That is the core use. The people who decide a case — jurors, adjusters, clients, hearing officers — are usually not clinicians. Inline definitions let them read a chronology or summary without a medical dictionary, while the citation behind each definition keeps the explanation legally defensible rather than paraphrase.
No — it is platform-wide term coverage built into every output. There is no separate glossary to maintain or look things up in: the definitions live on the terms themselves, wherever they appear in a chronology, report, digest, or answer, and they are generated from the record's own clinical context.
Related capabilities.
The outputs these definitions live inside.
Ask the record anything in plain English — every answer cited, every term defined.
ExploreAuto-categorized, source-linked lists of every diagnosis, medication, and procedure in the file.
ExploreColor-coded, page-by-page deposition digest — with the medical terms explained inline.
ExploreSee your own record, readable by anyone.
Upload a single file and get back a cited sample output — with the clinical terms defined inline. Handled under our BAA; never used to train a model.