Parse or generate
Manage or extend
Own the code
the transaction sets, versions and formats you would like to parse or generate. An example would be - format: X12, version: 004010, transaction sets: 810 and 835. Browse our collection of packages to ensure that we have what you need. Please note that ediFabric differentiates HIPAA from X12.
the packages. Each package contains all of the transaction sets shown for that version. There is a .NET class file and XSD file for every transaction set. The parser will convert the EDI message into a .NET object, which is an instance of that class. The XSD can be used for EDI rules validation.
each class file you need as 'Existing item' to project 'Definitions'. Add the corresponding XSD files as 'Existing item' to project 'Validators' and set their 'Build Action' to 'Embedded Resource'. In your application add references to Framework, Definitions and Validators projects. Rebuild and you are ready to go.