PCEI cheat sheet

Clinical engineering professional bodies publish codes of ethics covering patient safety primacy, competence limits, conflict-of-interest disclosure, and confidentiality of patient and proprietary data.

The four core ethical principles from biomedical ethics are beneficence, non-maleficence, autonomy, and justice; clinical engineers apply them to device selection, maintenance prioritization, and data handling.

Competence boundary rule: a CE who lacks documented training on a device class must escalate to a qualified colleague or the manufacturer rather than perform service, even if the task appears routine.

Conflict of interest: any gift, consulting fee, vendor-funded travel, or equity holding that could influence a procurement or evaluation decision must be disclosed in writing to the employer.

Whistleblower protection in most jurisdictions covers good-faith reports of device safety hazards or regulatory violations made to an internal compliance channel or an external regulator.

Accepting a manufacturer's free training is generally permissible; accepting it in exchange for an implied purchase commitment or exclusivity is not, and should be documented as a conflict.

Continuing education: many certifying bodies require recertification credits, and lapses in credential maintenance can disqualify a CE from signing certain inspection or compliance records.

Confidentiality extends to device-generated clinical data; discussing a specific patient's device alarm or therapy settings outside a need-to-know context breaches both ethics codes and privacy law.

Lifecycle stages: needs assessment, capital planning, procurement, acceptance testing, deployment, preventive maintenance, corrective maintenance, and decommissioning/disposal.

Incoming inspection and acceptance testing should verify the device against the purchase specification, confirm safety testing results, and record serial number, software version, and accessories before clinical use.

Preventive maintenance intervals typically follow manufacturer recommendations; deviation requires documented risk justification approved by the department head.

A computerized maintenance management system (CMMS) inventory record should include unique asset ID, manufacturer, model, serial number, location, acquisition date, warranty end, PM schedule, and service history.

Replacement or retirement decisions commonly use life-cycle cost analysis comparing cumulative maintenance cost against replacement cost, plus parts-availability risk and clinical demand.

Electrical safety testing for patient-connected equipment typically includes protective earth resistance, chassis leakage current, and patient leakage current, compared against IEC 60601-1 limits.

Decommissioning must include data sanitization of any stored protected health information, removal from the CMMS or archival of its record, and compliant disposal of batteries and hazardous components.

Uptime and downtime metrics: availability = (scheduled time - downtime) / scheduled time; tracking mean time between failures (MTBF) and mean time to repair (MTTR) supports reliability decisions.

US FDA device classification runs Class I (low risk, general controls), Class II (moderate risk, general plus special controls, often 510(k)), and Class III (high risk, premarket approval).

A 510(k) submission demonstrates substantial equivalence to a legally marketed predicate device; a De Novo request creates a new Class I or II pathway when no predicate exists.

The EU Medical Device Regulation (MDR 2017/745) uses risk classes I, IIa, IIb, and III, requires a CE marking via a notified body for most classes, and mandates a unique device identification (UDI) and post-market surveillance.

IEC 60601-1 is the general safety standard for medical electrical equipment; IEC 60601-1-2 covers electromagnetic compatibility, and collateral standards address specific modalities.

ISO 13485 specifies quality management system requirements for device manufacturers; ISO 14971 defines the risk management process for medical devices.

IEC 62304 defines software lifecycle processes with safety classes A (no injury possible), B (non-serious injury possible), and C (death or serious injury possible).

ISO 62366 (IEC 62366-1) governs usability engineering; use-related hazards must be identified and mitigated in the design process.

Post-market obligations include medical device reporting (MDR in the US for deaths, serious injuries, and certain malfunctions), recalls, and field safety corrective actions in the EU.

ISO 14971 risk process: identify hazards, estimate and evaluate risk, control risk, evaluate residual risk, and monitor in production and post-production.

Risk acceptability is evaluated as severity times probability of occurrence of harm; risk controls follow a hierarchy: inherently safe design, protective measures, then information for safety.

Root cause analysis (RCA) uses a structured timeline, causal factor charting, and the 'five whys' or fault tree analysis to move from proximate cause to system cause.

Failure mode and effects analysis (FMEA) prioritizes hazards by risk priority number (RPN) = severity x occurrence x detection; higher RPN drives mitigation priority.

Incident investigation must preserve evidence: quarantine the device, retain accessories and disposables, record alarm logs and error codes, and document the clinical sequence before any repair.

Human factors contribute to a large share of device incidents; use error is a design and system issue, not solely an operator failure, and should be analyzed as such.

Electrical safety limits under IEC 60601-1 include patient leakage current limits that are far stricter for cardiac-connected (type CF) applied parts than for body-connected (type B) parts.

Adverse event reporting timelines: in the US, a device-related death or serious injury must be reported to FDA within the timeframe set by the MDR regulation, commonly 30 calendar days, or 5 days if a public health threat exists.

HL7 v2 messaging remains the dominant clinical interface standard; HL7 FHIR uses RESTful resources and JSON/XML for modern interoperability.

DICOM governs medical imaging storage and transfer, including modality worklist, image objects, and the DICOM data dictionary for attributes.

IEC 80001-1 addresses risk management for IT networks incorporating medical devices; the responsible organization must assess network risk before connecting devices.

FDA premarket cybersecurity expectations include a threat model, security risk assessment, software bill of materials (SBOM), and coordinated vulnerability disclosure policy.

Core device hardening controls: change default credentials, disable unused services and ports, segment clinical networks, patch on a risk-based schedule, and maintain an asset inventory.

Network segmentation separates clinical device VLANs from enterprise and guest networks; unidirectional gateways or firewalls limit lateral movement from compromised IT systems.

Medical device integration engines translate between HL7, FHIR, and proprietary protocols; interface testing must verify message integrity, timing, and error handling before go-live.

A device inventory for cybersecurity should capture IP address, MAC address, OS and firmware version, open ports, and known vulnerabilities, refreshed on a defined cadence.

Project management phases: initiation, planning, execution, monitoring and control, and closure; each phase produces defined deliverables and gate approvals.

Critical path method identifies the longest dependent sequence of tasks; any delay on the critical path delays the project end date unless the schedule is compressed.

Earned value metrics: cost variance (CV) = earned value - actual cost; schedule variance (SV) = earned value - planned value; negative values indicate overrun or delay.

Stakeholder analysis maps influence against interest; high-influence, high-interest stakeholders require active management and regular direct communication.

Change control: any scope, schedule, or budget change should be documented, impact-assessed, and approved by the project sponsor before implementation.

A business case for a capital device purchase typically includes clinical need, volume projections, total cost of ownership, reimbursement or revenue impact, and risk of inaction.

Communication plans specify audience, message content, channel, frequency, and owner; clinical staff need plain-language explanations of device changes and downtime.

Team leadership in clinical engineering uses cross-functional collaboration with nursing, infection prevention, IT, and biomedical vendors; documented roles and escalation paths reduce handoff error.