TIBCO Foresight Overview

This document focuses on the transaction validation, response generation, document splitting, translation and other functions provided by TIBCO Foresight products as part of the EDI Plug-in.

Transaction Validation with Instream

Before using this document, familiarize yourself with Electronic Data Interchange (EDI). See Electronic Data Interchange for more information.

TIBCO Foresight products benefit customers by connecting partners, validating transactions, reducing administrative inefficiencies and addressing mandates such as HIPAA 5010. The TIBCO Foresight family of EDI management solutions allows organizations to trade electronic transactions with commonly-used formats (EDI, XML, and proprietary Flat File) and standards (HIPAA, X12, EDIFACT, and so on).

The EDI Plug-in provides access to the following TIBCO Foresight tools:
  • Validation with Instream, including:
    • ResponseGenerator
    • DocumentSplitter
    • DataSwapper
  • Translation with Translator
  • Additional functions:
    • pre-scanning of EDI and EDIFACT data to parse document header information using X12 or EDIFACTPrescanners
    • modification of error lines (also called DTL lines) in an Instream results file using ISErrorRefiner
    • incorporation of error records and other identifying information into data using Shuffler.

Instream ensures the compliance of inbound and outbound data using the fastest and most thorough transaction validation engine.

You can use Instream to automate transaction flow throughout your organization and validate transactions according to industry standards, organizational guidelines, and specific business rules.

Instream is designed to be highly configurable, with several components that work together. The following figure shows Instream, Response Generator, and Document Splitter working together to process inbound EDI.

Note: Instream validation can be run as a command line, usually from within a batchfile or script. Or you can integrate Instream validation into other applications, either statically (C/C++) or dynamically (C/C++, C#, and Java).

Reference

See Instream Validation Technical Manual PDF document for more information about the Instream validation function.

Response documents (also called acknowledgments) are used to give feedback to the sender of a transaction on the status of the acceptance of the transaction by its recipient. After validation, the Response Generator function can be used to generate a response document for transmission to the sender.

Response Generator generates the following response types:
  • For X12 data
    • 277CA Health Care Claim Acknowledgment (277CA)
    • 277U Unsolicited Health Care Claim Status Notification (277U)
    • 824 Application Advice
    • 997 Functional Acknowledgment
    • 999 Implementation Acknowledgment
    • TA1 Interchange Acknowledgment
    • Custom report
  • For EDIFACT data
    • CONTRL document

References

  • See Response Generator Technical Manual PDF document for more information about the response generation function.

After validation, the Document Splitter function can be used to split data into two types: valid and invalid. For example, Docsplitter can sift out invalid claims in an 837 so that you can process the valid ones and notify the sender of the invalid ones.

Document Splitter can be used with the following data types:
  • HIPAA EDI
  • X12
  • EDIFACT
  • Flat File
  • XML file

Reference

See Document Splitter Technical Manual PDF document for more information about the document splitting function.

After validation, Data Swapping can be used to substitute values in EDI data.

Dataswapper can perform the following functions:
  • Replace the value in a specified data element with another value in the EDI
  • Insert a new segment into the EDI
  • Delete a segment from the EDI
  • Create a report of the data that was changed.

Reference

See Dataswapper PDF document for more information about the data swapping function.

Translator is a specialized, high-speed transformation engine that enables the mass conversion of transaction files based on pre-built or custom maps, providing direct translation to and from EDI, XML, and Flat File formats with no interim staging required.

You can use Translator to translate the input data in one format to a new file in another format. The following figure shows the translation workflow.

Reference

See Translator PDF document for more information about the translation function.