EDI files offer many advantages in business and health care messaging, and BizTalk offers a premier suite for handling EDI interchanges and agreements. At the same time, EDI files are notoriously difficult to read, even for EDI experts and highly skilled Business Analysts. The T-Connect EDI Viewer is designed to address this gap. It supports converting the HIPAA EDI 837 transaction sets (for Professional, Institutional, and Dental) as well as the HIPAA EDI 834 Enrollment transaction set to a human-readable and printable PDF format.
The T-Connect EDI Viewer offers a library and a pipeline component that can be used to convert EDI messages sent to BizTalk into a PDF version of their Paper Form equivalents. This conversion could be done as part of an existing integration, or using archived/historical data on a case by case basis. The PipelineComponent offers a very simple way…
We are happy to announce the availability of our enhanced product, the T-Connect EDI Accelerator for BizTalk. We have seen a trend in the difficulties encountered while processing EDI messages. That trend includes all types – both HIPAA and Manufacturing/supply chain transactions. Originally, we developed the T-Connect HIPAA Accelerator to address these pain points, allowing companies in the Healthcare space to successfully process claims, authorizations, benefit enrollments, eligibility inquiries, and acknowledgements. The T-Connect EDI Accelerator was purpose built to address pain points that many companies experience in working with EDI files. This includes, but is not limited to:
The process of on-boarding of new trading partners is time consuming and expensive
There is a significant risk of implementing unproven platforms, especially complex point to point architectures.
Their current EDI platform is a “home grown” point-to-point or manual/paper-based system
This is very hard to maintain
A common trend that we have been seeing recently is the similarities in the pain points that companies are often faced with. One of those such pain points is the difficulty in quickly receiving and processing large EDI files having a file size over 10 MB. In one instance, there was a need to receive a HIPAA EDI 834 Enrollment file totaling 1.3 GB, containing roughly 800,000 enrollments. The already powerful BizTalk Server in a 1-1 architecture – 1 BizTalk Server, 1 SQL Server, was having difficulty processing the file. The file would take several hours to process, often taking up several gigabytes of drive space to attempt to disassemble the file using the EdiDisassembler pipeline.