PilotFish Interface Exchange (PIE)

A marketplace for eiConsole (IDE) interface templates, components and industry bundles
eiConsole IDE 90-Day Free Trial!
Licensor contacts
Associated Industry
Insurance
Associated Application
New Business/Underwriting
Prerequisites
The eiConsole IDE is highly recommended to support graphical development of interfaces for deployment to the eiPlatform runtime The eiPlatform is required to run in production interfaces configured using the eiConsole
Version
7.11R1
Release Date
March 15, 2011
Resource Type
Interface

Product details

MIB WEB-DIRECT Interface

This interface enables the connection of any system to the Medical Information Bureau's (MIB) WEB-DIRECT service. The interface produces the ACORD-compliant XML MIB Request transaction, consumes the MIB Response transaction and produces the MIB Update. Licensees can use the Data Mapper component of the XCS eiConsole to transform their in-house proprietary formats to and from the MIB ACORD-compliant format.

Services Description

For many, communicating with trading partners using ACORD compliant XML is a relatively new challenge. Fortunately, PilotFish Technology has experience working with the MIB and can take what may appear to be a daunting task and make it simple and quick. PilotFish is a Certified Alliance Partner with the MIB and has already built, tested and implemented the new ACORD XML MIB request and response. In most cases, we can provide end-to-end integration to get you up and running with MIB in 15 person-days or less.

PilotFish Technology will implement the new ACORD-compliant method of communication with the MIB that utilizes SOAP web services transport. Working collaboratively with your technical staff PilotFish Technology will:

* Analyze the required data output for the request and received in the response and determine additional data requirements.

* Create the transformation from the current format to the new ACORD format for the request and the transformation from the ACORD format to the preferred format of your company for the response.

* Configure the appropriate Listener to support your preferred method of outputting MIB request and update data. Listener support includes: Database Tables, Directory, Email (POP3), Encrypted FTP, FTP, HTTP Post, JMS, SOAP Web Service and Programmable Java.

* Configure the appropriate XCS Transport to support your company?s preferred method of receiving MIB responses. Transport support includes: Database Tables, Directory, Email (SMTP), Encrypted FTP, FTP, HTTP Post, JMS, SOAP Web Service and Programmable Java.

* Install the new MIB interface on the XCS eiPlatform server at your company?s site and test the end-to-end MIB interface with the MIB test bed using the digital certificate assigned by the MIB.

* Provide a detailed explanation of all components employed to accomplish the interface, hands-on training and formal education on the use and maintenance of the interface.

Why engage PilotFish to support the new MIB Inquiry/Response?

* The MIB interface is already developed, tested (including digital signature), implemented and certified by MIB. The only customization is transforming the older MIB Request or proprietary source format to and from the new format.

* PilotFish Technology is the only Certified Alliance Partner of MIB

* We are members of ACORD and participate in the Requirements Subcommittee that has defined the MIB TXLife 401, 402 and 404 transactions.

* According to Steve Marshall of the MIB, we have implemented the interface in less than 1/10th the time of the next closest alternative and more than 100 times faster than some who have chosen to tackle it in-house.