Download to read offline
Implementing a new clinical system
- 1. Implementing a NewClinical System By Shane Allen
- 2. The Pre andPost Procurement Phases • Pre-procurement – Feasibility study – Requirements Analysis • Procurement • Post-procurement – Testing – Implementation – Maintenance and Support
- 3.
- 4. Feasibility Review (TELOS) •Technical Feasibility – Does technology exist to implement new system? • Economic Feasibility – Is proposed system cost effective? • Legal feasibility – Any conflict with legal requirements? – e.g DPA • Operational Feasibility – Are current work practices/procedures adequate? • Schedule Feasibility – Can it be done in a desired time frame?
- 5. Requirements Analysis • Howdoes the current system work – Data gathering – Data analysis • What the new system will do – Functional – Non-Functional • Report is filed – Detailed description of the above – Recommend solution
- 6.
- 7. Testing • System Testing –Performance – Stress – Security – Regression Testing – Disaster Recovery • User Acceptance Testing – End user testing to validate that the system meets their requirements.
- 8. Implementation • Site preparation •System documentation • End user training • Conversion (Parallel, pilot, phased, plunge)
- 9. Maintenance and Support •Types of Maintenance: – Corrective Maintenance – Customized – Preventative – Data Backup/User configuration • Support: – Service Desk
- 10.
- 11. Thank you forlistening Any questions?
Editor's Notes
- #2 Good morning everyone, my name is Shane and I’m about to give you a short presentation about … title
- #3 The topics I will be discussing are: And briefly discussing who we need to engage with for successful delivery.
- #5 This is to check if the system is viable or not. Here are the main areas of review. Technical feasibility – We need to involve IT specialist to review the current technology or any hardware/software/network issues necessary for the proposed system. Economic feasibility – A cost/benefit analysis of the system needs to be performed. We need to involve Budget holders/finance and procurement. Legal Feasibility – We may need to involve legal teams E.g conflict of interest with Existing suppliers or information governance team for any legal issues with DPA. Operational Feasibility – An example of this checking the proposed system is in line with current working practices or is any change going to be detremental to quality of patient care. We therefore we need to interact with the user. Schedule Feasibility – The result of this stage can be a GO or NO GO.
- #6 We need to engage with the users e.g. Clinicians, nurses, bms to find out about the current system. Data Gathering - This can be done by interviews, reviewing current documentation and looking at the current system. Data Analysis - Entity relationship diagram – graphically represent the associations between the entities in the system. Data flow diagram – graphically show the flow of data in the system We also need to find out what the users want out of the new system. Functional Requirements - Describe the processing/functions of the new system. Non-Functional Requirements - These are the qualities of the system and usually supports the functional requirements e.g Performance Reliability requirements Security considerations Usability requirements At this point we may have to engage with IT specialists for information on Hardware/software configuration of the current and new system. Finance and procurement as regards to the costing of the system. Software developers if in-house design, And estates if there is any necessary structural modifications. Report:summarize the problems in the new system describes the requirements of the new system costing implementation options (in-house design, outsourcing) possible hardware configurations Recommend solution
- #8 The testing team may consist of ourselves, NWIS, the software company, and the users. Performance – Testing the system with a data/transaction volume that is within and at the top of the range that was stipulated in the requirements phase. Stress – Expose the system to data/transaction volume that is higher than what would normally be expected, and over a concentrated time period. Security – Testing that users have the correct level of access and that unauthorised users have no access. Disaster Recovery - Test to see if you can recover the system from a simulated disaster. User Acceptance Testing – This is allowing the end user to validate that the system meets their requirements that they stipulated in the requirements analysis phase by simulating real life tests. After the test is completed, the user either accepts the system or else identifies further changes required.
- #9 Site preparation. We have to engage with the users and This involves IT to co-ordinated deliveries of hardware/software to accommodate the new system. (New Pc’s, Barcode readers, Server config, Networking). Estates may be involved to make sure any structural changes are in place. System documentation. Systems manager - Writing of system manuals and SOP’s for all aspects of the system. End user training. Liase with the users as regards to training and suppliers if they are providing courses. Training the users on how to use the system. This could be via workshop courses or training one member of staff who will then act as the dept trainer Conversion –systems manager will need to schedule - IT staff for any technical problems, software developers, users with senior staff.
- #10 Maintenance – This is usually the longest phase of the system lifecycle as it continues throughout the whole life of the system. Usually in the form of patches or updates. Corrective Maintenance -Regardless of how well designed, developed, and tested, errors will inevitably occur. This type of maintenance deals with fixing or correcting problems with the system. Customized Maintenance. This type of maintenance refers to the creation of new features or adapting existing ones as required by changes in the organization or by the users. Enhancement Maintenance. It deals with enhancing or improving the performance of the system either by adding new features or by changing existing ones. Need to engage with the user’s support team and software developers Service Desk - It provides a single point of contact for users to gain assistance in troubleshooting, get answers to questions, and to log problems found in the system. The support team will prioritise user requests and reported problems, and manage them by passing them onto the appropriate staff via triage
- #11 To summarise, to successfully implement a clinical system, we need to ensure each of these phases are completed within schedule and budget whilst engaging with the necessary stakeholders that are appropriate for that particular clinical system.