EDISPHERE exhaustively validates the data integrity of your application and partner messages for syntax and situational requirements and reports errors where appropriate.
The mission of eliminating human error through the use of Electronic Data Interchange (EDI) in eliminating human error has not been properly accomplished if the EDI data itself contains errors or is otherwise unreliable. To ensure that outgoing and incoming EDI messages are free of error, an EDI translator must have excellent data validation capabilities to scrutinize EDI messages for syntax integrity, implementation guide requirements such as the need for data balancing requirement, conditional or situational requirements, validation of data against external code sets, trading partner specific data validation requirements, etc. This document describes these validation requirements and the validation capabilities of EDISPHERE.
Traditionally, EDI has referred to X12 and EDIFACT data interchange standards, which have been in existence for over three decades. Over a period of years, EDI has enhanced its scope since additional data interchange formats have been used for B2B (Business to Business transactions). For the purpose of this document, the term “EDI” will be used generically to refer to a number of file formats used for B2B, including XML, proprietary file formats (fixed length, variable length, comma separated value – CSV), databases and is interchangeably used with B2B. Wherever a distinction is necessary, the same is explicitly mentioned unless it is obvious from the context.
Different validation rules or business rules are categorized into different "testing types" by SNIP/WEDI(www.wedi.org) in their white paper "Transaction Compliance and Certification" for the Healthcare industry.
This document has generalized these testing-types as validation-types to describe the industry-neutral validation capabilities in EDISPHERE.