What is langcare-discharge-summaries?

A hospital discharge summary writer that compiles a patient's stay, diagnoses, treatments, medicines, follow-up plans, and pending results from FHIR health records. FHIR is a standard format for exchanging healthcare information.

Use it to prepare discharge summaries with admission and discharge details, the hospital course, procedures, diagnoses, discharge medicines, follow-up appointments, pending results, and patient instructions.

It reduces the manual work of collecting information from different parts of a hospital record and organizing it into one discharge document. It also supports checking medicines against those taken on admission.

langcare-discharge-summaries — Skill by langcare/langcare-mcp-fhir

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add langcare/langcare-mcp-fhir --skill discharge-summaries

Clone the repo

git clone --depth 1 https://github.com/langcare/langcare-mcp-fhir

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/discharge-summaries/github.svg)](https://agentmods.dev/skills/langcare/langcare-mcp-fhir/discharge-summaries)

Your own site

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/discharge-summaries"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/discharge-summaries/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/discharge-summaries"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/discharge-summaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 722 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.00722
Opus 5.5	$0.00023	$0.00289
Sonnet 5.5	$0.00012	$0.00144
Haiku 4.5	$0.00006	$0.00072

Measured 2mo ago against content hash ca11addd6c29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

langcare-discharge-summaries scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cma/skills/documentation/discharge-summaries/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Discharge Summary Writer

When to Use This Skill

Use when a clinician needs a comprehensive discharge summary document compiled from the patient's hospital course in FHIR.

Clinical Workflow

Use fhir_search to retrieve the Encounter (admission date, discharge date, reason, attending)
Use fhir_read to retrieve Patient demographics
Use fhir_search to pull Condition resources: admitting diagnosis, discharge diagnoses, complications
Use fhir_search to pull Procedure resources performed during the hospitalization
Use fhir_search to pull active MedicationRequest for discharge medications; compare against admission medications for reconciliation summary
Use fhir_search to pull key Observation results (admission labs, discharge labs, significant findings)
Use fhir_search to pull ServiceRequest resources for pending results and referrals
Use fhir_search to pull scheduled Appointments for follow-up
Assemble discharge summary: demographics, admission/discharge dates, admitting diagnosis, hospital course, procedures, discharge diagnoses, discharge medications, follow-up, pending results, patient instructions
Use fhir_create to persist as DocumentReference (LOINC 18842-5)

FHIR Resources

Encounter -- Admission/discharge dates, reason, attending
Patient -- Demographics
Condition -- Admitting and discharge diagnoses
Procedure -- Inpatient procedures
MedicationRequest -- Discharge medications
Observation -- Key lab results
Appointment -- Follow-up appointments
ServiceRequest -- Pending results, referrals
DocumentReference -- Output: discharge summary

FHIR Query Examples

Pull Encounter

fhir_read(resourceType="Encounter", id="[encounter-id]")

Pull Procedures During Admission

fhir_search(resourceType="Procedure", queryParams="patient=[patient-id]&encounter=[encounter-id]")

Clinical Guidelines

CMS Conditions of Participation require discharge summary within 30 days
Joint Commission: discharge summary must include reason for admission, significant findings, procedures, discharge condition, discharge medications, follow-up instructions, pending results
TJC NPSG.02.03.01: communicate pending test results to outpatient provider

Read the full file on GitHub · 68 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 68 lines · 58 tokens per session scan A ca11addd6c29

Subscribe to this mod's changes

langcare-discharge-summaries is a skill published in the GitHub repository langcare/langcare-mcp-fhir (71 stars, last pushed 6mo ago), licensed MIT. It adds 58 tokens to every session and 722 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Documents

langcare-discharge-summaries next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
langcare-discharge-summarieslangcare/langcare-mcp-fhir	Skill	71	6mo ago	MIT	A	58	Claude Code, Codex
orbit-notionnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	117	Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	2d ago	Apache-2.0	A	123	Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	48	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	68	Claude Code
ppt-reviewOrkas-AI/Orkas	Skill	9.0k	yesterday	MIT	A	2	Claude Code, Codex
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex