These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Clinic Management
- Data model
The tables behind Clinic Management
Clinic Management ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Patient and care team
Patients, People and Users identify the patient and staff. Care team assignments, Consents and clinical privileges hold access and decision context.
Visit
Encounters link Patients and People, then carry visit reasons, Observations, clinical notes and prescription orders.
Follow-up
Care tasks link a patient to an assigned person and due work.
Financial work
Charges link to Encounters; Payments link to Patients.
Every table, by feature
- Patient and care teams6
- Visit coordination8
- Clinical documentation5
- Prescriptions and privileges4
- Care follow-up4
- Charges and payments4
- Patients
Patient master with consent status and assigned clinician.
Linked to People - Consents
Purpose-specific patient consent records.
Linked to Patients - Care team assignments
Care-team access scope per patient and clinician.
Linked to Patients, People - People
Care team members linked to platform users.
Linked to Users - Users
Users
Linked to Users - Clinical privileges
Verified professional privileges per clinician.
Linked to People
- Encounters
Scheduled and completed visits linking patient and clinician.
Linked to Patients, People - Patients
Patient master with consent status and assigned clinician.
Linked to People - People
Care team members linked to platform users.
Linked to Users - Visit reasons
Recorded visit reason per encounter.
Linked to Encounters, People - Observations
Measured vitals and values recorded during an encounter.
Linked to Encounters, People - Clinical notes
Encounter documentation with draft, signed and amended states.
Linked to Encounters, People - Prescription orders
Prescription orders with prescriber and signing state.
Linked to Encounters, People - Charges
Service charges captured per encounter.
Linked to Encounters
- Visit reasons
Recorded visit reason per encounter.
Linked to Encounters, People - Observations
Measured vitals and values recorded during an encounter.
Linked to Encounters, People - Clinical notes
Encounter documentation with draft, signed and amended states.
Linked to Encounters, People - Encounters
Scheduled and completed visits linking patient and clinician.
Linked to Patients, People - People
Care team members linked to platform users.
Linked to Users
- Prescription orders
Prescription orders with prescriber and signing state.
Linked to Encounters, People - Clinical privileges
Verified professional privileges per clinician.
Linked to People - Encounters
Scheduled and completed visits linking patient and clinician.
Linked to Patients, People - People
Care team members linked to platform users.
Linked to Users
- Care tasks
Follow-up work assigned to clinicians.
Linked to Patients, People - Patients
Patient master with consent status and assigned clinician.
Linked to People - People
Care team members linked to platform users.
Linked to Users - Encounters
Scheduled and completed visits linking patient and clinician.
Linked to Patients, People
- Charges
Service charges captured per encounter.
Linked to Encounters - Payments
Patient payments received against care services.
Linked to Patients - Encounters
Scheduled and completed visits linking patient and clinician.
Linked to Patients, People - Patients
Patient master with consent status and assigned clinician.
Linked to People
Keys and references
The Id field identifies each business record except Users, where the User reference appears in the schema. A patient can have many Encounters; an Encounter has one Patient and one Clinician. Clinical notes has an Encounter and Author. Observations and visit reasons have an Encounter and recorded by. Prescription orders has an Encounter and Prescriber. Charges has an Encounter. Payments has a Patient, so payment reconciliation uses patient and receipt context rather than a direct charge reference. People links to Users through User.
Migration order
- Users and People. Establish named staff and their user links.
- Patients. Import patient numbers, names and assigned clinicians.
- Consent and authority. Add Consents, care team assignments and clinical privileges with status and dates.
- Encounters. Create visits with patient and clinician references.
- Clinical work. Bring in visit reasons, Observations, clinical notes and prescription orders against the correct encounter.
- Operations and finance. Add care tasks, Charges and Payments with the appropriate patient or encounter link.
Set up Clinic Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.