A map you can trust — because it shows its work
This site began as the working group's own document — the questions and findings the group assembled to prepare for its meetings with Anthropic. At a working-group meeting, that document was used, live, to charter a genesis campaign for a context graph: a structured knowledge base integrating the context behind every topic and question in the working document — references, examples, and case studies — with a chip on every claim saying how it was checked and how far to trust it. An agent working in the aDNA format built the first version of that graph, and the site you are reading from it, in about thirty minutes, during the meeting itself.
What it teaches is the material the group gathered about using Anthropic's Claude safely in rare-disease advocacy: folder access, secrets, data retention, HIPAA, Skills, and the questions still open. It is built for people doing patient-facing work who did not build these tools — plain language first, detail underneath, provenance on everything.
Two ways in. Advocacy and operations staff: read straight down — the six modules below are in teaching order. Clinicians and clinical researchers: start with the clinician path, which takes the same findings in a different order — what is covered, what is retained, and what the tool must not be trusted with. Either way you are reading the same graph, with the same chips and the same receipts. There is also a printable summary built to be handed to someone — the rules, with their dates and their marks, on paper.
Why this exists (and why it looks the way it does)
Your document asked: “How can we control what sources Claude pulls from?” One working answer is a context graph — a curated set of fact files, one claim per file, each carrying its source, its retrieval date, and an honest confidence rating, that an AI assistant is instructed to answer from, instead of from its general memory. This site is that answer, demonstrated: every page you're reading is rendered from exactly such a graph, and the graph itself is what the group's assistant queries. Control the graph, and you control the sources.
So this site is two things at once. It is the body of knowledge — the findings, rules, open questions, and validation state that medical and advocacy leaders need to use these tools for the good of patients. And it is a demonstration: the first version of the graph behind it was built from the group's working document in half an hour, by an agent, with every claim carrying its provenance — and what you are reading now has been through the review rounds recorded in the verification log since. The chips are not decoration — knowing how each piece of information was validated, and to what degree, is a critical dimension of building and understanding a system like this. What took thirty minutes was that first version — and that is what these tools now make possible for any group willing to show its work.
How to read the chips
Every claim carries a chip that tells you how much to lean on it. Each state is marked three ways at once — colour, icon, and label — so it reads the same in colour, in greyscale, and to a screen reader. This legend is on every page of the site; the printable one-pager carries the same marks in its own compact key, sized for paper.
How to read the chips
- Confirmed checked against Anthropic’s own page on the date shown, and the receipt kept.
- Documented not checked against an Anthropic page this round — either carried from the working group’s document, or this curriculum’s own practice recommendation. The source chip says which.
- Stale risk known-volatile, or the check found a discrepancy — treat as a question, not a fact.
- compliance a claim a patient-data decision could hang on — always confirm with your Anthropic contact first.
- our practice a practice recommendation — this curriculum’s or the working group’s — not an Anthropic product fact.
The six modules
Folder & Desktop Access
Where you let Claude work is the whole ballgame — dedicated folders, tiers, and the delete gate.
8 findings (6 confirmed · 1 not re-checked · 1 flagged) · 5 questions for the contactAPI Keys & Secrets
Credentials never travel through a conversation — where secrets should live instead.
5 practice recommendations (ours, not product facts) · 3 questions for the contactData Retention & What Goes Back
What happens to what you type — by plan, by surface, and the details that move.
7 findings (7 confirmed) · 6 questions for the contactHIPAA & Patient Privacy
Read slowly: most ways of using Claude are never covered for PHI. The two that can be, and how.
7 findings (6 confirmed · 1 not re-checked) · 9 questions for the contactSkills
Teach Claude your org’s way of doing a task once — and know the one retention edge.
7 findings (6 confirmed · 1 flagged) · 4 questions for the contact · 10 Skill ideasCross-Cutting Questions
Connectors, multi-org siloing, staying current, trusting outputs — and why this site exists.
10 findings (7 confirmed · 3 not re-checked) · 14 questions for the contactThe call agenda
Every open question across all six modules, consolidated and printable: the Open-Questions Register — the working group's agenda for its Anthropic contact. Currency baseline: 32 of 44 findings confirmed against primary sources, last verified 2026-09-19.