scores, one for a child at high risk, one for a child at moderate risk, and one for a child at low risk. The approach to families with children at different risk levels should be different. Obviously, the parents of children at high risk need to understand the severity of the problem, but it is just important that the parents of children at low risk not be burdened with undue worry about a problem unlikely to affect their infant. By incorporating these stakeholders into the change process at this point, accepting change in their workflow will not be as difficult. There will be excitement rather than resistance as they know what and how change is coming. At this point, it will be possible to identify nurses and neonatologists to serve as clinical champions to help those less involved in the process understand how to use the risk score clinically. Once the CDSS is developed, the system must be tested prior to implementation, to determine where improvements or changes need to be made. Among other methods of evaluation, a successful user acceptance test will be critical to the successful deployment and adoption of the CDSS. Any errors or failures of the CDSS must be identified during the testing period, triaged and fully documented, and eventually remediated. Otherwise, end-user adoption may not follow which will invariably result in an overall project failure. Implementation. One advantage of involving stakeholders and end-users in the creation of the CDSS is providing them with a sense of ownership. Clinical champions and super users will be critical at this phase, who will serve as ambassadors of the new CDSS. They should be available and ready to assist end-users when needed, particularly at the time when the CDSS will be utilized the most. Staff surveys initially may not be helpful but after implementation could provide crucial feedback about issues and needs for improvement. During the first few weeks after rollout, the project team members must be available to answer questions and help interpretation of the results. During the initial deployment stage, allowing end-users and other
scores, one for a child at high risk, one for a child at moderate risk, and one for a child at low risk. The approach to families with children at different risk levels should be different. Obviously, the parents of children at high risk need to understand the severity of the problem, but it is just important that the parents of children at low risk not be burdened with undue worry about a problem unlikely to affect their infant. By incorporating these stakeholders into the change process at this point, accepting change in their workflow will not be as difficult. There will be excitement rather than resistance as they know what and how change is coming. At this point, it will be possible to identify nurses and neonatologists to serve as clinical champions to help those less involved in the process understand how to use the risk score clinically. Once the CDSS is developed, the system must be tested prior to implementation, to determine where improvements or changes need to be made. Among other methods of evaluation, a successful user acceptance test will be critical to the successful deployment and adoption of the CDSS. Any errors or failures of the CDSS must be identified during the testing period, triaged and fully documented, and eventually remediated. Otherwise, end-user adoption may not follow which will invariably result in an overall project failure. Implementation. One advantage of involving stakeholders and end-users in the creation of the CDSS is providing them with a sense of ownership. Clinical champions and super users will be critical at this phase, who will serve as ambassadors of the new CDSS. They should be available and ready to assist end-users when needed, particularly at the time when the CDSS will be utilized the most. Staff surveys initially may not be helpful but after implementation could provide crucial feedback about issues and needs for improvement. During the first few weeks after rollout, the project team members must be available to answer questions and help interpretation of the results. During the initial deployment stage, allowing end-users and other
session_10_almacen_maria_and_kelly_christopher_the_rop_screening_and_risk_assessment_tool_finalpaper.docx