Page Comparison

Add & Delete facility CCE inventory

Add specific equipment info to facility CCE inventory

As a DIVO, I need to add device-specific information for each piece of CCE so that I can have a full record of each CCE at the facility

1. The following fields can be updated:
    

   • Serial Number

   • Installation / Commission date
   • Unique identifier (optional) - (CCE name within facility, e.g. "Fridge 1." Can be a text field.)
   • Barcode?
   • Year of warranty expiry (if applicable)

   • Does it have associated Stabilizer (req)  - Yes / No

   • Does it have associated manual temp gauge - Yes / No

   • Status (req) - defaults to Functional

   • Facility (move the equipment to a different facility)

   • Active - Yes / No (include decommission date?) (addressed by functionality status: decommissioned)

   • Additional notes (text area)
     
     

1. National cold chain manager can see/view a list of all CCE equipment in the country (including national store), with ability to filter or sort this list by Region and District

2. There is not a need to track what facility equipment used to be located (only current location is needed)

3. National logistician can move equipment to any other location in the country

4. RIVO can see/view a list of all CCE equipment in the Region (All DVS and All HFs) including Regional Vaccine Store, with ability to filter or sort this list by District

5. DIVO can see/view a list of all CCE equipment in their district (All Health Facilities that are in that particular district) including at the District vaccine Store

ADDED POST-COPENHAGEN

Do we need a feature where someone (EPI mgr, DIVO) can "move" (/re-register) CCE device at a different facility?

Notes moved from ticket:

* Are we OK having this as the same view for "View Functionality Status"? I don't think we need two separate pages for those things, as they display basically the same information.

* Archive vs Delete: do we want CCE list managers to be able to delete device form facility? If so, when would someone delete rather than decommission / transfer? Is there an approval process that needs to be put into place for deletions? Should the user at the facility level have final say in what devices show up in their list?

* Showing what user made the last edits is a feature in Logisitimo that I think we should incorporate. Does the system have the ability to keep log of previous changes?

* VIMS only “edit” is to change functionality status and delete. I think ours will be similar.

* Pop up to confirm “delete” / remove / archive

* Error handling dialog box for when CSV upload doesn’t fit specifications

As a CCE technician, I want to see whether a device is under warranty so that I can take the correct steps for repair.

As a DIVO, I want to refer to which of my devices is under warranty so that I can take the appropriate steps for arranging replacement, if necessary.

Acceptance criteria:

• It is possible to just include this information as a text field where the person entering the information can write "April 2018", etc.

ADDED POST-COPENHAGEN

8 votes

As a DIVO, I want to make note of which related equipment (voltage stabilizer, temperature monitor) is associated with each CCE device in a facility list so that I can see the full picture of how my CCE devices are being supported.

Acceptance criteria:

• Does not need to list specific make/models
• Can be "voltage stabilizer yes/no"

0 votes

Discussion was tha for the time being (MVP)  this can be customized for an implementation if needed.

As the system administrator, I need to determine which pieces of device-specific information will be required for each CCE added at the facility level so that a detailed CCE record is created for each facility.

Acceptance criteria:

• Pulls from a global set of fields agreed upon by stakeholders

• The following fields could be included:

• Serial Number (req?)

• Year of Installation (req) - must be 4 digit year

• Stabilizer (req)  - Yes / No

• Status (req) - defaults to Functional

• Facility (move the equipment to a different facility)

• Active - Yes / No

0 votes

Not a lot of discussion around this feature. Will need to engage with stakeholders to further understand. (Even user story was fleshed out from very stubby stub.)