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.
- Ayurveda / Alternative Medicine
- Data model and migration order
The tables behind Ayurveda / Alternative Medicine
Ayurveda / Alternative Medicine ships with 15 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
- 15
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Patient intake and consent
Patients stores patient number, display name, birth date, contact phone, consent status and assigned clinician. Consents references Patient and retains Purpose, Version, Document, signed at, expires at and Status.
Encounters and clinical notes
Encounters links Patient and Clinician. Clinical notes and Observations reference Encounter and attribute work through Author or recorded by, both pointing to People.
Practitioner assessments
Practitioner assessments references Encounter and records assessment type, accession number, collected at and Status.
Herbal dispensations
Herbal dispensations links Encounter and authorized by, with preparation name, batch number, Quantity and Unit for each entry.
Care team and follow-up
Care tasks links Patient and assigned to. Care team assignments connects Patient and Clinician with access purpose and effective dates. Clinical privileges links Clinician to verification evidence and effective dates. People links each staff identity to Users.
Charges and payments
Charges references Encounter, while Payments references Patient. Exchange rates supplies read-only effective rates with Currency and effective from; financial interpretation follows the agreed setup convention.
Every table, by feature
- Patient intake and consent2
- Encounters and clinical notes3
- Practitioner assessments2
- Herbal dispensations3
- Care team and follow-up6
- Charges and payments4
- Shared and settings1
- Patients
Patient identity and consent status
Linked to People - Consents
Purpose-specific patient consent
Linked to Patients
- Encounters
Patient visits and care episodes
Linked to Patients, People - Clinical notes
Attributed clinical documentation
Linked to Encounters, People - Observations
Measured clinical observations
Linked to Encounters, People
- Practitioner assessments
Practitioner assessments and their review state
Linked to Encounters - Encounters
Patient visits and care episodes
Linked to Patients, People
- Herbal dispensations
Herbal dispensations with batch and quantity
Linked to Encounters, People - Encounters
Patient visits and care episodes
Linked to Patients, People - People
Clinic staff and clinicians
Linked to Users
- Care tasks
Follow-up care tasks
Linked to Patients, People - Care team assignments
Care team access assignments
Linked to Patients, People - Clinical privileges
Verified clinician privileges
Linked to People - People
Clinic staff and clinicians
Linked to Users - Users
Users
Linked to Users - Patients
Patient identity and consent status
Linked to People
- Charges
Service charges for encounters
Linked to Encounters - Payments
Patient payments received
Linked to Patients - Encounters
Patient visits and care episodes
Linked to Patients, People - Patients
Patient identity and consent status
Linked to People
Keys and references
Preserve the source record identifiers and resolve references before importing dependent records. Most tables use Id; exchange rates uses ID. Users contains a User reference to Users, and People.User links staff to their application identity. Resolve that account relationship explicitly before using Author or assigned to filters for the current user.
A patient number, accession number or batch number is useful for human reconciliation. Match records by verified source identity during migration and inspect ambiguous matches before loading dependent entries. Charges and Payments reach the patient by different paths; keep that distinction when preparing financial reports.
Migration order
- Establish Users and reconcile its User self-reference. Import People with the intended account links.
- Import Patients with assigned clinician and reconcile patient numbers against the source register.
- Load clinical privileges, care team assignments and Consents with their clinician or patient references and original dates.
- Import Encounters, then clinical notes, Observations, practitioner assessments and herbal dispensations linked to those encounters.
- Load care tasks, Charges and Payments against their respective parent records. Compare amounts and states with the original source. Inspect exchange rates through its read-only source.
Set up Ayurveda / Alternative Medicine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.