Rhapsody Integration Engine
Our company is searching for an integration engine so we can interface with our customers EMR systems to place completed patient reports into their electronic charts.
This engine also must be easy to setup and maintain since we are not programmers and don't want to write code whenever we want to setup a new customer. Does anyone have experience with Rhapsody Integration Engine? Pros and cons?
StrongBad last edited by
Sorry, not familiar with it.
Interesting. How do you envision this will work?
travisdh1 last edited by
This sounds a lot like someone wanting a technical solution where one maybe isn't needed. Does your company and the customers both use EMR for some reason? If both are not using EMR, why do you want a 3rd party "ingegration" piece, just update the records like normal.
Asking it another way for those of you who work in healthcare and use and integration engine with your EMR which engine do you use and why?
@travisdh1 yes many of our customers use EMR and we need to be able to directly insert our completed transcribed reports into their EMR and our EMR is lacking in some features which is why we need a third-party
We have an EHR... Integration Engine - interesting term.
We get outside reports delivered through a HL7 interface. Basically this means that the Lab puts the data some place that our EHR can access, grabs the files, then our EHR runs a HL7 configuration script against that data to convert it into a forma that is compatible with our system, then uploads it the the DB.
I suppose the integration engine is the HL7 interface in this case.
Lab creates results
Results run through HL7 configurator to generate a HL7 compliant document
Lab SFTPs the file to a server controlled by my EHR
My EHR retrieves the file on a schedule
Runs my EHRs HL7 configurator to generate a file compatible with our system
imports to DB
We only do this with live data right now. Though I don't see any reason why an explanation file couldn't be included with PDF for example, and the explanation file tells me EHR what patient, type of file, etc and then my system stores the PDF in the correct location in our DB.
@alex-olynyk How do you see your product working differently than an HL7 interface?
@Dashrender Our HL7 works perfectly for communication on our internal apps. We want to create an outbound interface to insert reports into our referring physicians EMR and our HL7 is lacking in some areas. For example, each referring physician has an HL7 ID but there is no way to map that ID to a referring physicians EMR vendor which is why we need a 3rd party.
I'm assuming you already have all of your referring physicians on board for their part of the cost as well?
The third party will just be a broker for you.
You could create direct links between your EHR and each one of your referring physicians and use HL7 to send to them.
We have HL7 with several EHRs and labs, etc.
We also have a HL7 with a central hub, in my case called NeHii. My patients are linked to me (not sure how, I didn't do it) and inform that comes into the hub matching at least 2 identifiers is automatically pulled by my system into my DB and sorted as desired.