Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quarterly Metric: Hearings Show Rate #12390

Closed
alisan16 opened this issue Oct 15, 2019 · 6 comments · Fixed by #12939
Closed

Quarterly Metric: Hearings Show Rate #12390

alisan16 opened this issue Oct 15, 2019 · 6 comments · Fixed by #12939
Labels
Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Team: Delta 🔺 Type: Metrics or Reporting

Comments

@alisan16
Copy link
Contributor

This metric is required by OIT (Metric ID: 1812216039) and is critical to understand how the Caseflow Hearings products are helping to improve the appeals hearings process.

Metric definition: (Total scheduled meetings held – postposed hearings) / total scheduled meetings from Caseflow Hearing Schedule

Example SQL for AMA appeals from https://caseflow-looker.va.gov/looks/193

SELECT 
	hearings.disposition  AS "hearings.disposition",
	COUNT(DISTINCT appeals.id ) AS "appeals.count"
FROM public.hearings  AS hearings
LEFT JOIN public.appeals  AS appeals ON hearings.appeal_id = appeals.id 
LEFT JOIN public.hearing_days  AS hearing_days ON hearings.hearing_day_id = hearing_days.id 

WHERE 
	(((hearing_days.scheduled_for ) >= (DATE(DATE '2019-06-01')) AND (hearing_days.scheduled_for ) < (DATE(DATE '2019-06-30'))))
GROUP BY 1
ORDER BY 2 DESC
LIMIT 500

-- sql for creating the total and/or determining pivot columns
SELECT 
	COUNT(DISTINCT appeals.id ) AS "appeals.count"
FROM public.hearings  AS hearings
LEFT JOIN public.appeals  AS appeals ON hearings.appeal_id = appeals.id 
LEFT JOIN public.hearing_days  AS hearing_days ON hearings.hearing_day_id = hearing_days.id 

WHERE 
	(((hearing_days.scheduled_for ) >= (DATE(DATE '2019-06-01')) AND (hearing_days.scheduled_for ) < (DATE(DATE '2019-06-30'))))
LIMIT 1

Once this metric is instrumented, ensure delivery to OIT with #12389

@alisan16 alisan16 changed the title Instrument Quarterly Hearings Show Rate metric Metric: Hearings Show Rate Nov 1, 2019
@alisan16 alisan16 assigned alisan16 and lomaxap and unassigned alisan16 Nov 18, 2019
@alisan16 alisan16 changed the title Metric: Hearings Show Rate Quarterly Metric: Hearings Show Rate Dec 9, 2019
@D-L-Ware D-L-Ware added the Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns label Dec 19, 2019
@jimruggiero jimruggiero added the Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. label Dec 28, 2019
@pkarman
Copy link
Contributor

pkarman commented Jan 9, 2020

Run in production for 2019-09-01..2019-12-31

irb(main):278:0>
=> 0.7790697674418605

which I interpret as 77% -- does that seem right @D-L-Ware ?

@D-L-Ware
Copy link

D-L-Ware commented Jan 9, 2020

In the realm of the possible. Running old VACOLS reports on past fiscal years usually gives me a show rate of mid-60%, defined as hearings held versus the total of held, cancelled, postponed, and no show.

So I think I need to understand how we are defining Show Rate to better evaluated this one.

@alisan16
Copy link
Contributor Author

alisan16 commented Jan 9, 2020

This hovered around 75% between 2015 - Q3 2018 based on the Product Impact Statement: https://drive.google.com/file/d/1iw3QTGzy0I5lZx_xeWwvqkmPEvPyxfQc/view

It also states:

The percentage of scheduled hearings that are held, omitting postponed hearings. This
measure is believed to track the Veteran experience of Board hearings, potentially
indicating the effectiveness of VA communication with Veterans about their hearing and
the ease of attending a hearing. The target for this KPI is for the show rate to meet or
exceed the baseline of 75% by January 2020.

So if it's at 77%, wahoo we hit the goal!

@pkarman
Copy link
Contributor

pkarman commented Jan 9, 2020

When I fixed the date range to just Q4 (2019-10-01 .. 2019-12-31) it goes up slightly to 78.7% so I think we're good. wahoo!

@pkarman
Copy link
Contributor

pkarman commented Jan 9, 2020

@D-L-Ware the definition is here: https://github.com/department-of-veterans-affairs/caseflow/pull/12939/files#diff-ea02ec272fafb6f95e557b7406f28231R9

held / total - postponed

which you gave a +1 to here #12939 (comment)

@D-L-Ware
Copy link

Yeah, thinking about if it was reasonable or not the minus postponed was what I was missing. This looks correct to me.

va-bot pushed a commit that referenced this issue Jan 10, 2020
Resolves #12390 

- Creates `Metrics::Base` class that all future metrics will inherit from
- Adds `Metrics::HearingsShowRate` class
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Eng: Data Mark when data has been backfilled, or the issue has any data integrity concerns Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Team: Delta 🔺 Type: Metrics or Reporting
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants