Skip to main content

What Problem Does This Solve?

Medical device manufacturers typically manage risk in disconnected spreadsheets. This creates three problems that grow worse as products mature:
  1. Traceability gaps: Spreadsheet cells cannot link to requirements, test cases, or risk controls in real time. Auditors must manually cross-reference documents.
  2. Stale data: When requirements change, spreadsheet risk assessments do not update. Risk evaluations drift from the actual design state.
  3. Audit burden: Generating a Design History File (DHF) risk report requires manual extraction, formatting, and reconciliation across multiple documents.
The Medical Device Safety Solution solves all three by making risk analysis a first-class activity inside Polarion.

How the Solution Works

diagram Three tools share a common data layer:
  • Polarion LiveDoc manages requirements specifications (user needs, system requirements, design requirements) and test specifications (verification and validation)
  • Nextedy Risksheet provides the spreadsheet-like editing interface for HARA, DFMEA, PFMEA, and Risk Control Plan documents with formula-driven risk calculations
  • Nextedy Powersheet displays interactive traceability matrices (RTM) and verification/validation sheets that pull live data across all document types
All three tools read and write to the same Polarion work items and link relationships. A change to a risk control in the risksheet immediately appears in the PowerSheet RTM view and in the HARA report.

What the Solution Includes

The project template provisions a complete, production-ready environment:
CategoryContents
Spaces8 organized spaces: Requirements, Design, Risks, Testing, Catalogs, RiskTemplates, Documentation, _default
Work Item Types16 types spanning requirements, risk, design, testing, and change management
Link Roles18 constrained traceability relationships enforcing ISO 14971 structure
Risk Templates4 risksheet templates: HARA, DFMEA, PFMEA, Risk Control Plan
Catalogs68 hazards (4-level IEC 60601 taxonomy) and 25 standard harms with severity
PowerSheet Configs7 configurations: Whole RTM, Component RTM, 3 verification sheets, Use Steps, Process Steps
Reports3 automated Velocity reports: ISO 14971 HARA Report, Risk Matrix, DFMEA Summary
Reference DeviceSmart Infusion Pump with 6 subsystems and 29 components as working example data

Dual Risk Analysis

The solution supports two parallel risk analysis methods that cross-reference each other:
  • HARA (ISO 14971): Risk Record-centric analysis using the P1 x P2 probability model and a 5x5 severity matrix. Three-level classification: Acceptable, Investigation, Unacceptable. Includes benefit-risk analysis for residual risks per Clause 7.2.
  • DFMEA (AIAG VDA): Failure Mode-centric analysis using Severity x Occurrence x Detection = RPN scoring. Five-level color-coded severity from Negligible (green) to Critical (red).
Both methods share the harm catalog but use different probability and detection scales. Failure modes in DFMEA link back to risk records in HARA via the analyzedIn relationship, providing cross-methodology traceability. For details, see Dual Risk Methodology: HARA and DFMEA.

Risksheet-Only Editing

Risk records and failure modes are configured as fully read-only in the standard Polarion work item form. All editing happens through Nextedy Risksheet. This design ensures:
  • Formula consistency (P1xP2 bucketing and RPN calculations are always applied)
  • Structured data entry (enumeration pickers enforce valid values)
  • Audit trail integrity (all changes flow through a single editing interface)

Compliance Evidence

The solution generates three automated reports from live Polarion data, eliminating manual DHF preparation:
  • ISO 14971 HARA Report: Complete risk assessment with chapter numbering, all custom fields, print-ready formatting
  • Risk Matrix Report: Pre/post-mitigation 5x5 risk distribution with conditional alert boxes
  • DFMEA Summary Report: Executive-level failure analysis statistics by subsystem
These reports query type:riskRecord and type:failureMode across the entire project, so they always reflect the current state of the risk analysis.