The University of Colorado Health organization, aka, UCHealth is increasingly becoming a house-hold name in the Rocky Mountain region of the United States. Now, operating in 3 states, Colorado, Wyoming, and Nebraska, with approximately 441 facilities across 124 locations, UCHealth has grown exponentially over the past few years. In fact, UCH was named in the top 50 hospital rankings for 11 medical specialties in 2015-16 by U.S. News and World Report.
While the team within UCHealth that uses BuildMaster is simply labeled "E-business" on the organizational chart, they are more like a highly-decorated "special ops" team, or equivalent of the infamous "Seal Team 6" called in on special assignments to trouble-shoot, and help out other teams within the organizations when critically needed. They swoop in, save the day (or week, month, etc.) and disappear onto the next project.
Many projects the E-business team works on originate in other teams needing functionality above and beyond the tool sets at their immediate disposal. The E-business team has a direct line to the CIO, and in many occasions they are tasked by the CIO specifically to help out on projects deemed a priority.
Despite its prestige, the team and organization overall were running into challenges. At its core, the main challenge was the result of a manual/non-automated build-release process that was, like most organizations' testament to manual processes, inefficient, and error-prone. While the core challenge was the manual build-release process, a myriad of factors (challenges in their own right!) magnified, and exacerbated this core challenge. Some of these include:
With the culmination of all these challenges, the E-business team recognized a need for tooling and processes that could be standardized across the team and organization, eliminate manual errors, and enforce teamwork with contributors in various locations. After doing evaluations of several build automation tools, the robust functionality of BuildMaster, which provides automation for all aspects of the delivery process, emerged as the best fit.
With a "special forces" kind of team as the principle users of BuildMaster, there are a lot of different ways applications in BuildMaster can get set up, since each instance is unique. Fortunately, with BuildMaster's flexibility, a variety of application/project types are welcome.
For instance, an entire grouping in BuildMaster are applications that aren't actually "built," (ex: configuration versioning, or document versioning for XLST files). There is also an application that supports a legacy internal application to manage employee ID badges and pictures, for online identity and security purposes. Yet another application manages the patient portal for prescriptions where folks can log in, get medical information, watch information videos, pay bills online, etc.
The list goes on; needless to say, they're using BuildMaster in ways even we wouldn't have guessed!
With roughly 25 new applications created since the adoption of BuildMaster, BuildMaster has automated and empowered the E-business team to maintain 114 applications, divided into 28 separate application groups.
Because of the reduction in error-prone and manual processes that BuildMaster provides, the E-business team is able to manage this number of projects within BuildMaster, as well as jump to the next project and team that needs their help. Of course once they leave a project, the structure and rigor that BuildMaster provides, allows the maintenance team to manage the transition smoothly.
In terms of future BuildMaster use, the E-business team has interesting and ambitious plans: like many health care providers, UCHealth uses many of the products from Epic. However, unlike many of their peers, the E-business team has customized several different Epic products extensively for UCHealth.
The challenge arises when Epic releases a new version, and the customizations are lost when updating to the newest version. Soon the E-business team will be storing their Epic customizations in BuildMaster, as a "closed system," wherein the customized elements of Epic products can be deployed across multiple environments, and seamlessly re-integrated into use after upgrading to Epic's newest version.
This plan is only possible because of the time BuildMaster will save the E-business team from having to recode their customizations, while avoiding manual errors when deploying customizations across the UCHealth network. We're ecstatic to be part of the E-business team's success!