iSixSigma

Typo errors

Six Sigma – iSixSigma Forums Old Forums General Typo errors

This topic contains 11 replies, has 11 voices, and was last updated by  LAJISH IBRAHIM 10 years, 1 month ago.

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #52483

    persian
    Participant

    Hi
    I have a process where employees do data entry. Its a web based data entry where in they key from scanned (Healthcare claims)images.They have to follow rules while keying the predesignated fields.We do audits and our target quality is at 99.75%.
    The issue is with human errors like typos and omitting of fields that they were supposed to key. How do we addres this issue iam doing a SS on improving the quality and i cant find any other  RC for typos other than carelessnes.The claims may include handwritten or printed forms as well.
    Does anyone have similar issues

    0
    #184650

    Remi
    Participant

    Hai persian.
    offcourse carelesness is not the only RC. But it is the main RC people find when they have the following mindset: “typing text over from a piece of paper is easy to do”. Example: picking up a 10 kilo bag is easy; do it continuously for 8 hrs longterm is not easy but backbreaking.
    tips:
    1} use the Ishikawa (Fishbone) to decide what sorts of RC’s can be found in the other 5 bone’s.
    2} Brainstorm with others about RC’s: other people look at things differently so they can help you see things you haven’t thought of
    3} Ask the operators: why do they find it difficult to perform faultless continuously
    3b} For one week take over the job of an operator And complete that week (40 hrs), not just a short time. Then you really know how it is to be an operator and what the difficulties of the job are.
    Examples of other RC’s:
    Difficulty of the form (# fields to fill in; location of the fields; lettertype,..)Readability of textDifference between formsEnvironmental disturbances (light, noise,..)Variabel and Interesting work
    Good luck,
    Remi

    0
    #184660

    Adam L Bowden
    Participant

    Typically typos occur 1 in 200 key strokes – the key would be to
    mistake proof or eliminate by getting rid of paper and going all on-
    line.Adam

    0
    #184663

    Bower Chiel
    Participant

    Hi Persian
    If you post an e-mail address I’ll send you a summary of discussion of typos on another site.
    Best Wishes
    Bower Chiel

    0
    #184673

    I’Anson
    Participant

    Hi Bower,
    Could you please also send me the summary? I have done some work around data entry errors and would be interested in reading it.
    Thanks,
    Daniel.
    dbenson@australianunity.com.au

    0
    #184674

    eistein
    Participant

    Are the fields fixed?My thought is can you change the process as a pipelining.For instance, number the fields from 1 to X in each image. At 1st step, the operator just needs to key in the data from field #1 of all images, then key in the data from field #2, and so on. I think the operation can avoid the omitting of fields.

    0
    #184676

    Dbest
    Participant

    Hi Bower,
    Kindly send me the summary of typos as well for my added learning.
    My email add is dbest459@yahoo.com
    Regards
     

    0
    #184682

    Monika Anand Bidani
    Participant

    What you can try to minimise the Typo errors is to divide your team into best Data entry operator, Average, Low category. Further you can divide the most critical fields to be entered by BEST and Average performers, the low performers can be given non critical fields for data entry. If it works out a bit of improvement do share with me too!
     
    Regards
     
    Monika.

    0
    #184683

    Monika Anand Bidani
    Participant

    Try dividing your data entry operators into 3 categories- Best to specialise in Critical fields, Average to further key in comparatively less critical fields and low performers to key in the remaining fields. If it works out do let me know!
     
    Regards
    Monika
     

    0
    #184684

    Nik
    Participant

    I like the approach laid out by Remi. A couple of additional suggestions:

    One major advantage you have here (hopefully) is that the error rate is measurable. Quantifying the objective in a measureable and specific method is sometimes skipped, but is essential for determining if you had any effect.
    Consider using doing an attribute Measurement System Analysis, not on the measurement system you are using, but to quantify the typos and determine where the causes may lie. For example, take one field, have at least 3 operators enter a value into that field (30 times and 2 reps), this can give you a short term baseline and can be repeated to validate the effectiveness of solutions. You can also have them do entire forms to validate which fields are the largest problems, then determine root cause.
    In Lean there is a term Jidoka, which western translation is “automation with human touch.” What this could mean for you is strategically putting in automated “sanity checks” on critical fields to flag when a likely typo has occurred. For instance if a field must be 6 characters, limit the field to 6 and include a warning message. If a field’s value needs to match data in another table, have a quick check performed before submitting. (This is often considered “error-proofing” too). You can then use your modified MSA to validate the errors have dropped off.
    Good luck.
     

    0
    #184691

    Mr Kid
    Participant

    How do you define root cause?  We generally define it as “the thing that we can do something about that will solve the problem.”  I would say that “carelessness” is not your root cause, but “the process is designed poorly to require much manual data entry” is.
    With that in mind, a couple of common solutions are scanning software with character recognition, or having 2 operators enter the same data set, then do a data comparison, and flag any data that does not match between the 2. 

    0
    #185233

    LAJISH IBRAHIM
    Participant

    Hi Bower,
    Please send the article regarding the typo errors to my mail id too.
    my id is : lajish.ibrahim@acs-inc.com
    Thanks
    Lajish
     
     
     

    0
Viewing 12 posts - 1 through 12 (of 12 total)

The forum ‘General’ is closed to new topics and replies.