Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

5.
Challenges <ul><li>EDI vs XML </li></ul><ul><li>EDI has defined auditability, tracing, speed </li></ul><ul><li>XML has ease-of-use, easy viewing capability, more tools in the market </li></ul><ul><li>Time to take advantage of both sets of features </li></ul>

6.
Vision To be the leading cross industry standards organization for global business process interoperability and innovation.

7.
Mission To drive global adoption of business interoperability through collaborative standards creation, industry education and sustainable business practices.

8.
Core Values for Innovation <ul><li>Compatibility – X12 actions, deliverables and solutions will focus on delivering increased return on existing implementations and provide complimentary solutions which focus on accelerating and extending ROI with an easily understood total cost of ownership for solution implementers. </li></ul><ul><li>Inclusive – Welcoming of business, industry groups and solution providers collaboratively deliver business process automation solutions to the marketplace </li></ul><ul><li>Communication – X12 will conduct and provide continuous visibility to ongoing efforts and activities for the membership and market with consistent communication and ongoing requests for input and improvement </li></ul><ul><li>Awareness – X12 will focus on delivering industry education, highlight best practices and provide ongoing thought leadership which ensures member companies are able to maintain competitive advantages in the global marketplace. </li></ul>

11.
What is needed in X12 EDI <ul><li>A new envelope to support: </li></ul><ul><ul><li>Multiple destinations (i.e., carbon copy functionality) </li></ul></ul><ul><ul><li>Multi-hop capability </li></ul></ul><ul><ul><li>Wider (more digits/characters) in send/receive fields </li></ul></ul><ul><ul><li>Release and additional delimiters </li></ul></ul><ul><ul><li>Internationalization - Multi-byte character sets </li></ul></ul><ul><ul><li>Real time transactions with a session number </li></ul></ul><ul><ul><li>Publish and subscribe mode HL7 / Public Bid & Response </li></ul></ul><ul><ul><li>Harmonization with other SDO’s and national efforts </li></ul></ul><ul><ul><li>Have a separate field for versioning the code lists – so that the code lists are not dependent on the standard/implementation version numbers. </li></ul></ul>

12.
What is wrong with most existing XML implementations <ul><li>Too many command and control designs </li></ul><ul><li>Not always compatible with existing EDI </li></ul><ul><li>Have not thought through large batch and publish and subscribe needs. </li></ul><ul><li>No off line fill form capability </li></ul>

14.
Envelope Harmonization Benefits <ul><li>Envelope Harmonization will represent a common way for </li></ul><ul><li>identifying messages, recipients, senders and documents </li></ul><ul><li>across standards. </li></ul><ul><li>Benefits of a Standard Interchange Envelope </li></ul><ul><ul><li>Provides a unified way for systems to route and audit content across standards </li></ul></ul><ul><ul><li>Provides a common expression of a business identity across standards, systems and services </li></ul></ul><ul><ul><li>Will support diverse payloads </li></ul></ul><ul><ul><li>Will better support global and cross industry interoperability </li></ul></ul>

15.
Development Process <ul><li>Gather and validate requirements </li></ul><ul><ul><li>Information forum at June trimester meeting </li></ul></ul><ul><ul><li>Conference calls over the summer </li></ul></ul><ul><li>Develop and work project </li></ul><ul><ul><li>Start at September trimester meeting </li></ul></ul><ul><ul><li>Work under existing X12 procedures </li></ul></ul><ul><ul><li>Involve other SDOs </li></ul></ul><ul><li>How are the changes approved? </li></ul><ul><ul><li>The voting membership leverages input from forum participants and the membership prior to voting </li></ul></ul><ul><li>How can you becoming a voting member? </li></ul><ul><ul><li>Join ASC X12 </li></ul></ul>

16.
Information Forum <ul><li>What is it? </li></ul><ul><ul><li>A open discussion to gather and validate requirements for standards changes </li></ul></ul><ul><li>Who can participate? </li></ul><ul><ul><li>Any interested party who would benefit from the changes </li></ul></ul><ul><li>Why an information forum? </li></ul><ul><ul><li>ASC X12’s charter and values require input, participation and inclusiveness of business and industry </li></ul></ul><ul><li>When is it? </li></ul><ul><ul><li>Tuesday, June 3, 9:00 AM – 12:00 PM at trimester meeting </li></ul></ul><ul><ul><li>On meeting schedule under X12C/TG1 - Requirements Review for Interchange Envelope </li></ul></ul>