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.
- Patient Portal
- Data model
The tables behind Patient Portal
Patient Portal 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 and ownership
Patients connect to Consents, care team assignments, care tasks, Encounters and Payments. People represents clinic staff.
Visit evidence
Encounters connect to clinical notes, Observations, Specimens, pharmacy dispensations and Charges.
Governance
Clinical privileges connects to People, while care team assignments connects People and Patients.
Platform reference
Users connects to People; exchange rates holds read-only effective currency rates.
Every table, by feature
- Patient and care team4
- Encounters and notes5
- Follow-up care4
- Clinical governance5
- Specialty operations6
- Charges and payments4
- Shared and settings1
- Patients
Patient identity and consent status
Linked to People - Consents
Purpose-specific patient consent
Linked to Patients - Care team assignments
Care team access assignments
Linked to Patients, People - People
Clinic staff and clinicians
Linked to Users
- Encounters
Patient visits and care episodes
Linked to Patients, People - Observations
Measured clinical observations
Linked to Encounters, People - Clinical notes
Attributed clinical documentation
Linked to Encounters, People - Patients
Patient identity and consent status
Linked to People - People
Clinic staff and clinicians
Linked to Users
- Care tasks
Follow-up care tasks
Linked to Patients, People - Patients
Patient identity and consent status
Linked to People - People
Clinic staff and clinicians
Linked to Users - Encounters
Patient visits and care episodes
Linked to Patients, People
- Clinical privileges
Verified clinician privileges
Linked to People - Care team assignments
Care team access assignments
Linked to Patients, People - People
Clinic staff and clinicians
Linked to Users - Patients
Patient identity and consent status
Linked to People - Users
Users
Linked to Users
- Specimens
Lab specimens and their processing state
Linked to Encounters - Pharmacy dispensations
Medication dispensations with lot and quantity
Linked to Encounters, People - Encounters
Patient visits and care episodes
Linked to Patients, People - Clinical notes
Attributed clinical documentation
Linked to Encounters, People - People
Clinic staff and clinicians
Linked to Users - Clinical privileges
Verified clinician privileges
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
Each care record has its own identifier. Patient references identify the person receiving care; Encounter references identify the particular visit. The staff references on notes, observations, privileges, assignments and dispensations identify the person responsible for that evidence. Payment records reference Patients, while charge records reference Encounters. Keep those relationships intact when importing older records.
Migration order
- People and users. Establish staff identities and their user links.
- Patients. Import patient numbers, identity and assigned clinician.
- Governance and consent. Bring over privilege evidence, assignments and consent documents with dates.
- Encounters. Import visits with patient and clinician references.
- Visit evidence and follow-up. Add notes, observations, specimens, dispensations and patient tasks.
- Financial records. Import encounter charges and patient payments with their references.
Set up Patient Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.