PilotFish Interface Engine Powers COVID-19 Reporting
Little did we all know that when we helped our client (a state department of public health) implement PilotFish to support disease surveillance and reporting, how critical it would become when the pandemic hit. Despite the massive increase in volume due to COVID-19, PilotFish’s interface engine has performed flawlessly. PilotFish has helped the state meet this challenge by performing data normalization, validation and standardization critical to reporting to the CDC.
THE USE CASE
Implementing a major migration to newly extended HL7 standards for reportable data in over 100 categories could be overwhelming – not so, for this organization. The first foundational category, implemented in a little less than a month, met onboarding benchmarks and cut smoothly over to production.
Interfaces were created at unprecedented speed with PilotFish’s Interface Engine automated interface assembly line process. Leveraging PilotFish’s flexibility and extensibility, the client was able to easily create custom processors to meet key challenges. In this case study, learn how the client was able to rapidly architect and implement this solution and why they expect the next phase to be accomplished even faster.
This Department of Health (DPH) collects extensive data from a multitude of surveillance systems wherein hundreds of hospitals, healthcare providers and laboratories send public health data to local and state public health departments. Data is normalized, validated and standardized to meet further reporting and exchange requirements. Data is regularly submitted to the Centers for Disease Control and Prevention (CDC) programs through numerous systems, a key responsibility which adds to the workload of the state and local public health staff.
The client juggles to keep up with the rapidly changing landscape of healthcare data and the need for IT modernization. Pressure to meet ever-increasing state and federal mandates adds to their challenges.
The CDC has launched initiatives to increase the robustness of the National Notifiable Diseases Surveillance System (NNDSS) technological infrastructure so that it is based on interoperable, standardized data and exchange mechanisms. To that end, the client must implement newly developed CDC HL7 message mapping guides (MMGs) for nationally notifiable data.
The client is tasked with taking data from the state’s multiple surveillance systems and feeding back the relevant reporting data to the CDC’s NNDSS system in HL7 – as per the new CDC guidelines, HL7 specifications and milestones. The CDC has currently prioritized 9 MMGs for adoption— Arboviral, foodborne, Generic v2, hepatitis, STD, congenital syphilis, pertussis, mumps and varicella.
This case refers to the Generic v2 deployment. A template from the CDC serves as the underlying structure to guide the implementation and integration. It provides mapping from local to standardized data elements and provides links to a bound value set for vocabulary validation.
The client turned to PilotFish for a modern, extensible and flexible interface engine solution that radically simplified data transformation and reporting. The client had already leveraged PilotFish in other successful on-time and on-budget initiatives. The speed and ease-of-use delivered by PilotFish were critical to the client’s success for this current project.
PilotFish offers an enterprise integration middleware solution utilizing a complete Java framework that leverages application server technology, web services and industry XML standards for the rapid deployment of internal and external systems. In this case, by leveraging PilotFish, implementation of Generic v2 was completed in a little less than a month.
The PilotFish eiPlatform Interface Engine had debuted in the client’s environment during the ELR (Electronic Laboratory Reporting) and Meaningful Use initial projects. There it had replaced a competing interface engine that benchmarked as slower and more costly. With PilotFish, the IT lead impressively architected, designed and implemented an ELR messaging bus in record time that integrates the PilotFish eiPlatform, BaseX and custom Java classes.
In implementing the new CDC Generic v2 HL7 messaging standard in this staged project, the client leveraged:
Custom processors and listeners are easily created using PilotFish’s Open API or .Net bridge. The client employed custom processors for rules-based decision making to filter and convert or reject specific data elements collected and also updated LOINC and SNOMED codes.
Leveraging PilotFish, processes that were done manually became automated – freeing up the client’s resources and saving time. The surveillance team experienced immediate payback with automated data entry and automated monitoring of spreadsheets.
PilotFish Common Model
No matter how complex, integrations are handled by the same methodology with PilotFish – each and every time. The ROI is measurable in time and resource savings for the next set of integrations for this project.
Interfaces are constructed from a common set of stages via PilotFish’s graphical automated interface assembly line (including Listeners, Processors, Transformations, Routers, and Transports). With drop-down menus, drag & drop mapping and pre-configured screens – building healthcare interfaces is easy and fast. (Availability of a built-in computationally complete palette of XSLT structures, functions and macros is another advantage.) PilotFish integrations are self-documenting, allowing for cost-efficient changes, updates and removing the dependency on who created an interface.
PilotFish includes more HL7 specific tools and functionality than any other product on the market with features such as a proprietary lenient parser capable of importing non-standards compliant data. Format readers facilitate instant import of a format for the source or target from a file or other data descriptor. PilotFish’s software accommodates the specific version of HL7 that the CDC requires without any special handling and reading in the extended version of HL7 from the CDC took minutes.
PilotFish implementations typically take a few weeks, not months and months. Interfaces going forward can often be configured in less than 30 minutes.
Subsequent implementations by the client for these new HL7 MMGs for NNDSS reporting will be based on the foundation built with the Generic v2 integration.
The Generic v2 HL7 implementation took a little less than a month. It’s been onboarded and smoothly cut over to production. PilotFish’s integration solution’s simplicity and sophisticated architecture were critical to the success and speed of this implementation. The client confidently projects that each additional phase of this large-scale project will go even faster as they were able to easily extend PilotFish with custom processors that will automate further rollouts.
With PilotFish, there is no additional cost to access components or features. PilotFish offers a complete solution of integrated components that encompass the full life cycle of integration. With PilotFish’s integration solution in place, the client expects that up to 90% of the work involved for each new HL7 MMG can be done by non-developer professionals. Updates and maintenance ahead are projected to incur minimal internal resource cost and disruption.
The speed at which the first implementation was completed leveraging PilotFish has been noted. Attendant benefits of ancillary process innovations and improvements look to accrue to other integrations and data exchange going forward.
THE FUTURE STATE
The next phase being implemented by the client contains a 10x’s larger data set. PilotFish deals with diverse connectivity, validation, data transformation, routing and delivery of information and easily scales to handle tremendous volumes of data. PilotFish’s built-in components, extensive tools as well as its scalability, flexibility and extensibility make it a future-proof integration solution.
PilotFish adheres to the architectural principles that our integration solution should be easily extended using open source components and be infinitely flexible so that any integration, no matter how complex, can be handled with the same methodology and tools – each and every time.
The PilotFish eiDashboard component has been established by the client for operational reporting and transaction monitoring. It’s an excellent component for troubleshooting and management reporting. The client also employs the PilotFish eiTestBed for automated onboarding capabilities.
The CDC, in its initiatives, is committed to getting and sharing better data, faster. PilotFish delivers the integration solution to simplify and streamline processes, automate repeatable tasks, expedite results and build the foundations for trustworthy data-driven decision-making.
Since 2001, PilotFish’s sophisticated architecture and innovations have radically simplified how healthcare integration gets done. Today PilotFish offers the most flexibility and broadest support for healthcare integration of any product on the market and is system, platform and database agnostic. PilotFish’s healthcare integration suite includes support for all healthcare data formats (HL7 2.x, HL7 3.x, FHIR, CCD/CCDA, JSON, XML, X12 EDI, NCPDP, etc.) and communication protocols.
PilotFish is architected to be infinitely extensible with our Open API and flexible to meet any integration requirement. PilotFish distributes Product Licenses and delivers services directly to end users, solution providers and Value-Added Resellers. To learn more, visit our Case Studies or specific solutions like HL7 Integration or X12 EDI Integration.
PilotFish Healthcare Integration will reduce your upfront investment, deliver more value and generate a higher ROI. Give us a call at 813 864 8662 or click the button.
HL7 is the registered trademark of Health Level Seven International.
X12, chartered by the American National Standards Institute for more than 35 years, develops and maintains EDI standards and XML schemas.