Health IT and Electronic Health Activate your FREE membership today |  Log-in
 Has anyone connected the XDS.b protocol thru a Interface Engine?
We are beginning to Integrate multiple EMRs with our HIE which uses the XDS.b protocol to transfer CCDs. I'm thinking we will need to the ability to modify these CCDs as they travel between systems. One particular point of concern is the HTML embedded in the CCD will certainly need tweaking for differnt systems, not to mention all he advantages of central administration of the traffic. I'm finding that XDS.b in its early adoption is typically point-2-point, but I'm confident it can be routed thru an engine using SOAP. I'm just not sure it should be. Does anyone have any experiece with this or can address the advantages/dissadvantages.
ASKED: February 28, 2013  6:40 PM
UPDATED: December 11, 2018  9:42 pm

Answer Wiki:
Last Wiki Answer Submitted:  Be the first to answer this question.
All Answer Wiki Contributors:  Be the first to answer this question. billywatts   1,445 pts. , DHIT   15 pts. , Jenny Laurello   160 pts.
To see all answers submitted to the Answer Wiki: View Answer History.

Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


Curious to know the route you took.  We’re at a similar place right now looking at having the CCD’s and XDS.b things go via our engine.  

A couple of questions.
  1. What engine did you end up using to do this?
  2. What HIE do you have?
  3. What physician vendors are you receiving/sending too?
For my own edification, does XDS.b also imply web service?  Can those events be sent via a VPN tunnel? 
We are looking at a few solutions for the engine. 
In order of expense low to high:
  1. Mirth
  2. Cloverleaf
  3. Corepoint
In order of my preference:
  1. Corepoint
  2. Cloverleaf
  3. Mirth
 10 pts.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: