Dave Frenkel GEFEG USA frenkelgefeg'com

1
Dave FrenkelGEFEG USAfrenkel_at_gefeg.com
2
EC Standards Update

• Healthcare (HIPAA)
• www.cms.gov/hipaa, www.wedi.org
• Electronics (EIDX, Rosettanet)
• www.eidx.org, www.rosettanet.org
• Retail (UCC/VICS CPFR)
• www.uc-council.org , www.cpfr.org
• Aerospace (AIA UDEF)
• www.aia-aerospace.org
• Brokerage (GSTPA)
• www.gstpa.org, www.swift.com
• Permission granted to use industry
  presentations.

3
Intro. to HIPAA
2002 National Medicaid HIPAA MMIS
Conference Sunday, April 21, 2002 Updated 8/20/02
Sheila Frank CMS, Center for Medicaid and State
Operations Division of State Systems
4
Whos Covered?

• Covered Entities
• All health plans
• All health care clearinghouses
• Health care providers who transmit health
  information electronically in connection with
  standard transactions (providers not required to
  do electronic transactions)
• Penalties for non-compliance

5
Mandated Standards

• Specific EDI transaction standards
• Claims and equivalent encounters
• Remittance Advice
• Eligibility Inquiry and Response
• Claims Status Inquiry and Response
• Enrollment and Disenrollment
• Premium Payment
• First Report of Injury
• Referral certification and authorization
• Claims Attachments
• Coordination of Benefits

6
TRANSACTION STANDARDS
PROVIDERS
PAYERS
SPONSORS
Eligibility Verification
270
Enrollment
Enrollment
834
271
Pretreatment, Authorization and Referrals
Pre-certification and Authorizations
Premium Payment
278
820
Service Billing/ Claim Submission
Claim Acceptance
837
Numbers indicate applicable ASC X12N standards.
276
Claim Status Inquiries
Adjudication
277
Accounts Receivable
Accounts Payable
835
7
Administrative Simplification Compliance Act
(ASCA)

• Allows for one year extension for covered
  entities that file a compliance plan (except for
  small health plans)
• DHHS published a model form
• www.cms.gov/HIPAA
• Medicare requirement Providers (except small
  providers) must submit claims electronically to
  Medicare starting Oct 16, 2003)

8
Final Rules Published

• Rule Published Compliance Date
• Transactions 08/17/00 10/16/2002
• Privacy 12/28/00 04/14/03
• Privacy Revision 08/14/02 04/14/03
• National Employer ID
  05/31/02 07/30/04
• Extension permitted to 10/16/2003
• under ASCA

9
Business Associates

• Include contractors agents
• Perform functions, services involving
  use/disclosure of identifiable health information
• quality assurance, data analysis, accreditation
• Special rules to assure business associate
  safeguards the information

10
Electronics Industry Data Exchange Association

• GUIDELINE AND STANDARDS SUBCOMMITTEE
• Cross Reference Project
• www.eidx.org

11
XRT A View Across the Standards
ANSI ASC X12 ISA00 00
010967564380010 01 865983421
0202190701U004100000401150Plt GSPO0967564
38POPLUS20020219070140115X004010 ST8501598
71 BEG00SAZT89231999110894A17 CURSEUSD TAX
NT1327653 TD5O92UPSAESBWD5
N1SUSEA WORD SUPPLY N3892 SHAMU DRIVE N4SAN
DIEGOCA90234US PERCWGARY F. BERGTE619
555-2366 N1STRUNNER UNLIMITED92ST01 N3987
WILLIAMS RD N4PINACLENB87345US N1BTRUNNER
UNLIMITED92BPT01 N3PO BOX 1501 N4COOPERNB974
25US PERBDBETTY BLANDTE717
555-8765 SCH10EA01020000308 SCH10EA010
20000416 SCH25EA01020000308 SCH25EA010
20000416 SCH10EA01020000517 SCH1EA0102
0000416 CTT3 SE24159871 GE140115 IEA1000040
115
EDIFACT UNA.? UNBUNOB100389773301IECIRLXX
CHQ10201251043661 UNGPO00389773301IECIRLX
X0201251043619UNS UNH1160ORDERSS93AUN
BGM2267300001251 DTM01120020125102 DTM01920
020125102 DTM02029991231102 CTAPDEric
Cameron NADSE001001999692COLIN
GREEN LIN10001252159-031 IMDF82ASSY,
DOCS,PKG UK ML530 QTY211000000EA UNT111160 UN
H1161ORDERSS93AUN BGM2267300001252 DTM011
20020125102 DTM01920020125102 DTM02029991231
102 CTAPDEric Cameron NADSE001001999692C
OLIN GREEN LIN10001252159-041 IMDF82ASSY,
DOCS,PKG GR ML530 QTY211000000EA UNT111161 U
NH1162ORDERSS93AUN BGM2267300001253 DTM011
20020125102
12
EIDX CROSS-REFRENCE PROJECT Status/Work to be
Done As of 4 AUG 2002
/Done
/27 AUG
OVERALL
95
XLS Setup STD Format Example Group
Review Hyperlinks Initial Proof Final
Proof OVERALL Data Set Groups
95 100 100 100 100 100 0 85 10
40 0 0 0 0 0 0
5 0
78 72 62 47 51 37 0
49 2
85 90 75 0 35 0 0
40 0
95 100 75 90 70 50 0 68
0
92
95
96
100
90
85
93
60
40
100
100
80
78
100
50
85
42
56
67
13
RosettaNet Implementation Guide (RIG)
www.rosettanet.org

• August 6, 2002

14
What is a RIG?

• RosettaNet Implementation Guide
• Includes two files
• Implementation Guide that describes the specific
  business scenario(s), usage notes and lessons
  learned.
• Mapping Tool to assist future trading partners on
  the type of information acceptable to populate
  each data field, including appropriate format
  within the specification guidelines.
• The RIG will help reduce implementation time and
  accelerate adoption of the process scenario by
  sharing the experience of early implementers.

15
Accelerating Adoption
The creation and use of implementation guides
directly support RosettaNets primary objective
for 2002 Accelerate Global Adoption Production
Implementation of Current Standards. Using a
RIG will enablesmooth sailing for future
implementers.
16
Implementation Guide Document
2 Introduction
2.1 Business Process Definition The "Distribute
Work in Process" Partner Interface Process (PIP)
supports the manufacturer or assembler to notify
a party of product configuration status. A
recipient of this notification could be either an
end customer or another party acting on behalf of
the end customer.   For further information
regarding the business process for this PIP,
refer to the Business Operational View (Section
3) of the 7B1 Specification (.doc).  
 
Contents of the document
Introduction Description of the specific
business scenario(s), assumptions and a summary
of the PIP purpose. Usage Notes This section
focuses upon the building blocks of the PIP
detailing the business view, business purpose,
use cases and usage notes for data element blocks
for the PIP. Lessons Learned Specific
implementation issues or recommended steps to
assist future implementers of the PIP in a
similar business scenario. Glossary Guide
describing the business terminology used in this
business scenario(s) to assist future
implementers understanding of the data exchanged.
17
Value of the RIG

• Provides a data map which significantly reduces
  the effort of data mapping.
• Reduce the negotiation time between trading
  partners operating in similar business scenarios.
• The guide illustrates a production worthy
  implementation which will further accelerate
  future implementers of a specific PIP.
• Faster implementations results in cost savings.

18
Guidance for New Implementers

• It is recommended that the PIP Specification
  package for the specific PIP has been reviewed
  prior to utilizing the RIG.
• Supporting resources
• RIG Fundamentals
• Understanding a PIP Specification, etc.

19
Current RIGs in Development

• Process Area/PIPs Publish Date
• Work in Process (7B1) Aug 2002
• Quality Reporting (7C6) Aug 2002
• Direct Ship/3PL (3B12,13 4B2) Sep 2002
• Warranty (3C1 6C2) Sep 2002
• Ship From Stock (5D3 5D5) Sep 2002
• Global Billing (3C3) Oct 2002

20
Summary

• The RIG is designed to
• Shorten implementation lead-times by documenting
  the best way to map internal systems to
  RosettaNet Standards
• Provide consistency in standards deployment
• Increased interoperability
• For more Information about RosettaNet
  Implementation Guides
• Visit the RosettaNet Web Site
• RosettaNet Home/Programs/Methodology
  Programs/Validation
• Contact
• Annabelle Kongkeo Marlow (annabelle.marlow_at_rosett
  anet.org)

21
CPFR is a Registered Trademark of the Voluntary
Interindustry Commerce Standards (VICS)
Association.
22
Agenda

• CPFR Business Process Guidelines
• CPFR Technical Standards
• Data Model
• VICS EDI Mappings
• EAN.UCC XML Standards
• Technical Infrastructure Guidelines
• Future Developments

23
CPFR Technical Standards

• Data Model / Data Dictionary
• Messaging
• EDI
• XML
• Infrastructure
• Data transport
• Security

24
CPFR Data Model

• Master Data Companies, Products, Item-Location
  Profiles
• Historical DataProduct Activity, Performance
  History
• Planning DataPromotional Events, Forecasts
• Collaboration DataException Criteria, Exceptions

25
Companies and Locations
Master Data

• A company collaborates in either a buyer or
  seller role.
• Companies are identified by a GLN (preferred) or
  DUNS number.
• Company locations are identified by a GLN
  (preferred) or DUNS4 number.
• Collaboration is between company (buyer/seller)
  locations.

26
Product Activity
Historical Data

• Product movement data, including
• Sales Orders
• Shipments Receipts
• On-hand inventory Emergency orders
• Canceled orders

27
Notification Models
Collaboration Data
Synchronized Notifications
Exception Criteria (local)
Forecast Owner
Forecast
Forecast Reply
Forecast Recipient
Exception Criteria (local)
Exception Message (4AX)
28
EDI Messaging

• VICS CPFR provides a partial mapping to VICS EDI
• 852 Product Activity
• 830 Planning Schedule
• 850 Purchase Order
• 897 Item Information Request
• Exceptions, promotional events and performance
  history are not supported.

29
XML Messaging

• The EAN.UCC CPFR Business Message Standards
  provide a complete mapping of VICS CPFR messages.
• V1.0 published in March 2002.
• UCC-sponsored software vendor interoperability
  testing is in progress.

30
XML Messaging Details

• Messages modeled graphically in Unified Modeling
  Language (UML).
• Message formats are mechanically translated to
  W3C XML Schema for tight validation.
• Messages are self-describing.

31
Technical Infrastructure

• The VICS Internet Commerce Model defines
  guidelines for data transport, security and other
  technical standards.
• Preferred data transports are
• EDIINT AS2
• ebXML Messaging

32
XML Standards Relevant to the Aerospace
Industry Ron SchuldtCo-Chair, AIA Electronic
Enterprise Working GroupAugust 7,
2002ron.l.schuldt_at_lmco.com 303-977-1414
33
EB Interoperability Framework
Industry-level interoperability enabled by common
framework that defines scope and elements of the
Information Backbone
Business Applications
Business Applications
(AIA Member Unique

Out of Scope for e
-
BSG)
(AIA Member Unique

Out of Scope for e
-
BSG)
Information Backbone
Information Backbone
Business Process
Business Process
AIA Member Company
Component Elements
Component Elements
Business Partner
Outreach
Outreach
Registry Repository
Registry Repository

Security

Security
Policy
Policy
Trading Partner Profile
Trading Partner Profile
Transport Package
Transport Package
Technical Environment
Technical Environment
(AIA Member Unique

Out of Scope for e
-
BSG)
(AIA Member Unique

Out of Scope for e
-
BSG)
Modeled after ebXML Architecture
AIA ebusiness workgroups aligned with the
Framework
34
Two Types of Exchange Documents

• Transactions
• Purchase Orders
• Purchase Order Changes
• Purchase Order Acknowledgements
• Purchase Order Change Acknowledgements
• Invoices
• Remittance Advice
• Request for Quote
• Request for Quote Response
• Shipping Schedule
• Etc.

• Collaboration Documents
• Mission Requirements
• Concept of Operations
• Specifications
• Product Designs
• Engineering Change Proposals
• Trade-off Studies
• Test Reports
• Meeting Minutes
• Plans
• Schedules
• Presentations
• Etc.

35
XML Specs and Standards Framework
Others Insurance, Transportation, Banking
PLCS Product Life Cycle Support - Collaboration
Content Payload Standards
ISO 10303 - STEP - Collaboration
EIA-836 - Configuration Management - Collaboration
UDDI - Trading Partner Profile
AIA EDI Transactions
Architecture Specifications
Global ebXML - Architecture Specifications
W3Cs - XML Schema Specification
Foundation Specifications
W3Cs - XML 1.0 Specification - DTDs
36
The Problem Summarized
EIA-836 Config Mgmt
Conflicting Overlaps
STEP (CAD)
X12/EDIFACT (EDI)
Other XML Standards
Legacy Data
Though semantically equal, the following are 4
different XML tag names
ltPARTNUMBERgt111-222-333lt/PARTNUMBERgt ltpartNumbergt1
11-222-333lt/partNumbergt ltPartNumbergt111-222-333lt/P
artNumbergt ltpartnumbergt111-222-333lt/partnumbergt
As result, many industries including aerospace
are defining their metadata (tag name) XML
standards necessary for e-business
37
UDEF Rules Based Naming Convention
Complies with ISO 11179 Naming Convention and
Supports ebXML
Data Element Name
Object Class List Entity Document Enterprise Place
Program Product Process Person Asset Law-Rule Env
ironment Condition Liability Animal Plant Mineral
Property List Amount Code Date Date
Time Graphic Identifier Indicator Measure Name Per
cent Picture Quantity Rate Text Time Value
Object Class Term 0...n qualifiers 1 or more
reqd Object Class
Property Term 0..n qualifiers 1 reqd
Property

Example Data Element Names Document Abstract
Text Enterprise Name Product Price Amount Product
Scheduled Delivery Date Engineering Design
Process Cost Amount
Names constructed follow the rules of English
modifiers precede the word they modify
38
UDEF Objects Establish Context
Entity
Enterprise B
Enterprise
A
Place
Laws-Rules
Program
Product
Product
Process
Document
Environment
Person
Asset
Condition
Resources
39
Goal - UDEF IDs Become Global Unique IDs (GUIDs)
ltProductPartIdentifier PRDGUID9_5.8gt123-456-78
9lt/ProductPartIdentifiergt
ltProductServiceID PRDGUID9_5.8gt123-456-789lt/Pr
oductServiceIDgt
ltPartNo PRDGUID9_5.8gt123-456-789lt/PartNogt
Benefit GUIDs eliminate the baggage associated
with changing names
40
AIA Mapping Matrix Summary
Sample Mapping Matrix Extract

• Phase One Summary
• Focus on four topics
• Enterprise Identification
• Document Identification
• Product Identification
• Asset Identification
• Four standards EIA-836, X12, STEP, UCC
• Goal to understand the process and the
  necessary resources to proceed into second phase
• Target completion August 2002

• Phase Two Summary
• In planning stages
• Include additional standards such as ATA Spec
  2000
• Require support from tool such as Contivo
• Require XMLization of the UDEF
• Require UDEF transfer to non-profit
• Require additional business process experts
  especially contracting and inbound/outbound
  logistics
• Target completion November 2003

41
Concept of Implementation
42
Global UDEF Registry
REGISTRATION SERVICE
Registered Name
PRODUCT Part IDENTIFIER
System A
System B
External
External
PartNum
PartNum
Conceptual
Conceptual
Registered Universal ID
Part_Number
Part_Num
Physical
Physical
9_5.8
AIA and EIDX working with UCC to establish this
service
43
(No Transcript)
44
In the E-world, Choice Matters but you cant
afford to be time-poor...
Multi-language
Multi-local
Real-time Right time Just in time...
Multi-currency
Trading on demand
45
Clarity of Focus

• The GSTPA Initiative is
• Only industry initiative focused on STP
  inclusively (international fund manager/broker
  and custodian banks)
• Not-for-profit, grassroots, pragmatic
• A pressure group, well-supported in the industry.
• GSTPAs Solution is NOT
• Reinventing the wheel...
• An ETC service per se...
• Anti-vendor or Exclusive
• A mandated single choice or Big Bang...
• An exchange, clearing house or CSD...

46
GSTPA Membership Support -15th May 2000
Member Locations
Member Interest
81 member firms (15 in pipeline)
Over 100 member entities thousands of branches
47
Conferences

• X12 Trimester Meeting Oct 6/10, 2002 Miami, FL
• www.x12.org (HIPAA, XML Transportation)
• CHITA HIPAA Readiness Forum Sept 25, 2002
• Seattle, WA www.chita.org