Answer/Fill-in these questions about the legacy system project to plan for success.
At PDE Health, we strive to understand the unique needs of our clients and tailor a solution that best fits their needs. We assign a Project Manager and Developers to each project to provide real-time support and timely deliverables. Each legacy system implementation is unique, but largely includes a current state review and analysis, small-scale testing, large-scale testing, go-live, and support.
Please review and provide as many details as possible to the below questions. That will allow for the best possible chance for project success.
SOURCE SYSTEM FOR EXTRACTION
• Practice / Office Name
• Source EHR System
• EHR Version
• Source DBMS
• DBMS Server/Instance
• Approximate Size of Database
• Approximate Size of Images/Documents
• Approximate Patient Population in legacy system
REMOTE ACCESS
In this section, we define how our consultants will access the client systems in order to extract data from the various legacy systems. Since it is possible that we will need to access multiple servers, there are several spaces below to define connection points.
• Connection Type
- VPN
- RDP
- Other
- None
CONVERSION ELEMENTS
Please indicate which elements are to be extracted:
- Demographics
- Images
- Documents
- Encounters
- Vitals
- Assessments
- Immunizations
- Medications
- Allergies
- Chronic Problems
- Orders
- Procedures
- Labs
- Flow Sheets
- Notes
- Claims / Charges / Ledger Data
- Other – as each system is unique and custom content can be added, working with the client to ensure that all areas of the medical legal record are captured is a top priority. Luckily, we have worked with enough legacy system vendors and enough organizations to ensure we capture everything needed.
TIMELINE
Please indicate the date in which the data must be extracted from the source legacy system and delivered to the destination:
Date:
SYSTEM REQUIREMENTS
If your organization is planning costs for archival, and plan on hosting the system locally, then it’s important to plan for a system that needs the approximate following specifications:
| Description | Minimum | Recommended |
| Web Server / DB Server | — 2 Cores –Internet Information Server (IIS) 6.0 or later –Server operating system able to run IIS –8 GB Ram | –4 Cores –Internet Information Server (IIS) 6.0 or later –Server operating system able to run IIS –12 GB Ram |
| DBMS | –SQL Server 2012 or later –Server OS capable of running SQL Server | SQL Server 2012 or later –Server OS capable of running SQL Server |
| Storage | Determined by the amount of data in the source system | Determined by the amount of data in the source system |
| Backup / Restore | TBD | TBD |
| Supported Browsers | –Current and one Version Prior –Internet Explorer 10+ –Firefox 29+ –Chrome 34+ | –Current and one Version Prior –Internet Explorer 10+ –Firefox 29+ –Chrome 34+ |
KEY CONTACTS
• Client Project Manager – Stakeholder
- Name
- Phone
• Client Project Sponsor – this is a user that is a decision maker who can start and stop a project whenever is necessary.
- Name
- Phone
• Client Security Officer — this is a user that is a decision maker who can start and stop a project whenever is necessary.
- Name
- Phone
• Client IT Contact
- Name
- Phone
Partner Up
As more features and requirements are collected, we will post them here as well. If you have any immediate questions, shoot me a message, I can steer you in the right direction.
No matter what you end up doing with your legacy systems, do something. “There are two types of people in this world, those that have lost data, and those that are about to.” Archive those old servers and save funds today by ensuring you dont need to upgrade the hardware and software of those old legacy systems.
-Dan Holleran | 314-471-3409 | dan@pdehealth.com | www.pdehealth.com
PDE Health is an advanced data solutions firm, and have developed the CHR Base product. Visit our website to learn more about who we are and what we can do as a good business partner in the healthcare data industry.
