> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://blueprint.ziro.health/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://blueprint.ziro.health/_mcp/server.

# Testing & Clinical Validation

Testing in health products spans multiple dimensions — from software quality to clinical efficacy. Each type of testing serves a different purpose and may be required by regulators.

## Testing Types in Health

| Type                  | What It Validates                    | Regulatory Relevance                     |
| --------------------- | ------------------------------------ | ---------------------------------------- |
| Unit testing          | Individual components work correctly | IEC 62304 software lifecycle             |
| Integration testing   | Components work together             | Required for all medical device software |
| System testing        | Full system meets requirements       | Submission evidence                      |
| Usability testing     | Users can complete tasks safely      | FDA requires for all devices             |
| Clinical testing      | Product improves health outcomes     | Required for most SaMD submissions       |
| Security testing      | System resists attacks               | HIPAA, GDPR, SOC 2                       |
| Performance testing   | System handles expected load         | Deployment requirement                   |
| Accessibility testing | System works for all abilities       | WCAG compliance, EAA                     |

## Regulatory Testing Requirements

Software as a Medical Device (SaMD) requires specific testing evidence:

**FDA (US)** :

* 510(k): Substantial equivalence testing to predicate device
* De Novo: Safety and effectiveness evidence
* PMA: Clinical trial data required
* Usability validation per IEC 62366

**EU MDR**:

* Clinical evaluation per MEDDEV 2.7/1 Rev.4
* Performance evaluation for IVDs
* Usability testing per IEC 62366-1
* Software lifecycle per IEC 62304

## Usability Validation

FDA requires usability testing with representative users performing critical tasks:

* **Formative testing**: Early iterative testing to identify issues
* **Summative validation**: Final testing to demonstrate safe use
* **Use error analysis**: Identifying potential use errors and mitigations
* **Labeling comprehension**: Can users understand instructions?

## Clinical Trials vs. Real-World Evidence

| Approach                    | When to Use                                      | Timeline     |
| --------------------------- | ------------------------------------------------ | ------------ |
| Randomized controlled trial | Regulatory submissions, high-risk devices        | 12-36 months |
| Pragmatic trial             | Real-world effectiveness, reimbursement evidence | 6-18 months  |
| Single-arm study            | Initial efficacy signal, feasibility             | 3-12 months  |
| Real-world evidence         | Post-market surveillance, payer evidence         | Ongoing      |

***

## Related Chapters

* [Launch & Go-to-Market](/product-lifecycle/launch-gtm) — Taking validated products to market
* [Regulatory Landscape](/foundations/regulatory-landscape) — Testing requirements by regulation
* [AI/ML Integration](/technical-architecture/ai-ml-integration) — Validation for AI-powered features