Blog

Less than two years remain for healthcare payors to fully comply with CMS-0057-F (CMS Interoperability and Prior Authorization Final Rule). Among other things, this impressive acronym requires developing or improving Patient Access APIs. This guide will cover everything you need to know to comply.

Cost optimization is again a priority for tech companies. Some engineers are uneasy about AI replacing them with codeless test automation (TA). But are these platforms as powerful as their marketing? What ROI can businesses expect in a real-world setting? What exactly do you need to maximize the return?

CMS-0057-F brings massive changes to the US healthcare. Our team has looked at the new CMS Interoperability and Prior Authorization Final Rule published on January 17, 2024. The regulation aims to make health information more accessible, and easier to exchange.

There has been considerable talk about AI software development. Will AI replace human engineers? Can startups make production-level software with AI? Beyond the hype and fear-mongering, there’s very little empirical evidence of its use on commercial projects.

Why would you want to import existing cloud resources into Terraform? Well, there are many reasons. I once joined as a Lead DevOps Engineer on a healthcare project developed outside the US. Since 2018, multiple teams have supported the project, fueled by coffee and bad decisions. Eventually, the founders sold the startup to a new owner and drove their Tesla Roadsters off into the sunset. 

Codeless test automation has surged in popularity, promising to streamline the testing process without extensive coding knowledge. However, despite the growing interest, there remains a significant lack of detailed information about the implementation of no-code QA tools in real-world projects. This gap in knowledge leaves many organizations, including ours, cautious about their adoption.

HIPAA compliance often takes a backseat for medical startups. Competition is high, funding scarce, and deadlines merciless. When resources are limited, upfront costs seem like a huge burden. Such thinking is pervasive among business stakeholders.

When businesses ask themselves, “What is important for a successful DevOps transformation?”, the first thing that comes to mind is adopting new technologies. Yet, despite experimenting with new tech, only 11% of teams are DevOps high-performers, according to the latest DORA research.

Why move to microservices? You’ve probably heard this question when discussing your IT budgets. After all, businesses need to scale rapidly to stay competitive. But are the benefits of microservices enough to outweigh the costs of app modernization?

Cloud costs can be unpredictable, volatile, and hard to understand. Engineers at Adobe once burned through $80,000 of cash in a single day on Microsoft Azure. Five years ago, another SaaS company was overpaying AWS “just” $14,000 a month. Intervention from our DevOps team saved them over $840,000!

Poor quality of software products costs American companies more than $2 trillion a year. You don’t have to put much effort into finding examples – just take a look at Bó, the digital bank developed by the high street lender RBS to compete with banks like Monzo and Starling. It was supposed to become a major mobile banking player, providing budgeting and security features.

Modern software development can be labeled anything, but definitely not a cakewalk. To ensure effective collaboration of all participants and build advanced solutions, companies apply various software development approaches, and one of them is Lean. It was developed as an effective anti-crisis solution, and it’s not surprising that it is in high demand now.