| If you've got an electronic patient record system, | | | | software to be able to work with other software, |
| and it's causing more problems than it's worth, or | | | | and it doesn't then this can cause problems. |
| isn't providing you with the information you need, | | | | Perhaps you need to be able to export the date |
| or means that patients are waiting or suffering | | | | for reporting purposes, or need to be able to |
| unnecessarily, then you might need to replace it. | | | | import patient data for patients who have moved |
| 1. If your electronic patient record software is | | | | to a new surgery. An electronic healthcare |
| hard to use, then you and your staff won't want | | | | system that is easy to use, and is flexible will be |
| to use, and certainly will be fed up with it when | | | | better for all concerned. |
| you're busy and at the end of your shift. | | | | 8. If your current healthcare system meets staff |
| 2. In order for it to be useful, the software needs | | | | needs but not patient needs, then it's not right. |
| to be quick, so that patients are not caused | | | | Your patients need to be the priority, not your |
| additional distress whilst they and you wait for | | | | staff. |
| databases to connect, and records to be updated. | | | | 9. The security of the system is of paramount |
| 3. Reliability is key, as the information contained is | | | | importance. With so much personal data around, |
| obviously very sensitive, and can be a matter of | | | | as well as their medical history and current |
| life and death. A system that is unpredictable, or | | | | treatment, your electronic healthcare software |
| crashes a lot can't be used in a hospital. | | | | needs to be safe. If your software doesn't have |
| 4. If you're system doesn't really meet your | | | | different levels of access, or the ability to restrict |
| current needs, then it's very unlikely to meet | | | | patient information so that only those who need |
| your future needs either. You'll need to establish | | | | to know can access it, then it might be time to |
| what sort of requirements you're likely to have | | | | change it for a healthcare system that is more |
| so that you can implement the systems and | | | | secure. |
| facilities your patients really need. | | | | 10. It might be that your healthcare system can |
| 5. If there is a steep learning curve before people | | | | be tailored to provide everything that you need |
| can use the system effectively, then there are | | | | and want from it, but the costs keep spiralling. |
| likely to be additional training requirements, which | | | | Perhaps there is downtime and additional staff |
| can impact on the number of staff available and | | | | training as well as the financial costs to think |
| the standard of care given. | | | | about. If you're not getting the value for money |
| 6. If support staff are constantly on site trying to | | | | that you think you should be doing, then why not |
| resolve problems, or a lot of time is spent calling | | | | see if there's another option? |
| helpdesks or waiting for patches, fixes and | | | | Now you know what sort of things you need to |
| updates, then it might be time to replace your | | | | be aware of, does your electronic patient record |
| electronic health record software? | | | | software need replacing? |
| 7. If you need your electronic patient record | | | | |