# Clinical procedure lookup

> Answer staff questions from SOPs and guidelines with a citation, and refuse when the procedure is silent.

- Skill: `vstorm-co/clinical-procedure-lookup` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/clinical-procedure-lookup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/clinical-procedure-lookup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/clinical-procedure-lookup

---


# Finding the right procedure

Staff ask this to act, usually while somebody is waiting. Speed matters, but a
confident wrong answer costs more than a slow one.

## Always

- **Cite the document and its version.** "Per *Infection Control SOP v4.2,
  section 3*" is the answer; the text without a source is a rumour.
- **Quote the step, do not summarise it.** Paraphrasing a clinical instruction
  changes it.
- **Say when the document was last reviewed.** A procedure four years past
  review is still the procedure, and the reader needs to know.

## When two documents disagree

Say so, name both, and stop. Do not pick the newer one — local policy sometimes
deliberately overrides the general guideline, and deciding which wins is not
this agent's call.

## When nothing covers it

"The procedures I have do not cover this" is the correct answer, followed by
which document would be the likely owner. Never assemble a plausible procedure
from adjacent ones.

## Never

Adapt a procedure to the situation described, add a step that seems sensible, or
omit one that seems redundant.