Our Work: Electronic Medical Records System
In compliance with federal requirements, the Alaska Psychiatric Institute (API) implemented a commercial-off-the-shelf (COTS) Electronic Medical Records (EMR) system. Although the implemented EMR modules were functional, API was planning to add modules and make enhancements to achieve their vision of a paperless medical records system.
API asked Resource Data to provide expert IT project management help to create and implement a strategic plan, particularly around EMR and tele-behavioral health initiatives.
“RDI has been a valued partner in our efforts to continually improve the quality of care our patients recieve.” —Ron Adler, CEO, Alaska Psychiatric Institute
After documenting API’s EMR implementation, our Project Manager developed and maintained a multi-year IT strategic plan. In this plan, he identified upcoming IT projects related to the EMR and API’s tele-behavioral health initiative. For each project, he
- Determined criticality, benefits, and risks
- Developed cost estimates
- Defined a high-level schedule, identifying the general timeframe based on API’s priorities and dependencies between projects
In addition to serving as the Program Manager for this collection of projects, our Project Manager also managed some individual projects. For example, he
- Implemented a process for organizing, prioritizing, and tracking issues, with particular focus on the EMR
- Managed multiple major EMR upgrades and enhancements, including incorporating electronic billing, clinical records, and medicine administration
- Developed the requirements for procuring voice recognition software to automate transcription (populate the EMR by speaking), such as for physician notes
- Created downtime reporting so that API knows which medications to give patients when the EMR is unavailable
- Integrated systems to enable sharing of medical records with outpatient providers
- Developed an IT disaster recovery plan to ensure that medical records are available in an emergency
Our Project Manager became an integral part of API, filling a role similar to a CIO. In this role, he worked closely with stakeholders throughout API as well as with individuals from State agencies, the behavioral health community, software vendors, clinical and billing consultant teams, and contract developers.