What is langcare-progress-notes?

A clinical documentation skill that creates daily hospital progress notes from FHIR data, a standard format for exchanging healthcare records. It gathers recent events, observations, laboratory results, fluid balance, medicines, conditions, and pending orders.

Use it to write hospital-day updates with subjective, objective, assessment, and plan sections, and optionally save the note as a healthcare document.

It reduces the manual work of collecting changing inpatient information into one current note.

langcare-progress-notes — Skill for Claude Code and Codex by langcare

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 progress-notes

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/progress-notes/github.svg)](https://agentmods.dev/skills/langcare/langcare-mcp-fhir/progress-notes)

Your own site

<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/progress-notes"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/progress-notes/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/progress-notes"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/progress-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 749 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.00059	$0.00749
Opus 5.5	$0.00024	$0.00300
Sonnet 5.5	$0.00012	$0.00150
Haiku 4.5	$0.00006	$0.00075

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

Security

Grade A, and why

langcare-progress-notes 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/progress-notes/SKILL.md · 63 lines

How it starts

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

Progress Note Writer

When to Use This Skill

Use when a clinician needs a daily inpatient progress note summarizing the patient's hospital course, overnight events, current clinical status, and updated plan.

Clinical Workflow

Use fhir_search to retrieve the current inpatient Encounter (calculate hospital day number)
Use fhir_read to retrieve Patient demographics for note header
Use fhir_search to pull Observation resources (vitals from last 24h with trends, overnight extremes)
Use fhir_search to pull Observation resources (labs from last 24h)
Use fhir_search to pull active MedicationRequest with changes from last 24h (compare authoredOn)
Use fhir_search to pull active Condition resources for problem list
Use fhir_search to pull pending ServiceRequest resources for outstanding orders
Structure as: Date/HD#, Subjective (overnight events, patient-reported symptoms), Objective (vitals, I/O, labs, imaging), Assessment (updated problem list), Plan (per-problem with changes from prior day)
Optionally persist as DocumentReference (LOINC 11506-3)

FHIR Resources

Encounter -- Hospital day calculation from period.start
Patient -- Demographics
Observation -- Vitals (24h with min/max), labs (new results), I/O if available
MedicationRequest -- Current medications with recent changes
Condition -- Active problem list
ServiceRequest -- Pending consults, tests

FHIR Query Examples

Pull 24h Vitals

fhir_search(resourceType="Observation", queryParams="patient=[patient-id]&category=vital-signs&date=ge[24-hours-ago]&_sort=-date&_count=50")

Pull Today's Labs

fhir_search(resourceType="Observation", queryParams="patient=[patient-id]&category=laboratory&date=ge[today]&_sort=-date")

Clinical Guidelines

CMS inpatient documentation requirements
Attending physician must document assessment/plan at least daily
Problem-based daily progress notes preferred for complex patients

Read the full file on GitHub · 63 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 · 63 lines · 59 tokens per session scan A e8b3e62d3fa3

Subscribe to this mod's changes

langcare-progress-notes is a skill published in the GitHub repository langcare/langcare-mcp-fhir (71 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 749 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.

Writing and docs

langcare-progress-notes next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
langcare-progress-noteslangcare/langcare-mcp-fhir	Skill	71	6mo ago	MIT	A	59	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code