The patient calls at 4:47 PM. She's been on hold with her insurer for an hour, the auth code she was promised yesterday hasn't been faxed over, and the procedure is on the book for tomorrow morning at 7:30. The chart in your EHR shows her demographics, the procedure, and the order. It does not show that this is the third call this week, that the insurer's representative gave a different name each time, or that her daughter — listed as the contact — is the person who actually returns voicemails.
The clinical record is for clinical decisions. The conversational thread that surrounds a patient — coordination, communication, the texture of working with this particular person — usually lives in a sticky note, a sent-items folder, or whoever's memory happens to be in the room when the patient calls back.
This post is for the people whose job is the thread, not the chart: front-desk coordinators, billing specialists, care navigators, schedulers, intake teams, social workers, patient-experience leads. The scope is your own internal working notes. It's not the medical record, and the boundary between the two is a workflow decision the practice or organization makes — usually with the clinician's input.
What non-clinical patient documentation actually needs
The shape is different from a SOAP note. The work is to remember:
- Who this person is in their own words — that they prefer text over phone, that their daughter handles paperwork, that they once mentioned a transportation barrier
- What the running issues are — the open auth, the pending records request, the unresolved billing dispute, the appointment that needs to be rescheduled when the lab comes back
- What you said and what they said back — the texture of the last three calls, the commitments made on each side
- What's owed and by whom — the call you owe back tomorrow morning, the form that's still missing, the payment plan you proposed and they're still considering
- The cross-patient pattern — every patient flagged for the same insurance carrier issue, every family that's working with the same outside specialist
Most front offices try to hold all of this in their working memory and a folder of half-finished sticky notes. It mostly works until it doesn't, and the moment it fails is usually the moment a patient is on the phone needing a fast answer. Adjacent shapes for the clinical side are in AI Notes for Healthcare and AI Notes for Dentists.
A page per patient, scoped to your work
In Docapybara, every patient who needs a coordination thread gets a markdown page in your private workspace. Title it with their name and the relevant identifier — usually the chart number or the case ID — so it cross-references to the chart system without duplicating it.
Inside the page is a running log. Each entry is dated, attributed (if multiple people use the workspace), and short — two or three sentences capturing what was discussed and what the next step is. The latest entry sits at the top so you read the most recent context first.
A common shape:
## 2026-04-25 — auth follow-up
Spoke with Maria at Anthem. She confirms the auth was approved
yesterday but flagged it had not been faxed to our office. She is
re-sending today. Patient called at 4:47 to confirm. Told her to
call back at 8 AM if not received.
## 2026-04-23 — auth status
Initial call from patient asking about status. Anthem rep "Jeff"
gave reference number REF-887421 and said decision pending. Patient
preference: text > phone. Daughter (cell on file) actually returns
messages.
Plain markdown. Searchable, copyable, exportable. If the patient transfers to another practice and the medical chart is released, you can review your coordination notes separately and decide what's appropriate to share. The boundary between this and the chart stays in your hands.
The agent reads across your whole patient list
Capy, the assistant inside the workspace, reads across your accumulated notes when you ask. The sort of question a front office actually has to answer in a moment:
- "Which patients are still waiting on auths I called about last week?" — the agent scans the recent notes and lists them
- "What did we tell the Garcia family about the rescheduled appointment?" — finds the page, quotes the relevant entry
- "Pull every patient flagged for the Anthem prior-auth backlog from this month and what stage each one is at." — cross-page retrieval, returns a list
The clinical decisions stay with the clinician. The coordination work — the part of patient care that's about communication and follow-through — gets vastly easier when the workspace remembers what you told the patient on Tuesday by the time they call back on Friday. The agent-acts-on-docs shape behind this is described in Claude Code for Documents.
A live database of what's outstanding
A :::database::: directive embeds an interactive database directly inside any markdown page. The most useful place to put one in a front office: a single page called Open Loops, with rows for every outstanding action across every patient.
Six column types cover the work: text, number, date, select, checkbox, link. A typical Open Loops board looks like:
| Patient |
Owed |
Due |
Owner |
Status |
Last Note |
| Garcia, M. |
Auth re-fax follow-up |
2026-04-26 |
front desk |
Waiting |
2026-04-25 |
| Chen, R. |
Records request to outside cardiology |
2026-04-28 |
care coord |
Sent |
2026-04-22 |
| Patel, S. |
Payment plan proposal callback |
2026-04-29 |
billing |
Proposed |
2026-04-24 |
Sort by due date, you see the day. Filter by status, you see what's stuck. When you ask the agent "what's owed today and what's overdue?", it reads the database and answers. When you finish a call, you tell the agent "mark Garcia auth as resolved and add a note that auth was received at 7:15 AM". Done.
The same database lives next to the prose context — the why of each row sits in the surrounding page text, the what sits in the table.
Recording difficult conversations so the texture survives
Not every interaction needs a recording. Some do. The conversation where the patient is explaining a complicated insurance situation. The intake interview with a family in crisis. The discharge planning call that involves three outside agencies. The detail in those conversations is exactly the texture that gets lost when you try to remember it three days later from a sentence in your notes.
Docapybara records audio inside the workspace and transcribes with speaker labels — so when you replay the call, you can see what was said by whom. The transcript drops on the patient's page. Later when the patient calls back, the conversation is searchable text, not a half-remembered impression of a Wednesday afternoon. The recording question is a workflow choice for your practice — what's appropriate to record, what consent looks like, what gets retained, what gets purged. Make that decision before you record. The workspace just holds whatever you decide to capture.
Old PDFs and faxes count too
A front office accumulates PDFs by the dozen — auth forms, records requests, insurance correspondence, intake packets, signed consents. They're useful when findable and a problem when not.
Drop the PDFs into the workspace. Each one is converted to markdown, so the agent can read across all of them. When you ask "what did the prior insurance authorization say about the date range?", it pulls the answer as text and points to the file. The original PDF is one click away when you need to see the signed version.
For a billing coordinator with three years of EOBs sitting in folders, this is often the single most useful afternoon of setup. The accumulated correspondence becomes searchable instead of staying locked in PDFs nobody can find.
Cross-patient patterns the front office actually sees first
Front-office staff often see operational patterns before anyone else does. Every patient with this carrier needs a second fax. The new EHR module always loses the chief-complaint field on certain templates. The pharmacy partner started routing refill requests through a different number last month and nobody told the practice.
The page-per-patient shape only captures one patient at a time. The pattern needs a second layer — an Operational Issues section with a page per recurring problem, plus an inline database of which patients hit it. When the agent reads across the patient pages and the issues database together, you can ask "how many patients this month hit the Anthem fax issue, and what was the resolution path that worked?" The answer is in your own notes, surfaced.
This is the layer that turns front-office coordination from individual heroics into something the practice can actually learn from. The cross-cutting SOP layer is covered in Standard Operating Procedures, Without the Wiki Maintenance Tax.
Try Docapybara free
The fastest test: open Docapybara, create a page for the three patients who are most actively in your working memory right now — the ones you'd call back tomorrow morning before checking the schedule. Paste in whatever notes, emails, or call summaries you have on each. Add an Open Loops database for what's outstanding. Try Docapybara free, bring the messiest active patient threads and one stack of EOBs you've been meaning to reconcile, and see how the workspace holds the thread.