Implement a New Customer in Under 30 Minutes!
As a solution provider, you know time is money. The quicker you can automate processes and implement a new customer the faster you can get revenues in the door. To accomplish this, you need an HL7 Interface Engine that offers automation, flexibility and an architecture designed to highly leverage reuse so that you can implement new clients, fast!
PilotFish Puts You on the Road to Reuse Success
The secret to reusability and how easily an interface can be cloned and tweaked is directly related to an engine’s design and architecture. Not all interface engines make it easy; some don’t offer the capability at all. PilotFish, on the other hand, is designed to make interface reuse fast and easy.
Here’s why. Interface configuration in the eiConsole for Healthcare starts in the Route File Management window. Reuse starts by selecting “Duplicate” from a drop-down in the File menu. You “Create Duplicate”, rename it and double click the “OK” button to open the Automated Graphical Interface Assembly Line window. Next, a user steps through the 7 stages of the assembly line to quickly tweak the interface for new client requirements.
In the Assembly Line, working left to right, you start with the Source System. Perhaps you need a new Source System. You select the stage, rename it and select a new representative icon (if required). Changing communications protocols is simple, as well. It’s done in the Listener stage. Select it and a panel opens. You may need to change connectivity from HL7 LLP to a Directory/File. From the drop-down select the new Listener type and fill in a couple of fields in the custom configuration panel.
The next stage is the Transform stage. Here you may have new data that is coming in as a CSV, and it needs to get pushed into a SQL database. The eiConsole converts Source data into a canonical XML format. When converting from more than one source into more than one target, a canonical format significantly reduces the number of transformations that need to be written. Data transformation is accomplished in the eiConsole’s Data Mapper. In the XML panel, clicking the “Edit” button opens the Data Mapper. The Data Mapper component has three panes. You map data by dragging from your Source column on the left, or Target on the right, into the middle panel. Using drag & drop you can easily remap your data as needed. You can even reuse whole or portions of mappings from other interfaces.
Next, is the Route stage where you can set up Routing Rules or Transaction Monitors. Need to set up an email alert?. This is done by selecting the Transaction Monitoring tab and choosing Email alert from the drop-down. A new configuration panel opens where you simply need to fill in a few fields. Next, the Target Transform stage. If we want to take the CSV file that was converted into XML and push it into a SQL database, here too, we will use the Data Mapper to convert the XML data into an SQLXML. After we map our data, we’ll move on to the Transport stage. If we needed to, as on the Listener stage, configure a new Transport, we use the drop-down to select a new transport type and fill in a few fields. If we need to add a new Target System, we’d click the Add Target button, name it, select a representative icon. You can test your interface end to end in the graphical test mode by selecting Testing Mode from the Route menu.
That’s it. All of your tweaks can be made following the eiConsole’s assembly line process and generally, per our clients, accomplish this in under 30 minutes.
Nearly Every Organization Can Benefit from Reuse
Speed and ease of use are why organizations in virtually every area of healthcare have been able to leverage PilotFish for reuse and shorten their implementation timelines. Leveraging PilotFish interface templates and components makes great business sense by making your implementation costs and time very predictable. Here are just a few examples of the kinds of PilotFish customers who are leveraging reuse:
Food Nutrition Management Service Provider (FNMS)
The division of one of the nation’s largest foodservice and support services company offers a cloud-based solution that provides patient-specific dietary food requirements. This solution is integrated with Hospital EMR and billing systems. After licensing PilotFish, receiving a few days of training and the initial creation and implementation of half a dozen interfaces the client created their “gold standard” interface (based off of an Epic integration). This interface, by the company’s account, is the most flexible and extensive so that it can be tweaked to suit nearly every new client requirement. By using their default interface template, they can now implement a new customer by simply cloning and tweaking the interface. This is being done in under 30 minutes.
Revenue Cycle Solutions Management Company
This clinical laboratory billing and collection company offers a cloud-based solution that enables lab clients to maximize profitability through optimization of their revenue cycle and reimbursement process. After some initial training and the creation and implementation of just half a dozen interfaces the client can copy an existing live interface, rename it, tweak the mapping to fit, run a couple of test files through and then turn it on live, all in under two hours.
Medical Equipment Company
This medical equipment company with international distribution provides the automated medication dispensing carts that are integrated with Hospital EHR systems. The client bundles the PilotFish engine with their medication dispensing application which gets deployed on a server at their hospital clients site. They have created a default interface which can be tweaked in minutes to support a new customer. Working remotely, which is crucial to keep costs down for international deployments, all software configurations including setting up the database and the PilotFish engine, tweaking the interface and connecting to the EMR is being done in under 4 hours.
Claims Clearinghouse and HIE
A clearinghouse for healthcare claims data and HIE for clinical data provides a secure gateway for the electronic exchange of data and serves large healthcare networks and private practices. They connect to over 4,000 payers nationwide, ensuring that transactions are timely and secure. This organization has created several standard interfaces where they can chain different components together and tweak the needs of specific customers. Due to the component driven architecture of PilotFish they can leverage entire routes, transformations, custom modules, and call-outs to meet customer needs. The client has reported that 95% of its customers now fall into a category where they can use PilotFish out of the box. It is just a matter of assigning their credentials and providing them with documentation on their endpoints.
The client is a subsidiary of one of North America’s largest labs and a leading provider of medical laboratory services and health as well as insurance solutions. Their laboratory and insurance systems need to be integrated with hospitals, practices, other medical labs, Provincial Ministries of Health, Government and patient portals. PilotFish is well suited to help them meet their diverse integration requirements where they are able to leverage multiple patterns for reuse which includes: cloning existing interfaces and tweaking them; utilizing their library of existing templates and selecting which is closest to what is required for new one; using an existing interface as-is for multiple integration points an chaining “standard” interfaces with implementation-specific variants.
PilotFish interface engine solutions can help you shorten your interface timelines, too.