An EDI 834 file parsing, validating, and database solution simplifies member enrollment for Health Plans and other Healthcare Software service companies. T-Connect provides a complete solution that's simple to install, configure, and start processing compliant 834 files. The out-of-the-box translator can validate according to SNIP 1, 2 and send the message directly to the database. Some of our customers implement member lookup logic and automate handling invalid records.
Common 834 Processing Problems
1. Processing very large monthly 834 enrollment files
We've seen many systems out there that can't handle very large files. They are either based on XML parsing technologies or require significant server scaling to process. Our solution is built from the ground up to handle large X12 healthcare files, especially the EDI 834. Our metrics show parsing, validating, and saving to a full relational database in minutes, not hours.
2. Add, Change, Term, Reinstatement records are jumbled
Wouldn't it be nice to parse an 834 and reorder the file by things like transaction type (A, C, T, R)? With T-Connect's parsing engine, you can configure to sort based on the transaction code. This helps to meet requirements such as processing Adds before Terms or variations of that order. In addition to reordering, T-Connect can also split those into separate files.
Here is an example of the original file and it's transaction type with counts:
Original Full 834 File: FullTest834.edi - 500,000 records
Here is an example of how T-Connect can sort and split by transaction codes:
Adds File: adds834.txt- 50,000
Changes File: changes834.txt - 400,000
Terms File: terms834.txt - 35,000
Reinstatements File: reinstate834.txt - 15,000
T-Connect can also break those files down further by allowing you to custom configure a max file record count or size limit.
3. Post 834 rules and member matching
In some cases, companies may want to run additional post-processing logic on the file. This may include special member lookup logic, duplicate checks, or other data scrubbing rules. T-Connect provides a relational database that stores every single EDI data element. Creating custom logic against the database is simple as writing a SQL query.
4. Data Integration and ETL 834 Records
With T-Connect, it's simple to write your SSIS or integration process when used as staging database. All of the difficult work of parsing, validating, and storing the complete EDI is handled for you with T-Connect. This ensures your data is compliant, complete, and ready to integrate.
A Better Database Solution
T-Connect Database plus SDK solution provides everything you need to process 834 files. We have pre-built templates for the most common processing scenarios. It's flexible, so you can create your own templates by starting with ours. This saves 1,000's of hours when compared to building your own custom database solution. We've taken all the guess work out and have created a solution that's extremely fast and complete.
Step 1: Configure polling interval, connection string, and file drop location:
Step 2: Drop a file into your configured In folder:
Step 3: Open the database and select the records from the 837P database 'TConnectEDI834':
Step 6: View Results of the inbound 834 process:
Step 5 (optional): Use T-Connect Stored Procedure template to query 834 tables and produce a valid EDI file straight from the database: