Exercise set
Medical Device Intended-Use Validation and Claim Coverage Exercises
Solved medical-device validation exercises for intended-use scenarios, user groups, environments, claim coverage, acceptance criteria and release gates.
These exercises focus on intended-use validation and claim coverage for medical devices. They cover scenario coverage, representative user groups, operating environments, claim matrix closure, acceptance criteria, validation sample balance, residual scenario gaps and release gates. They are engineering evidence exercises, not clinical guidance or regulatory advice.
Usability critical tasks and clinical/post-market evidence are handled in companion specialist exercise sets. Verification and risk scoring are separate evidence domains.
How to use these exercises
Use the set as a claim-coverage review, not as a generic validation checklist. Exercises 1 to 4 test whether intended-use scenarios, users, environments and workflow steps are covered. Exercises 5 to 11 check claim matrix closure, acceptance criteria, pass rate, evidence strength, sample balance and evidence age. Exercises 12 to 17 add residual scenario risk, simulation-to-use justification, boundary-condition coverage, claim narrowing, evidence completion and RPN. Exercise 18 combines these items into a release gate.
Before calculating, state the exact claim, intended user, intended environment, workflow boundary, device version and acceptance criterion. A validation result supports only the claim it actually tested. The engineering comment below each exercise identifies whether the correct response is more testing, a narrowed claim, a risk control, a bridge justification or release hold.
Release Evidence Notes
Intended-use validation evidence should state the claim being supported, user group, environment, scenario, workflow boundary, acceptance criterion and residual gap. A bench result can verify a requirement, but it does not automatically validate the intended use.
Claim coverage should be explicit. Each public, clinical, technical or usability claim should map to evidence strong enough for the claim scope.
The evidence package should separate scenario coverage, claim coverage and acceptance evidence. Scenario coverage asks whether the intended use was exercised. Claim coverage asks whether every claim has direct evidence or justified indirect evidence. Acceptance evidence asks whether the result passed a predefined criterion. Treating these as one percentage can hide a high-risk gap.
Engineering Boundary Notes
These calculations do not replace validation protocol design, clinical evaluation, regulatory strategy, ethics review, usability engineering process or independent quality review. They are screening exercises for evidence completeness.
The main boundary is intended-use scope. Users, environments, workflow steps, boundary conditions and device versions must match the claim. The second boundary is residual risk: an untested high-risk scenario cannot be cleared by high aggregate coverage. It should either be tested, controlled, justified with strong bridging evidence or removed from the claim.
Common Release Mistakes
- testing easy scenarios while leaving high-risk intended-use scenarios untested;
- counting users without matching target user groups;
- validating one environment and claiming another;
- accepting a claim without acceptance criteria;
- treating traceability as complete when residual gaps remain unresolved.
Another common mistake is confusing verification with validation. A bench test may prove a technical requirement, but intended-use validation must show that the device, user, environment and workflow support the claim. If those elements are missing, the claim should be narrowed or the validation plan expanded.
Do not use claim narrowing as a paperwork shortcut. Narrowing is acceptable only when labeling, training, risk controls, supported environments and user expectations all match the narrower claim. Otherwise the gap remains a release risk.
Scenario Map
| Scenario | Exercises | Primary check | Engineering decision |
|---|---|---|---|
| Intended-use scope | 1, 2, 3, 4, 5 | scenario, user, environment and workflow coverage | Decide whether the validation plan matches the claim. |
| Claim evidence | 6, 7, 8, 9, 10, 11 | claim matrix, acceptance criteria, evidence strength and traceability | Decide whether claims can be supported. |
| Gap closure | 12, 13, 14, 15, 16, 17 | residual gaps, sample balance, uncertainty and release evidence | Decide whether the claim should narrow or testing continue. |
| Release gate | 18 | all-of intended-use release | Decide whether intended-use validation can close. |
Exercise 1: Intended-Use Scenario Coverage
A validation plan defines 18 intended-use scenarios. Testing covers 15. Compute coverage.
Solution
Engineering Comment
Uncovered scenarios may be acceptable only if the claim is narrowed or a documented rationale is approved.
Plausibility Check
Three uncovered scenarios out of eighteen leaves coverage below ninety percent.
Exercise 2: Representative User Coverage
A study requires at least 12 novice users and 12 trained users. It includes 10 novice users and 14 trained users. Which group fails?
Solution
Novice users fail:
Trained users pass:
Engineering Comment
Overall user count is not enough if one target group is underrepresented.
Plausibility Check
The total is 24 users, but coverage still fails because distribution matters.
Exercise 3: Environment Coverage
The intended use includes home, clinic, ambulance and ward environments. Validation covers home, clinic and ward. Compute environment coverage.
Solution
Engineering Comment
The ambulance environment should be tested or removed from the claim.
Plausibility Check
One missing environment out of four gives three-quarter coverage.
Exercise 4: Workflow Step Coverage
A use workflow has 22 required steps. Validation directly exercises 19 steps. Compute direct workflow coverage.
Solution
Engineering Comment
Untested steps may include setup, cleaning, calibration or shutdown tasks that still affect safety.
Plausibility Check
Missing three of twenty-two steps leaves coverage below ninety percent.
Exercise 5: Claim Matrix Closure
A claim matrix lists 32 validation claims. Twenty-six have direct evidence, four have indirect rationale and two are open. Compute direct-evidence fraction.
Solution
Engineering Comment
Indirect rationale may be acceptable for low-risk claims, but open claims block broad release.
Plausibility Check
Twenty-six of thirty-two is a little above eighty percent.
Exercise 6: Acceptance Criteria Traceability
There are 18 validation scenarios. Sixteen have predefined acceptance criteria. Compute traceability.
Solution
Engineering Comment
Acceptance criteria defined after seeing results weaken validation credibility.
Plausibility Check
Two missing criteria out of eighteen leaves just under ninety percent.
Exercise 7: Scenario Pass Rate
Fifteen covered scenarios are tested and fourteen pass. Compute pass rate.
Solution
Engineering Comment
Pass rate is not enough if the failed scenario is high risk or central to the intended use.
Plausibility Check
One failure among fifteen scenarios gives a pass rate above ninety percent.
Exercise 8: Claim Strength Score
Assign 2 points for direct evidence, 1 point for indirect rationale and 0 for open claims. With 26 direct, 4 indirect and 2 open claims, compute score relative to maximum.
Solution
Actual score:
Maximum:
Fraction:
Engineering Comment
This score helps compare evidence maturity but does not replace risk-based review of the open claims.
Plausibility Check
Most claims have direct evidence, so the score is high but not complete.
Exercise 9: Claim Gap Count
A release rule allows no more than one open validation claim. The matrix has two open claims. Compute excess open claims.
Solution
Engineering Comment
The release decision should hold or narrow the claim until the excess gap is closed.
Plausibility Check
Two open claims exceed a one-claim allowance by one.
Exercise 10: Validation Sample Balance
Validation includes 24 users: 10 novice and 14 trained. Target split is 50/50. Compute novice fraction and deviation from target.
Solution
Deviation:
Engineering Comment
A skewed sample can overstate performance if trained users find the device easier to use.
Plausibility Check
Ten out of twenty-four is less than half.
Exercise 11: Evidence Age Check
Validation evidence is 30 months old. The release policy requires review if evidence is older than 24 months after a major software change. Compute age exceedance.
Solution
Engineering Comment
Old evidence may still be usable, but the change impact must be justified.
Plausibility Check
Thirty months is six months beyond a two-year threshold.
Exercise 12: Residual Scenario Risk Count
Three untested scenarios remain. Two are low risk and one is high risk. A release rule allows only low-risk residual gaps. Does the release pass?
Solution
The rule fails because one residual gap is high risk:
Engineering Comment
Risk category matters more than the raw number of gaps.
Plausibility Check
Any high-risk untested scenario violates the stated rule.
Exercise 13: Simulation-to-Use Justification Fraction
A validation plan uses simulation for 8 scenarios. Six have justification linking simulation to real use. Compute justification fraction.
Solution
Engineering Comment
Simulation evidence should be tied to real users, environments or physiological boundary conditions.
Plausibility Check
Two missing justifications out of eight leaves three-quarter coverage.
Exercise 14: Boundary-Condition Coverage
Five boundary conditions are defined: low battery, high temperature, low light, high motion and weak network. Four are included in validation. Compute coverage.
Solution
Engineering Comment
Boundary conditions often reveal failures absent in nominal workflow tests.
Plausibility Check
One missing condition out of five gives eighty percent.
Exercise 15: Claim Narrowing
A broad claim covers 18 scenarios. If the claim is narrowed by removing 3 untested scenarios, and 15 remaining scenarios are tested, compute narrowed coverage.
Solution
New scenario count:
Coverage:
Engineering Comment
Narrowing a claim can be valid if labeling, training and risk controls match the narrower use.
Plausibility Check
If all remaining scenarios are tested, narrowed coverage is complete.
Exercise 16: Validation Evidence Completion
The release package requires intended-use statement, scenario list, user groups, environments, acceptance criteria, raw results, deviations, residual gaps, claim matrix and approver. Eight of ten are complete. Compute completion.
Solution
Engineering Comment
Missing residual gaps or claim matrix evidence should block release.
Plausibility Check
Eight of ten is exactly eighty percent.
Exercise 17: Claim Coverage RPN
An unvalidated high-motion scenario has severity 8, occurrence 3 and detection 5. Compute RPN.
Solution
Engineering Comment
The RPN supports either adding the scenario to validation or narrowing the claim.
Plausibility Check
Moderate-high ratings produce a three-digit score.
Exercise 18: Intended-Use Release Gate
A release gate requires scenario coverage above 95\%, all required user groups passing, environment coverage 100\%, no high-risk residual scenario and evidence completion above 90\%. Current values are 83.3\%, novice group fail, 75\%, one high-risk residual scenario and 80\%. Decide release status.
Solution
All required conditions fail:
Release status:
Engineering Comment
The correct decision is to hold intended-use release or narrow the claim.
Plausibility Check
Multiple independent coverage gaps make release technically unjustified.
Validation Package Checklist
- Intended-use scenarios, users, environments and workflows match the claim.
- Acceptance criteria are predefined before validation execution.
- Claim matrix entries are tied to direct evidence, indirect rationale or open gaps.
- Residual gaps are risk-ranked and either closed or reflected in a narrowed claim.
- Boundary conditions and simulated scenarios include justification to real use.
- Evidence age and device version are reviewed before release.
- Release status states accept, narrow claim, bridge evidence, test more or hold.