Healthcare · App Starter
Clinic Template
Patient records, scheduling, intake, notes, and billing in one generated app — owned and run by the practice itself.
Describe your practice — who you see, how visits run, what intake asks — and Dual7 generates a working clinic system around it: six connected entities, a calendar built for clinical days, and records that stay in a database you control. It's a codebase, not a subscription, so the software bends to the practice.
- 6 core entities
- Your data, your database
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Everything in a practice hangs off the patient chart. Six entities connect the person, the schedule, the paperwork, and the money — and because the schema is generated for you, the chart holds what your specialty actually records.
| table | what it holds |
|---|---|
patients | The chart's spine — demographics, contact details, alerts, and links to every appointment, form, note, and invoice. |
practitioners | Clinicians and their working patterns — specialties, schedules, and the appointment types each one offers. |
appointments | Booked visits with type, duration, status, and practitioner — including cancellations and no-shows, which are data, not deletions. |
intake_forms | Digital intake — history, consents, screeners — completed before the visit and filed against the chart, not a clipboard. |
visit_notes | Structured clinical notes per appointment, signed and timestamped, building the longitudinal record a chart is for. |
invoices | Charges tied to visits, with payment status and balance — so the clinical record and the billing record stop disagreeing. |
02 · Screens
Signature modules
Patient records
01One screen per patient: upcoming and past visits, completed forms, note history, and balance, in reverse-chronological order. The thirty seconds before you call someone in, answered without opening four tabs.
Clinic calendar
02Day and week views per practitioner, with appointment types carrying their own durations and colors. Booking respects each clinician's working pattern, and a cancelled slot is visibly reclaimable instead of silently lost.
Digital intake
03Patients complete history, consents, and screeners from a link before they arrive; responses file directly to the chart. Front desk stops transcribing handwriting, and the clinician reads intake before the visit instead of during it.
Visit billing
04Each visit generates its invoice from the appointment type's fee, adjustable per encounter. Outstanding balances surface on the chart and in a receivables view, so following up is a list to work, not an archaeology project.
03 · Process
How it works
- 1You
Describe how your clinic runs
Specialty, visit types and lengths, what intake needs to capture, how you charge. The structure is supplied by the starter; the vocabulary and fields come from you.
- 2Vibe mode
Shape it in Vibe mode
Refine the generated app conversationally — add a referral-source field, a new appointment type, a screener to intake. Each change lands as reviewable code, not a settings toggle you'll forget.
- 3Governed mode
Deploy through the governed pipeline
Ship through approval gates to infrastructure you choose, with patient data in your own database from day one — the control posture clinical software should start from.
04 · Fit
Who the Clinic starter is for
Solo practitioners replacing paper and spreadsheets
A practice of one still needs a chart, a calendar, and a ledger — what it doesn't need is enterprise practice-management pricing. This starter is the minimum honest system: everything filed against the patient, nothing rented.
Multi-practitioner clinics outgrowing shared calendars
When three clinicians book out of one shared calendar, double-bookings and orphaned notes are structural, not careless. Per-practitioner schedules and per-visit notes give the clinic one source of truth that scales by adding a row, not a license.
Specialist practices with fields no vendor ships
Every specialty has the fields generic software lacks — lactation consults, sports rehab, travel medicine all chart differently. Because the schema is generated to your description, the odd-but-essential field is a first-class column from the start.
Clinic owners with data-control obligations
Owners answerable for where patient data lives — by regulation, by conscience, or both — get an unusual answer here: it lives in your database, on your infrastructure, readable by software you can audit line by line.
05 · Yours
Customize it, own it
Make it yours
Start by making the chart yours. Add the fields your specialty records — range-of-motion measures, dosage histories, referral sources — and structure visit notes as the sections you actually write, so notes are queryable rather than prose. Appointment types, durations, and fees are your rules in your code, down to a different cancellation window per visit type.
From there, extend in any direction: reminders by SMS or email before appointments, a document upload on the chart for referral letters and results, a waitlist that offers cancelled slots automatically. The generated app is a standard full-stack codebase with no runtime dependency on Dual7 — your developers, or Dual7 in Vibe mode, can keep going as far as the practice needs.
Why a starter, not a subscription
Practice-management subscriptions hold the two things a clinic can least afford to rent: its patient records and its daily schedule. Leaving means an export negotiation; staying means per-practitioner pricing that punishes growth. This starter generates the system as source code in your repository — the records are rows in your database, and adding a clinician costs nothing.
For clinical software, ownership is also a compliance posture. Auditing what code touches patient data, controlling where it's hosted, and answering a records request are all simpler when the entire system is yours to inspect. Dual7's governed pipeline adds the discipline that freedom needs: approval gates and an audit trail on every change between development and the live clinic.
06 · Industries
Industry versions
Clinic template — frequently asked questions
What does the clinic template include?
A working practice system generated into code you own: patient records, per-practitioner scheduling, digital intake forms, structured visit notes, and visit-linked billing — six connected entities, deployed on your infrastructure with data in your database.
Is it HIPAA compliant?
Compliance is a property of how a system is deployed and operated, not a checkbox any vendor can hand you. What this starter changes is your position: you control hosting, encryption, access, and audit — the levers compliance work actually turns — because the entire stack is your code on your infrastructure.
Can patients book appointments themselves?
The starter ships with staff-managed scheduling; a public booking page is a natural extension, and Vibe mode can add one that respects practitioner schedules and appointment types. Many clinics prefer request-then-confirm — that's your policy to encode.
Can I customize the intake forms and visit notes?
Fully — both are structured data you define, not fixed vendor templates. Ask for a new screener, a consent, or a different note structure per appointment type, and the schema, forms, and chart views update together in your code.
Does it handle insurance claims?
The starter bills patients directly — visit-linked invoices, payments, balances. Claim submission is jurisdiction- and clearinghouse-specific, so it's left as an integration; the visit and charge data a claim needs is already structured, which is the hard half.
Can I migrate existing patient records into it?
Yes — the schema is a normal relational model, so exports from your current system map to patients, appointments, and notes tables directly. Owning the schema means migration quirks are fixable in your code rather than negotiated with an importer.
Related
Dual7 App Starters
Build your Clinic on your terms
Patient records, scheduling, intake, notes, and billing in one generated app — owned and run by the practice itself. Describe your version to start — the output is a project you own.