09 – Strengthening Information Systems and Linkages to Care

After determining requirements, it is essential to create an implementation plan in consultation with the software development team. This plan should detail when specific components of the system will be made available to test and use, ideally synchronized with when the programme will actually start implementing those processes in the field. As a basic example, for a programme just starting out, it is more important to have a screening tool in place up-front than a follow-up tool, since the first follow-up will likely not happen until a month or two after the first patient is diagnosed. The implementation plan should also detail timelines for end-user feedback, the timelines by which a delivered component should be tested in the field, and the timelines by which any changes and bug-fixes must be incorporated before the component goes live. It is usually not a good idea to build the whole system first and then test it in its entirety. A better and more efficient approach is usually an iterative one, whereby implementers get to try out different components at different stages of development and provide feedback. Of course, this means that implementers need to be involved throughout the whole process. Having a detailed implementation plan agreed to by all stakeholders will ensure that all groups are aware of how the system will be introduced and improved over time, thus helping to manage expectations over timelines, scale, the features that will be made available over time, and the effectiveness of the system.