Microsoft Technology Licensing, LLC

Surendra Machiraju

Suraj Gaurav

Mathrubootham Janakiraman

An EDI data dictionary management and versioning system is provided having reusable EDI building blocks that are stored in relational format. Reusable EDI elements include, but are not limited to, data types, simple data elements, composite data elements, segments and loops. Storage of EDI building blocks is performed such that building blocks of new Schema are compared to existing building blocks to encourage re-use of building blocks, and to avoid duplicating blocks in storage. An EDI data dictionary editor tool is also provided that hides the complexity of an additional type system, such as an XSD Schema representing a TSD, so that only the EDI elements pertaining to the relevant TSD are displayed so that users are relieved from knowing about the additional type system.

Electronic data interchange (EDI) data dictionary management and versioning system

Recreating an electronic data interchange (EDI) schema from a file. The file is received from a source and the file includes a plurality of data values. The plurality of data values is identified. The plurality of data values is analyzed to determine the structure of the EDI schema. A set of decoding rules is analyzed to the analyzed plurality of data values. The EDI schema is recreated as a function of the applied set of decoding rules and the analyzed plurality of data values.

Scalable algorithm for sharing EDI schemas

An EDI document instance is generated or edited via an editor tool that also displays a corresponding EDI schema, thus allowing editing of an EDI document instance alongside its corresponding EDI schema, thereby interrelating EDI document creation or editing with the corresponding EDI schema. Either the EDI document instance or the EDI schema elements can be modified via the editor tool, and in various non-limiting embodiments, any errors in the formation or modification of an EDI document are automatically highlighted or otherwise recorded and/or displayed via the editor tool. EDI instances can be edited in either native or XML form.

Electronic data interchange transaction set definition based instance editing

Creating an electronic data interchange (EDI) transaction from a description of the EDI schema. The description defines the EDI schema in a non-EDI structure. The description of the EDI schema is received. A plurality of data units included in the received description of the EDI schema is identified. The plurality of data units describes the content of the EDI schema. The identified plurality of data units is analyzed to determine the content of the EDI schema. The document definition is generated for the EDI schema as a function of the analyzed plurality of data units. The document definition is used to create an EDI transaction according to the EDI schema.

EDI instance based transaction set definition

Systems and methods are disclosed that facilitate transforming business and encoding rules defined in a persistent and relational format into XML schemas that provide a message format and validation logic for the message. A message can be received in delimited flat-file format and parsed to facilitate generating a value-added XML schema that represents both encoding rules and business rules associated with the message. The systems and methodologies detailed herein can be employed, for example, in applications utilized in a healthcare provider space and can be consistent with Health Level 7 standards to improve message validation and/or processing.

Schema generator: quick and efficient conversion of healthcare specific structural data represented in relational database tables, along with complex validation rules and business rules, to custom HL7XSD with applicable annotations

Transforming one or more of a collection of electronic data interchange (EDI) transactions. A type of EDI transactions is identified to be transformed from a source format to a destination format. The collection of the EDI transactions is received according to the source format. A particular one or more of the collection of the EDI transactions is identified corresponding to the identified type of EDI transactions. A transformation map is defined to transform the identified particular one or more of the transactions from the source format to the destination format. The identified particular one or more transactions is transformed according to the defined transformation map.

Scalable transformation and configuration of EDI interchanges

Modeling an electronic data interchange (EDI) document using extensible Markup Language (XML) at runtime. A plurality of structural elements is identified in the EDI document. A plurality of corresponding data values is identified from the identified plurality of structural elements in the EDI document. A plurality of annotations is generated for a plurality of rules included in the EDI document. The plurality of rules defines operations associated with the plurality of corresponding data values. The determined data values and the generated annotated is transformed into an XML schema corresponding to the EDI document. The XML schema is processed at runtime.

XML payload specification for modeling EDI schemas

Extensible Markup Language (XML) specification for transforming electronic data interchange (EDI) transactions. A collection of EDI data is received in a batch. The batch of EDI data includes a plurality of EDI documents and each of the plurality of EDI documents has at least one EDI transaction corresponding to a transaction type. The EDI transactions included in the EDI documents are identified by decoding the received EDI data according to EDI standards. A consolidated EDI document is generated from the EDI documents in the batch of EDI data. The consolidated EDI document includes the identified EDI transactions organized according to the transaction type.

XML specification for electronic data interchange (EDI)

Synchronous validation and acknowledgment of electronic data interchange (EDI) transactions. A connection session on a communication network is established for handling EDI transactions from a source. A collection of EDI transactions is received via the communication network. A receipt acknowledgement is returned to the source indicating the EDI transactions have been received. The EDI transactions are validated as the EDI transactions are received. A validation acknowledgement is transmitted via the communication network to the source before the connection session is terminated. The validation acknowledgement indicates the EDI transactions have been validated.

Synchronous validation and acknowledgment of electronic data interchange (EDI)

Developing a file corresponding to an electronic data interchange (EDI) schema. The EDI schema is selected for transmission to a destination device. A plurality of syntax structures in the selected EDI schema is identified. The plurality of syntax structures defines a type of transaction associated with the EDI schema. A plurality of EDI data values is extracted from the identified plurality of syntax structures according to the defined type. A file is generated corresponding to the type and including the extracted data values in the generated file such that the EDI schema can be re-created from the generated file.

Electronic data interchange schema simplification interface for representing a plurality of electronic data interchange (EDI) schemas to a user. Each of the plurality of EDI schemas has data associated therewith. A unitary structure is identified representing the plurality of EDI schemas by decoding the data in the plurality of EDI schemas. Properties are determined to be included in the unitary structure. The properties define characteristics of the plurality of the EDI schemas. A unitary meta-schema is defined to the user as a function of the defined characteristics and the unitary structure. The defined meta-schema corresponds to the plurality of EDI schemas. Determined properties are provided in the defined meta-schema so that the user is able to modify the characteristics of each of the plurality of EDI schemas.

Electronic data interchange (EDI) schema simplification interface

Systems and methods are disclosed that facilitate formally describing structured documents and complex validation rules associated therewith using value-added XSD schemas (VAXs). In accordance with aspects of the invention, structured documents can be translated, parsed, validated, and acknowledged in a single pass via utilization of XSD schema representations that capture complex data and business rules related to validation as a translation specification to convert delimited flat-file and/or structured documents to an XML format while providing ambiguity resolution and acknowledgements.

Single-pass translation of flat-file documents into XML format including validation, ambiguity resolution, and acknowledgement generation

Systems and methods are disclosed that facilitate formally describing structured documents and complex validation rules associated therewith using value-added XSD schemas (VAXs). Native XSDs can be utilized and annotated to generate VAXs that represent both the structure of a document and the complex validation rules used to validate the documents. VAXs can be annotated with declarative validation rules that can be assessed at run time to facilitate document validation. Additionally, VAXs can be annotated with validation handlers that comprise a predefined library of validation routines that can be called at run time to facilitate document validation.

Complex syntax validation and business logic validation rules, using VAXs (value-added XSDs) compliant with W3C-XML schema specification

Automatic schema discovery for electronic data interchange (EDI) in EDI documents. The EDI documents are received in a batch from a source. Each of said EDI documents has at least one EDI transaction corresponding to a transaction type. Rules are applied according to EDI standards to decode the EDI transactions according to the corresponding transaction types. One or more configuration items are identified in the decoded EDI transactions. One or more schema types are determined based on the configuration items.

Growing community of inventors

Redmond, WA, United States of America

Surendra Machiraju