A patient walks in for a six-month cleaning and casually mentions the crown on number 14 has been a little sensitive since the holidays. You think you remember placing it about two years ago. You think there was a note about deep margin near the distal. The chart says one thing, the radiographs say another, and the gap between the two is where mistakes start.
Most dental practices don't have a clinical-knowledge problem. They have a clinical-context problem. The information exists — it's just spread across the practice management system, a folder of intraoral photos, your handwritten chair-side notes, the lab slip from the crown, and a Post-it on the monitor that says "call about night guard". None of it talks to anything else.
This post is about keeping that context in one private place that you can actually search — and getting an AI assistant to do the cross-referencing your brain shouldn't have to.
What dentists actually need from a notes system
Before getting into the mechanics, the workflow shape matters. Dentists need three things from their notes that a generic notes app rarely provides:
- Per-patient continuity — what happened last visit, what was deferred, what to bring up this time
- Cross-patient pattern recognition — every Class II composite that fell out within a year, every implant case from a particular surgeon
- Operational memory — the running list of things that aren't about a single chart, like supplier issues, the autoclave service log, and the new-hire onboarding checklist
A practice management system handles the first one well enough. It usually handles the second one badly. It barely tries the third. So most dentists end up with a personal scratchpad system bolted on the side, and that scratchpad is the part this post is about. The same shape shows up across regulated work — see AI Notes for Healthcare for the broader clinician version of the same problem.
Markdown pages, one per patient
In Docapybara, every patient gets a markdown page. Not a structured form, not a database row — a plain markdown document where you write notes the way you'd dictate them. You can paste in a treatment plan, list out the consult conversation, drop in a photo, and end with a few bullet points for next visit.
The reason that shape works is that markdown is searchable, copyable, and survives any export you ever need to do. If a patient transfers to another practice and asks for their records, you have a clean text file you can hand off. If your front office needs to read the next-visit notes for tomorrow's schedule, they open the same page you wrote in.
Page nesting goes as deep as you need. A common structure: Patients → Active → Smith, J. with sub-pages for Restorative History, Perio Records, Lab Cases. You don't have to build it that way — many dentists run flat with a single page per patient. Both work. The point is the tool gets out of the way.
A live database of active treatment plans
Plain notes are fine for narrative. But there's some information about a chart that really wants to be a row in a table — open treatment plans, pending lab cases, follow-up calls owed. That's where Docapybara's inline databases come in.
A :::database::: directive embeds a live database directly inside any page. So your morning huddle page can include a table of every active treatment plan with columns for patient, procedure, scheduled date, lab vendor, and status. It's not a separate app to open — the table sits next to your written notes about the day. Six column types are available, which covers what you'd want for clinical tracking.
When the assistant in the workspace updates the table — say, marking a lab case as Returned after you tell it the crown came back — the change is live. Sort by scheduled date and you see the week. Filter by lab vendor and you see which lab is slowing things down.
Recording the consult so the chart doesn't lose what was said
Some of the most valuable detail in a patient encounter is the conversation, not the clinical findings. The patient mentions her teenager grinds his teeth at night. She brings up a budget concern that means the implant case will need to be staged differently. She says her insurance changed in February. Six months later, none of that is in the chart unless you wrote it down at the time.
Docapybara records audio inside the workspace and transcribes it with speaker labels — so when you play back the consult, you can see what you said and what the patient said separately. That's useful when you're trying to remember the exact wording of a treatment-plan acceptance, or when a hygienist hands off a perio re-eval to you and you want the patient's actual words about the home-care change.
You don't need the transcript for every appointment. But for new-patient consults, treatment-plan presentations, and any conversation with an unhappy outcome, having the audio + transcript on the patient page is a different level of context than what fits in a chart note field.
Treatment context across visits, not just within them
Here's where the AI part starts paying for the whole setup. Capy, the assistant in Docapybara, has 27 tools and the habit of reading across your entire vault when you ask a question. So you can ask things like:
- "Pull every patient with a posterior composite I placed in the last 18 months who hasn't been back yet." The agent searches your patient pages, returns a list with the relevant visit dates and any notes you wrote about each restoration.
- "What did I tell Mrs. Garcia at her last visit about the night guard?" It finds her page, locates the consult notes from that visit, and quotes them back to you.
- "Which of my implant cases from Dr. Chen's referrals had any post-op complications?" It scans referral notes, surgical notes, and follow-up entries — and gives you the cases with the relevant detail.
This isn't anything magical. It's just the agent reading the same notes you wrote, doing the cross-reference faster than you could open twelve charts in a row.
Old PDFs of patient records can come along
Most established practices have a folder of older patient records in PDF form — referrals, scanned consult forms, lab slips, perio charts from the prior PMS. Those are useful as historical reference and a hassle to actually use, because they're not searchable as text.
Drop the PDFs into Docapybara and the conversion pipeline turns each one into markdown the agent can read. So when you ask "what did the periodontist's referral letter say about the gum graft on patient X?", the agent pulls the relevant excerpt back as text. The original PDF is still one click away when you need to see the actual document.
This matters most for legacy data — the years of records you accumulated before you had a working notes system. Instead of those records being a closed archive, they become part of the searchable vault. The institutional memory of the practice gets a lot deeper without anyone re-typing anything.
Operational notes that aren't about a single patient
A practice runs on more than charts. It runs on supplier orders, equipment maintenance schedules, hygienist re-care templates, end-of-day cash-out protocols, the new-employee onboarding packet, and a hundred other operational details. Those don't fit in a PMS, and they usually live as a mess of Word docs in a shared drive.
In Docapybara, those operational notes are just more markdown pages — nested however your practice is shaped. A common layout: Operations → Equipment → Autoclave Service Log, with the log itself as an inline database tracking date, technician, parts replaced, next-due. Or Operations → Front Office → Insurance Verification SOP as a written page, with a separate database tracking which payers have pending verification calls.
When you ask the assistant "when's the autoclave next due for service?", it reads the database row and tells you. When you onboard a new front-desk hire, you point them at one nested folder and they have everything — written process, live trackers, and the patient-context conventions the practice uses. The SOP side of this overlaps with Standard Operating Procedures, Without the Wiki Maintenance Tax, and the new-hire packet side overlaps with AI Notes for Customer Onboarding Documentation.
This is where the workspace stops being just a notes app and starts being the operational brain of a small practice. One person, one vault, every category of practice memory in the same searchable place — the agent-acts-on-docs idea behind that is laid out in Claude Code for Documents.
A note on regulated workflows: a notes app is a place to keep your own structured private notes. It's not a substitute for a clinical-records system that handles the regulatory side of patient charts. Use this for the layer of context, planning, and operations that lives around your charts — not as the chart of record.
Try Docapybara free
The fastest way to feel the difference is to try it on next week's schedule. Open Docapybara, create a page for tomorrow morning's first three patients, paste in whatever notes or photos you've got from their last visit, and ask the agent for a one-paragraph summary of what to bring up at the chair. Five minutes of setup, and you'll see whether having the context next to you instead of buried in a chart actually changes the visit.
Try Docapybara free — bring your messiest patient-context notes, a few legacy PDFs, and one operational SOP you've been meaning to clean up. See how the workspace handles them.