Quality Assurance

With the pace of change being forced down by the government through the regulations, ISVs are being kept busy. On one hand they have newer functionalities to implement to satisfy regulations. Then there are customers whose business context is changing and hence require innovative features to delight their customers. With all this change, ISVs are busy guiding their armies of developers. And in order to make sure that these changes do not impact them adversely, quality needs to be maintained.


No product can be competitive if it isn’t consistent and reliable. In order to ensure both these parameters, what’s needed is an understanding of the needs, the context and the users. However, with healthcare being a vast domain facing the flux of changes, it isn’t always possible to achieve all three. No matter how good the QA resources happen to be technically, if they do not have a firm understanding of healthcare ecosystem it will result in poor quality or increased cost or both.

Time to market

With competition more fierce than ever, ISVs are striving to get better products to market before anyone else can. The nature of SDLC makes it impossible to do everything in parallel. As quality cannot be compromised, in every iteration a comprehensive testing of the code needs to happen. This stretches the development cycle beyond what ISVs would like most often.

Resources Spent

Time isn’t the only variable in the equation described above. While quality is an important factor, so is the cost. In attempt to deliver a quality product in the most aggressive timelines, ISVs cannot afford to overshoot their budgets. However, when everybody is competing for similar resources, they become scarce and/or expensive. This is a concern for more ISVs as the management wants to maximize what gets done with the same set of resources.

How can we help you?

As ISVs provide many major and minor releases in an year, there is always something on the QA team’s plate. Regression is paramount to ensure that customers aren’t annoyed once they apply a patch or upgrade to a newer version. Such recurring testing can be accomplished using tools that cut-short the release time significantly while bringing about savings. We realize that healthcare solutions often change and result in modification of test scripts. Therefore, to make life easier we have developed wrappers or dashboards that make it possible for business users to control automation testing. 

While automation might make testing faster, its not the silver bullet. As there is significant cost associated with it, it might not be wise to automate everything. There will be some scenarios that are difficult to achieve through automation. However, the testers who validate the application need to understand the workflows and not look at the solution as a technical offering. If they don’t understand the users, they cannot test an application successfully. At Nalashaa we have been working with EHR vendors and understand their world. 

One of the ways to accelerate SDLC is to reduce the number of sequential steps. Geo-distributed teams can be a good way to achieve this. While your developers work towards an objective (or user story) our QA teams can prepare themselves for it. When at the end of the day developers check-in their code into the repository, our QA teams can pick that up when their day begins, test if thoroughly and report the test results in your project management tool. When your developers are back in the office next day, they can straightaway start by addressing the defects reported. The cycle continues and cuts the development time in half. Connect with us to know how we can make this run like clockwork.

Here is a brief snapshot of the different services we provide. Link to the QA services slide/put the picture here.

If you are already hear, we would love to hear your voice. Give us a call and we would be happy to brainstorm on a solution for you.