I85PREP
⌘ K
PCEI study materials
PCEI study resources

PCEI: Regulatory Compliance and Standards

PCEI · Work through your exam, one topic at a time.

All guide sections

Regulatory Compliance and Standards

What this domain tests

This domain tests whether you can map a device or a hospital process to the correct regulatory pathway and standard, and recognize when a change triggers a new submission or reporting obligation. Key sources include FDA 21 CFR Part 820 (now aligned with ISO 13485 through the Quality Management System Regulation), 510(k)/PMA/De Novo pathways, EU MDR 2017/745, IEC 60601-1 and its collateral standards, ISO 14971, ISO 13485, IEC 62304, IEC 62366-1, UDI rules, and the FDA Safe Medical Devices Act reporting duties that fall on user facilities.

Core rules

  • Premarket pathway: Class I low-risk devices are generally exempt; Class II usually require 510(k) with substantial equivalence; Class III require PMA. The EU uses MDR classification rules and CE marking, which is not interchangeable with FDA clearance.
  • Quality system: ISO 13485 certification supports but does not replace FDA establishment registration and device listing.
  • Change control: a design, software, or labeling change may require a new 510(k) if it significantly affects safety or effectiveness; document the assessment.
  • Hospital reporting: user facilities must report device-related deaths to FDA and the manufacturer, and serious injuries to the manufacturer (and FDA if the manufacturer is unknown), within the required timeframes.
  • Standards hierarchy: IEC 60601-1 general standard, collateral standards (e.g., 60601-1-2 EMC), and particular standards (e.g., 60601-2-24 infusion pumps).

Worked example

A manufacturer adds a new alarm algorithm to an already-cleared monitor. Reasoning: assess whether the change affects safety or effectiveness; if it does, a new 510(k) is likely needed unless the change falls within FDA's guidance for device software functions. Update risk analysis (ISO 14971), verify software under IEC 62304, and validate usability under IEC 62366-1. Document the decision; “it's just software” is not a regulatory rationale.

Traps that cost marks

  • Assuming CE marking satisfies FDA requirements.
  • Confusing ISO 13485 certification with product approval.
  • Missing the user-facility MedWatch reporting duty.
  • Ignoring UDI and labeling changes during procurement.