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.
- Infection Control System
- Implementation
How a Infection Control System rollout works
Set up case identity, team access, investigation evidence and review in a pilot cycle.
Agree the case rule
Choose patient number ownership, duplicate handling and consent purposes. Map the first cases and the people who will investigate them.
Set access
Link users to People, confirm configured role permissions, and enter team assignments and privilege evidence.
Run an investigation
Schedule an episode, record arrival, notes, observations, specimens and a case follow-up action.
Rehearse review
Move the episode to awaiting review. Have the Clinical Reviewer inspect dates, author and evidence before completion.
Check ongoing work
Review open actions and specimen states after the episode closes. Correct ownership or due dates before the next operating cycle.
What the customer provides
Bring a small set of representative cases, consent versions, staff accounts, clinical privilege evidence and investigation histories. Include a repeat investigation and a rejected specimen so the handoff is tested beyond a straightforward case. Name the coordinator, clinician, governance administrator and reviewer who will run the rehearsal.
Changing it afterwards
Review the pilot’s questions before importing more records. Keep case identity and investigation links stable when changing an assignment. Record a new consent version when the purpose or document changes. Recheck reports and role access whenever the team changes the operating rule. Continue with get started for the first cycle.
Set up Infection Control System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.