Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Documenting Procedure Notes

ASecurity

Creates structured procedure documentation with indications, technique, findings, and complications. Use when documenting inpatient procedures, recording procedural details, or writing procedure notes.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
securitydocumentation

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill documenting-procedure-notes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Documenting Procedure Notes?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Documenting Procedure Notes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-documenting-procedure-notes/badge)](https://www.skillsdirectory.com/skills/lev-os-documenting-procedure-notes)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: documenting-procedure-notes
description: Creates structured procedure documentation with indications, technique, findings, and complications. Use when documenting inpatient procedures, recording procedural details, or writing procedure notes.
tags:
  - documentation
  - hospital-medicine
  - patient-care
metadata:
  author: casemark
  practice_areas:
    - Hospital Medicine
    - Internal Medicine
  document_types:
    - Clinical Documentation
  skill_modes:
    - Documentation
---

# Documenting Procedure Notes

Creates structured procedure documentation with indications, technique, findings, and complications for inpatient bedside procedures.

## Why This Skill Exists

Procedure notes serve three critical functions: clinical communication (informing subsequent providers about what was done), medicolegal documentation (the note is the definitive record if complications arise), and billing justification (CPT coding requires specific documentation elements). The Joint Commission requires that procedure notes be completed immediately after the procedure, and CMS requires documentation of informed consent, indication, technique, findings, and complications for reimbursement.

Common hospitalist bedside procedures — central venous catheter (CVC) insertion, lumbar puncture (LP), thoracentesis, paracentesis, arthrocentesis, and intubation — each have procedure-specific documentation requirements. Incomplete procedure notes are the #1 reason for denied procedure charges and a leading source of malpractice vulnerability when complications occur. A well-documented procedure note that includes real-time findings and a normal complication-check is the strongest defense in litigation.

---

## Checkpoint A: Pre-Draft Intake (Mandatory)

Before documenting any procedure, confirm:

1. What **procedure** was performed? *(Default: Specify exact procedure name and CPT code)*
2. What was the **clinical indication**? *(Default: Must match documented clinical need in progress notes)*
3. Was **informed consent** obtained and documented? *(Default: Verify signed consent form exists)*
4. Who **performed** the procedure and who **supervised** (if trainee)? *(Default: Document names and roles)*
5. Was a **time-out** completed per Universal Protocol? *(Default: Required for all invasive procedures)*
6. What **imaging guidance** was used, if any — ultrasound, fluoroscopy? *(Default: Document or state "landmark technique")*
7. Were **specimens** sent — and to which labs (microbiology, cytology, chemistry)? *(Default: Document specimen disposition)*
8. What **post-procedure monitoring** was ordered? *(Default: Per procedure-specific protocol)*

### Documents to Request

- Signed informed consent form
- Pre-procedure labs (coagulation studies, platelet count)
- Pre-procedure imaging (if relevant — e.g., chest X-ray before thoracentesis)
- Time-out documentation
- Ultrasound images (if US-guided)
- Specimen labels and lab order confirmations
- Post-procedure imaging orders (e.g., chest X-ray post-CVC or thoracentesis)

---

## Step 1: Use the Standard Procedure Note Template

Every procedure note must contain these elements in order:

```
PROCEDURE NOTE

Date/Time: [MM/DD/YYYY HH:MM]
Procedure: [Full procedure name]
Operator: [Name, credentials]
Supervising physician: [Name, if applicable — required for resident procedures]
Assistant(s): [Name(s) and role(s)]

Indication: [Clinical reason with supporting data]
Consent: [Informed consent obtained from (patient/surrogate); risks, benefits, 
          alternatives discussed; patient verbalized understanding; 
          signed consent on file]
Time-out: [Completed per institutional Universal Protocol — correct patient, 
           correct procedure, correct site confirmed]

Pre-procedure: [Relevant vitals, labs, positioning, site prep]
Anesthesia: [Type, agent, volume — e.g., "1% lidocaine, 10 mL local infiltration"]
Technique: [Step-by-step description of what was done]
Imaging guidance: [US-guided / fluoroscopy / landmark — specify probe, views]
Findings: [What was found — fluid character, CSF appearance, catheter position]
Specimens: [Type, volume, lab destination]
Complications: [None / describe if any — include hemodynamic changes]
Estimated blood loss: [If applicable]
Post-procedure: [Patient tolerance, post-procedure vitals, orders placed]
Post-procedure imaging: [Ordered / Not indicated — with rationale]

Disposition: [Patient returned to [unit] in stable condition]
```

---

## Step 2: Procedure-Specific Documentation Requirements

### Central Venous Catheter (CVC) Insertion
- **Site**: IJ / Subclavian / Femoral — document laterality
- **Catheter**: Type, size (French), number of lumens, length inserted
- **Guidance**: Ultrasound — document vein visualization, compressibility, confirmation of wire in vein
- **Confirmation**: Aspiration of dark venous blood from all ports, transduced waveform, or post-placement chest X-ray
- **Chest X-ray**: Mandatory for IJ and subclavian; document tip position (SVC-RA junction)
- **Complications to document**: Pneumothorax, arterial puncture, hematoma, arrhythmia

### Lumbar Puncture
- **Position**: Lateral decubitus (specify side) or sitting
- **Level**: L3-L4 or L4-L5 interspace
- **Opening pressure**: Document in cm H2O (normal 6-20 cm H2O)
- **CSF appearance**: Clear, cloudy, xanthochromic, bloody — document serially by tube
- **Tubes sent**: Tube 1 (cell count, differential), Tube 2 (protein, glucose), Tube 3 (culture, gram stain), Tube 4 (cell count for traumatic tap comparison)
- **Closing pressure**: If measured

### Thoracentesis
- **Site**: Posterior axillary line, one interspace below fluid level
- **Guidance**: Ultrasound with documentation of effusion depth and diaphragm location
- **Volume removed**: Document in mL — limit to 1500 mL to prevent re-expansion pulmonary edema
- **Fluid appearance**: Serous, bloody, purulent, milky
- **Specimens**: Cell count, LDH, protein, glucose, pH, culture, cytology
- **Light's criteria assessment**: Document intent to evaluate exudate vs. transudate

### Paracentesis
- **Site**: LLQ preferred (left of midline, lateral to rectus muscle)
- **Guidance**: Ultrasound with fluid pocket measurement
- **Volume removed**: Document; if > 5L, document albumin replacement (6-8g per liter removed)
- **Fluid appearance**: Straw-colored, bloody, cloudy, milky
- **Specimens**: Cell count with differential (SAAG calculation requires serum albumin), culture (inoculate blood culture bottles at bedside), total protein, glucose

---

## Step 3: Post-Procedure Documentation

Within 1 hour of procedure completion, verify and document:

1. **Patient status**: Vital signs stable, no immediate complaints
2. **Post-procedure imaging**: Ordered and result reviewed (CVC chest X-ray, post-thoracentesis X-ray if indicated)
3. **Specimen tracking**: All specimens labeled and sent to correct lab
4. **Complication monitoring orders**: Frequency of vital checks, site checks, neurological checks (post-LP)
5. **Nursing communication**: Procedure completed, monitoring orders active, when to call physician

---

## Checkpoint B: Post-Draft Alignment (Mandatory)

Before finalizing any procedure note:

1. Does the **indication** clearly justify the procedure based on the clinical scenario?
2. Is **informed consent** documented with specific risks, benefits, and alternatives?
3. Does the **technique** section provide enough detail for another physician to understand exactly what was done?
4. Are **findings** documented objectively — not just "within normal limits"?
5. Is there a clear **complication** statement (even if "no complications")?

---

## Quality Audit

- [ ] Procedure note completed within 1 hour of procedure (Joint Commission standard)
- [ ] All mandatory elements present (indication, consent, time-out, technique, findings, complications)
- [ ] Operator and supervisor names documented with credentials
- [ ] Informed consent form is signed and in the chart
- [ ] Time-out documentation confirms correct patient, procedure, site
- [ ] Imaging guidance is documented (type of guidance or "landmark")
- [ ] Specimen disposition is documented (lab, tubes, volumes)
- [ ] Post-procedure imaging ordered when indicated
- [ ] Complications documented explicitly (even if none)
- [ ] Post-procedure monitoring orders are in place
- [ ] Note supports CPT code billing requirements
- [ ] Laterality is documented for all applicable procedures
- [ ] Estimated blood loss documented when applicable

---

## Guidelines

- Write the procedure note immediately after the procedure — delay degrades accuracy and creates medicolegal risk
- Never document consent as "obtained" without specifying what was discussed — list risks, benefits, alternatives
- Always document the use or non-use of ultrasound guidance — this affects CPT coding (76937 for US guidance)
- For trainee procedures, the supervising physician must document their presence and level of involvement per CMS Teaching Physician rules
- Quantify findings: "450 mL of serous pleural fluid removed" is better than "fluid removed"
- If a complication occurs, document it factually without blame or speculation — describe what happened and what was done in response
- Store ultrasound images in the medical record (PACS or EMR) per institutional policy
- Post-procedure orders must include specific parameters for when to notify the physician (e.g., "Call if SBP < 90, HR > 110, O2 sat < 92%, or new respiratory distress")

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Springboot Security

Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。

2456590 votes

Security Review

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

2456590 votes

Paperclip Task Bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

805540 votes

Summarize Status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

805540 votes

Paperclip Evals

Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.

805540 votes
View all in security →