clinical-reports

Overview of clinical-reports skill

clinical-reports is a specialized writing skill for producing clinical documentation that is structured, precise, and suitable for real-world medical workflows. Use the clinical-reports skill when you need clinical reports for publication, diagnosis, trial documentation, or patient records and you want more than a generic prompt: you want a workflow that respects format, terminology, and compliance constraints from the start.

What clinical-reports is best for

This skill fits users writing case reports, radiology/pathology/lab reports, clinical study reports, SOAP notes, H&P notes, and discharge summaries. It is especially useful when the output must be de-identified, defensible, and aligned with standards such as CARE, ICH-E3, HIPAA, FDA, and ICH-GCP.

Why this skill is different

The main value of clinical-reports is not just “write medically.” It pushes you toward report types, section order, and compliance-aware phrasing that reduce rework. That matters when the reader is a clinician, reviewer, regulator, or chart auditor rather than a general audience.

Who should install it

Install the clinical-reports skill if you routinely draft or edit clinical content and need a repeatable way to turn notes, findings, and trial data into polished report text. It is a strong fit for medical writers, researchers, clinicians, and documentation teams. It is a weaker fit if you only need a one-off plain-language summary with no formatting or standards pressure.

How to Use clinical-reports skill

Install and load the skill

Use the documented install flow for your environment, then open the skill files before drafting. The repository indicates the skill path under scientific-skills/clinical-reports, so treat this as the working package, not a standalone prompt. Start with SKILL.md, then read references/README.md to see the report families, templates, and supporting standards the skill expects you to use.

Give the skill the right input

For best clinical-reports usage, provide four things up front: report type, audience, source material, and constraints. For example: “Draft a CARE-style case report for a dermatology journal from these de-identified notes; preserve chronology, avoid diagnosis overstatement, and flag missing consent details.” That is better than “write a clinical report” because it tells the skill what structure and level of evidence it should produce.

Suggested workflow for better output

Start by selecting the report class, then ask for a skeleton before a full draft when the source material is messy. For example, request a section outline for a discharge summary, confirm missing data, then ask for the final version. This reduces hallucinated details and helps the skill stay aligned with the clinical record.

What to read first in the repo

For clinical-reports install and usage, prioritize SKILL.md and references/README.md. The reference file points to the highest-value guidance on case reports, diagnostic standards, trial reporting, patient documentation, regulatory compliance, terminology, and templates. If you are deciding whether the skill fits your task, those two files give faster signal than scanning the whole tree.

clinical-reports skill FAQ

Is clinical-reports only for formal publications?

No. The clinical-reports skill covers both publication-grade writing and operational documentation. You can use it for CARE case reports, but also for SOAP notes, H&P notes, discharge summaries, and trial-related reports where structure and accuracy matter.

How does it differ from a normal prompt?

A normal prompt may produce acceptable prose, but clinical-reports is designed to keep the report type, standards, and compliance expectations explicit. That lowers the chance of missing required sections, mixing narrative styles, or exposing sensitive information inappropriately.

Is clinical-reports beginner friendly?

Yes, if you can describe the report goal and supply source notes. You do not need deep familiarity with every standard to start, but the quality improves when you state the target format, intended use, and any constraints such as de-identification or institution-specific style.

When should I not use it?

Do not use clinical-reports if you need legal advice, direct medical diagnosis, or a consumer-friendly health explanation with no formal structure. It is also a poor fit when the input data is too incomplete to support objective reporting and you are not ready to review missing facts carefully.

How to Improve clinical-reports skill

Lead with report type and standards

The fastest way to improve clinical-reports output is to name the exact document class and governing standard. Examples: “ICH-E3 clinical study report,” “CARE case report,” “radiology impression,” or “SOAP progress note.” This prevents the model from blending report conventions and improves section-level accuracy.

Provide source notes in clinical language

The skill performs better when inputs are organized, dated, and de-identified. Instead of a free-form paragraph, give bullet notes like chief complaint, exam findings, labs, interventions, and outcome. For clinical-reports for Report Writing, that format gives the model enough structure to produce a cleaner narrative without inventing transitions.

Watch for common failure modes

The most common problems are over-interpretation, missing chronology, and unsupported certainty. If the first draft sounds too definitive, ask for more cautious phrasing, explicit limitations, and a separate “missing data” list. If privacy matters, instruct the skill to remove names, dates, locations, and other identifiers before finalizing.

Iterate with tighter revision prompts

After the first draft, improve the result by asking for one targeted revision at a time: strengthen the discussion section, align terminology with SNOMED-CT/LOINC/ICD-10 if relevant, or convert a narrative into a journal-ready case report. This is usually more effective than asking for a full rewrite, because it preserves the parts of the report that already fit the intended clinical use.