Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

HandsOnAid: Building and Evaluating an Offline First-Aid Assistant for Emergency Response Scenarios

Rezwan Islam Salvi, Saiyma Sittul Muna, Mushfiqur Rahman Mushfique

Published

Nov 10, 2026

Citations

0

Trust level

Moderate

Usefulness score

57/100 (Medium)

Extraction confidence

65% (Moderate)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Nov 10, 2026

Should you rely on this paper?

This paper has useful evaluation signal, but protocol completeness is partial; pair it with related papers before deciding implementation strategy.

Use this for comparison and orientation, not as your only source.

Best use

Secondary protocol comparison source

Use if you need

A secondary eval reference to pair with stronger protocol papers.

What to verify

Read the full paper before copying any benchmark, metric, or protocol choices.

Main weakness

The abstract does not clearly name benchmarks or metrics.

Human feedback signal
Detected
From extracted signals
Evaluation signal
Detected
Eval setup described
Usefulness for eval research
57/100
Moderate-confidence candidate

Useful as a secondary reference; validate protocol details against neighboring papers.

Abstract

Emergencies can occur where there is no phone signal and no ambulance nearby. A small language model on a phone can be helpful in such situations, but its advice needs to be safe and accurate. We built HandsOnAid, a 4-bit Gemma 2B model fine-tuned with QLoRA on FirstAidQA dataset, a corpus of 5,550 first-aid question-answer pairs. We compared seven configurations, including the base, 4-bit and 8-bit fine-tuned models, and versions with a length floor, safety gate, or retrieval. We used a 41-pair question-answer bank with medically reviewed references that followed ANZCOR guidelines, and a strict 0-5 score rubric, with twelve safety overrides. Four frontier LLM judges (GPT-5.6 Sol, Claude Opus 5, DeepSeek V4 Pro, GLM-5.3) blindly scored every answer, with 45 hidden controls used to check judge reliability. Fine-tuning improved the mean score by +1.08 over the base model to 2.34. The best configuration scored 2.51 out of 5 which was the fine-tuned 4-bit model with retrieval. A medical professional also conducted a blind evaluation of 40 answers across the base, the 4-bit fine-tuned, and the retrieval configurations, and the scores were similar to the LLM judges' average scores. A keyword audit found limited coverage of several details of ANZCOR guidelines in the training corpus, that are required by the rubric, which suggests that missing information in the training data could be a cause of the low scores. On a smartphone device (Pixel 7 Pro) with six CPU threads and no network connection, the 4-bit fine-tuned model produced its first displayable text in 6.86 seconds and a complete answer in 14.88 seconds on average over ten questions.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

strong

Rubric Rating

Directly usable for protocol triage.

"Emergencies can occur where there is no phone signal and no ambulance nearby."

Evaluation Modes

strong

Llm As Judge

Includes extracted eval setup.

"Emergencies can occur where there is no phone signal and no ambulance nearby."

Quality Controls

missing

Not reported

No explicit QC controls found.

"Emergencies can occur where there is no phone signal and no ambulance nearby."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"Emergencies can occur where there is no phone signal and no ambulance nearby."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"Emergencies can occur where there is no phone signal and no ambulance nearby."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
Yes
Feedback types
Rubric Rating
Rater population
Not reported
Unit of annotation
Multi Dim Rubric
Expertise required
Medicine
Evaluation details
Evaluation modes
Llm As Judge
Agentic eval
None
Quality controls
Not reported
Evidence quality
Moderate
Use this page as
Secondary protocol comparison source

Research brief

Metadata summary

Emergencies can occur where there is no phone signal and no ambulance nearby.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • Emergencies can occur where there is no phone signal and no ambulance nearby.
  • A small language model on a phone can be helpful in such situations, but its advice needs to be safe and accurate.
  • We built HandsOnAid, a 4-bit Gemma 2B model fine-tuned with QLoRA on FirstAidQA dataset, a corpus of 5,550 first-aid question-answer pairs.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • Emergencies can occur where there is no phone signal and no ambulance nearby.
  • A small language model on a phone can be helpful in such situations, but its advice needs to be safe and accurate.

Why it matters for eval

  • Four frontier LLM judges (GPT-5.6 Sol, Claude Opus 5, DeepSeek V4 Pro, GLM-5.3) blindly scored every answer, with 45 hidden controls used to check judge reliability.

Researcher checklist

  • Human feedback protocol is explicit

    Detected: Rubric Rating

  • Evaluation mode is explicit

    Detected: Llm As Judge

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    No metric terms extracted.