For visitors who'd rather read than walk.
# Small dental practice — the multi-entity attestation chain
You're a solo dentist with a perio-and-implants focus, working with
an outside endodontist, an outside CT imaging center, and an
out-of-state lab on every implant case. Staff is small. Implant
pre-auths land on the front-desk and on your evenings.
The appeal you wrote on a Saturday afternoon was the right answer,
but you should not have had to write it.
Thirty minutes between patients. Mr. Almeida's implant pre-auth is
the next packet on your desk — single-tooth at site #19, scheduled
for next month. You bookmark the URL the peer at the AGD chapter
mentioned and open it.
The walk is the test drive — no install required.
Four real install paths exist when you decide to act. For a solo
practice coordinating across three to five outside entities per case,
the order is:
Subscribe to a regional operator. A HIPAA-compliant operator
serving dental practices runs the chain; you and each of your
referral partners configure your own attestation surfaces; everyone's
records flow through their own sovereign space. The operator handles
the multi-entity scaffolding without forcing your endodontist or
imaging center onto your software stack.
Paste the markdown into your LLM. Card files plus documentation
into Claude or another LLM you trust. The .md files are the product
surface; the LLM is the runtime. Lightest path.
Clone GarrisonNode from GitHub. Self-install on the practice's
back-office machine. Open source. For practices with technical
capacity in-house.
Join the mesh. GitHub install plus public-chain anchor and
cross-attestation with peer practices. The deepest path; appropriate
when the practice's referral network spans multiple operators.
A fifth option holds the cursor for now: keep evaluating. The walk
is the test drive.
A sandboxed Merkle Trust loads with a synthetic implant case: Mr.
Almeida, scheduled for a single-tooth implant at site #19. The
record already contains five attestations from three independent
parties.
Periodontal charting (your practice): probing depths, mobility,
recession, bone loss visible on bitewings. Signed and timestamped at
the day of recall.
Pre-op CT (outside imaging center): three-dimensional scan with
bone-density measurement at the proposed implant site. Imaging
center's signature, instrument ID, technician, date.
Endodontist referral (outside endodontist): adjacent tooth #18
evaluated, declared non-restorable, recommendation to extract.
Endodontist's signature, date.
Surgical plan (your practice): implant size, position, depth,
planned abutment timing. Your signature, date.
Lab specification (out-of-state lab): custom abutment, crown
shade match, lab's acknowledgment with timestamp.
The walk takes the appeal scenario — that's the one that ate the
last three Saturdays. A synthetic denial letter loads: "Pre-
authorization denied. Periodontal status documented after the
implant recommendation; insufficient justification for implant over
bridge."
The robot fetches each document from its source-of-record and tosses
it into the appeal box in chronological order. The ticker streams
the merkle leaf for each as it lands. Periodontal charting timestamped
2026-01-14, signed at your practice, anchored to your ceremony of
2026-01-14 22:00. Endodontist referral timestamped 2026-01-21, signed
at the endodontist's practice, anchored to a separate ceremony on his
system. Imaging-center CT timestamped 2026-01-23, signed at the
imaging center, anchored to a third ceremony there. Surgical plan
timestamped 2026-01-28, signed at your practice, anchored to your
ceremony again.
Five documents, four signatures, three independent ceremony chains.
A pre-drafted appeal cover letter populates: "Attached, please find
the complete pre-authorization record. Each document carries an
independently verifiable timestamp anchored to a public chain. The
periodontal evaluation predates the implant recommendation by two
weeks; the verification URL for each anchor is included in the
document metadata."
The response that took four hours and two phone calls is now a
ten-minute review of a packet that assembles itself.
Each document was hashed at its source. The endodontist hashed
his referral on his system. The imaging center hashed the CT on
theirs. Your practice hashed the periodontal charting and the
surgical plan. The hashes converge in the patient's record without
anyone needing to trust anyone else's word.
Each hash was anchored. Your practice's daily ceremony anchors
your documents. The endodontist's practice anchors his. The imaging
center anchors theirs. Three separate ceremonies, three separate
anchors, one verifiable record.
The packet ships with all three anchors visible. The payer's
auditor verifies each one independently. There is no chain-of-custody
dispute because there is no custody chain to dispute — each party
signed at the moment of authorship.
The single-clinician case is the entry-level shape: one practice,
one ceremony, one chain. A perio-and-implants practice coordinates
care across three to five entities per case, and the attestation
chain has to span them without forcing them onto the same software
stack. The infrastructure is the same; the chain just has more
parties signing at the moment of authorship.
The .md button at the bottom puts a structured summary of this
multi-entity pattern into your tag-along bundle. If you would like
a critical reviewer to read it and ask questions a payer's auditor
might ask, the comment field carries one to your own claude.ai
session — with the full prompt shown to you before it sends.
Before the walk goes further, run a ceremony. It takes 15 seconds
and it's the thing that makes the multi-entity chain defensible.
The robot collects the practice's day-of leaves. The ticker streams
the hex of each leaf as it joins today's tree. Real SHA-256 fires in
your browser, real merkle leaves combine into a real root, the new
anchor lands at the configured chain. Progress bar reads "done —
1,847 files attested, 22 critical files verified, new anchor at "
followed by the first eight hex characters of the root.
The output: we checked everything in your practice. Nothing has been
tampered with. Here is today's proof. The endodontist's practice and
the imaging center run their own ceremonies on their own schedules;
their proofs link to your packet through the cryptographic chain,
not through any shared system you have to trust.
Three ways to leave, no pressure either way.
Whichever direction the walk takes from here, you take a signed
package with you — yours to keep, downloaded directly when you
finish. The package contains the manifest with the merkle root of
every file, a certificate of registration carrying your earliest
attestation timestamp, the architecture docs, the verification
scripts (verify.sh and verify.py, stdlib only), aclaude_prompt.md you can paste into any LLM for an independent
audit, the JSON schemas, and a DISCLAIMERS.md.
A second file rides along with the cert: a recovery seed. Twelve
words written into a file with a self-protecting preamble — if it
ever ends up pasted into an LLM by accident, the preamble tells the
LLM to STOP and warn the user. Daily access uses the cert; the seed
is the fire exit.
For a multi-entity practice, the most useful close is to take a
referral kit. A one-page explainer for an outside provider's IT —
the endodontist, the imaging center, the lab — that walks them
through what attestation costs them (almost nothing) and what it
gives back to the cases you both touch. The referral lunch with the
endodontist is on Friday; the kit is what you bring.
<!-- finish_text -->
That was the simulated path through a multi-entity dental case and
the appeal that didn't have to be a Saturday afternoon. The full
card breaks out the savings, what this work gives back to small
specialty practices coordinating across referral partners, and a
prediction that's yours to test.