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
- Implementation and migration
How a Public Health Surveillance rollout works
Start with patient identity, authority and one encounter-linked report.
Name the team
Set up Users and People for coordinators, clinicians, governance staff and reviewers.
Establish patient scope
Bring in Patients, signed Consents, active care team assignments and verified clinical privileges with effective dates.
Rehearse a care case
Schedule an Encounter, record an Observation and clinical note, then move the encounter into review.
Rehearse reporting
Create a surveillance report linked to that encounter, validate it and follow it through investigation and closure.
Add adjacent work
Record a vaccination event, follow-up care task, Charge and Payment using their correct patient or encounter links.
What the customer provides
Provide patient identifiers, staff identities, consent purposes and versions, privilege evidence, care-team access purposes, condition codes, reporting facilities and vaccine and lot naming rules. Name the people who may make each review decision. Bring a representative case for each exception the team expects to handle.
Changing it afterwards
Review the effect of a changed consent purpose, privilege window or care-team assignment before continuing clinical work. Correct patient and encounter links at their source record and ask the reviewer to revisit any affected report. Keep external connection mapping under a named owner. The get-started guide gives a first-cycle checklist.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.