Two vaults, not one

Hospital machine

Stays put. Not synced to a consumer cloud. This is where a draft might still be dangerous. When the teaching point is clear, you rewrite it without identifiers into the other vault. You do not copy the file across.

Teaching vault

De-identified from the first sentence. This is the one Obsidian Sync, a colleague, or an AI project is allowed to see. If you would not put the note on a projector in a closed conference, it is not done yet.

The folder tree

Numbers keep the sort stable when you rename a word. Don't invent a 15 later. Archive a folder instead of nesting forever. Paste this into the teaching vault and create the folders. Empty is fine.

Folder tree
00 Inbox
10 Practice
  Cases
  Techniques
  Complications
20 Research
30 Teaching
  Talks
  Video scripts
40 AI
  Prompts
  Tool notes
  Decisions
50 Admin
Templates
assets
_Archive
  • 00 Inbox — capture. It should get empty.
  • 10 Practice — cases, technique hubs, complications. The part fellows actually need.
  • 20 Research — questions, outlines, reading. Not a dump of every PDF you have ever saved.
  • 30 Teaching — talks and video scripts, linked back to a technique.
  • 40 AI — prompts and a note about what a model got wrong. Judgments live here so you don't relearn them.
  • 50 Admin — the boring stuff that is still yours.
  • Templates and assets — machinery, not content.
  • _Archive — cold storage. Search still finds it. Your eyes don't have to.

Names and properties

Name the file the way you would say it out loud: “Posterior urethroplasty — teaching outline.” Not Untitled 12, not a patient initial, not a date that pins a case.

A property is the small field block at the top of a note. Four is enough: type (case, technique, prompt, video, decision), procedure, status (draft, teaching, published), and phi. In the teaching vault, phi is always none. That line is a promise you can see, not a lock. The lock is that you never typed the identifier.

Teaching case
---
type: case
procedure:
status: draft
phi: none
---

# 

## The decision
One sentence. What was actually in question.

## What you can see
Only findings you are willing to teach. No names, MRN, dates of birth, or rare combinations.

## What you did
The maneuver, in order.

## What you would do differently
Write this while it is still uncomfortable.

## Clip
Link the video note. Say what the clip does not show.
Video note
---
type: video
procedure:
status: draft
phi: none
length:
---

# 

## Shows

## Does not show

## Decision point

## Narration script

## Export
file:
preset: web-1080

Handing the setup to a colleague

Send a chapter, not your vault. Ask how much they already know about the tools and about note-taking before you generate a primer for them. Do not assume.

  • Write the primer for that one person. Don't name other people you have sent it to, and don't leave a footer about whose notes it was patterned on.
  • If you include a terminal command, start from home and cd into the vault folder. Don't assume their terminal is already sitting in the right directory.
  • Never attach a vault that might still contain an identifier “just so they can see the structure.” Send the empty tree.

Mark this chapter

Saved on this browser. Not an account.

0 of 4 marked on this browser

Questions in this chapter

What folders should a surgeon's vault have?

Short answer

Inbox, practice, research, teaching, AI notes, admin, templates, assets, archive. Number the top level so the sort never depends on clever names.

  1. Paste the tree from the vault chapter and make the folders, empty.
  2. Technique notes are hubs. Cases and videos link to them.
  3. Don't add a new top-level folder because one note feels special. Put it in practice or archive it.

Read it in The vault

How do I keep patient information out of notes I might show an AI?

Short answer

Rewrite the lesson into a separate teaching vault with the chart closed. Don't copy the hospital note and delete the header.

  1. Hospital drafts stay on the hospital machine, unsynced.
  2. The teaching note starts from the template, phi set to none.
  3. No names, MRNs, dates of birth, faces, or rare story-plus-date combinations.
  4. If you wouldn't project it, it is not ready for a model.

Read it in The vault

What goes at the top of a teaching case?

Short answer

The decision, in one sentence, under four properties: type, procedure, status, and phi: none.

  1. Then what you can see, what you did, and what you would do differently.
  2. Link the clip and write what the clip does not show.
  3. Write it the day it happened, from memory.

Read it in The vault

How should I name files?

Short answer

Plain speech, procedure plus the job of the note. No initials, no case dates, no Untitled.

  1. Good: “Appendiceal ureteroplasty — bailout.”
  2. Bad: “Case 4-12 final FINAL.”
  3. Video files follow the same rule: procedure-maneuver-1080.mp4.

Read it in The vault

A colleague wants my system. What do I send?

Short answer

One chapter and an empty folder tree. Not your vault. Ask what they already know before you write the primer.

  1. Write it for that one reader. Don't name other recipients.
  2. If you include commands, start with cd to their vault. Don't assume the terminal is already there.
  3. Don't attach notes “so they can see the structure.”

Read it in The vault

What is a property, and do I need Dataview?

Short answer

A property is a field at the top of the note, like status or procedure. You don't need Dataview until those fields can answer a question you actually ask.

  1. Use type, procedure, status, and phi.
  2. Search and the quick switcher cover the first months.
  3. Add Dataview when you want a list such as every draft video for one procedure.

Read it in The vault