How to Log Procedures for Credentialing: a Practical Guide

For residents, NPs, PAs, and nurses · Written by an emergency physician

At some point — credentialing, privileging, a new job, a fellowship application — someone will ask you for your procedure numbers. The people who suffer at that moment are the ones reconstructing a year of central lines from memory. The people who don't are the ones with a log. Here's what a defensible log looks like.

What committees actually ask for

Requirements vary by institution, but nearly every privileging request boils down to the same fields:

What not to put in your log

No patient identifiers. Ever. Your procedure log needs counts, dates, roles, and technique details — it does not need names, MRNs, or clinical details that identify a patient. A log with PHI in it is a liability you carry on a personal device; a de-identified log is just your professional record. If you attach ultrasound images for documentation, strip the banner data first.

The habits that make a log survive

Spreadsheet vs. purpose-built app

A spreadsheet works if you're disciplined — the failure mode isn't the format, it's the friction. The advantages of a purpose-built logger are speed (seconds at the bedside), structure (role and ultrasound guidance as real fields), and output (a signable summary instead of raw rows).

That's why I built ProcVault — an iPhone app with two-tap bedside logging, ultrasound-guidance tracking, progress toward your own targets, and attestation PDFs with signature lines. The core logging is free, and everything stays on your device: no account, no server, "Data Not Collected" on the App Store privacy label. Search ProcVault on the App Store.