Calendar

November 2017
M T W T F S S
« Oct    
 12345
6789101112
13141516171819
20212223242526
27282930  

Calendar

November 2017
M T W T F S S
« Oct    
 12345
6789101112
13141516171819
20212223242526
27282930  

Follow us on…

  • {name}
  • Google Profile
  • LinkedIn
  • Twitter
  • Facebook
  • YouTube
  • slideshare

Facebook

Recent videos

Posted on: February 20-2015 | By : Sandeep Satyaprakash Mysore | In: Business Agility,Healthcare Informatics,Testing | 3 Comments

The U.S. healthcare model has achieved great technological advancements. The implementation of Electronic Health Record (EHR) systems has further streamlined care delivery. However, the focus so far has been on implementation and maintenance of technology. The need to document business processes in the provider environment, product optimization or testing EHR systems has taken a back seat.
 
The lack of business process driven test coverage becomes more prominent when the EMR system undergoes a release cycle or a version upgrade. This leads to massive defect leakage resulting from inadequate business coverage during the documentation process, the root cause of which is the failure to identify the traceability and analysis while capturing potential test scenarios.
 
To understand the fallout of the conventional testing approach, let us consider the following hypothetical examples for release of EMR. Let’s assume that the release cycle data for upgrades and fixes is over a period of one month. We have listed the affected business areas in each release.
 

 
You must have noticed that the admission process is affected four times in five months. Assuming the absence of a test repository the probability of repeating previous errors is high. Testing of some key parameters could be missed, for example, if we do not test inpatients during regression testing. With a business test repository in place we can overcome these challenges easily.
 
The example scenario, we are considering, is limited to the business process level, however, it can be extended to a sub process level. As a consequence multiple defects or applications breaks might go unnoticed. This can lead to confusion causing delay in care delivery and cascading complications.
 

 
Business processes are integral to the entire system and it’s imperative that they are tested along with other components to ensure system accuracy. Business process driven testing introduces domain intelligence into the test design phase, addressing gaps between business knowledge and testing, thereby mitigating risk and weeding out the possible scenarios of breakdown.
 
The Road Ahead
Business process driven testing is paving the way to integrate testing practices enriched with domain specifics. This approach becomes imperative as organizations move towards vertical consolidation and new application providers. The possibility of usability increases manifold due to its domain-agnostic nature.
 

1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
Loading ... Loading ...

Sandeep Satyaprakash Mysore


Sandeep is currently working as a Usability Analyst in the Healthcare domain, he has also been...

Read More...

 
 
  1. Aarohi on February 23, 2015 at 3:58 pm Says:

    With the assistance of outsourcing companies, the above process can be carried out simply…

  2. flower on April 23, 2015 at 2:46 pm Says:

    I see nothing new out here, all test scenarios usually mimic business process only.
    surprised to see that syntel learnt it recently.
    All over the world functional test cases are derived and traced back to business process which are basis for business requirement, software requirement and so on.

    of course like every other Indian IT outsourcing company , u may also claiming to be achieving efficiencies through accelerators(which are for show casing purpose only and don’t stand hard scrutiny) Most indian IT firms are hiring non-engineering and non technical graduates at low salaries for testing work and trying show to clients that they are cheaper due to accelerators.

    if your accelerators are so good why dont you sell your stuff as a product like HP, QTP.

  3. Moumita Adhikary on July 24, 2015 at 4:45 pm Says:

    Root Cause: failure to identify the traceability

    Timeline: four times in five months;
    observation – testing repeatedly the same test object over such a longer period is a waste of time, cost, resources, and gross business.
    Suggestion – Three month makes a quarter which must be more than good a timeline as per industry standard. Not to forget, action items that follows testing
    has to be taken care of.

    Setback: delay in care delivery and cascading complications.

    Suggestion:
    i.Delegation of responsibilities of SME’s within team to practise inverted prism approach which might include
    following action plans : -
    a.Considering right people for teamwork to get work done right to optimize resource utilization to attain
    benefits for a project.
    ii.Understanding and getting done with the action items needs to be done within timeframe to obtain optimal business coverage.

Leave a Reply

 

*

© 2017 Syntel, Inc.