| About UPN®
Who will benefit from this Repository?
Everyone-customers, manufacturers, and distributors-will benefit,
since the UPN facilitates the use of EDI, thereby increasing the ease,
speed and accuracy of ordering and distribution. The UPN will also
assist trading partners in capturing demand/sales information and
identify industry-wide trends.
What is HIBCC’s role in this project?
As a Standards Development Organization, HIBCC has committed itself to
developing grassroots support for the UPN among major medical/surgical
companies and their customers. The UPN has been endorsed by all of the
organizations represented on the HIBCC Board of Directors: American
Hospital Association, American Medical Association, American Society
for Automation in Pharmacy, American Veterinary Distributors
Association, Health Industry Distributors Association, Health Industry
Group Purchasing Association, Health Industry Manufacturers
Association, Healthcare Information and Management Systems Society,
National Wholesale Druggists Association, Pharmaceutical Research
& Manufacturers Association and the US Department of Defense.
HIBCC has administered the successful HIN® System database for the
healthcare industry since 1987. With this expertise in database
management, HIBCC was the natural choice to take on the administration
of the UPN Repository.
What is UPN On-Line?
UPN On-Line is a web-based data portal designed to
allow easy and immediate access to UPN Repository data. Through
UPN On-Line, users can download the Repository file, query for
specific UPN records and submit additions or updates to UPN data.
Registration is required to access the application, but is free of
charge.
For more information, please download the
User
Guide.
What is the cost to submit my data?
There is no cost: HIBCC has made this task as inexpensive as possible
to encourage your participation. All manufacturers are being asked to
include their items in the Repository.
How do I submit my data?
HIBCC has developed and made available to all interested parties an
on-line application for the submission of UPN data. For more
information please download the
User Guide.
What is the most common problem when submitting my data?
The most common problem is using an apostrophe in entering your data. The system does not recognize the apostrophe. Do not use apostrophes in entering your address information, business information or any other information.
What data structures are acceptable?
The UPN is intended to unambiguously identify medical/surgical products in the supply chain, thereby simplifying product distribution. Each product at all levels of packaging will be assigned a unique UPN, consisting of either the HIBC-LIC or UCC SCC-14 primary data structure.
The HIBC-LIC primary data structure includes the manufacturer's LIC (Labeler Identification Code), manufacturer assigned product number, packaging level indicator and a link character (check or Link digit).
The UCC/EAN primary data structure consists of a packaging level indicator, UCC/EAN manufacturer ID number, manufacturer assigned product number and a check character.
Data Structure Examples
HIBC-LIC: +H216040A353
Component Definition
+ HIBC flag character
H216 Manufacturer LIC
040A3 Manufacturer assigned product number
5 Packaging level indicator
3 Modulus 43 link character (check character)
Please note: each level of packaging will have its own record, even if the product is identical. Also note that the "+" sign and check character from the HIBC structure are dropped in the data repository. If these elements are supplied for inclusion into the UPN Repository, they will be stripped off prior to being added to the database.
UCC SCC-14: (01)10399999004081
Component Definition
(01) UCC application identifier
1 Packaging level indicator
0399999 Manufacturer identification number
00408 Manufacturer assigned product number
1 Modulus 10 check digit
Please note: each level of packaging will have its own record, even if the product is identical. Also note that the application identifier "(01)" used in the UCC/EAN structure is dropped in the data repository. If this element is supplied for inclusion into the UPN Repository, it will be stripped off prior to being added to the database. U.P.C. and EAN-13 data structures must be converted to the 14-digit format by adding the necessary leading zeros.
UPN REPOSITORY DATA FILE STRUCTURE
|
Field Name
|
Width
|
Start
|
Description
|
|
UPN
|
20
|
1
|
UPN
|
|
SUPPLIER
|
35
|
21
|
Supplier name
|
|
DIVISION
|
35
|
56
|
Division name
|
|
TRADENAME
|
35
|
91
|
Trade name
|
|
DESCRIPTION
|
80
|
126
|
Product description
|
|
UOM
|
2
|
206
|
Unit of measure code. (ANSI code list)
|
|
QTY
|
8
|
208
|
Quantity of eaches in unit of measure
|
|
PARTNO
|
20
|
216
|
Product number
|
|
SALEABLE
|
1
|
236
|
Saleable flag indicating whether
supplier considers product to be saleable at the packaging
level specified in unit of measure field.
|
|
UPNQUAL
|
2
|
237
|
UPN qualifier code (HI=HIBCC, UK=UCC-EAN)
|
|
SRCCODE
|
2
|
239
|
Data source indicator (MC=sourced from
supplier; otherwise empty)
|
|
TRAKREQ
|
1
|
241
|
Indicates that the item is required by
regulations to be tracked. (Y/N)
|
|
UPNCRTDT
|
8
|
242
|
Date the UPN was entered into the
repository (YYYYMMDD).
|
|
UPNEDTDT
|
8
|
250
|
Date the UPN record last edited (YYYYMMDD).
|
|
STATUSCODE
|
2
|
258
|
UPN status code (AC=active,
DE=inactive).
|
|
ACTIONCODE
|
2
|
260
|
Last action taken on UPN repository
record (UA=add, UC=change, UD=deactivate)
|
|
REFERENCE
|
20
|
262
|
Reference field. Field content is a UPN
that replaces or substitutes for the UPN in this record.
|
|
REFQUAL
|
2
|
282
|
Reference qualifier. Indicates the type
of reference in the REFERTO field. Valid qualifiers are
(UR=replaces; US=substitutes)
|
Field length = 283
Code Lists
|
Field
|
Code
|
Description
|
|
UPNQUAL
|
HI
UK
|
HIBCC
UCC-EAN
|
|
SRCCODE
|
MC
|
UPN sourced from supplier
|
|
STATUSCODE
|
AC
DE
|
Active
Inactive
|
|
ACTIONCODE
|
UA
UC
UD
|
Add UPN
Change UPN
Deactivate UPN
|
|
REFQUAL
|
UR
US
|
Replaces
Substitutes
|
Please note: each level of packaging will have its own record, even if the product is identical. Also note that the application identifier "(01)" used in the UCC/EAN structure and the "+" sign and check character from the HIBC structure are dropped in the data repository. If these elements are supplied for inclusion into the UPN Repository, they will be stripped off prior to being added to the database. U.P.C. and EAN-13 data structures must be converted to the 14-digit format by adding the necessary leading zeros.
|
|
|
