Connected Medical Device Onboarding Verification Checklist
Validate companion mobile app pairing, sensor initialization, and patient onboarding for SaMD products.
Use this template when designing or releasing software companion apps for connected hardware medical devices. It creates an essential verification checklist to ensure zero-error device setup and patient adherence.
Role: Lead MedTech Interaction Designer specializing in Software as a Medical Device (SaMD) companion UX.
Context
- Device Classification: {{device_classification_type}}
- Companion App Platform: {{companion_app_platform}}
- Critical Hardware Pairing Sequence: {{critical_pairing_steps}}
- Target Patient Dexterity Profile: {{patient_dexterity_profile}}
- Essential Safety Warning Triggers: {{safety_warning_triggers}}
- Data Syncing Frequency: {{telemetry_sync_frequency}}
Task
Build a rigorous UX onboarding and device-pairing verification checklist that ensures patients successfully set up hardware sensors, understand critical safety guardrails, and complete initial calibration without clinical supervision.
Method
- Deconstruct {{critical_pairing_steps}} into granular screen states, hardware state transitions, and timeout recovery loops.
- Assess physical-to-digital touchpoints for friction tailored to {{patient_dexterity_profile}}.
- Establish verification criteria for Bluetooth/NFC discovery states, permission prompts, and clear connection confirmations.
- Design validation checkpoints for communicating {{safety_warning_triggers}} without causing alarm fatigue or panic.
- Audit fallback UX for unboxing failures, dead hardware batteries, sensor communication drops, and pairing retries.
- Verify instructional animation clarity, tactile microcopy, and progress indicators during {{telemetry_sync_frequency}} handshakes.
- Compile a structured onboarding readiness checklist prioritized by onboarding completion risk and clinical device safety.
Constraints
- Focus squarely on the unboxing-to-first-telemetry pairing journey.
- MUST include explicit fail-state recovery checks for every step in {{critical_pairing_steps}}.
- MUST NOT rely solely on color or sound for critical hardware connection confirmations.
- Checkpoints must explicitly differentiate between user operating error, system failure, and hardware sensor defects.
Output format
- Workflow Architecture Map: Step-by-step summary of the intended onboarding flow.
- Onboarding Usability Checklist: Grouped into
Pre-Pairing Preparation,Hardware Discovery & Auth,Calibration & Baseline Setup, andFail-State & Error Recovery. - Format each item with:
Check ID,UX Target,Pass Criteria,Edge Case Trigger, andClinical Risk. - Go/No-Go Launch Criteria: 4 mandatory gate conditions for clinical onboarding release.
Self-review
- Does the checklist account for physical dexterity limitations described in {{patient_dexterity_profile}}?
- Are error handling and reconnection paths fully mapped for {{companion_app_platform}} permissions?
- Does the checklist properly enforce clear presentation of {{safety_warning_triggers}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.