Structuring Radiology Reports logo

Structuring Radiology Reports

CommunityPopular
maziyarpanahi
structuring-radiology-reports

Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression), lesion measurements and laterality captured, BI-RADS / Lung-RADS assessment categories pulled, or incidental findings and recommended follow-up tracked. Trigger keywords: radiology report, findings, impression, RadLex, DICOM-SR, BI-RADS, Lung-RADS, ACR, laterality, measurement, nodule, incidental finding, follow-up, structured reporting. Pairs after OpenMed: run openmed.analyze_text on the report (Anatomy/Disease/measurement entities), then assemble structured findings. De-identify the report first. Decision-support only — not a diagnostic medical device.

Overview

Publishermaziyarpanahi
Repositoryopenmed
Skill namestructuring-radiology-reports
Stars
5.6K
Forks
708
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by maziyarpanahi on GitHub. Read the source before you install it.

Installation

Install the Structuring Radiology Reports AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/maziyarpanahi/openmed/tree/master/skills/structuring-radiology-reports
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/maziyarpanahi/openmed.git /tmp/openmed
mkdir -p .claude/skills
cp -r /tmp/openmed/skills/structuring-radiology-reports .claude/skills/structuring-radiology-reports
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Structuring Radiology Reports in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Structuring Radiology Reports on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Structuring Radiology Reports is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Structuring radiology reports

A radiology report is prose, but its meaning is structured: a technique, a comparison, a list of findings (each with anatomy, laterality, and a measurement), and an impression that may carry an assessment category (BI-RADS, Lung-RADS) and a follow-up recommendation. This skill turns the narrative into that structure so findings are trackable — especially incidental findings that need downstream follow-up.

OpenMed extracts the anatomy, disease/finding, and measurement spans on-device; this skill organizes them into sectioned, coded findings. It is decision-support, not a diagnostic device — every structured finding must be attributable back to its source sentence for radiologist review.

When to use

  • You have a CT/MRI/X-ray/US/mammography report and need {technique, comparison, findings[], impression} with measurements and laterality.
  • You must capture BI-RADS (breast) or Lung-RADS (lung screening) assessment categories and the recommended action.
  • You need to track incidental findings and the follow-up interval/modality the report recommends.
  • You are mapping findings toward RadLex terms or a DICOM-SR structured report.

Quick start

python
import openmed

report = (
    "TECHNIQUE: CT chest without contrast.\n"
    "COMPARISON: CT 2023-11-02.\n"
    "FINDINGS: A 8 mm solid nodule is noted in the right upper lobe, "
    "unchanged. No pleural effusion.\n"
    "IMPRESSION: 8 mm right upper lobe nodule, stable. Lung-RADS 2. "
    "Recommend annual low-dose CT screening."
)

# 1) De-identify the report on-device first (synthetic example shown).
deid = openmed.deidentify(report, policy="hipaa_safe_harbor")
text = deid.deidentified_text

# 2) Run NER for anatomy / finding / measurement spans.
ents = openmed.analyze_text(
    text,
    model_name="anatomy_detection_superclinical",   # Anatomy category
    output_format="dict",
)["entities"]

# 3) Split sections by header, then attach entities + measurements per finding.
import re
SECTION = re.compile(r"(?im)^(TECHNIQUE|COMPARISON|FINDINGS|IMPRESSION)\s*:")
sections, last, name = {}, 0, None
for m in SECTION.finditer(text):
    if name: sections[name] = text[last:m.start()].strip()
    name, last = m.group(1).upper(), m.end()
if name: sections[name] = text[last:].strip()

structured = {
    "technique": sections.get("TECHNIQUE"),
    "comparison": sections.get("COMPARISON"),
    "findings": _split_findings(sections.get("FINDINGS", "")),   # one per sentence
    "impression": sections.get("IMPRESSION"),
    "measurements": re.findall(r"\b\d+(?:\.\d+)?\s?(?:mm|cm)\b", text),
    "laterality": sorted({w for w in ("right", "left", "bilateral")
                          if re.search(rf"\b{w}\b", text, re.I)}),
    "assessment": (re.search(r"\b(?:BI-RADS|Lung-RADS)\s*\d[A-C]?\b", text, re.I)
                   or [None])[0] if re.search(r"RADS", text, re.I) else None,
    "follow_up": _extract_followup(sections.get("IMPRESSION", "")),
}

_split_findings / _extract_followup are your sentence splitter and a recommendation matcher ("recommend …", "follow-up in N months"); keep each finding tied to its source sentence offsets.

Workflow

  1. De-identify first. openmed.deidentify(report, policy=...); structure from deidentified_text. Patient name, MRN, accession, and dates go before anything is stored or shared.
  2. Split sections by the standard headers (TECHNIQUE, COMPARISON, FINDINGS, IMPRESSION; also HISTORY/INDICATION). Reports vary — fall back to position if headers are missing.
  3. Run analyze_text for anatomy and finding entities; capture measurements ("8 mm", "1.2 cm") and laterality ("right", "left", "bilateral") near each finding.
  4. Build one structured finding per observation: {anatomy, finding, laterality, measurement, change_vs_prior, source_offsets}. "Unchanged", "stable", "increased", "new" capture temporal change against the comparison.
  5. Pull the assessment category (BI-RADS 0-6, Lung-RADS 1-4X) from the impression and the recommended follow-up (modality + interval).
  6. Flag incidental findings — findings unrelated to the exam indication — and route them to a follow-up tracker so they aren't lost.
  7. Map toward RadLex / DICOM-SR if you need coded interoperability, and surface the whole structure to a radiologist for verification.

Hand-off to / from OpenMed

OpenMed's analyze_text returns a dict; result["entities"] items carry text, label, confidence, start, end.

  • From extracting-clinical-entities: Anatomy and Disease/finding entities populate each structured finding; keep offsets so every field traces to a source sentence.
  • From extracting-lab-tables / OCR: if the report is a scan, OCR it first (openmed.multimodal.ocr.ocr), then run NER on the recognized text.
  • From segmenting-clinical-sections: reuse section detection if your reports don't use canonical headers.
  • To building-patient-timelines: dated findings + change-vs-prior feed a longitudinal view (e.g. nodule size over time).
  • To extracting-dicom-metadata: pair the structured findings with the study's DICOM metadata when assembling a DICOM-SR object.
  • De-identify with deidentifying-clinical-text (openmed.deidentify) before any export. Everything runs on-device.

Edge cases & gotchas

  • Negation and uncertainty change meaning. "No pleural effusion" and "cannot exclude metastasis" are findings about absence/uncertainty — don't record them as positive findings. Use resolving-clinical-context (openmed.clinical) for negation/hedging before asserting a finding.
  • Laterality errors are clinically dangerous. "Right" vs "left" must bind to the correct finding; a misattributed side can drive wrong-site decisions. Tie laterality to the nearest anatomy span by offset, not document-wide.
  • Measurements need their unit and axis. "8 mm" vs "0.8 cm" are equal; a bare "8" is ambiguous. Capture the unit; for masses, capture all reported dimensions ("2.1 x 1.4 cm"), not just the first.
  • Assessment categories have controlled value sets. BI-RADS 0-6 and Lung-RADS 1, 2, 3, 4A, 4B, 4X each map to a defined management action — don't invent or round categories; pull the literal value from the impression.
  • Incidental findings get lost. A renal cyst mentioned in a chest CT is the classic missed follow-up. Explicitly separate incidental from indication-related findings and push incidentals to a tracker.
  • The impression is the actionable summary, but findings may contain detail the impression omits — structure both, and prefer the impression for follow-up/assessment.
  • Decision-support disclaimer. This is not a diagnostic medical device; it organizes text a radiologist authored. Every structured field must be reviewable against its source. Do not auto-act on a derived category or follow-up without clinician sign-off.

Standards & references

Frequently asked questions

What does the Structuring Radiology Reports AI skill do?

Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression), lesion measurements and laterality captured, BI-RADS / Lung-RADS assessment categories pulled, or incidental findings and recommended follow-up tracked. Trigger keywords: radiology report, findings, impression, RadLex, DICOM-SR, BI-RADS, Lung-RADS, ACR, laterality, measurement, no...

Why use Structuring Radiology Reports on TypingMind?

Because you install it once and use it with any model. Structuring Radiology Reports is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Structuring Radiology Reports in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/maziyarpanahi/openmed/tree/master/skills/structuring-radiology-reports. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Structuring Radiology Reports?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Structuring Radiology Reports?

As many as you like. As long as a model supports skills, you can use Structuring Radiology Reports with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Structuring Radiology Reports AI skill free?

Yes. It is published on GitHub by maziyarpanahi under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇