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
- Features
- Surveillance reporting
Surveillance reporting
Follow surveillance reporting through its source records and decisions.
OverviewReports awaiting validation×
Public Health Surveillance · Surveillance reporting
New
Reports awaiting validation
Validation waits for the clinical reviewer
| Operational record | Reporting facility | Condition code | Report date | Case count | Status | |
|---|---|---|---|---|---|---|
| ENC-7341 | RF-507 | CC-797 | 07 Oct | 35 | Submitted | |
| ENC-5942 | RF-331 | CC-704 | 04 Oct | 27 | Submitted | |
| ENC-6085 | RF-907 | CC-167 | 23 Oct | 4 | Submitted | |
| ENC-6006 | RF-106 | CC-622 | 26 Oct | 37 | Submitted | |
| ENC-7798 | RF-893 | CC-765 | 11 Oct | 5 | Submitted |
6 of 6 records
RF-507Surveillance reports · SR-71754
SubmittedOperational recordENC-7341
Condition codeCC-797
Report date07 Oct
Case count35
What you can do
Work from the source record
A condition report points to the encounter that supplied its operational context. The Licensed Clinician enters the reporting facility, condition code, report date, case count and population denominator. A Clinical Reviewer follows the encounter link and checks the source and the clinician’s authority before authorizing validation. Submitted, Validated, Investigating and Closed describe distinct stages of the report; the encounter has its own status and can move on a different schedule.
For a suspected condition, open the linked encounter before reviewing a Submitted report. Compare the condition code and facility with the report date and read the case count alongside the denominator. The reviewer checks the clinician’s identity through the encounter and authority records. A wrong encounter reference stops the validation decision until the Licensed Clinician corrects the source report.
How the work is organized
- Source. Keep condition code, reporting facility, report date, case count and population denominator on the record that owns the work.
- Responsibility. Licensed Clinician starts from the relevant list and checks the linked record before acting.
- Handoff. Use the status and dates to decide what the next person should inspect.
What to agree during setup
Agree who selects the reporting facility and condition code, what the case count represents and how the denominator is defined. Decide how reviewers resolve a wrong encounter link and how investigation ownership is recorded outside the report’s limited fields. Set the human review point before a report is marked Validated. Treat external notification as a separately configured destination with its own owner.
Check the handoff on an actual case
Create a Submitted report against a known encounter. Have the Licensed Clinician enter facility, condition code, date, case count and denominator. Ask the Clinical Reviewer to open the encounter, verify the clinician and check consent, assignment and privilege for the action. Follow the authorized validation, investigation and closure decisions on that report. Repeat with the wrong encounter link and stop before validation until the source is corrected.
Keep the report date distinct from the visit date. A facility can submit a report about an encounter recorded earlier, and the reviewer needs both dates to interpret the case. Case count and population denominator are separate numeric fields; agree their definitions before comparing reports. A Closed report records the end of its own review path, not a change to the linked encounter.
What your team sees
- Active Surveillance Reports — See submitted, validated and investigating reports.
- Reports awaiting validation — Open submitted reports with their source encounters.
- Surveillance status board — Compare report stages by facility and condition.
Follow the work through
Use the process walkthrough to rehearse the decision and the data model to check record links. The roles page explains the access responsibilities.
What it keeps track of
Data model- Surveillance reports
- Notifiable condition reports submitted against an operational encounter record.
- Encounters
- Scheduled and completed care encounters between a patient and a clinician.
- People
- Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
- Clinical privileges
- Verified professional privileges covering a clinician and effective window.
- Care team assignments
- Active care-team access assignments scoping a clinician to a patient.
Who uses it
Permissions- Licensed Clinician
- , Clinical Reviewer, Clinical Governance Administrator.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.