Health IT and Electronic Health Activate your FREE membership today |  Log-in
Home > IT Answers > Health care applications and vendor organizations > Application interface strategy
CurtKwak
5 pts.
 Application interface strategy
epic, HIS, Integration Engine
Hello,

We are in the process of maintaining our current portolio of legacy applicatins while we move ahead with implementation of Epic as our primary HIS.  What is the most recommended application & data interface strategy to ensure the key & critical legacy applications are successfully interfaced back to Epic/HIS?

thank you.



Software/Hardware used:
Epic
ASKED: May 13, 2011  5:26 AM
UPDATED: June 6, 2011  7:02 am
RELATED QUESTIONS
Answer Wiki:
The best approach would be to review what data your HIS team will be looking at transferring into the EPIC system. Identify whether you will be needing the x-rays, MRIs, Scanned documents, Lab results, scanned labs, etc. Once you review that, then I identify which ones you can migrate over or interface (completing the Epic Bridges training will be a huge help at this stage).
Last Wiki Answer Submitted:  May 16, 2011  3:07 am  by  RedaChouffani   1,785 pts.
All Answer Wiki Contributors:  RedaChouffani   1,785 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Is your concern the interfacing of these legacy applications to Epic or is it the ability to import data from your existing HIS to Epic? If integration is your concern then I would document your existing messages to and from your current HIS to the other legacy systems.

Yetters
 10 pts.
 

We have had experience migrating several legacy application historical data into EPIC, and it really is a customized scenario depending upon the legacy system. One possible strategy is to load 1-2 years worth of clinical information into EPIC, and maintain the prior data in a “legacy portal” while turning off the legacy system (and saving on licensing fees).
The portal can be implemented in a modern supported platform, and meets records retention requirements.

Sanjaypatil464
 10 pts.