Extract the accession number, specimen, gross and microscopic findings, diagnosis, and stains from a pathology report PDF. Extraction only, no interpretation.
The full guide: Specimen, ICD-O diagnosis, and IHC on a pathology report
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
A pathology report is the diagnosis of a tissue or fluid specimen examined under the microscope, not an imaging read or an analyzer result. The extractor reads the accession or case number, the report status (preliminary, final, amended), the specimen type, collection date, anatomic location, and laterality, and the ordering provider and pathologist names — the specimen-centered structure a radiology or lab document does not have.
The clinical history, the gross (macroscopic) description, the microscopic findings, the final diagnosis, the special stains performed, the immunohistochemistry markers and results, the molecular or genetic studies, and the concluding summary each come back as their own field, preserving the report's section structure.
Yes. A specimens table returns each specimen's ID, type, collection date, anatomic location, and laterality; a diagnoses table returns each diagnosis with its ICD code as printed; and a special studies table returns each study's type, name, and result. The tool transcribes codes present on the page — it does not assign or interpret them.
No. It is extraction-only: it captures the text and values already on the report — including the pathologist's stated diagnosis — into structured fields. It does not make a diagnosis, interpret findings, or provide medical advice. The report contains PHI and is handled accordingly.
One PDF up to 10MB and 100 pages. The report is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Export as CSV, XLSX, or JSON.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for clinical and billing teams, or the extraction API if you are building it in.