| EDIdEv - Electronic Data Interchange Development | EDIdEv | |
|
EDI Tool for Developers | |
|
The purpose for this page is to provide support and assistance to users using EDIdEv Framework EDI with their HIPAA EDI X12 projects. Please download, install and familiarize yourself with Framework EDI before downloading the sample programs on this web page. HIPAA EDI Guidelines Standard Exchange Format (SEF) Files 270_4010X092.SEF
Eligibility, Coverage or Benefit Inquiry SEF files are machine readable files that contain the implementation guideline of Transaction Sets. They basically contain the same information of the EDI guidelines that we view in pdf format; but SEF files are in a format that can easily be read and parsed by a computer. FREDI-COM and FREDI-NET components takes advantage of SEF files to obtain the implementation guideline information so that they can parse, construct and validate corresponding EDI files correctly. Even though a SEF file contains the implementation guidelines of an EDI Transaction Set, it does not however contain any mapping information to your existing system. For example, a SEF file cannot tell which data element in an EDI file gets mapped to a certain field in your database. Therefore, this 'mapping' has to be done in your program. Also, please note that none of the SEF
files contain the .TEXT section, nor do they include external codes. Example Programs Visual Basic .NET sample programs using FREDI-NET Hybrid component to process outbound and inbound EDI files.
C# .NET sample programs using FREDI-NET Hybrid component to process outbound and inbound EDI files.
Visual Basic 6 sample programs that generate and translate HIPAA EDI files using Framework EDI.
Delphi 5 skeleton programs that uses Framework EDI
FoxPro 6 skeleton programs that uses Framework EDI
Visual C++ skeleton programs that uses Framework EDI
Access - sample programs to demonstrate how one can map EDI files to/from a database
Excel - demonstrates how to generate an EDI file from a spreadsheet
Framework EDI validates an EDI file by checking it against the corresponding SEF file. Any discrepancy between them will be regarded as an error in the EDI file. Framework EDI can check for any expression that can be entered into the SEF file. Validation includes the following types of testing recommended by WEDI SNIP (please visit their website for more information http://www.wedi.org/snip/ )
Framework EDI does not automatically test Type 3: Balancing. This test type would have to be implemented by the programmer at the time of translation. For test Type 7: Implementation Guide-Specific Trading partners,
programmers would have to create separate SEF files specific to the trading
partners. Example Validation
Programs Visual Basic 6
ASP.NET Visual C++
Access
Note: The correct version of SEF files must be used in both the "ValidateHipaa" and "Ack" sample program to generate a correct report and Functional Acknowledgment 997 file respectively. Also, Framework EDI does not validate the calculations of an EDI file (e.g. total sum of ...). To include this kind of test, you would have to do it programmatically. For more information about Framework EDI's validation capabilities, please read EDI Validation.
Click
here to download Framework EDI
Other Topics
If you have further questions or requests, please email support@edidev.com. EDIdEv provides programming examples for illustration only, without warranty
either expressed or implied, including, but not limited to, the implied warranties of
merchantability and/or fitness for a particular purpose. This article assumes that you are
familiar with the programming language being demonstrated and the tools used to create and
debug procedures. EDIdEv support engineers can help explain the functionality of a
particular procedure, but they will not modify these examples to provide added
functionality or construct procedures to meet your specific needs. |
Source Code Examples |
EDIdEv - EDI Development
www.edidev.com