Healthcare Company Adds API Testing and Monitoring for a CI/CD Pipeline While Migrating from CDA to FHIR®

As with other healthcare companies, this customer’s IT department was overseeing a couple of significant and potentially risky migrations:
1) moving from on-premises datacenters to self-hosted public clouds
2) migrating from the CDA API protocol to FHIR®
Both migrations involve a sharp rise in the usage of database-connected REST APIs to accelerate the development of new features, tools, and applications. In an effort to accelerate their goals with these migrations, the healthcare customer supplemented their agile development processes with a CI/CD pipeline.
While development velocity did increase, so did the number of API errors that were not caught before going to production. Even worse, some bugs were only caught after going live. Any functional API errors may not only be devastating for the company and its customers – but also for the DevSecOps team as in the case of a recent Twitter API error that exposed the private data of 17 million accounts.
The healthcare company searched for multiple solutions to solve their three biggest needs:
Replace their unreliable API tests and monitors
Deploy proper automated API testing, and increase regression testing without decreasing go to market times
Detailed monitoring of these critical APIs for internal and external SLAs
With API Fortress, the healthcare company realized that only one platform could solve all of their biggest needs.
—Chief Architect at the Healthcare Company