|
Field Name |
Description |
|
Job Name |
Enter an optional descriptive name that will allow you to monitor the job as it processes more easily. By default, the job receives a number and date time stamp. |
|
Event Name |
Enter an event that the inventory in the file is allocated for. If this field is left blank, then the items are not linked to or designated for any specific event. |
|
Site Name |
Enter the site at your organization into which you are loading the inventory. Only sites which hold inventory are available as a choice. This is a required field. |
|
Inventory File Name |
This is the SNS Push Package inventory file delivered in pipe-delimited format from the CDC. Enter the full pathname or select the file using the Browse button. |
|
Functionality |
The following table describes the buttons on the Import CDC Inventory screen.
|
Button |
Description |
|
|
Click on the Upload button to initiate processing of the SNS Push Package file. |
|
|
Click on the Browse button to give you an interface which allows you to select the SNS Push Package file from your machine. |
|
File Format Details |
It is essential that the SNS Push Package File be formatted correctly as follows:
Each row in the file is pipe-delimited and contains twelve fields.
Each row must contain all of the required fields, properly formatted.
If the row contains a value for a non-required field, it must be properly formatted.
A single item number (Field 4) must not map to more than one product description.
A single item number (Field 4) must not map to more than one unit of measure.
The table below outlines the fields that the system expects in order for the import to work:
|
Field No. |
Field Name |
Data Type |
Req'd |
Notes |
|
1 |
Container Number |
Number(5) |
No |
Number on the shipping container storing the item. |
|
2 |
Seal Number |
Number(10) |
No |
Number on the plastic seal to determine if the container has been opened. |
|
3 |
Locator |
String(42) |
No |
The pre-deployment warehouse location of the container. |
|
4 |
NDC/Mfr Item Number |
String(20) |
Yes |
The item number which identifies the product. It may be a National Drug Code (NDC) or a manufacturer item number. |
|
5 |
Product Description |
String(120) |
Yes |
Descriptive name for the inventory item. |
|
7 |
Unit of Measure |
String(3) |
Yes |
This is the unit that the item was originally shipped in.
It becomes the unit of measure in the SNS application. The acceptable values are as follows:
CS (Case) PKG (Package) BT (Bottle) EA (Each) BX (Box) KT (Kit) TU (Tube) VI (Vial) |
|
6 |
Quantity |
Number(7) |
Yes |
The quantity of the product which has shipped. |
|
8 |
Unit Price |
Number(8,2) |
No |
The price in dollars for one unit of measure of the product. |
|
9 |
Unit Pack / Unit Equivalency |
Number(5) |
No |
This is the number of EA (or single units) per unit of measure. For example, if the CDC has shipped 10 cases and there are 144 pill counters per case, this number is 144. |
|
10 |
Lot Number |
String(15) |
No |
A more granular identifier after the NDC/Mfr Item Number. A single NDC/Mfr Item Number can have multiple lot numbers. A single drug (with the same NDC number) may have different lot numbers based on the expiration date or when the batch of that drug was manufactured. |
|
11 |
Expiration Date |
Date |
No |
The date on which the product shipped expires. |
|
12 |
Product Type - Composite |
String(30) |
Yes |
This is a composite field consisting of a product type and product subtype, concatenated together with a semi-colon. The product type groups the inventory items into 10 major categories. The subtype further narrows down the product type groupings. The acceptable values for product type are as follows:
The acceptable values for product subtype are as follows:
|