How do Healthcare Organizations Automate and Modernize Mainframe EDI Data Handling using TIBCO?

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 solution:  data handling modules and processes import required data from the main EDI into Transaction Insight without impacting downstream processes. The Transaction Insight-focused solution also allows for data storage and user access via LDAP.}

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