What is Data Courier? If you worked with Epic or some other enterprise level software, most likely somebody configured it.
- There will be connectivity to set up with one or more database engines.
- There will likely be application servers, web servers, print servers, special purpose servers.
- There will be networking and load balancers
- and a ton of configurations,
- and of course, issues related to them all–version compatibility, security, networking.
And once you have an idea what this gargantuan King Kong configuration will look like, you’ll want to have it replicated.
- You’ll need a disaster recovery copy of the database that you can move to if, or when, the main database breaks.
- You’ll need a reporting mirror or shadow copy of the main database.
- You will likely need extract data from that shadow via some ETL software which will require its own software, it’s own configuration, and it’s own database engine.
So, now that you have a perfect production environment with every possible necessity met, there is still something missing. Are you going to do all configuration modifications Willy-Nilly in Production all the time? Are you OK with someone making a mistake and blowing away something business critical for all your thousands of users?
You will most likely need a Proof of Concept environment to try out your changes. You will most likely need a Test environment so you can “deploy” your changes or install your changes to Test, and if all works well, you can put them into Production.
You will most likely need several environments where you can try things out safely, and you will most likely need training environments that have no critical production information in them–environments that are as much like Production as possible without invading the privacy of real people with real Production records.
With all of this, you will need some method for migrating your changes from POC to Test to Production and to Training environments.
Data Courier is that.
A website called Health IT Social has a nice layout of typical Epic environments. In this case, they address a special case you will likely run into if you have upgraded your POC environment, for instance and need to migrate data to your TST and PRD environment which have not yet been updated. We went through this experience a number of times, and for awhile even had separate TST environments for ICD 9 and ICD 10.read more