These should be at regular intervals (every week or as the project dictates) to discuss any outstanding hazards, functional risk assessment, hazard log review and any related topics. It is advised that at least one day a week is allocated for clinical safety activities and may be adjusted according to need which must be justified.
Clinical safety review meetings
The safety review meetings will usually include the supplier and health organisation clinical safety officers (CSO), but may invite other members of the project team if there are specifics that need to be discussed in greater detail.
3. Hazard log review
This is the best opportunity to review the hazard log including any new hazards that have been introduced by the risk assessment process. It is important that all hazard log references are documented against any development work and incidents that have been reported for clarity and consistency.
4. Clinical safety management review
The review meeting can also include discussion regarding the clinical safety management in general and review how it is working. This gives the CSOs an opportunity to update documentation and process if required.
Clinical safety process outputs
Expected outputs at this stage of the clinical safety process which will be reflected in the risk management file.
Updated hazard log
Whilst the hazard log is a living document and continues to be updated during the lifecycle of the health IT system, a base-lined version is to be issued with each clinical safety case report.
Each version of the hazard log has to be reviewed and approved by the clinical safety officer to signify that the clinical safety information recorded is accurate and appropriate.
Clinical safety documentation updated
Any clinical safety documentation can be reviewed and updated accordingly depending on need.