ChartWise Medical Systems specializes in cloud-based solutions for Computer-Assisted Clinical Documentation Improvement. AI-driven, integrated, and comprehensive, ChartWise’s scalable Software as a Service (SaaS) assists physicians and clinical documentation specialists and features prioritization, electronic queries, flexible workflow, robust reporting, and denials prevention. Developed by renowned physician Jon Elion, M.D., ChartWise is the only CDI software designed by CDI customers for CDI customers, offering reduced risk, actionable data, and a proven fast ROI.
Sahi Pro: Tell us a little about ChartWise Medical Systems, Inc.
Ms. Linda Markhart: The company’s premiere product is ChartWise:CDI, a Computer-Assisted Clinical Documentation Improvement (CACDI) software system, designed to improve precision in quality clinical documentation to support revenue assurance. In February 2014, ChartWise launched an upgraded system, ChartWise 2.0—redefining CDI with powerful new features and an advanced new user interface.
Sahi Pro: What challenges in your business influenced you to look for a solution? Did you have a previous solution that could no longer meet your company’s needs? If so, how did your needs change?
Ms. Linda Markhart: As the test engineering manager and initially the only test engineer, my biggest challenge was initially the size of my team. As a startup company in 2009, I was a one person team validating a new product against initially 2 software engineers. In the early days, all testing was done with paper test cases. My first automation tool was with a well-known company with a web testing tool. It was not robust nor easy to maintain with all the changes that come with a new product.
The next edition of this tool utilized C# and was much better. It however did not support multiple browsers and to determine where to click on a button within a page utilized x and y coordinates. So, with a rapidly changing web application it was time consuming to maintain.
As the years have passed, I have added one additional test engineer and an intern for a short period of time. As the product increased in size and complexity so did the tests. Maintenance continued to be a huge time taking task.
Currently, my team involves two test engineers, myself and one other person. We write a manual test for each test case that is automated within Sahi, and store in source control. We also do a lot of ad hoc testing.
The development team we provide our test service for consists of 3 software engineers, 1 report engineer and 2 ETL engineers.
Sahi Pro: How did you search for a solution to your problem? Why did you choose our firm over our competitors?
Ms. Linda Markhart: Early in March 2016 while searching for other tools I came across a comparison of automated tools. Sahi stood out among the others. I downloaded the free version followed by the Pro version. I watched a couple of YouTube videos of the “how to use the product”. I soon had quite a few of our old Coded UI tests translated over to the hybrid java scripting. The recorder was helpful but I found it just as easy to hand code the tests.
By mid-March I had many of our regression tests moved over to Sahi. I went to my manager and told her the price, how quickly the regression test ran and all I was able to do with Sahi that I could not do with the other test automated software. I was given the okay to purchase the product for my team.
Sahi Pro: What specific results have you seen from implementing our product?
Ms. Linda Markhart: We are able to run all our regression testing on our supported browsers in less than 3 hours across 3 machines and an iPad. With the old product it required 8 hours to run on just the Internet Explorer supported browsers. We still needed to run tests manually on Chrome, Firefox and the iPad. With the other product we spent a huge amount of time just to keep the tests running. With Sahi, we are able to add our product’s new features to our regression test suite as well. When something changes in the app it is easy to fix quickly. We had several data driven tests that easily translated to Sahi as well.
We test multiple screen resolutions with basic surface tests. The old automation tool required many versions of the basic core test as they behaved slightly differently with each screen resolution. Now I have a function for each specific object it tests that works for all resolutions. So if something changes there is one place to change instead of numerous places. Big Plus on time saving.
Now when something fails it is very easy to see the cause. Previously I would triage with the mindset “run it again and maybe it will work” vs now “something in the new code delivered broke the test” it is a bug.
Sahi Pro simplifies Test Automation so you can invest your time in creative testing.
Click here to download this case study in pdf format.
