Menu ▾ ▴

#2497 Billing simulation doesn't indicate which invoice has bad ver code

RELEASE_12_1
closed-fixed
Victor Van Herk
None
6
2014-04-23
2013-05-01
Trimara Corporation
No

Problem Summary:
The billing simulation (Admin-->Simulation OHIP File) fails if the version code for a patient's heath card is invalid (e.g. if you put something like '##' in it) but it does not indicate which invoice the problem is in. For other errors, it will fail but it provides an indication of which billing the error is in by writing a message in the "Comment" field. Screenshot attached.

Expected Result:
The simulation should fail but it should indicate which invoice the problem is in.

Actual Result:
The simulation fails but it does not indicate which invoice the problem is in.

Steps to Reproduce:
(1) Open the demographic for a patient.
(2) Put '##' in the version code for the heath card.
(3) Save the demographic.
(4) Bill an appointment for the patient to OHIP.
(5) Go to Admin-->Simulation OHIP File and run a simulation.
(6) The simulation will fail indicating "Header 1: Ver. code wrong!" but it will not indicate which invoice contains the error.

Reproduced In:
12_1 Deb 362 (fresh install) + Ubuntu 12 LTS (fresh install)

Additional Information:

  • This applies to other errors as well - OSCAR does not indicate which invoice the error applies to. When you are doing a simulation with a number of invoices on it (or a number of providers) this makes it very difficult to find which invoice to correct.

Discussion

  • Trimara Corporation

    Trimara Corporation - 2013-05-01
     
    Thumbnail
    screenshot.jpg

  • Victor Van Herk

    Victor Van Herk - 2013-05-02
    • assigned_to: nobody --> vanherk
     

  • Victor Van Herk

    Victor Van Herk - 2013-05-03
    • status: open --> open-accepted
     

  • Victor Van Herk

    Victor Van Herk - 2013-05-03
    • status: open-accepted --> pending-accepted
     

  • Victor Van Herk

    Victor Van Herk - 2013-05-08
    • status: pending-accepted --> pending-postponed
     

  • Trimara Corporation

    Trimara Corporation - 2013-05-09
    • status: pending-postponed --> open-postponed
     

  • Trimara Corporation

    Trimara Corporation - 2013-05-09

    Hi Victor. I notice that this one was changed to a resolution of "postponed". Is there a reason why it has been postponed?

     

  • Victor Van Herk

    Victor Van Herk - 2013-05-09
    • status: open-postponed --> pending-postponed
     

  • Victor Van Herk

    Victor Van Herk - 2013-05-09

    Hello Kris.

    Yes, I had exchanged emails with you last week on this topic. I just resent last dialogue to your inbox.

    I need a valid test case the demonstrates correct handling of validation message in the comment field in order to proceed.

     

  • Hagir

    Hagir - 2013-05-31

    Same error occurs. It can be produced also by putting a space before the version code on the master. For example " R", or " FV". Error will result but without specifying the invoice at which it occured.

     

  • Trimara Corporation

    Trimara Corporation - 2014-03-16
    • summary: Billing Simulation Doesn't Indicate which Bill Has Bad VC --> Billing simulation doesn't indicate which invoice has bad ver code
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -16,4 +16,7 @@
 \(6\) The simulation will fail indicating "Header 1: Ver. code wrong\!" but it will not indicate which invoice contains the error.

 Reproduced In:
-12\_1 Deb 118 \(fresh install\) + Ubuntu 12 LTS \(fresh install\)
+12\_1 Deb 362 \(fresh install\) + Ubuntu 12 LTS \(fresh install\)
+
+Additional Information:
+* This applies to other errors as well - OSCAR does not indicate which invoice the error applies to. When you are doing a simulation with a number of invoices on it (or a number of providers) this makes it very difficult to find which invoice to correct.
    • Group: --> RELEASE_12_1
     

  • Trimara Corporation

    Trimara Corporation - 2014-03-16
    • status: pending-postponed --> open-accepted
    • Priority: 5 --> 6
     

  • Trimara Corporation

    Trimara Corporation - 2014-03-16

    Hi Victor. Looking through the comment history, I didn't see any comments about setting this to postponed so I set it back to open-accepted in case it was a mistake.

     

  • Victor Van Herk

    Victor Van Herk - 2014-03-30
    • status: open-accepted --> open
     

  • Victor Van Herk

    Victor Van Herk - 2014-04-18
    • status: open --> open-accepted
     

  • Victor Van Herk

    Victor Van Herk - 2014-04-18
    • status: open-accepted --> open-fixed
     

  • Trimara Corporation

    Trimara Corporation - 2014-04-23
    • status: open-fixed --> closed-fixed
     

  • Trimara Corporation

    Trimara Corporation - 2014-04-23

    Validated in 12_1 Deb 385...changing status to closed-fixed

     
MongoDB Logo MongoDB