Cold Chain Equipment Inventory Data Model
Version 1.0, May 25, 2013
Version 1.2, June 5, 2013
Version 1.3, July 9, 2013
Proposed data model
Here is a basic data model, structured around facilities (which can be either health facilities or vaccine storage facilities), with equipment associated with specific health facilities. The model includes both Cold Chain Equipment Inventory as well as addition information that would be used across applications
- Health/ Vaccine storage facilities – information on each of the country’s health and vaccine storage facilities. The basic model for the inventory is to associate assets with facilities
- Core Assets – cold rooms, refrigerator/freezers, coldboxes and vaccine carriers.
- Asset catalogs – information associated with particular models of assets. (The issue of non-cataloged assets needs to be addressed).
- Country administrative hierarchy.
- Country name table.
- Facility equipment lists.
Facility data model
Required indicates if this is essential for the inventory. Other fields could be made required by specific tools or deployments.
Name |
Type |
Comments |
Req. |
|
1. |
Facility ID |
String |
Primary key for the application. This ID must be unique. |
Y |
2. |
National Facility ID |
String |
Official ID of the facility, from a master facility list. |
N |
3. |
Facility Name |
String (UTF-8) |
The name of the facility. Standard capitalization should be used. The UTF-8 representation allows multiple scripts to be used. |
Y |
4. |
ASCII Name |
String (ASCII) |
The name of the facility in ASCII (e.g., basic Latin characters, without accents). |
N |
5. |
Administrative Region |
Composite |
Location in the administrative (geographic) hierarchy. The exact format is to be determined, but it must link to a country administrative table. |
Y |
6. |
GIS Coordinates |
String |
Use the ISO 6709 standard for representing latitude and longitude (and possibly altitude). Decimal degrees is the preferred format. |
N |
7. |
Facility Type |
Enumeration |
Type of facility from a fixed list of possibilities: StorageX, HospitalX, HealthCenterX, HealthPostX. X is an integer that allows different levels of the same type. [List TBD] |
Y |
8. |
Facility Ownership |
Enumeration |
Ownership of facility from a fixed list of possibilities: Public, Private, NGO, FaithBased, Other. [List TBD] |
Y |
9. |
Facility Population |
Numeric |
Total catchment population for the facility. |
Y |
10. |
Immunization Population |
Numeric |
Population receiving immunization services from the facility |
Y |
11. |
Storage Type |
Enumeration |
Storage for transfer to another facility, or storage for use at the facility. These names could be improved: {Depot, Delivery, NoStorage} |
Y |
12. |
Vaccine delivery type |
Enumeration |
Static, Outreach, StaticAndOutreach, None |
Y |
13. |
Power Infrastructure |
Composite |
See below |
Y |
14. |
Cold Chain Logistics |
Composite |
See below |
N |
15. |
Contact Information |
String |
Phone number and contact official |
N |
Power Infrastructure
Four power sources are generally considered for the cold chain: electricity, kerosene, gas, and solar. Countries may restrict their number of power types, so NotApplicable should be an option (even if not available at the user level)
Name |
Type |
Comments |
Req. |
|
1. |
Electricity Source |
Enumeration |
Grid, Generator, GridAndGenerator, None |
Y |
2. |
Grid Power Availability |
Enumeration |
MoreThan16, 8To16, LessThan8, None |
Y |
3. |
Gas Availability |
Enumeration |
Available, Irregular, NotAvailable, Unknown, NotApplicable |
Y |
4. |
Kerosene Availability |
Enumeration |
Available, Irregular, NotAvailable, Unknown, NotApplicable |
Y |
5. |
Climate suitable for solar |
Boolean |
True if area gets a sufficient number of hours of sunshine throughout year |
N |
6. |
Site suitable for solar |
Boolean |
True if there are possible unshaded locations for solar panels |
N |
Cold Chain Logistics
Cold chain logistics information is technically not part of the equipment inventory, so it has been put into a separate component.
Name |
Type |
Comments |
Req. |
|
1. |
Vaccine Supply Interval |
Numeric |
Interval of delivery or collection (in weeks). This is needed if it overrides national policy |
N |
2. |
Vaccine Reserve Stock Requirement |
Numeric |
Required reserve stock (in weeks). This is needed if it overrides national policy |
N |
3. |
Mode of Vaccine Supply |
Enumeration |
Delivered, Collected, DeliveredAndCollected, None |
N |
4. |
Distance to supply point |
Numeric |
One way distance in KM to closest supply point. |
N |
5. |
MainSupplyPoint |
String |
FacilityId of main supply point |
N |
6. |
SecondarySupplyPoint |
String |
FacilityId of secondary supply point |
N |
Storage Assets
Refrigerator/Freezers
Refrigerators and Freezers are the most important asset for the inventory. There should also be a distinction between vaccine and icepack freezers. Since most of the equipment in use is from the PQS/PIS list, the way to handle asset information is to only store the model number, and then use a secondary table to represent the catalog information. We will assume that the catalog is augmented to include additional models. Generic entries can cover unidentified types of domestic refrigerators.
Name |
Type |
Comments |
Req. |
|
1. |
Application ID |
String |
Unique ID for the application. (This ID should be unique across all asset types) |
Y |
2. |
Catalog ID |
String |
Key into an official catalog. Information about the model is derived from this. |
Y |
3. |
Equipment tracking ID |
String |
Ideally, the real serial number. However, this is not always available or maintained at the facility. |
N |
4. |
Bar Code |
String |
If a barcode is used, the information can be stored here |
N |
4. |
Year |
Numeric |
Year of installation. Often not accurate (but may not need to be.) |
N |
5. |
Working status |
Enumeration |
WorkingWell, WorkingNeedsMaintenance, NotWorking |
Y |
6. |
Reason not working or not in use |
Enumeration |
NeedsSpareParts, NoFinance, NoFuel, Surplus, Dead, NotApplicable |
N |
7. |
Utilization |
Enumeration |
InUse, NotInUse, InStoreForAllocation |
Y |
8. |
Proper installation |
Enumeration |
Yes, No, Unknown, Assessment on whether or not the equipment is installed properly. |
N |
9. |
Voltage regulator |
Enumeration |
For electric equipment, is it connected to a voltage regulator. Yes, No, Unknown, or NotApplicable. NA for non-electric |
N |
10. |
Power source |
Enumeration |
Electricity, Gas, Kerosene, Solar, Unknown |
N |
Coldrooms
TODO
Refrigerator Catalog
This information is associated with the PIS/PQS catalog. We don’t need all of the information from the PQS/PIS sheets. (Is there additional information that is of interest?) This will be augmented to handle other equipment types
Name |
Type |
Comments |
Req. |
|
1. |
Catalog ID |
String |
Primary Key from PQS/PIS |
Y |
2. |
Model Name |
String |
Y |
|
3. |
Manufacturer Name |
String |
Y |
|
4. |
Power source |
Enumeration |
Electric, Gas, GasElectic, Kerosene, KeroseneElectric, Solar, PassiveCooler |
Y |
5. |
Equipment Type |
Enumeration |
A simplified version from PQS without the power source: ChestFreezer, IcePackFreezer, IceLinedRefrigerator, UprightRefrigerator, SolarPhotvoltaicRefrigerator, SolarThermalRefrigerator |
Y |
6. |
Climate Zone |
Enumeration |
PQS Designation: Hot, Moderate, Temperate |
Y |
7. |
Data Source |
Enumeration |
PQS, PIS, Custom, Generic |
|
8. |
Storage volume: Gross+4, Net+4, Gross-20, Net-20 |
Numeric |
Can we just do Net volume. Although I would prefer just to report a single number, we probably need to give both +4 and -20 numbers |
Y |
Other Assets
The cold room format needs to be completed. The inventory also includes other asset types – there are vaccine carriers, which are often counted. These should be included in the inventory – although likely viewed as “supplies” – we are only interested in how many there are – not information on each individual carrier.
Transportation assets should be defined. These would be an optional component.
Facility Equipment Lists
The link between equipment and facilities is no longer represented as part of the asset. In most cases, an asset can be associated with a facility, is it was convenient to represent the information by just recording a facility with an asset. However, there are a few exceptions to this, and logically, the facility is not a property of the asset.
For completeness, we specify a simple scheme of asset, facility pairs.
Name |
Type |
Comments |
Req. |
|
1. |
FacilityID |
String |
Y |
|
2. |
EquipmentID |
String |
Y |
|
3. |
AssetType |
Enumeration |
Refrigerator, ColdRoom, etc |
Y |
Administrative Hierarchy
The administrative hierarchy is represented as a collection of nodes. Each node in the hierarchy has a unique ID, so that facilities can be assigned to an arbitrary position in the hierarchy.
Name |
Type |
Comments |
Req. |
|
1. |
NodeID |
Integer |
Unique non-negative integer ID |
Y |
2. |
Name |
String |
UTF |
Y |
3. |
Ascii Name |
String |
Ascii |
N |
4. |
Level |
Integer |
National level (root) is level 1 |
Y |
5. |
Parent |
Integer |
Node ID of Parent. (-1 for root) |
Y |
6. |
Category |
String |
UTF – Subdivision category |
Y |
7. |
AsciiCategory |
String |
N |
|
8. |
ISOCode |
String |
Code from ISO 3166 |
N |
Country Name Table
For compatibility across countries, some information is represented generically (names of administrative levels, health facility types). To enable applications to appropriately display this information, a table of names in presented. Names are represented in both UTF-8 and Ascii. Information will be recorded for Adminstrative Levels, Facility Ownership, Facility Types. The level is given for each type to allow an arbitrary number of levels.
Name |
Type |
Comments |
Req. |
|
1. |
GenericName |
Enumeration |
Subdivision, VaccineStore, Hospital, HealthCenter, HealthPost, OtherHealthFacility, Public, Private, NGO, FaithBased, OtherOwner |
Y |
2. |
Level |
Integer |
Starting from 1 |
Y |
3. |
Name |
String |
UTF-8 |
Y |
4. |
AsciiName |
String |
Ascii |
Y |