#Meditech expanse software license
#Meditech expanse drivers
#Meditech expanse update
#Meditech expanse full
#Meditech expanse software

In addition to all the other projects and phases that support the implementation of Expanse, it must be kept in mind that the data conversion almost always requires more time and resources than originally intended. How will downstream systems be affected by new patient identifiers?.How long do I need to license the legacy system before pursuing decommissioning?.How much am I going to be paying each month in maintenance for my legacy system?.

Do I have enough resources to cover extended trainings and existing maintenance?.

#Meditech expanse software

Does the reporting software allow me to combine data from multiple systems?.How are business offices going to continue to collect revenue?.

#Meditech expanse full

Are our processes fine-tuned enough to be down for a full day?.

How am I going to access legacy patient data?.

Other considerations for planning, scoping and strategy include: Keep in mind though that the data that can be extracted from the legacy system often limits what can be converted to Expanse.

Document Images (Notes and Scanned Documents).

MEDITECH supports conversion of the following data elements to Expanse: When scoping the data conversion (which clinical elements should be migrated, how many years of data should be converted), formation of a Physician Advisory Council can be effective to ensure proper data governance.

#Meditech expanse software license

Examples include software license renewal dates for legacy systems, mandated pending hardware refresh dates, loss of data center or system access, and replacement system go-live dates and transition timelines.

#Meditech expanse drivers

It is critical that all drivers for Expanse transition are clearly communicated. There should be advance notice about the deadline for making validation resources available. To meet the project’s timelines, client end-users must provide validation support at the right time and in a prompt manner. This SME should also be relied on to make decisions about data for the system in which they have expertise.Ĥ. This SME will need to carve out dedicated time throughout the project to support the project team. It is important that an SME be identified prior to contract signature for each in-scope application. Institutional knowledge of the legacy OV system is critical to data conversion success.

#Meditech expanse update

There should also be a contract provision that the legacy OV will update extracts for missing data at no additional cost and in a timely manner.ģ. In the event a full database copy cannot or will not be provided, a detailed specification should be available for review before data delivery. This risk can be reduced by requiring the legacy OV to provide full database copies throughout the project. When an OV is required to provide an extract of the data, such as a vendor-hosted application, it almost always produces incomplete data, resulting in project delays and additive costs.

This can be mitigated by organizations starting well before contract signature to identify who is able to grant and process the access. Typically, this an afterthought, but once an organization starts to request access, the institutional knowledge needed for dependencies including granting database and front-end access to several in-scope applications can be elusive. The single biggest hurdle to starting and delivering a project on time is obtaining required access to the legacy data. That said, a data conversion project does come with its own risks, and we have distilled the top considerations to address: Migrating that data makes a marked difference in the ability to achieve increased provider satisfaction and return to full utilization. But if your organization utilizes an EHR that is not built or supported by MEDITECH, you should maintain the value of your clinical data that has already been entered into existing EMRs through a data conversion to Expanse.Ĭonverting legacy system data to Expanse ensures clinical continuity and maximization of usability at go-live. With Expanse, MEDITECH has delivered a single EMR platform that gathers all the health data needed for treatment across care settings. Note: While this article addresses specifically converting data to MEDITECH Expanse, most of these principles apply to any EHR data conversion. The following is a guest article by Justin Campbell, Vice President, Strategy, at Galen Healthcare Solutions.