Clinics & Medical Practices
Specialized care, end to end: streamline scheduling, secure clinical records, and automate complex billing for outpatient clinics and medical practices.
What you manage
Your patients, on a single authoritative record.
In this setting, the care subject is the patient. Every patient carries one authoritative record across every visit, episode and document — versioned, provenance-tracked and instantly retrievable for the people cleared to see it.
- Modules
- 21
- Roles
- 6
- Terms
- 12
Modules for this setting
The modules this clinics & medical practices workspace runs.
Each card below is a configuration of the same governed core — not a separate app. Enable what you need; one isolation, authorization and audit baseline ties them together.
Dashboard
A role-scoped command view: each user lands on only the tiles they are cleared to see.
Subjects
The authoritative registry of every care subject, with one record across every visit and episode.
Scheduling
Bookings, reminders and a live queue, constrained by resource and eligibility rules.
Encounters
Service events captured as versioned, provenance-tracked records — never an editable free-for-all.
Documents
Generate referrals, certificates and reports from structured notes — jurisdiction-aware.
Finance & billing
Invoices, claims and payment models wired straight to the events that justify each charge.
Consents
Recorded, jurisdiction-aware authorizations for treatment, data use and portal access.
Subject portal
A scoped, transparent portal for subjects and representatives — never exposing internal records.
Users & roles
Accounts, roles and assignments under one centralized, tenant-scoped authorization engine.
Compliance
Policy, consent and accreditation oversight built into the core, ready for inspection.
Audit trail
A tamper-evident, append-only record of every access and action, captured automatically.
Workforce
Credentialing and eligibility that feed scheduling, encounters and compensation.
Integrations
Connectors and an event system for devices and external systems via a governed registry.
Settings
Tenant configuration — what is enabled, by whom and under which jurisdiction rules.
AI agents
Identified, capability-gated, tenant-scoped agents — assistive drafting, never final.
AI evidence
Every recommendation carries a content hash and cited source — or it is refused, not guessed.
Algorithmovigilance
Drift, refusals and guardrail trips monitored continuously, the way pharmacovigilance watches a drug.
Lab orders
Requisitions, accessioning and result reporting with end-to-end specimen provenance.
Imaging
Study ordering, acquisition and reporting wired to PACS/RIS connectors.
Treatments
Timed treatment and care orders executed against the subject's record and inventory.
Reports
Operational and quality metrics drawn from the same governed data, scoped to the viewer.
Purpose-built roles
Each role sees only what it needs.
Roles are mapped to per-role dashboards: a user lands on the exact modules their job requires and nothing else, all under one centralized, tenant-scoped authorization engine.
Practice Owner / Administrator
Full control over modules, users, AI policy and tenant configuration for this workspace — the account that stands it up and governs it.
Clinician / Physician
A scoped dashboard of 11 modules, with only the permissions this role needs.
Nurse / Clinical Assistant
A scoped dashboard of 8 modules, with only the permissions this role needs.
Front Desk / Reception
A scoped dashboard of 6 modules, with only the permissions this role needs.
Billing & Finance
A scoped dashboard of 5 modules, with only the permissions this role needs.
Compliance & Privacy Officer
A scoped dashboard of 8 modules, with only the permissions this role needs.
Your domain's language
It speaks your domain's language.
Labels, templates and workflows use the vocabulary your teams already use — so the platform reads like your practice, not a generic record system.
- Patient
- The individual receiving care; the clinic's CareSubject, with a single authoritative record across visits.
- Appointment
- A scheduled service slot for a patient with a provider, room, and service type.
- Intake
- Pre-visit collection of patient demographics, history, and consent via digital forms before the encounter.
- Queue
- The live list of patients checked in and waiting, ordered by appointment time and status.
- Encounter
- A documented clinical service event (consultation, follow-up, procedure) tied to a patient and provider.
- SOAP note
- Structured clinical documentation with Subjective, Objective, Assessment, and Plan sections.
- Referral
- A request directing a patient to another specialist, service, or facility for further care.
- Order
- A clinician-issued request for a lab test, imaging study, or treatment as part of the care plan.
- Claim
- A billing submission to an insurer for covered services; tracked through approval or denial.
- Fee-for-service
- A billing model charging per individual service rendered, distinct from bundled or capitation models.
- Capitation
- A billing model paying a fixed per-patient amount per period regardless of services used.
- Consent
- A patient's recorded, jurisdiction-aware authorization for treatment, data use, or portal access.
Why the governed core matters here
Same security baseline as every other sector.
This is the same configurable platform core, configured for clinics & medical practices — not a standalone product. You inherit the platform's isolation, auditability, interoperability and AI governance unchanged: one security baseline, not a bespoke one.
Tenant isolation & complete audit
Every patient record is scoped to your organisation and isolated in the data layer (PostgreSQL row-level security). Who saw, changed or shared it — and why — is captured automatically in a tamper-evident trail.
AI is assistive, never final
Drafting, coding hints and summaries speed the work, but every clinical, legal and financial output is cited and human-confirmed before it counts for your patients. Nothing is auto-decided.
FHIR-first interoperability
Orders, results and records exchange over HL7/FHIR through a governed connector registry — so this setting plugs into the systems around it without bespoke, brittle glue.
Jurisdiction-aware by design
Documents, signatures and timestamps adapt to the local rules wherever you operate, and centralized authorization (RBAC + ABAC + ReBAC + PBAC) is enforced before any sensitive module is exposed.
Start your Clinics & Medical Practices workspace.
Stand up clinics & medical practices on the same secure, governed core that powers every DrClick, DrVet, DrCare, DrLegalMed and DrRetailHealth deployment. You become its owner, configured for your patients from day one.