Closed hannahkane closed 7 years ago
In general, we want to compute response times ( #26 ) and then dump them into a table with FMA ID as primary key.
This will be the same table where we store the FMA-specific demographic stats for #75.
Mostly, this is straightforward, but there are two important questions to be answered:
These are open for discussion.
Suggested initial answers to these questions, from discussion during tonight's meeting (3/22):
Any thoughts?
@futurechris The suggested initial answers sounds good to me.
As far as "average" goes, are we still going to use the median?
Yeah, I think median is probably more appropriate - we were just using 'Average' conversationally, hard habit to break.
In support of median: NFPA standards say "<6 minutes for 90% of calls", so 'median-style' metrics are already appropriate for the domain.
For that matter, we could actually mention the NFPA standard somewhere in the UX, might be interesting to users. I think PF&D handily beats the NFPA standard, though I haven't calculated that to be certain.
I added median_response_time by FMA to the fma_api_rollup
. Next onto average # of incidents per week per FMA.
Updated fma_api_rollup
to include average number of incidents per week by FMA. Going to close this ticket now unless you guys want to add anything else.
We're looking for: