If you are like many healthcare organizations, you may find yourself several years post go live and yet you still don’t have a plan to handle your legacy system data. Sound familiar? When a new system is introduced like an electronic medical record (EMR) or practice management system, complete with new bells and whistles, it’s common for the legacy system to lose focus. And yet the costs of running an out of date system for longer than necessary can be significant and painful.
Hayes' Healthcare Blog
Topics: Legacy System
If you are like most healthcare organizations, chances are you are currently implementing a new electronic medical record (EMR) system, preparing for a new initiative like Meaningful Use or ICD-10 or upgrading a current system. It’s not always easy to put together an effective go-live support team. Early acquisition and training of the go-live team is often overlooked or under-appreciated, despite its direct link to the success of the project
Workflow is a major concern for most clinicians with the introduction of an electronic health record (EHR) or other new technology into the clinical practice. An EHR promises many advantages for improving quality and efficiency, yet the introduction of an EHR can be very disruptive to existing workflows. The EHR major usability pain point is usually to include configuration, integration, presentation, content, data integrity, policy, and performance.
Don't you hate it when you go to the store and you can't seem to remember the item that you went out for because you didn't write it down?
With a healthcare IT project the importance of documentation is magnified a hundred fold. This is particularly true if you are involved in creating processes and procedures, are responsible for managing a project or part of a team that is designing or implementing a new system. Let’s face it, most healthcare projects are fast moving and evolve significantly from beginning to end. To keep track of changes there are a few best practices we suggest. Get into the habit of documenting changes, notes and to do lists. Share your documents with other team members and ask for feedback. Utilize a sharing system like a shared file or software (e.g. SharePoint, LiveLink, etc.) so that it can be easily accessed and referenced. For example, when working on a system enhancement it’s best to have a test plan where a team can work collaboratively to create test scripts and document results and findings. When working on an implementation, a project plan will help you and the rest of the team members coordinate work efforts and help head off any potential surprises.