A technical operating guide for reviewing emCall subscriber activation behavior, Medical Help and Police Help routing, operator workflow states, location handling, and Medical Information Transfer Screen visibility before release.
This manual defines the observable system behavior required when a subscriber initiates a Medical Help or Police Help alarm from the emCall mobile app. Product, QA, and support reviewers should validate the activation threshold, event payload, route resolver, operator queue state, subscriber context, and final disposition as one traceable transaction.
The app creates an alarm event only after the selected help button is tapped three times. The event type, subscriber identifier, device timestamp, and location state are treated as the minimum review fields.
Medical Help opens the speaker path for private alarm operator review. Police Help moves through callback and Safe Word validation before a cancellation or response disposition is recorded.
The Medical Information Transfer Screen must display critical subscriber information after the alarm begins. Missing fields, clipped content, or stale profile data should block release.
The two alarm paths use different routing rules and cancellation logic. QA should validate the subscriber action, event type, route selection, operator behavior, data state, Safe Word result, and expected disposition independently for each path.
Three taps create a medical alarm record.
Private operator channel begins immediately.
Health and subscriber details are visible to support response decisions.
Operator documents outcome and escalates when needed.
Three taps create a police alarm record.
Operator attempts subscriber contact before disposition.
Cancellation requires the subscriber's Safe Word.
Location may be sent if response criteria are met.
The subscriber interface should remain intentionally simple while the operator view exposes the context needed to triage the active event. QA should test the user-facing control, event record, route state, MITS revision, Safe Word field, and operator disposition as one connected workflow.
{
"event_id": "evt_2026_001",
"alarm_type": "medical_help",
"activation_count": 3,
"profile_id": "subscriber_2457",
"profile_revision": "current",
"location_status": "available",
"mits_visibility": "visible",
"operator_route": "speaker_path"
}
IF alarm_type = "medical_help" OPEN speaker_path DISPLAY MITS REQUIRE operator_disposition IF alarm_type = "police_help" START callback_path REQUIRE safe_word_for_cancel SEND location_when_response_criteria_met
MITS is the subscriber context layer used during medical alarm review. The screen must be accurate, readable, synchronized with the active subscriber profile revision, and stable across operator viewport states before a product or content update is approved.
Verify field labels, line wrapping, profile freshness, state persistence, and visibility across desktop and mobile operator views. A release should fail if a critical field is blank without a defined reason, overlaps another field, or renders outside the visible MITS panel.
For regression testing, create one controlled medical event with full profile data and one with minimal profile data. Confirm both display predictable labels, empty-state handling, and no truncation of emergency contact information.
Use this checklist before approving subscriber instructions, product updates, operator scripts, support articles, release notes, or regression test plans that affect alarm behavior, route logic, MITS rendering, Safe Word handling, or disposition storage.
Confirm each help button requires three taps and does not create duplicate events during rapid input or network delay.
Confirm Medical Help uses speaker path and Police Help uses callback path with Safe Word controlled cancellation.
Confirm subscriber data is visible, current, and readable after a medical alarm begins.
Confirm event status, operator note, location state, and disposition timestamp remain available after closure.
Open a controlled test account and trigger Medical Help with exactly three taps.
Verify speaker path opens, MITS displays profile data, and the route is logged as medical_speaker.
Close the event only after operator disposition and timestamp fields are recorded.
Trigger Police Help with exactly three taps and confirm callback routing begins.
Attempt cancellation with a mismatched Safe Word and verify the event remains active.
Complete the correct Safe Word workflow and verify the cancellation disposition is logged.
Update subscriber medical notes, emergency contact, and location permission state.
Trigger a medical alarm and compare MITS values against the current profile revision.
Fail the review if labels, values, or field containers clip or overlap at any viewport width.
Submit this manual for review when a release changes alarm copy, activation behavior, operator routing, MITS visibility, Safe Word handling, profile field mapping, or subscriber support instructions.