CCE Knowledge Transfer
1 June 2017 - Chongsun takes us on a CCE journey through his experience with VIMS
Equipment types
Added new type called CCE
Might already be equipment in the system, but only this CCE type would have PQS devices
Had to map equipment types and programs together
each Program has different equip types associated with it. If program and type aren't matched, then that prog isn't managing that type of equpiment
Equipment list
dropdown to see catalog items
specify program dropdown, then only equipment types that match that program are shown
you can Add New equipment
Equip name, Manufacturer, Model, Energy type
Equipment inventory
Functional status
Functional, Non functional, Functional but not installed, Waiting for repair, Obsolete
Obsolete was how VIMS dealt with "archiving"
Obsolete items still show up in inventory list
If you change status to Obsolete it bring up pop up with input for decommission date
System needs to know "good" and "bad" status so that we can do additional logic if needed
Should v3 have a delete button?
Maybe to deal with equipment that had been incorrectly added to inventory list
Moving equipment between facilities
There were permissions in place to allow reassigning facility for a CCE device, but that was turned off to disallow people from doing that within VIMS
Permissions within CCE
Is this the same as with Requisitions? Or is supervisory hierarchy different than CCE management for some countries?
Chat log from Webex:
VIMS = Vaccine Information Management System
from Brandon to Everyone:
Inventory = any number of Cold Chain Equipments that are installed for use at a specific facility
from Brandon to Everyone:
PQS = Performance, Quality and Safety, a device catalogue by the World Health Organization (WHO)
from Brandon to Everyone:
http://apps.who.int/immunization_standards/vaccine_quality/pqs_catalogue/
from VillageReach Admin to Everyone:
Performance, Quality and Safety (PQS)
from Josh Zamor to Everyone:
http://apps.who.int/immunization_standards/vaccine_quality/pqs_catalogue/
from VillageReach Admin to Everyone:
Nick your comment only came to me.
from Josh Zamor to Everyone:
Mary Jo: to your dashboard question, I believe that yesdashboards in vims used this cold chain info.
from Josh Zamor to Everyone:
CHAI did build a number of reports, and we also tied this in with Requisition's Cold Chain tab, which I think powered a dashboard widget.
from VillageReach Admin to Everyone:
ok, thanks Josh.
Open Questions for v3:
Equipment Types: Are we replicating the concept of "Equipment Types" like V2? And mappings of Programs to Equipment Types? Hopefully we can have a simpler model where a program just gets CCE enabled by flipping a switch.
Permissions/RBAC: will we use the Requisition Supervisory Hierarchy which uses Programs to control who can see fridges?
what if the hierarchy of CCE staff is different than Requisition hierarchy?
And what happens for facilities that are not using Requisitions and are not inside a hierarchy?
Catalog: Will v3 have just one catalog shared by all programs?
Inventory: In v3 will CCE inventory items need to be assigned to a program?
Do facilities add their own CCE inventory items? Or is it centrally managed?
Can you remove a fridge? And would that same fridge be tracked if it later ends up at another facility?
Functional Status: Do we use the same "seed data" of statuses and their meaning that v2 had?