Help | My Account | Checkout
Home
HIPAA
EDI Publications
EDI Standards
EDI Table Data
Code Lists

WPC Change Description Guides

WPC Change Description Guides closely resemble the official X12 documents available as bound books or as a PDF. Those documents are Page-based, while this electronic-only presentation is Topic-based. Each topic is generated from the same databases as the page-based presentation.

This electronic product is Compiled HTML (Windows Help File) with a table of contents, extensive hyperlinks, pop-ups for industry name definitons and code source references. Each contains all of the information from the 005010 guides and all of the segments from the 004010A1 guides along with a change description of each segment and element.

Pricing and Availability


The complete collection of all nine Change Description Guides is available at a price of $1,250 for X12 Members, or $2,750 for Non-Members. Individual guides are also available at $550 each: 270/271, 276/277, 278, 820, 834, 835, 837 Professional, Institutional, and Dental.



More About the Product

Table of Contents Icons


This Table of Contents uses several icons to indicate the type of content found when clicking a title.

Front/Back Matter Section Icons
Section with sub-parts
Page

Loop Icons
An 005010 loop compared to it's 004010A1 counterpart
An 005010 loop without an 004010A1 counterpart, a new loop
An 004010A1 loop without an 005010 counterpart

Segment Icons
An 005010 segment compared to it's 004010A1 counterpart
An 005010 segment that moved location within the implementation guide between the 004010A1 release and 005010 and compared to it's 004010A1 counterpart
A single purpose 005010 segment that was split from a multi-purpose 004010A1 segment and compared to that 004010A1 counterpart
An 005010 segment without an 004010A1 counterpart, a new segment
These informational segments represent various 004010A1 information:
  • A segment that appears in 004010A1 without an 005010 counterpart
  • The location of a 004010A1 segment that has moved within the implementation guide between the 004010A1 release and 005010
  • The location of a multi-purpose 004010A1 segment that has been split into single purpose segments for 005010
  • The location of a 004010A1 segment that has been combined into a multi-purpose segment in 005010

Transaction Set Listing


This section lists the levels, loops, and segments contained in this implementation. It also serves as an index to the segment detail. The following description uses the Health Care Claim Status Request and Response transaction set as an example.

Hover over a icon for a description of the item.

 
  POS ID NAME USG RPT LOOP RPT
  0100  ST Transaction Set Header R 1                      
  0200  BHT Beginning of Hierarchical Transaction R 1                      
 
  LOOP ID - 2000A INFORMATION SOURCE LEVEL >1
  0100  HL Information Source Level R 1   -
                       

Segments


This section repeats once for each segment used in the implementation providing segment specific detail and X12 standard detail, including Segment Detail, Diagram, and Element Detail. Each segment page contains a change description, the 004010A1 segment, if there was one, and the 005010 segment.

Hover over a icon for a description of the item.

Click Here to view a sample segment page in a new browser window.

Segment Detail


Hover over a icon for a description of the item.

 
SEGMENT DETAIL 
 
 N1 - PAYER IDENTIFICATION
 
X12 Name:Party Identification
 
X12 Purpose:To identify a party by type of organization, name, and code
 
X12 Set Notes:
1.COMMENT: The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery.
 
X12 Syntax:
1.R0203
At least one of N102 or N103 is required.
2.P0304
If either N103 or N104 is present, then the other is required.
 
Loop:
1000A — PAYER IDENTIFICATION
Loop Repeat: 1
Segment Repeat:
1
Usage:
REQUIRED
 
Situational Rule:
Filler text ...
 
TR3 Notes:
1.Use this N1 loop to provide the name/address information for the payer.
2.The payer's secondary identifying reference number is provided in N104, if necessary.
 
TR3 Example:
N1PRINSURANCE COMPANY OF TIMBUCKTUXV8888888888~

Diagram


This section provides a pictorial view of the standard and shows which elements are used in this implementation. Each element is briefly described in a box. The border of the box conveys the requirment of a given element within the segment. A heavy red box indicates a required element, a grey box indicates a situational element and a dashed grey box, along with the name in strike-through type indicates a not used element.

Sample
Hover over text below for pop-up help. For "Reference Desginator," "Condition Designator," and "Data Element Type," click that same text to link to Appendix B for a complete description.

 
N10198
Entity ID
Code
M 1ID2/3

Element Detail


This section specifies the implementation details of each data element. Although the example below does not contain a composite data structure, the individual components of those structures contain the same entities as the simple data elements displayed here.

Hover over a icon for a description of the item.

ELEMENT DETAIL 
USAGEREF. DES.D.E. NUM.NAMEATTRIBUTES
REQUIRED        
N101
98
Entity Identifier Code
M 1ID2/3
Code identifying an organizational entity, a physical location, property or an individual
CODE      DEFINITION
PRPayer
REQUIRED        
N102
93
Name
X 1AN1/60
Free-form name
SEGMENT SYNTAX: R0203
INDUSTRY NAME: Payer Name
SITUATIONAL
N103
66
Identification Code Qualifier
X 1ID1/2
Code designating the system/method of code structure used for Identification Code (67)
SEGMENT SYNTAX: R0203, P0304
SITUATIONAL RULE: Required when the National PlanID is mandated for use. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
CODE      DEFINITION
XVCenters for Medicare and Medicaid Services PlanID
 
Required if the National PlanID is mandated for use.
CODE SOURCE 540: Centers for Medicare and Medicaid Services PlanID
SITUATIONAL
N104
67
Identification Code
X 1AN2/80
Code identifying a party or other code
SEGMENT SYNTAX: P0304
COMMENT: This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
SITUATIONAL RULE: Required when the National PlanID is mandated for use. If not required by this implementation guide, may be provided at the sender's discretion, but cannot be required by the receiver.
INDUSTRY NAME: Payer Identifier
NOT USED
N105
706
Entity Relationship Code
O 1ID2/2
NOT USED
N106
98
Entity Identifier Code
O 1ID2/3


Washington Publishing Company © 2010. All rights reserved. Help | Privacy Policy | Contact Us

  21