Replacement of eGate for Hospital MediTech Integration
October 14, 2010Challenge: This client needed a more capable integration solution that would allow for the replacement of the existing eGate and Iatric MediTech interfaces. It was important for the client to utilize technology such as XML, Database Direct and other web services for near-future integrations. They desired a platform for building a service oriented architecture that could integrate with other organizations, including Health Information Exchanges.
Solution: As the client already had Microsoft SQL server and .Net experience in-house (the underlying BizTalk technologies), they naturally chose to utilize Microsoft BizTalk Server for all their interfacing needs (including HL7). They contacted Prosch to help get them started.
The Prosch team helped to identify existing interfaces that needed replacing and new interfaces that required additional planning. Once identified, a solution was delivered that allowed the client to work collaboratively with Prosch in replacing over 50 interfaces. Through additional training provided by Prosch, the client was able to bring interface development in-house.
The components developed for the BizTalk implementation were then reused across the organization. These components were even used outside of BizTalk, including integration with Active Directory.
By replacing eGate with BizTalk 2009, the Prosch team was able to help this client become self-sufficient in regards to its integration needs. Interfaces that once took 2 months to create are now taking just days or even hours. The additional cost per interface has been eliminated, as all the interfaces are now developed using internal resources. The solution also allows the client to host non-HL7 interfaces on the same platform.
This customer now counts on a significantly higher level of capability that did not exist with the legacy integration solution. They can count on the ability to take on more complex, long-term projects while keeping down their costs.
Are you evaluating BizTalk as an integration solution? Contact Prosch to get help with a proof of concept project, or schedule a BizTalk Lunch and Learn for your group.
MediTech Integration Solution
September 22, 2010Challenge: This hospital client needed a more flexible integration solution for increasingly complex integration projects. They were in search of an integration partner that could ensure significantly faster turn-around times on new MediTech interfaces and lower per-interface costs long term.
Solution: The client chose to utilize Microsoft BizTalk Server for its HL7 interfaces, and contacted Prosch to help them get started.
The Prosch team worked closely with the client to determine the scope of their needs. The first step was to establish BizTalk 2009 infrastructure and best practices for development of new interfaces. Once the infrastructure was in place, the Prosch team started by helping to establish several new ADT interfaces.
BizTalk Server, the Prosch team, and our integration apps are now delivering new HL7 interfaces within a couple of weeks start to finish, compared to eight to ten weeks from the previous vendor. Cost per interface has been reduced by more than 25%, with no per-interface maintenance fees.
This customer now counts on a significantly higher level of capability that did not exist with the legacy integration solution.
Are you evaluating BizTalk as an integration solution? Contact Prosch to get help with a proof of concept project, or schedule a BizTalk Lunch and Learn for your group.
Billing integration for Reference Laboratory
September 13, 2010Challenge: Consolidate charges from two laboratory information systems
Solution: This complex integration required warehousing HL7 charge messages from two separate lab information systems, then consolidating them by order before transmission to the client’s billing vendor. Prosch worked with both LIS teams and the billing vendor to architect and built a BizTalk Server solution with reconciliation reporting to ensure that all charges were delivered successfully.
Client integration infrastructure for Laboratory
September 13, 2010Challenge: Simplify on-boarding of new client interfaces and replace legacy integration solution with Microsoft BizTalk Server
Solution: This reference laboratory client needed to replace its Cloverleaf engine and existing client interfaces as part of a larger effort to implement a new lab information system. The client was leaning toward Microsoft BizTalk Server for its HL7 interfaces, and contacted Prosch to help them get started.
The Prosch team observed and documented laboratory workflow from accessioning through report generation, got up to speed on the legacy integration solution, then built a small proof-of-concept (POC) BizTalk proof of concept project. Once the client verified BizTalk as a good fit for needs, Prosch architected the production solution, provided BizTalk HL7 training to the interface team, and built the first 25 client interfaces.
The BizTalk Server solution that Prosch delivered significantly reduced the development effort for each new client interface.
To Do: Discuss Centralized exception handling and notification. Replaced code with BizTalk maps?
Are you evaluating BizTalk as an integration solution? Contact Prosch to get help with a proof of concept project, or schedule a BizTalk Lunch and Learn for your group.