This weeks edition is a bit more recap than release as we spent much of the Sprint laying behind the scenes foundational work for some larger projects
Customer Deliveries
Data Fulfillment
Tracking the Asset Trackers (02/02/2022):
In an effort to track engagement to the dashboard, Novant has requested a cadenced report detailing how many users are signing into the Asset Tracking Application. Previously CS has had to manually manage generate this report. Now an automated report has been created to negate the need for manual work.
Operational Deliveries
New Team. Who This? (1/26/2022):
Worked to uncover some previously undocumented information about how our hygiene sensors generate a ‘last ping’ line item in admin.
What we learned:
“Every 10 minutes an hard calibration of the capacitive sensor is performed so to guarantee always a right calibration of the sensor (added once it was realized that the sensor was somehow less responsive if not recalibrated.”
This was tested and verified in the field. Last Ping is counted every ten minutes regardless of dispense events or badge activity.
Escalations during Sprint 107
Access to CT Tracing App - User is showing that they have access to Contact Tracing regardless of whether or not facility has purchased Contact Tracing. Determined that this Enterprise had one facility that was incorrectly enabled for contact tracing. Disabled this feature to resolve the issue. No further escalation required.
Converting Static Comm Hubs to DHCP Assignments - Lovelace has requested that their previously deployed Static IP comm hubs be reconfigured to DHCP Assignments. - Researched and determined that this could be done in a one off scenario (don’t want to make this a regular occurrence). After developing a deployment plan, facility requested to hold off any any additional reconfigurations. No further escalation required.
Potential EMR Issue - Facility reported they were still receiving compliance information for unoccupied rooms. Determined this was due to the facilities EMR Integration being set to ‘internal’. Troubleshooting has been updated here.
HRIS 2.0
Breaking Ground! - We completed our first major story for HRIS 2.0 which involves retrieving a .CSV file from a separate service in AWS. These first stories are often large and difficult, because in order to do the first story you also have to complete all the necessary ancillary work in getting a new service up and running. Which is significant. Progress!
Storybook
An application that gives a home to our global design components. It allows us to document design standards and streamline our UI/UX.
The end goals are:
To code global components into storybook. (i.e. changing the look of a header to a universal standard)
Integrate it into all of our applications.
This is a central location to set/house our standards so that we do not have inconsistent designs across our app.
Here’s what we completed in this Sprint:
Upgrades to the latest version of storybook and updated the readme.
Added the first components (Buttons and H1)
Security
In order to deploy our software we use certain languages, frameworks, tools, and even operating systems (For Example: For a given application of ours like admin we might use a specific version of Ruby and similarly various versions of other packages. All of these things get updated over time.) In the natural course of progress these deployment methods become susceptible to security vulnerabilities. We have additional tools that notify us of these Common Vulnerabilities and Exposures (CVE).
In response, the maintainers of these languages and packages implement upgrades/fixes.
We were notified of some CVEs during this sprint and it became a priority to mitigate them by upgrading versions of an underlying operating system, upgrading various packages we use, land rebuilding ‘images’ representing environments in which code is deployed and runs. This is a natural part of our security maintenance procedures, and when done preemptively is no cause for alarm.
The bulk of this work is now done and we are continuing to roll out mitigation steps. Because this is security related, it was necessary that it take priority over other work in the sprint. For more information take a look at the work we did in Confluence.
Release notes created with input from our dev team: Paul Lorsbach, Ryan Schaul, Emily Spieler, & Jeff Wagner.