Estimate time spent retyping lab results
estimate_time_savedUse when someone wants to know how much staff time manual entry of analyzer results costs them, or would be saved by connecting analyzers to the EHR or LIS (e.g. 'we run 80 tests a day and typing each result takes 2 minutes, how much time is that?', 'is it worth interfacing our analyzers?'). Uses only the user's own numbers (tests per day, minutes of manual entry per result, sites, optionally results per test, working days and their own error rate) and returns hours per day, month and year and entries not retyped. Adds no benchmarks, prices or error statistics; without an error rate from the user it makes no error estimate.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"tests_per_day": "<tests_per_day>",
"minutes_per_result": "<minutes_per_result>"
},
"name": "estimate_time_saved"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sites | No | Number of sites, default 1. | |
| tests_per_day | Yes | Tests per day (per site unless tests_per_day_is_total). | |
| results_per_test | No | Results produced per test (panels give several). Default 1. | |
| error_rate_percent | No | The user's own transcription error rate in percent. Omit unless the user gives it. | |
| minutes_per_result | Yes | Minutes of manual entry per result. | |
| tests_per_day_is_total | No | True if tests_per_day is the total across all sites. | |
| working_days_per_month | No | Working days a month. Default 21. |