he following is estimates on the duration spent at each milestone when migrating to a newer version of Mirth® Connect by NextGen Healthcare. The caveat is that the duration is an estimate and will vary based on resources available to perform the migration.
- Setting up the test environment (~1-2 weeks). During this time the system and the version of Mirth® Connect by NextGen Healthcare that is being migrated to, should be setup and installed. All the relevant Mirth® Connect by NextGen Healthcare plugins should be installed. All the channels and their dependencies (code template libraries, JAVA libraries, and so on) should also be copied to the new test environment. Essentially a copy of your current production instance should be made to this new test environment with the only difference being the Mirth® Connect by NextGen Healthcareversion.
- Testing channels with messages (~2-6 months). During this time, each channel is tested with messages that are production-level. The messages should be as close as the ones being processed in your current production instance. Any issues with the version change are logged and fixed during this process.
- Migration of channels to production (~1-24 months). Once the channels have been fully tested, they are moved to the new instance of Mirth® Connect by NextGen Healthcare and deployed for go-live. The estimated time for this milestone is broad because some data sources are slow to change configurations on their side. It is all dependent on how your resources and your vendors can coordinate the IP change.
The above milestones can be done in staggered phases where the high priority interfaces or vendors that are quick to change are part of the first phase. The others are done in subsequent phases.
