PlaygroundHealth care
Cedar Ridge Clinic
Fictional companyHealth care
A multi-provider outpatient clinic running intake through discharge under consent, privacy, and escalation rules.
Modeled on
- HL7 FHIR R4: Resource names and field names — Patient, Encounter, ServiceRequest, CarePlan, Consent.
- HL7 v3 ActCode: Encounter classes: AMB, EMER, IMP, VR.
- LOINC: Observation codes.
- ICD-10-CM: Condition codes.
The genome map
Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.
Roles Select a role to see its reach.
Patient Care Pathway Operated by Medical Director
Arrival through discharge, with consent verified before any chart is opened.
- 1 Register patient
- Registration is front desk
- 2 Verify consent
- 3 Triage
- Triage belongs to nursing
- 4 Assess
- Only clinicians assess
- 5 Submit requests
- Prescribing is licensed
- 6 Update care plan
- 7 Discharge
Resources
- Patient
- Encounter
- Care Plan
- Service Request
- Consent
- Observation
- Condition
Rules on no step They govern operations outside the process.
- Consent precedes chart access
Three questions this genome answers
Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.
Medical Director, Physician may perform Encounter.Assess. The rule: Only clinicians assess.
These steps wait for Physician:
- Assess Patient Care Pathway
- Submit requests Patient Care Pathway
- Discharge Patient Care Pathway
Medical Director, Physician, Triage Nurse act on Encounter, by a process step or under an access rule.
Every artifact from one genome
The same derivations and renderers the Playground runs, here for Cedar Ridge Clinic at build time. Open it in the Playground to pick your own set.
Operations
How the work actually runs — who owns what, in what order, under which rules.
Process flow
The end-to-end sequence, each step with its owner.
Arrival through discharge, with consent verified before any chart is opened.
- 1Register patientConfirm identity, demographics, and coverage; open the encounter.
- 2Verify consentConfirm a current consent covers treatment before the chart is opened.
- 3TriageTake vitals, set acuity, and route — anything emergent leaves the pathway here.
- 4AssessExamine, form the working diagnosis, and record the assessment.
- 5Submit requestsOrder labs, imaging, medication, or a referral against the encounter.
- 6Update care planRevise problems, goals, and the review date; schedule the follow-up.
- 7DischargeGive discharge instructions, set disposition, and close the encounter.
Owned end to end by Medical Director.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Register patientConfirm identity, demographics, and coverage; open the encounter.Performed by Front Desk Coordinator
- 2. Verify consentConfirm a current consent covers treatment before the chart is opened.Performed by Front Desk Coordinator
- 3. TriageTake vitals, set acuity, and route — anything emergent leaves the pathway here.Performed by Triage Nurse
- 4. AssessExamine, form the working diagnosis, and record the assessment.Performed by Physician
- 5. Submit requestsOrder labs, imaging, medication, or a referral against the encounter.Performed by Physician
- 6. Update care planRevise problems, goals, and the review date; schedule the follow-up.Performed by Care Coordinator
- 7. DischargeGive discharge instructions, set disposition, and close the encounter.Performed by Physician
Key positions
The roles this operation needs and who reports to whom.
Care Team
- Medical DirectorClinically accountable for the practice and its protocols.
- PhysicianAssesses, diagnoses, and orders.AssessSubmit requestsDischarge
- Care CoordinatorOwns the care plan and the follow-up loop.Update care plan
- Triage NurseSets acuity and routes patients on arrival.Triage
- Front Desk CoordinatorRegisters patients and verifies consent and coverage.Register patientVerify consent
Each chip is a step of the process that role owns.
RACI matrix
Every step against every role — responsible, accountable, consulted.
| Step | Medical Director | Physician | Triage Nurse | Care Coordinator | Front Desk Coordinator |
|---|---|---|---|---|---|
| Register patient | A | R | |||
| Verify consent | A | R | |||
| Triage | A | C | R | ||
| Assess | A | R | |||
| Submit requests | A | R | C | ||
| Update care plan | A | R | |||
| Discharge | A | R | C |
R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.
Policies & rules
The constraints that govern each operation, stated as rules.
- Consent precedes chart access condition
A chart does not open until a current consent covering treatment is on file.
- Only clinicians assess access
Assessment is a clinical act. Administrative staff never perform one.
- Prescribing is licensed access
Orders are placed by the licensed provider who will answer for them.
- Triage belongs to nursing access
Acuity is set by triage nursing, so the standard is applied the same way every time.
- Registration is front desk access
Demographics and coverage are captured once, by the desk that owns them.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
RegisterReadA person under the clinic’s care, with their demographics and consent state.
- identifier string required
- birthDate date required
- active boolean required
- generalPractitioner string
TriageAssessDischargeOne visit — the unit everything clinical hangs off.
- class enum required AMB · EMER · IMP · VR
- period datetime required
- priority enum required routine · urgent · asap · stat
- status enum planned · in-progress · finished · cancelled
UpdateFHIR CarePlan — addresses a Condition, carries goals and the review date.
- addresses string required
- goal text
- status enum required draft · active · on-hold · completed · revoked
- periodEnd date
SubmitListFHIR ServiceRequest — a lab, imaging, medication, or referral order on an encounter.
- category enum required laboratory · imaging · medication · referral
- code string required
- intent enum required proposal · plan · order
- status enum required draft · active · on-hold · completed · revoked
VerifyFHIR Consent — what the patient permitted, for which purpose, and until when.
- scope enum required patient-privacy · treatment · research
- status enum required draft · active · inactive
- dateTime date required
- provisionPeriodEnd date
RecordFHIR Observation — a measurement or finding, LOINC-coded.
- code string required
- valueQuantity number required
- unit string
- effectiveDateTime datetime required
DiagnoseFHIR Condition — a problem on the patient’s list, ICD-10-CM coded.
- code string required
- clinicalStatus enum required active · recurrence · remission · resolved
- onsetDateTime date
Screen map
Every route and the page it resolves to.
Shell: ClinicalShell
/board/patients/:id/service-requests/care-plansExample UI
A working admin table and detail form, built from the fields.
| Patient | Visit | Acuity | Arrived | Provider |
|---|---|---|---|---|
| M. Alvarez | urgent | elevated | 2026-08-18 08:14 | Dr. Reyes |
| J. Whitfield | follow-up | routine | 2026-08-18 08:40 | Dr. Osei |
| S. Nakamura | new | routine | 2026-08-18 09:05 | Dr. Reyes |
| D. Kowalski | telehealth | routine | 2026-08-18 09:30 | Dr. Osei |
API surface
The endpoints, grouped by namespace, with their operations.
/api/clinicalEncounter, chart, order, and consent operations.
- GET
/api/clinical/encountersEncounter.List Today’s board. - POST
/api/clinical/encounters/{id}/triageEncounter.Triage Set acuity and route. - POST
/api/clinical/encounters/{id}/closeEncounter.Discharge Discharge and close. - GET
/api/clinical/patients/{id}Patient.Read Open a chart. - POST
/api/clinical/patientsPatient.Register Register a patient. - GET
/api/clinical/encounters/{id}/service-requestsServiceRequest.List Requests on an encounter. - POST
/api/clinical/service-requestsServiceRequest.Submit Submit a clinical request.
Technology
Where it runs and who can reach it.
Architecture diagram
The cells this runs on and what talks to what.
CedarRidgeClinic.Product.WebCedarRidgeClinic.Product.ApiCedarRidgeClinic.Product.ApiCedarRidgeClinic.OperationalCedarRidgeClinic.Product.Core- ClinicalWeb → EncounterService board
- ClinicalWeb → ConsentGate chart access
- ConsentGate → ClinicalDb consent lookup
- EncounterService → ServiceRequestRouter encounter.assessed
- EncounterService → ClinicalDb depends-on
- ServiceRequestRouter → ClinicalDb depends-on
Environment topology
Dev, staging, and production, with the providers behind each.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Medical Director | Physician | Triage Nurse | Care Coordinator | Front Desk Coordinator |
|---|---|---|---|---|---|
Patient.RegisterRegistration is front desk | ✓ | ✓ | |||
Encounter.TriageTriage belongs to nursing | ✓ | ✓ | |||
Encounter.AssessOnly clinicians assess | ✓ | ✓ | |||
ServiceRequest.SubmitPrescribing is licensed | ✓ | ✓ |
Patient.ReadConsent.VerifyEncounter.DischargeEncounter.ListServiceRequest.ListCarePlan.UpdateDerived, not declared — this is the list an audit asks about.
Make yours
Start from Cedar Ridge Clinic and change what differs, or pick another company as your template. Three ways in:
1. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download Cedar Ridge Clinic as JSON2. Start an agent from it
Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.
Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works. Start from the Cedar Ridge Clinic genome at https://dna.codes/genome/healthcare.json. It is an example company, not mine. Read its roles, process steps, rules and resources, then ask me how my company differs. Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft. Do not save anything: call `apply` only when I ask you to save.
3. Join the waitlist
The hosted product runs your model for your team and your agents.