X12 Standards in the DLMS—Forward Codes and Delimiters

Slides:



Advertisements
Similar presentations
Of X12 Standards Richard Bort Robert Dempsey Bort & Co., Inc. Southern California Edison (818) (626) Southern California e-Business Forum.
Advertisements

1 Operating Rules Status NCVHS Subcommittee on Standards December 3, 2010 Updated on enhancements to Operating Rules for Eligibility and Claim Status.
Lesson 2 Preparing to Test the 837
Morris Bodnar Director, Compliance and Interior Offices Tel: (250) Fax: (250) Pilot Implementation of.
webMethods platform solutions
Procurement Forum August 8, WORKFLOW What is it anyway? Susan Banasiewicz Rojas Aasis Service Center
© 2007, TSI Incorporated 2009 TSI Alliance Program.
G.T.R. Data Inc. Welcome to our EDI Overview. G.T.R. Data Inc. EDI Demonstration This demonstration will take you on a guided tour of our software. After.
Topic 6 Topic 6 PDC 264, Revise DS 867I and MILSTRAP Issue Transactions to Support Navy Requirements for Reason for Reversal Code SDR Committee Meeting,
1 WARFIGHTER SUPPORT ENHANCEMENT STEWARDSHIP EXCELLENCE WORKFORCE DEVELOPMENT WARFIGHTER-FOCUSED, GLOBALLY RESPONSIVE, FISCALLY RESPONSIBLE SUPPLY CHAIN.
Final Report on Improvements to the RAA Steve Metalitz 5 December 2010.
Solution Provider Agreement (SPA) Re-enrollment 2006 Name Title Group Microsoft Corporation.
Web Server Administration Web Services XML SOAP. Overview What are web services and what do they do? What is XML? What is SOAP? How are they all connected?
Conformance Mark Skall Lynne S. Rosenthal National Institute of Standards and Technology
Update on the API Work Group Activities on Pipe Markings.
Know the Earth…Show the Way NATIONAL GEOSPATIAL-INTELLIGENCE AGENCY Peggy Poindexter Business Executive Acquisition Directorate Peggy Poindexter Business.
AIA RFID Data Exchange Guideline Status AIA / Electronics Enterprise Integration Committee May 10, 2005.
GTR Data Inc. Welcome to our EDI Demonstration G.T.R. Data Inc. August 1997.
INTRODUCTION TO C C was developed by Dennis Ritchie at Bell laboratory in 1972 It is an upgrade version of languages B and BCPL.
HIPAA Summit Audioconference Analysis of Addenda to HIPAA Transactions and Code Sets Rule Larry Watkins Executive Vice President, Claredi Co-chair, WEDI.
Moving To the Year 2000:Implementing 4010 Implementation Resolution Process Rich Emrich EDI Manager J.M. Schneider.
Projects System Protection Coordination Draft 2 of TOP Texas Reliability Entity NERC Standards Reliability Subcommittee November 2, 2015.
How did we get here? United Mutual 5/17/20121Residents Voice.
Gensuite ® Step-by-Step Guide for the setup of Gensuite Compliance Calendar and Training Calendar integration with Microsoft Outlook Some computers experience.
WAWF/UID/RFID Industry Group Meeting Acceptance Transaction Requirements Document Develop a set of requirements for a structured Acceptance/Rejection transaction.
Welcome To Maricopa’s Hiring Processes Overview Hiring Managers, Screeners, Interviewers, HR Professionals College or District Executives involved in.
1 DEFENSE LOGISTICS AGENCY AMERICA’S COMBAT LOGISTICS SUPPORT AGENCY WARFIGHTER SUPPORT ENHANCEMENTStewardship Excellenceworkforce Development.
FIRE PROTECTION CONTRACTS Workshop on Senate Bill 239 (Hertzberg) July 21, 2016 Nevada LAFCo – Presented by P. Scott Browne, Counsel.
SPS Spotlight Series October 2014
Microsoft Word Basics.
Item Unique Identification (IUID) - Update
THE SBA’s NEW SMALL BUSINESS MENTOR-PROTÉGÉ PROGRAM
HIPAA Implementation Guides Down and Dirty Dan Petrosky April 7,2005
Global Standards Collaboration (GSC) GSC-15
Southern California e-Business Forum
SCC P2P – Collaboration Made Easy Contract Management training
CIIMS Proposal for TOP-003 Approach
IUID and Serial Number Tracking: Proposed Addendum to ADC 1198A (Capital Equipment) and Draft PDC 1244 (Unique Item Tracking (UIT) Programs Supply.
Routing Identifier Code (RIC) Availability
Routing Identifier Code (RIC) to DoD Activity Address Code (DoDAAC)
Tracking time spent here with us today WO# Task code: 886
Acceptance Process for Manufactured Products by Certification:
Sylvia Williams, DLMS Data Manager
Javascript, Loops, and Encryption
Hiring Processes Overview
Chuck Fenton Principal Research Engineer
Who needs to understand them?
Web Server Administration
Travel and Expense Tips & Tricks
Computer Symbols
Regulatory Policy Analyst McKesson Information Solutions
Sylvia Williams, DLMS Data Manager
HIPAA Implementation Guides Down and Dirty
OpenAccess Coalition: Goals and Status
DNR List NITS Application Detail
Funds Verification Obligation Recording Process
Tour of DLMS Website For Finance Process Review Committee
Roster Update Training
Guidelines to Refilling a Position
Guidance for Patient Interactions
CEOS Organizational Matters
PolyAnalyst Web Report Training
NORMAL BUSINESS ELIGIBILITY VERIFICATION CUST SERVICE ALLIANCE
Adding Like Terms Guided Notes
Issues in Standard-setting work
Keyboard Test Study Guide
Transaction, Code Sets and Identifier Update
Bill Coleman IWVTA Ambassador to GRPE
Issues in Standard-setting work
SAE Standards Works Training Module - Useful Tabs
Presentation transcript:

X12 Standards in the DLMS—Forward Codes and Delimiters Frank Napoli, LMI November 16, 2017

Topics Forward Codes Delimiters Decoupling Code Versions from Transaction Versions Delimiters Allowed Delimiter Characters in DLMS X12-based Data Exchanges

Forward Codes Background: X12 versions published annually—“carved in stone” Published versions include code values DLMS ICs based on Version/Release 4010 (1997) and 4030 (1999) Two types of codes: Internal (e.g., Identification Code Qualifier, DE 66; 10=DoDAAC) External (e.g., Zip Code, DE 116; Code Source: 51 USPS National Zip Code and Post Office Directory)

Forward Codes Background (continued) New business requirements need new codes (e.g., Work Order Number—SLOA Code) New codes added to “future” version of X12 Codes approved today would be added to 7050 DOD unlikely to migrate to newer version X12 Standards New codes added to current (4010/4030) ICs with DLMS note identifying them as “Migration” codes Currently this is non-compliant with the X12 Standard

Forward Codes Current status: “Words” solution: Add the following paragraph to X12 guideline “Compliance in X12” “While compliant code values for each version of X12 are documented in the published standard, new emerging business requirements often necessitate that trading partners exchange code values that are published in versions of the X12 Standard other than what is specified in the GS08 of the transmission. X12 recognizes that this business requirement is met by specifying those codes in an industry-approved implementation guide or by mutual trading partner agreement prior to use.” * (highlighting added)

Forward Codes Great News for DOD! Caveats: Approved by all X12 subcommittees Published for member vote by X12 PRB voting closes 11/22/17 Caveats: “Compliance in X12” is out for member vote X12 Guidelines not part of the X12 Standard, but are approved by X12 membership at large Codes must be added to (future) X12 Standards, and codes must be explicitly enumerated in the DLMS ICs—both are DLMS standard practices

Allowed DLMS Delimiters PDC 1275 - Bottom Line:   Allowed DLMS Delimiters & Ampersand * Asterisk { Open Bracket } Closed Bracket ^ Caret “ Double Quote ! Exclamation Mark > Greater Than < Less Than % Percent Sign | Pipe (Vertical Bar) ; Semicolon ‘ Single Quote ~ Tilde Newline (Line Feed/Carriage Return) * * Newline is an unprintable character; senders may use it only as segment terminator in X12-based DLMS transactions.

DLMS X12 Team Contact Sylvia Williams DLMS Data Manager (804) 279-1802 Frank Napoli DLMS X12 Contractor Support (703) 767-0753 Group DLMSX12@dla.mil