PointClickCare · 2021 - 2022
PointClickCare: the provider portal, a shared UI library, and 30% faster CI
At PointClickCare, which makes healthcare software for senior care, I worked on the provider portal, built its shared UI component library, and made the CI pipelines 30% faster.
- role
- software engineer
- domain
- healthcare software for senior care
- focus
- provider portal, UI library, CI
An illustration of the component library and the pipeline speedup, not PointClickCare's real UI.
Context
PointClickCare builds cloud software for senior care and post-acute providers, which means the people using it are clinicians in the middle of a shift. A slow page or an inconsistent form is time taken away from a patient, so frontend quality isn’t cosmetic there.
What I built
The provider portal. I was a software engineer on PointClickCare’s provider portal, one of its web apps for healthcare providers.
A shared UI library. I built the portal’s UI component library: the buttons, inputs, selects, tables, tabs and badges that every screen is assembled from. Instead of each team rebuilding the same pieces slightly differently, the portal got one set of components that look and behave the same everywhere, and new screens could be assembled from parts that were already tested.
CI, 30% faster. I optimized the CI pipelines and cut their run time 30%, which shortened the wait between pushing a change and knowing whether it was safe to merge, for every engineer on the team.
What I learned
Shared components and fast CI solve the same problem from two ends. Both make the right way to build something also the fastest way, and teams follow the fast path.