Skip to content
Compliance & Traceability

ISO 13485 Test Data Requirements with TofuPilot

Learn how to meet ISO 13485 test documentation requirements for medical devices using TofuPilot's structured data and traceability features.

JJulien Buteau
advanced11 min readMarch 14, 2026

ISO 13485 Test Data Requirements with TofuPilot

ISO 13485 is the quality management standard for medical device manufacturers. It requires rigorous control of production processes, including complete test records for every device produced. TofuPilot provides the structured, traceable test data storage that ISO 13485 demands.

What ISO 13485 Requires for Test Data

ISO 13485 Section 7.5.1 (Control of Production and Service Provision) and Section 8.2.4 (Monitoring and Measurement of Product) require:

RequirementISO 13485 clauseWhat it means for testing
Process validation7.5.2Prove your test process produces consistent results
Identification and traceability7.5.3Link every test result to a specific device serial number
Monitoring and measurement8.2.4Define acceptance criteria and record conformity evidence
Control of records4.2.5Maintain test records, ensure they're retrievable and protected
Nonconforming product8.3Document what happens to devices that fail testing

How TofuPilot Maps to ISO 13485

Traceability (7.5.3)

Every test run in TofuPilot is linked to a unit serial number. Search by serial to see the complete test history of any device.

medical_device_test.py
from tofupilot import TofuPilotClient

client = TofuPilotClient()

# Every run ties to a unique device identifier (UDI)
client.create_run(
    procedure_id="FINAL-INSPECTION-IEC60601",
    unit_under_test={
        "serial_number": "MD-2025-00421",  # UDI or serial
        "part_number": "PULSE-OX-V3",
    },
    run_passed=True,
    steps=[{
        "name": "Electrical Safety",
        "step_type": "measurement",
        "status": True,
        "measurements": [
            {"name": "earth_leakage_ua", "value": 287, "unit": "uA", "limit_high": 500},
            {"name": "patient_leakage_ua", "value": 8.3, "unit": "uA", "limit_high": 10},
            {"name": "insulation_resistance_mohm", "value": 520, "unit": "Mohm", "limit_low": 100},
        ],
    }, {
        "name": "Functional Performance",
        "step_type": "measurement",
        "status": True,
        "measurements": [
            {"name": "spo2_accuracy_pct", "value": 1.2, "unit": "%", "limit_high": 2.0},
            {"name": "heart_rate_accuracy_bpm", "value": 1.5, "unit": "BPM", "limit_high": 3.0},
        ],
    }],
)

Acceptance Criteria (8.2.4)

ISO 13485 requires documented acceptance criteria for every inspection and test. In TofuPilot, limits on measurements serve as your acceptance criteria.

MeasurementAcceptance criteriaStandard reference
Earth leakage< 500 uAIEC 60601-1
Patient leakage< 10 uA (Type BF)IEC 60601-1
Insulation resistance> 100 MohmIEC 60601-1
SpO2 accuracy< 2% ARMSISO 80601-2-61

These limits are defined in the test procedure and enforced by TofuPilot on every run.

Control of Records (4.2.5)

ISO 13485 requires records to be:

RequirementHow TofuPilot meets it
LegibleStructured data, not handwritten
Readily identifiableSearchable by serial, procedure, date
RetrievableAPI and dashboard access
Protected from damageCloud-hosted, backed up
Protected from lossRedundant storage
Retained for defined periodData retention per your QMS policy

Nonconforming Product (8.3)

When a device fails testing, ISO 13485 requires documentation of:

  1. The nature of the nonconformity (which measurement failed)
  2. Actions taken (rework, scrap, use-as-is disposition)
  3. Re-inspection results after rework

TofuPilot captures #1 automatically (failed measurements with values and limits). For #2 and #3, the retest flow creates additional run records linked to the same serial number.

retest_after_rework.py
# Device failed initial test
# After rework, retest and record
client.create_run(
    procedure_id="FINAL-INSPECTION-IEC60601-RETEST",
    unit_under_test={
        "serial_number": "MD-2025-00421",
    },
    run_passed=True,
    steps=[{
        "name": "Post-Rework Electrical Safety",
        "step_type": "measurement",
        "status": True,
        "measurements": [
            {"name": "earth_leakage_ua", "value": 312, "unit": "uA", "limit_high": 500},
            {"name": "patient_leakage_ua", "value": 7.1, "unit": "uA", "limit_high": 10},
        ],
    }],
)

The device now has two test records in TofuPilot: the initial failure and the post-rework pass. Both are traceable, timestamped, and immutable.

Device History Record (DHR)

The DHR is a compilation of records that documents the production history of a finished device. Test records are a key component.

TofuPilot contributes to the DHR by providing:

  • All test procedures executed on the device
  • All measurement results with pass/fail status
  • Dates and times of each test
  • Which station/tester ran each test
  • Any retests after rework

Pull a device's complete test history by serial number for DHR compilation.

Audit Readiness

When an auditor asks for test records, you need to produce them quickly and completely.

Common audit requests and how to answer them with TofuPilot:

Auditor requestTofuPilot response
"Show me test records for lot 2025-03"Filter by date range, export all runs
"What's the acceptance criteria for leakage testing?"Show measurement limits in the procedure
"Show me all devices that failed and were reworked"Filter for failed runs, check retests by serial
"Prove your test equipment is calibrated"Station metadata with calibration dates
"What's your first-pass yield for this product?"Procedure dashboard FPY metric

IEC 60601 Electrical Safety Tests

Medical devices connected to patients require IEC 60601-1 electrical safety testing. Key measurements:

TestType BF limitType CF limit
Earth leakage (normal)500 uA500 uA
Earth leakage (single fault)1000 uA1000 uA
Patient leakage (normal)100 uA10 uA
Patient leakage (single fault)500 uA50 uA

Log all of these in TofuPilot with limits matching your device classification. The structured records serve as evidence of conformity for regulatory submissions.

Software Validation

If you're using TofuPilot as part of your quality system, ISO 13485 Section 7.5.2.1 requires validation of software used in production and quality management. Work with your quality team to document TofuPilot's role in your QMS and include it in your software validation plan.

More Guides

Put this guide into practice