Agree the clinical, digital and information-governance review before any live use.
Wai offers clinical workflow tools. Define the intended pathway and assess the evidence, controls and responsibilities with your local teams before deployment.
Assess how drafts are created, reviewed and signed for your proposed pathway.
Review the approval and exception rules for each patient-facing workflow before use.
Define responsibility for results, follow-up and escalation with the care team.
Agree the hosting, access and data-processing terms for your organisation.
Agree the manufacturer and deploying organisation responsibilities, the safety evidence and any open work for your intended use.
Check the approval rules, automated actions and exception handling for the proposed pathway.
Agree the hosting, access and processing terms with your information-governance team.
Discuss the intended use, relevant evidence and review process with clinical safety teams before deployment.
Review which actions require human approval, what can happen automatically and how exceptions are handled for the proposed workflow.
Review the applicable clinical safety, data protection, technical assurance, interoperability and accessibility requirements for your intended use.
Request the current assurance evidence, scope and any open items through a named review process.
Agree the data flow, access and processing terms for the intended deployment.
Tell us the pathway you are considering. We can arrange a scoped discussion with the relevant clinical, digital and procurement teams.
Ask for relevant wai assurance materials through our team. Procurement information is on the public sector page.