langcare-problem-list-audit

langcare-problem-list-audit is a skill for Claude Code, Codex from langcare/langcare-mcp-fhir. It costs 67 tokens per session (758 once invoked), scanned A, original, MIT.

A clinical record review that checks whether a patient’s active diagnoses match their medicines, lab results, and recent visit diagnoses.

In plain words
What is it for?
Use it to audit and clean up a patient’s problem list using medication records, laboratory results, and encounter history.
Why use it?
It helps find missing diagnoses, outdated conditions that should no longer be active, and diagnosis coding mismatches in the patient record.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to audit and clean up a patient’s problem list using medication records, laboratory results, and encounter history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/langcare/langcare-mcp-fhir/problem-list-audit
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 problem-list-audit
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.

agentmods badge for langcare-problem-list-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/problem-list-audit/github.svg)](https://agentmods.dev/skills/langcare/langcare-mcp-fhir/problem-list-audit)
Your own site
<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/problem-list-audit"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/problem-list-audit/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.

agentmods 80×15 button for langcare-problem-list-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/langcare/langcare-mcp-fhir/problem-list-audit"><img src="https://agentmods.dev/badge/skills/langcare/langcare-mcp-fhir/problem-list-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 758 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00758
Opus 5 $0.00034 $0.00379
Sonnet 5 $0.00013 $0.00152
Haiku 4.5 $0.00007 $0.00076

Measured 12d ago against content hash c9c6a95d5297, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

langcare-problem-list-audit 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 12d 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/patient-data/problem-list-audit/SKILL.md · 61 lines

How it starts

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

Problem List Audit

When to Use This Skill

Use when a clinician needs to validate the accuracy and completeness of a patient's active problem list by cross-referencing against medications, lab results, and encounter history.

Clinical Workflow

  1. Use fhir_search to pull all Condition resources (active, resolved, inactive) for the patient
  2. Use fhir_search to pull active MedicationRequest resources -- infer expected diagnoses from medications (e.g., metformin implies diabetes, levothyroxine implies hypothyroidism)
  3. Use fhir_search to pull recent Observation (laboratory) results -- infer conditions from abnormal lab patterns (e.g., elevated HbA1c implies diabetes, elevated TSH implies hypothyroidism)
  4. Use fhir_search to pull recent Encounter resources and their associated Condition resources (encounter diagnoses) to find conditions documented in visits but missing from the problem list
  5. Cross-reference all sources: flag medications without a supporting active problem, lab patterns without a corresponding diagnosis, encounter diagnoses not on the active problem list, and active problems with no supporting evidence in recent encounters/medications/labs

FHIR Resources

  • Condition -- Problem list entries with clinicalStatus, verificationStatus, code (ICD-10/SNOMED), onset, abatement
  • MedicationRequest -- Active medications implying diagnoses
  • Observation -- Lab results with patterns suggesting undiagnosed conditions
  • Encounter -- Recent visits with encounter-specific diagnoses

FHIR Query Examples

Pull All Conditions

fhir_search(resourceType="Condition", queryParams="patient=[patient-id]&_count=200")

Pull Active Medications

fhir_search(resourceType="MedicationRequest", queryParams="patient=[patient-id]&status=active&_count=100")

Pull Recent Encounter Diagnoses

fhir_search(resourceType="Encounter", queryParams="patient=[patient-id]&date=ge[12-months-ago]&_sort=-date&_count=50")

Clinical Guidelines

  • CMS requires accurate problem list maintenance for quality reporting and risk adjustment (HCC coding)
  • ICD-10 coding specificity requirements: prefer specific codes (E11.65 T2DM with hyperglycemia) over unspecified (E11.9)
  • SNOMED CT preferred for clinical documentation; ICD-10-CM required for billing

Read the full file on GitHub · 61 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.

  1. 12d ago First seen · 61 lines · 67 tokens per session scan A c9c6a95d5297

Subscribe to this mod's changes

langcare-problem-list-audit is a skill published in the GitHub repository langcare/langcare-mcp-fhir (55 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 758 once invoked, about $0.0003 per session on Opus 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.

Related

Other skills, from other repositories

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

matlab

Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.

K-Dense-AI/scientific-agent-skills · 42 tokens

phylogenetics

Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.

K-Dense-AI/scientific-agent-skills · 68 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens