A | Â | Protocol including minimal requirements [10] | User manual [10] | Education module | Guidance by the coordinating centre | User-group meetings |
Content | Definitions (surveillance population and case) Acceptance criteria algorithm Data specifications Minimal requirements AS system Internal and external validation | How to write local implementation plan Formation of a project group Involvement of stakeholders of the implementation of AS Identification and solving local barriers for implementation | Basic principles of AS Validation of source data and algorithm components Hospital information systems Information standards Governance Development of AS system Maintenance | Discuss progress Questions or issues | Exchange experiences and examples between hospitals Updates/information from the coordinating centre | |
Developed by (actor) | Coordinating centre Expert and stakeholder consultation | Coordinating centre | Coordinating centre and AS Expert (coordination & education); Experts specific topics (education) | Coordinating centre | Coordinating centre– interactive participative meetings with intended users | |
Goal (implementation outcome affected) | Implementation Sustainability | Adoption Implementation Sustainability | Implementation Sustainability | Adoption Implementation Sustainability | Adoption Implementation Sustainability | |
Elements ERIC [17] | Develop a formal implementation blueprint Develop and organize quality monitoring systems Promote adaptability | Develop educational materials Develop an implementation glossary | Conduct educational meetings Create a learning collaborative | Audit and provide feedback Conduct local needs assessment Provide ongoing consultation Tailor strategies | Use advisory boards and workgroups Create a learning collaborative Promote network weaving Capture and share local knowledge | |
Timing roll-out | Start of the implementation | Start of the implementation | Day 1: 2 months after start Day 2: 5 months after start | Every three months or whenever requested, physical and online meetings | Quarterly meetings 1Â h in online format | |
Intended users | Project leader Team members | Project leader Team members | Project leader Team members | Project leader Team members | Project leader Team members | |
Type of element | N.A. | Passive | Active | Active | Active | |
B | Results survey | |||||
Exposed | N.A. | 12/17 (71%) | 8/12 (67%) | 13/17 (76%) | 10/17 (59%) | |
Users by profession n /exposed (%) | N.A. | 8/12 (67%) ICP: 6 IT: 1 Project manager: 1 | 4/8 (50%) ICP: 4 | 7/13 (54%) ICP: 5 MM: 1 IPC management: 1 | 6/10 (60%) ICP: 5 MM: 1 | |
Users by rolea n/total users (%) | N.A. | Project leader: 4/8 (50%) Team member: 4/8 (50%) Developer: 5/8 (63%) User: 5/8 (63%) Leader department: 2/8 (25%) | Project leader: 3/4 (75%) Team member: 3/4 (75%) Developer: 3/4 (75%) User: 3/4 (75%) Leader department: 1/4 (25%) | Project leader: 3/7 (43%) Team member: 6/7 (86%) Developer: 4/7 (57%) User: 4/7 (57%) Leader department: 3/7 (43%) | Project leader: 3/6 (50%) Team member: 5/6 (83%) Developer: 4/6 (67%) User: 4/6 (67%) Leader department: 2/6 (33%) | |
Phase usea n/total users (%) | N.A. | At the start: 5/8 (63%) During implementation: 6/8 (75%) End of implementation: 2/8(25%) Specific questions: 4/8 (50%) | At the start: 3/4 (75%) During implementation: 3/4 (75%) Specific questions: 4/4 (100%) | At the start: 6/7 (46%) During implementation: 3/7 (23%) End of implementation: 1/7 (8%) Specific questions: 4/7 (31%) | N.A. | |
Recommendation to colleaguesb | N.A. | 88% | N.A. | 100% | 67% | |
Self-reported effectivenessc | N.A. | 38% | 100% | 100% | 83% |