PilotFish on FHIR – Accelerating Implementations
HL7 Fast Healthcare Interoperability Resources (FHIR) is a specification of a common API for exchanging healthcare data between information systems. Any information system supporting the healthcare ecosystem can choose to implement the common API and exchange data following the rules. PilotFish provides impressive, robust support for HL7 FHIR. We offer a platform-neutral FHIR API and experience in applying FHIR data models to client data and implementations.
Enthusiasm, optimism and high expectations continue around HL7 FHIR as a rapid path to robust interoperability. You see a real push from both the private and public sectors to finally make things happen. The strategic goal, if a rather distant reality, is for FHIR to be the standardized healthcare plug-and-play approach for rich data exchange. FHIR is definitely now on the technology roadmap for healthcare solution providers. PilotFish’s Integration Suite easily deals with Healthcare’s complex mix of legacy technology, FHIR APIs, existing standards and terminologies, EHR vendor APIs and commercial APIs.
PilotFish’s Cutting-Edge API XL Functionality Enables Advanced RESTful API Interaction and Communication
For lightweight RESTful APIs, our innovative and state-of-the-art API XL architecture offers a means to encapsulate entire API-driven business processes. PilotFish delivers a common and consistent foundation for any FHIR-based implementation. It supports FHIR versions STU2 and STU3 as well as the latest R4 release.
FHIR’s data model defines a set of “resources” that represent granular clinical concepts, breaking down the data into its simplest, usable form, e.g., Patient, Problem List, Medication List and Allergy List. FHIR enables resources to be managed alone or aggregated into complex documents. The data model is represented as either XML (eXtensible Markup Language) and/or JSON (JavaScript Object Notation). FHIR also specifies REST (REpresentational State Transfer) to exchange data resources between two systems. Although FHIR transactions are based on expert clinical modeling, developers are not required to understand these details.
Rapidly Implement FHIR-Based Interfaces with PilotFish’s Integration Engine
PilotFish’s graphical assembly line integration approach makes FHIR configurations a virtual breeze for implementers at all levels.
The graphical Data Mapper with FHIR format reader allows users to drag & drop FHIR documents for mapping. As with our other format readers included in the PilotFish eiConsole for Healthcare, users only need to select from a drop-down menu to read in the format. Users can select the FHIR version and desired FHIR schema to load the desired subset of the standard and associated documentation.
PilotFish’s Integration Engine has also been enhanced to validate FHIR extensions, a key component of implementing FHIR-compliant integration.
PilotFish methodology offers a straightforward, repeatable process – no matter how complex or simple the configuration or whether working with FHIR, EDI, HL7, CDA, XML or any other data type. Now, teams only need to learn and use one tool.
FHIR Frequently Asked Questions
Yes, PilotFish enables seamless data format conversion between different data formats, including converting data from HL7 2.0 to HL7 FHIR.
Our JSON format builder can take a sample FHIR JSON message as a sample for target mapping. The mapping generated from that will be translated to a normal JSON string in a target transformation transformer.
PilotFish fully supports the FHIR standard, including conversions from X12 EDI to FHIR, and handles all X12 EDI transactions (i.e. EDI 837, EDI 278).
PilotFish integrates different data formats to target systems by transforming them into a common format and then routing the data into the database. Watch the PilotFish Data Analytics & Reporting Video to see this demonstrated.
Yes, PilotFish can convert fax data to FHIR, provided the fax is in a digital format on a fax server and contains the necessary information.
Check out our FAQ pages for more.
PilotFish Shows FHIR Conformance with Project Crucible
The MITRE Corporation’s Project Crucible* was used to test for conformance to the FHIR standard. It is an open source tool designed to promote correct FHIR implementations. Project Crucible gives you the ability to test in a defined, robust way and offers the credibility of a respected 3rd party. It’s a great aid in getting FHIR interfaces up and running in record time.
Note: PilotFish is one of only a few vendors that have successfully tested with 100% conformance to the FHIR standard using Project Crucible.
Project Crucible PilotFish FHIR Test
*Project Crucible is MITRE’s Open Source FHIR testing facility with a suite of testing tools for HL7 FHIR.
PilotFish Leads in FHIR Innovation, Impressive Usability and Extensibility
PilotFish’s eiConsole for Healthcare for FHIR’s impressive usability and growing capabilities are a testimony to its superior extensibility as healthcare technology continues to evolve.
With the eiConsole for FHIR, PilotFish gives FHIR healthcare customers the integration options and strategies to adapt more quickly and profitably to the rapid changes across healthcare. Stay tuned to PilotFish for many exciting developments around FHIR as it evolves and is utilized by many major EHR and EMR vendors, leading solution providers, software vendors and medical device and equipment manufacturers.
If you’re curious about the software features, free trial, or even a demo – we’re ready to answer any and all questions. Please call 813 864 8662 or click the button.
HL7 is the registered trademark of Health Level Seven International.