Price authorization acknowledgment (X12)

Interchange sender partner ID qualifier.

Interchange sender identification mapping to:

• fileSenderNumber with party type defined in ISA05.

• linkIdentifier

• x12InterchangeControlEnvelope for sender in X12 control file header

Interchange receiver partner ID qualifier.

This value is dependent on X12 version. Version 4012 and earlier, this is the interchange control standards identifier. Valid value is U.

Version 4020 and later, this is the repetition separator, a delimiter that separates repeated occurrences of a data element or composite data structure, which must be different than the data element separator, component separator, and segment terminator."

Interchange Control Number mapping to:

• file control header

• X12 control file header interchangeControlIdentifier.

Interchange level acknowledgment requested.

Valid values:

• 0 - No acknowledgment requested

• 1 - Interchange level acknowledgment requested

Indicates whether the interchange is for production, test, or information purposes.

Valid values:

• I - Information

• P - Production data

• T - Test data

GS group function code.

Valid value is PA - Price Authorization Acknowledgment X12 845

Responsible Agency Code.

Valid values:

• T - Transportation Data Coordinating Committee (TDCC)

• X - Accredited Standards Committee X12

Price authorization acknowledgment/status beginning segment.

Note: There is no transaction identifier in BPA.

Transaction set purpose code.

Valid values:

• 00 - ORIGINAL

• 02 - CREATE (Add)

• 03 - DELETE

• 04 - CHANGE

• 05 - REPLACE

• 45 - FOLLOWUP

DTM date segment for mapping to:

• contract effective date

• contract expiration date

• group contract effective date

• group contract expiration date

• wholesale contract effective date

• wholesale contract expiration date

Date type qualifier for the effective date.

Valid values:

• 092 - contract effective date

• 093 - Contract expiration date

• 124 - Group contract effective date

• 125 - Group contract expiration date

• 126 - Wholesale contract effective date

• 127 - wholesale contract expiration date

• 999 - Document date

Entity identifier code for an organization, physical location, property or individual for use of the currency.

Valid value:

• SE - Selling party currency

• BY - Buying party (Purchaser) currency

N1 name segment loop for:

• Purchasing group(customer or buyer) party information extended with dates and reference identifiers

• Supplier party

• manufacturer party

• distributor party

• distributor branch location

• customer party information extended with dates and reference identifiers

• contract party information extended with dates and reference identifiers

Entity qualifier for the Customer or Buyer party identifier and address information.

Valid values:

• BG - Buyer party

• SU - Supplier party

• MF - manufacturer party

• DS - Distributor party

• DB - Distributor branch

• BY - Customer Party

• 90 - Contract Party

Identifier code qualifier.

Valid values:

• 01 – DUNS
• 09 – DUNS+4
• 11 – Drug Enforcement Agency registration number
• 21 – Health Industry Number
• 91 – Company identifier
• 92 – Company location identifier
• UL – Global Location Number

Contact function code identifying major duty or responsibility of person or group named as contact.

Valid value:

AJ - Primary contact

Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:

• TE - Telephone number

• EM - email address

Communication number:

• Telephone number of the contact person expected in this field.

• Email address of the contact person.

Valid values:

• TE - Telephone number

• EM - email address

Communication number:

• Telephone number of the contact person expected in this field.

• Email address of the contact person.

Transaction reference type for X12 segments REF and N9 and EDIFACT RFF for general reference data that is not a transaction document identifier.

HDA mapping for price authorization in N1 party loop for buying group only.

Valid value is CT

Transaction reference identifier value as defined by enum in transactionReferenceType.

HDA: Contract header type code defining identifier/description in description attribute (REF03).

Reference identification qualifier.

Transaction reference type for X12 segments REF and N9 and EDIFACT RFF for general reference data that is not a transaction document identifier. HDA mapping.

Valid values:

• VC - Vendor/Supplier contract number

• CT - Contract Number

Reference identification id, Reference information as defined for a particular transaction set or as specified by the Reference Identification Qualifier

vendor or supplier contract id.

Contract current status code.

Valid values:

• OC - Original contract

• VA - Valid open contract

Reference identification qualifier for the previous contract number.

Valid values:

• P1 - Previous contract number

• BC - CUSTOMERCONTRACT

Date type qualifier for the contract reference dates in CON loop.

Valid values:

• 092 - Contract effective date

• 093 - Contract expiration date

• 124 - Group contract effective date

• 125 - Group contract expiration date

• 999 - Document date

CON-N1 name segment loop for:

• customer party information extended with dates and reference identifiers.

• bill to party information extended with dates and reference identifiers.

• contracted pharmacy party information extended with dates and reference identifiers.

• eligible contract party Information extended with dates and reference identifiers.

• eligible party for rate Information extended with dates and reference identifiers.

• ship to party information extended with dates and reference identifiers.

• purchasing group party information extended with dates and reference identifiers.

• distributor party information extended with dates and reference identifiers .

HDA usage note: This N1 loop at the Detail Level in the CON loop is required to identify eligible customers belonging to the buying group or individual parties eligible for the contract.

Entity qualifier for the Customer or Buyer party identifier and address information.

Valid value:

• BY - Buyer party

• BT - Bill to party

• C9 - Contracted pharmacy party

• EB - Eligible contracted pharmacy party

• EP - Eligible party for rate Information

• ST - ship to party

• BG - Purchasing group party

• DS - Distributor party

Identifier code qualifier.

Valid values:

• 01 – DUNS
• 09 – DUNS+4
• 11 – Drug Enforcement Agency registration number
• 21 – Health Industry Number
• 91 – Company identifier
• 92 – Company location identifier
• UL – Global Location Number

REF reference segment for mapping for reference identifiers.

HDA Description: This REF segment at the Detail Level in the CON/N1 loop is used in the bid award/change to provide other information regarding the customers eligible for the contract including: previous identifiers, trade classification(s), GPO membership IDs, and account class codes. REF01 and REF02 must be present and in some instances, REF03 may be appropriate for description clarification.

Reference information for identifiers that are not related to transaction documents. This group would map to X12 segments REF and N9 and EDIFACT RFF for information other than transaction documents.

HDA mapping.

Valid values:

• 1W

• 9X

• DH

• HI

• P2

• P3

• X8

• ACD

Transaction reference identifier value as defined by enum in transactionReferenceType.

HDA: Contract header type code defining identifier/description in description attribute (REF03).

A free-form description to clarify the related data elements and their content.

HDA: Identifier or description defined by qualifier code in transactionReferenceIdentifier (REF02).

DTM date segment in CON-N1 loop group 110.

HDA usage description: This DTM segment at the Detail Level in the CON/N1 loop is used to provide the effective and expiration dates of the individual customers. This segment is required only if these dates are different from the dates of the buying group contract indicated at the Header level. DTM01 and DTM02 must be present. This segment can also be used to provide the effective date of an identifier being implemented. DTM01 and DTM02 must be present.

Date type qualifier for contract dates in CIN-N1-DTM loop.

Valid values:

• 092 - Contract effective date

• 093- Contract expiration date

• 124 - Group contract effective date

• 125 - Group contract expiration date

• 129 - Customer contract effective date

• 130 - Customer contract expiration date

Change or response type code specifying the type of change recorded in the product adjustment details loop.

Valid values:

• AI - Add additional items

• CA - Changes to line items

• CT - Change dates

• DI - Delete items

• OA - Original confirmation of revised announcement

• OC - Original confirmation of original announcement

• PC - Price change

• RB - Replace all dates

• RE - Replacement item

Item unit data information such as shipping, ordersing. CON-PAD-UIT

Two occurrences of this segment at the detail level in the productAdjustmentDetails loop are required to add an item in a bid award: one to specify the wholesale price and the other to specify the contract price.

This is not necessarily the case in a bid award/change, when specifying a price change, for example. If the contract price changed then only one occurrence of the UIT segment would be required for the manufacturer to notify the distributor of this change.

Unit of measure for recorded product in adjustment.

Valid values :

• UN (HDA)

• EA

• CA

Code identifying the type of unit price.

Valid values:

• CT

• LE

• RE

• WH

DTM date segment in CON-PAD loop group 120.

HDA usage description: This date segment at the detail level in the canonical productAdjustmentDetails array (X12CON/PAD loop) is only used to provide the item contract effective and expiration dates that are different from the buying group dates at the header level.

When adding an item in a bid award/change, two occurrences of this date segment are required — one to specify the item contract effective date and the other to specify the item contract expiration date. DTM01 and DTM02 must be present.

Date type qualifier for contract dates in CON-PAD-DTM loop.

Valid values:

• 131 - Item contract effective date

• 132 - Item contract expiration date

Pricing information segment in CON-PAD, optional

Pricing information for product.

HDA usage note: Used to communicate pricing scenarios where multiple price points exist for a given product on the same contract ID. This array does not represent tier contracts with unique contract IDs, which are typically sent in separate X12 845s messages.

Use of this segment must be agreed on by the manufacturer and wholesaler to ensure interpretation/implementation is as the manufacturer intended.

The price point for example, could be based on quantity purchased per order, per calendar quarter or some other parameter. Impacts on membership should also be considered. Feasibility may dictate all attached members are be able to access all price points sent in this segment.

Pricing type for Price Authorization catalog.

Valid values:

• C01 - Contract tier 1 price

• C02 - Contract tier 2 price

• C03 - Contract tier 3 price

• C04 - Contract tier 4 price

• C05 - Contract tier 5 price

• C06 - Contract tier 6 price

• PBQ - Begin quantity

• CON - Contract

• DIS - Distributor

Unit of measure used for pricing at the price conditions line item details level.