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.
- Public Health Surveillance
- Data model and migration order
The tables behind Public Health Surveillance
Public Health Surveillance 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
Identity and access
Users connect to People; People are referenced by clinician, author, recorder and provider fields.
Patient and authority
Patients connect to Consents and care team assignments, while clinical privileges connect to People.
Care
Encounters connect Patients and People, then carry clinical notes, Observations and Charges. Care tasks connect Patients and People.
Surveillance
Surveillance reports refer to Encounters; vaccination events refer to Patients and People.
Account
Payments refer to Patients.
Every table, by feature
- Surveillance reporting5
- Vaccination events6
- Encounter coordination6
- Clinical documentation6
- Consent and authority6
- Follow-up and billing6
- Surveillance reports
Notifiable condition reports submitted against an operational encounter record.
Linked to Encounters - Encounters
Scheduled and completed care encounters between a patient and a clinician.
Linked to Patients, People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users - Clinical privileges
Verified professional privileges covering a clinician and effective window.
Linked to People - Care team assignments
Active care-team access assignments scoping a clinician to a patient.
Linked to Patients, People
- Vaccination events
Administered vaccination doses with vaccine, lot and provider.
Linked to Patients, People - Patients
Individuals under surveillance or care, with consent status and assigned clinician.
Linked to People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users - Consents
Purpose-specific patient consent records with version and validity window.
Linked to Patients - Clinical privileges
Verified professional privileges covering a clinician and effective window.
Linked to People - Care team assignments
Active care-team access assignments scoping a clinician to a patient.
Linked to Patients, People
- Encounters
Scheduled and completed care encounters between a patient and a clinician.
Linked to Patients, People - Patients
Individuals under surveillance or care, with consent status and assigned clinician.
Linked to People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users - Clinical notes
Attributed clinical documentation attached to an encounter.
Linked to Encounters, People - Observations
Measured values captured during an encounter with unit, time and author.
Linked to Encounters, People - Care tasks
Follow-up work assigned to a responsible clinician for a patient.
Linked to Patients, People
- Clinical notes
Attributed clinical documentation attached to an encounter.
Linked to Encounters, People - Observations
Measured values captured during an encounter with unit, time and author.
Linked to Encounters, People - Encounters
Scheduled and completed care encounters between a patient and a clinician.
Linked to Patients, People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users - Consents
Purpose-specific patient consent records with version and validity window.
Linked to Patients - Clinical privileges
Verified professional privileges covering a clinician and effective window.
Linked to People
- Consents
Purpose-specific patient consent records with version and validity window.
Linked to Patients - Care team assignments
Active care-team access assignments scoping a clinician to a patient.
Linked to Patients, People - Clinical privileges
Verified professional privileges covering a clinician and effective window.
Linked to People - Patients
Individuals under surveillance or care, with consent status and assigned clinician.
Linked to People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users - Users
Users
Linked to Users
- Care tasks
Follow-up work assigned to a responsible clinician for a patient.
Linked to Patients, People - Charges
Service charges raised against an encounter for billing.
Linked to Encounters - Payments
Confirmed payments received against a patient account.
Linked to Patients - Patients
Individuals under surveillance or care, with consent status and assigned clinician.
Linked to People - Encounters
Scheduled and completed care encounters between a patient and a clinician.
Linked to Patients, People - People
Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
Linked to Users
Keys and references
The Id fields identify most operational records. Patient number is a patient identifier, while the explicit reference fields carry the actual links. A surveillance reports operational record points to Encounters; it is not a free-standing patient reference. The vaccination events Patient and Provider links preserve dose attribution. People.User links the staff record to Users.
Migration order
- Bring in Users and People so named staff can be referenced.
- Add Patients, then Consents, care team assignments and clinical privileges with their effective dates.
- Add Encounters before clinical notes, Observations, Charges and surveillance reports.
- Add care tasks, vaccination events and Payments with their patient or encounter links.
- Reconcile status values and sample references with the staff who will review them.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.