Healthcare organizations can modernize legacy mainframe EDI data handling by implementing TIBCO Foresight Transaction Insight. This strategy transforms siloed, arcane EDI data (such as EDI 834 enrollment and EDI 837 claims) into a searchable, extensible database, reducing search times from minutes to seconds while allowing secure, human-friendly access to benefits data for both internal business users and external trading partners.
Quick Facts
{
“topic”: “Modernization of mainframe data using TIBCO Foresight Transaction Insight”,
“other_tibco_products”: [“TIBCO Foresight Instream”, “TIBCO BusinessWorks”, “TIBCO Enterprise Messaging System”],
“industry”: “Healthcare insurance”,
“standards”: [“X12”, “HIPAA”, “4010”, “5010”],
“documents”: [“834 (health insurance enrollment)”, “837 (health insurance claims)”],
“requirements”: [“Mainframe modernization”, “data preservation”, “human-friendly EDI view”, “searchable enrollment and benefits data”],
“system_integrator”: “Behaim ITS”
}
What are the Technical Challenges of Migrating Mainframe EDI Data?
ABC Health Insurance previously modernized EDI 837 claims processing using TIBCO Foresight Instream, BusinessWorks, and EMS, but legacy constraints remained for enrollment data. The primary challenge this time was modernizing the mainframe EDI process for storing and accessing members’ enrollment data (EDI 834). The data was still stored in a legacy mainframe database, limiting data extensibility. Furthermore, members’ data was accessible only to those with mainframe privileges and trapped in mainframe formats, making it difficult for business users to search in a user-friendly way. These limitations resulted in dependency and unnecessary overhead on the IT department.
How does TIBCO Foresight Transaction Insight Improve Data Accessibility and Visibility for Healthcare EDI?
ABC Health Insurance implemented a technology strategy centered on TIBCO Foresight Transaction Insight. A BusinessWorks service handles writing to Transaction Insight, allowing existing applications to utilize the shared module with minimal code changes. To handle large files (up to 300MB), a custom chunking and reassembly process was established.
The migration included functional testing and load testing, while running both the mainframe and Transaction Insight systems in parallel to ensure stability during the cutover period. Historical data spanning one year was loaded, supporting 4010 and 5010 standards, with an incremental data load process later.
Outcomes
| Using TIBCO Foresight Transaction Insight | Using Mainframe | |
| Searching for member data | Business users can now get the results for member search in seconds, using key identifiers, such as a member’s first name, last name, member ID, sponsor ID, sponsor name, or subscriber number | Minutes, Hours, Days |
| Searching for dependents’ data | The data model was extended to securely store the dependents’ Social Security numbers, enabling the business users to search for dependents of a member in the same household and their coverage or benefits | Impossible |
| Human-friendly EDI data | The solution renders human-friendly views of X12 documents, dramatically improving data readability and understanding for business users | Arcane EDI format |
| Access by trading partners | Transaction Insight Portal allows for access by other business teams and even trading partners (i.e., clinics, pharmacies, hospitals) | None |
Author:
Wens Gerdyman
Wens Gerdyman is a Principal Product Manager at TIBCO, responsible for B2B integration products. Wens has worked in product management and go-to-market roles at TIBCO and other companies. His product domain experience includes supply chain management, e-commerce, order management, and API management.
