Management Changes: Data report for when someone else besides visit report submitter makes changes to a visit report

[cbeaulaurier]

Background

In addition to the approach outlined in this ticket, the DCYF team also wants insight into who is making the edit after a visit report is unsubmitted (for edits) before approval. If the worker adjusts, it's OK. If other people besides original submitter adjust, that's what they want to see. These cases aren't necessarily fraud but the Department would like to review.

They care about changes that were made after the visit report was submitted by the worker for their supervisor's approval, until the visit report is invoiced for.

Scenario that would be included in the report:
Worker submits visit report > Manager 1 unapproves > Manager 2 edits and submits > Manager 1 approves

Description

Report includes any changes to visit reports made by someone other than the visit worker(s), prior to invoice submission.

Minimum report:

• Times
• Mileage
• Expenses
• Report Type
• Totals
• Difference in dollar amount between totals

(If a change to a visit report happens after invoice submission, it is included in #54 instead.)

[cbeaulaurier]

Jordan was thinking:
Can we see total dollar value before and after, and the difference?
They care about cases when the total has changed as a result of doing these changes. Auditors will review more details in Sprout, though not all changes will be obvious in Sprout. Changes to billing include time, mileage, expenses. Also include type of report.

Minimum report:

• Times
• Mileage
• Expenses
• Report Type
• Totals
• Difference (?)

Concern about seeing legs change: new legs added, makes it hard to understand. Jordan is not interested in detail at the leg level, wants to see the information rolled up to the visit report.

Sarah brought up a case where a provider switches a visit from a no show visit for a canceled visit, because the payment for these visit types is different. So it isn't just mileage and time and expenses, what is paid depends on many potential variables.

Gregor thinks the report won't necessarily show every field that caused the change in billing, it will show the easy ones and that will be a good starting place. If the report is useful, it can be improved to take all the billing code special cases into account.

What's the scope? Is it this Management Changes & Approves situation, or is it all changes that result in billing differences?

Gregor is concerned about the flood of data if we flag any changes pre-invoicing. In fact we encourage providers to audit their visit reports before invoicing. You'll be looking at 10-15k rows per month as most visit reports get edited at least once. So we need a filter, what do we care about?

Decision: Let's stick with Management and then see where to go from there.

Jordan thinks a lot of data could be manageable in a pivot table.