Allied Health & Imaging · Independent exam preparation
CCE Oral Examination: Clinical Engineering Judgment Guide Study Guide
Practise technology selection, service, safety and leadership decisions for the advanced CCE oral pathway through 60 focused concepts and original scenario drills.
By CertMedbry · Updated 30 October 2026
Build defensible decisions about equipment investment, maintenance, connected systems and patient safety, then explain the evidence, tradeoffs and follow-up that make those decisions credible. This selective 60-concept guide addresses the U.S. CCE pathway under the HTCC Certification Handbook—2026 Virtual Edition and the eight work categories in the 2025 ACCE Body of Knowledge. The complete official BOK responsibilities remain the full study scope. Practise stating assumptions, identifying immediate risks, comparing alternatives and assigning measurable follow-up.
Try 20 free practice questionsWhat is the exam format?
Check the question types, timing and outline before planning your revision.
Which certification pathway does this guide address?
This guide selects the U.S. pathway to the advanced Certified Clinical Engineer credential. The 2026 handbook permits candidates meeting CCE education and experience requirements to advance to the CCE Oral Examination after passing the ACE written examination while remaining in good standing. ACE and Clinical Technology Professional are separate credentials awarded through written assessment; neither should be substituted for CCE.
What is verified about the CCE oral examination format?
The CCE Oral Examination is a structured, scenario-based virtual assessment administered by the HTCC Board of Examiners. Candidates respond to standardized cases assessing analytical reasoning, professional judgment, leadership and communication. A qualified panel conducts and scores the examination, and oral sessions are recorded. The handbook does not specify an oral scenario count, duration, scored/pretest breakdown or adaptive selection method.
What are the preceding written examination’s question count and duration?
The handbook describes approximately 150 multiple-choice questions, including scored and unscored pretest items, with up to four hours allowed. Each question has four response options and one correct answer. Separate scored and pretest counts are not stated. Question order is randomized; randomization does not establish computerized adaptive testing. These written-examination specifications are not the specifications of the CCE oral examination.
Which outline and effective date govern this guide?
The HTCC Certification Handbook—2026 Virtual Edition is effective January 1, 2026 and supersedes previous editions. It references the 2025 ACCE Body of Knowledge Survey Final Report for examination scope. The handbook and official certification page were current on October 30, 2026. The handbook filename does not establish a separate effective or revision date.
HTCC Certification Handbook—2026 Virtual Edition · 2025 ACCE Body of Knowledge Survey Final Report
Are numerical examination domain weights published?
No fixed numerical examination-category weights are established by the handbook and BOK evidence. The BOK percentages describe respondents’ work time and must not be treated as examination weights. Coverage here is an editorial selection emphasizing technology management and service delivery while including every official domain: 15, 11, 7, 8, 7, 5, 3 and 4 concepts respectively in this guide’s domain order.
2025 ACCE Body of Knowledge Survey Final Report · HTCC Certification Handbook—2026 Virtual Edition
How is virtual delivery verified, and is a passing score published?
The handbook specifies secure virtual delivery with identity verification, a browser-locked platform, live and AI-based remote proctoring, and continuous monitoring. Candidates complete a readiness test using their intended equipment and environment. The handbook does not establish a numerical passing score for the oral examination. The 20 MCQs here are independent learning exercises and provide no pass prediction.
How do Canadian, international and historical written pathways differ?
ACCE supports U.S. and Canadian Boards and links a separate Canadian handbook; this guide does not establish that pathway’s eligibility or administration rules. The official page describes ACE and CTP as new 2026 offerings for U.S./international applicants, while the handbook calls them U.S.-only, so international applicability requires clarification from HTCC. The page also mentions people who previously passed the CCE written examination; the current handbook names ACE as the preceding written stage for CCE progression.
ACCE: Get Certified · HTCC Certification Handbook—2026 Virtual Edition
How should the supporting technical sources be applied?
The BOK establishes scope, while WHO management resources, FDA technical guidance, AHRQ safety methods and ACCE ethics support particular principles. FDA medical device user-facility reporting rules discussed here concern the United States. The FDA human factors guidance identifies an August 3, 2026 revision. Older WHO resources support stable management principles and are not alternative examination outlines.
2025 ACCE Body of Knowledge Survey Final Report · FDA: Medical Device Reporting—How to Report Medical Device Problems · FDA: Applying Human Factors and Usability Engineering to Medical Devices
CCE is HTCC’s advanced clinical engineering credential. Its structured oral examination evaluates analytical reasoning, professional judgment, leadership and communication after the preceding ACE written examination. These independent learning materials support that reasoning; the MCQs are knowledge drills, not a reproduction of the oral assessment.
Outline used: HTCC Certification Handbook—2026 Virtual Edition, effective January 1, 2026; current handbook linked by ACCE on October 12, 2026, with the 2025 ACCE Body of Knowledge. The workbook label Certified Clinical Engineer (CCE) names the advanced credential. The handbook calls its advanced assessment the CCE Oral Examination and identifies passage of the ACE written examination as the preceding examination stage. The assigned slug is preserved for this CCE pathway.
60 key concepts: understand, apply and avoid the traps
Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.
Technology Managementnot stated
1.How does a needs assessment prevent an unsuitable technology purchase?
A needs assessment starts with the clinical service gap, intended users, workload and operating environment before selecting a device. It distinguishes a missing capability from a problem caused by workflow, access or training. The resulting requirements should connect measurable performance to available infrastructure, staffing and support. The discriminating question is whether the proposed technology can deliver the needed service reliably in the actual setting, rather than merely offering impressive specifications.
Apply it
A clinic requests a second analyzer because results are delayed. Map specimen arrival, processing capacity and staffing first. If most delays occur before samples reach the analyzer, address that bottleneck before recommending another purchase.
Common pitfall: Treating a department’s preferred model as the requirement skips the service problem and can commit capital without increasing usable capacity or improving access.
2.What makes a procurement specification objectively testable?
A testable specification states the required function, operating conditions and evidence that will demonstrate compliance. It separates mandatory safety or compatibility requirements from preferences that may be traded against cost. Performance claims should include relevant accessories, interfaces and environmental conditions so bidders address the same need. Selection becomes defensible when evaluators can trace each requirement to an operational purpose and later confirm it during acceptance, using agreed criteria rather than subjective impressions.
Apply it
A hospital needs portable monitors for transport. Specify required monitoring functions, compatible accessories, transport conditions and demonstrated battery performance under a defined workload, then require bidders to show compliance using the same evaluation conditions.
Common pitfall: Copying a vendor brochure can favor one product while leaving essential operational requirements untested, especially when a feature’s presence does not establish adequate performance.
3.How should a vendor comparison handle mandatory requirements and preferences?
Vendor evaluation should first determine whether each offer satisfies essential requirements, then compare acceptable offers using transparent criteria such as lifecycle cost, support, usability and integration burden. A weighted preference score cannot compensate for failure of a mandatory requirement. Document the evidence behind ratings and involve relevant clinical, engineering and purchasing stakeholders. This approach makes a close decision explainable and reduces the influence of demonstrations, familiarity or unsupported marketing claims on procurement.
Apply it
Two infusion systems receive similar overall evaluation scores, but only one supports the hospital’s required interface. Confirm whether that interface is mandatory and demonstrated before comparing negotiable preferences such as cart design or display layout.
Common pitfall: Allowing a high convenience score to offset an unmet essential requirement produces an attractive total score for a device that cannot perform the required service.
4.How does total ownership cost change an equipment comparison?
Total ownership cost includes acquisition and the resources needed to install, operate, support and eventually retire equipment over a defined period. Relevant differences can include consumables, software, maintenance, utilities, training and disposal. Comparisons require the same service output, time horizon and accounting assumptions. A lower purchase price is meaningful only after recurring costs and required infrastructure are considered; a self-contained estimate should state whether discounting, residual value and downtime costs are included.
Apply it
For equal five-year service, system A costs $40,000 plus $12,000 annually; system B costs $60,000 plus $6,000 annually. Ignoring discounting and residual value, compare $100,000 with $90,000 before assessing nonfinancial differences.
Common pitfall: Comparing one device’s purchase price with another device’s full operating cost mixes accounting boundaries and can reverse an otherwise sound decision about affordability.
WHO: Procurement process resource guide · WHO: Health technology management, section 3.4
5.When is replacement more defensible than continued repair?
Replacement decisions combine clinical suitability, reliability, supportability, safety and lifecycle economics. Age can trigger review, but it does not alone establish that equipment is unsuitable. Increasing failures, unavailable parts, unsupported software or an inability to meet current clinical needs may change the balance even when repair remains technically possible. Compare realistic alternatives over a common planning period and identify the risks that continued operation would require the organization to control.
Apply it
An older ventilator still passes testing, but its essential replacement parts are no longer available. Evaluate expected service disruption, backup capacity and replacement lead time rather than waiting for an unrepairable failure to force an urgent purchase.
Common pitfall: Using age alone can retire reliable equipment prematurely, while using the latest repair invoice alone can conceal loss of support and unacceptable service vulnerability.
WHO: Health technology management, section 3.4 · 2025 ACCE Body of Knowledge Survey Final Report
6.How should a return-on-investment claim be tested?
A useful investment analysis connects incremental costs with benefits that the organization can actually realize. State the baseline, time horizon, utilization and whether benefits represent cash savings, avoided costs or additional capacity. Simple payback divides initial investment by constant annual net cash benefit, but it does not account for the time value of money or benefits after payback. Test uncertain utilization assumptions because nominal capacity does not guarantee demand, staffing or reimbursement.
Apply it
A $120,000 upgrade is expected to save $30,000 annually after added support costs. Its simple payback is four years. Recalculate the result if only half the projected workload shifts to the upgraded system.
Common pitfall: Counting gross revenue as net benefit ignores operating costs and demand constraints; calling released staff time a cash saving also requires a realizable staffing change.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Procurement process resource guide
7.Which factors should drive capital replacement priorities?
Capital prioritization compares the consequences of deferring each request, rather than treating all old equipment or vocal departments equally. Useful factors include patient-care impact, failure history, support status, capacity constraints, strategic fit and available alternatives. Document how criteria are applied and distinguish urgent risk reduction from discretionary improvement. A defensible recommendation explains the service consequence of delay and the evidence supporting it, including uncertainty and temporary measures when funding is limited.
Apply it
A committee can fund either cosmetic workstation improvements or replacement of a frequently unavailable imaging component with limited backup. Present downtime, service impact, support evidence and interim options so the committee can compare consequences explicitly.
Common pitfall: Ranking requests solely by purchase age or departmental influence obscures actual consequences of deferral and gives weak evidence the same status as demonstrated service risk.
2025 ACCE Body of Knowledge Survey Final Report · ACCE Code of Ethics
8.How does a technology roadmap connect strategy with implementation?
A technology roadmap translates future clinical service goals into sequenced capability, infrastructure and support decisions. It should identify dependencies such as network readiness, facilities work, workforce skills and replacement timing. The roadmap is useful when it distinguishes committed work from assumptions requiring review. Rather than listing desired purchases, it shows how each investment enables a service objective and how changes in demand, support availability or funding would alter the sequence.
Apply it
A hospital plans remote monitoring next year. Sequence identity management, network assessment, interface validation, training and support arrangements before deployment, and tie each milestone to the clinical service expected to become available when that milestone is complete.
Common pitfall: A shopping list with dates is insufficient when infrastructure and staffing dependencies remain unresolved; purchasing early can leave equipment idle or increase avoidable integration expense.
9.How should a technology project define completion?
Project completion should be defined by agreed deliverables and acceptance evidence, including operational readiness, rather than shipment or installation alone. Establish scope, accountable owners, dependencies and measurable completion criteria before execution. Clinical users, engineering, IT and facilities may each own different conditions for release. A project can be physically installed yet incomplete if interfaces, support documentation, training or continuity arrangements remain unverified, so closure should reflect the service being ready for intended use.
Apply it
A monitoring installation is mounted and powered, but alarm routing has not been tested. Keep operational release open until the responsible teams demonstrate routing, document results and confirm that users and support staff can manage failures.
Common pitfall: Equating delivery with completion hides unfinished work and can transfer unresolved safety, integration or support problems to clinical staff without an accountable resolution owner.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Procurement process resource guide
10.When should a project change trigger formal reassessment?
A proposed change warrants reassessment when it affects requirements, interfaces, cost, schedule, support or risk controls. Compare the requested benefit with its downstream effects before approving implementation. Record who authorizes the change, which tests or documents must be updated and whether prior acceptance evidence remains applicable. This protects the project baseline without making it inflexible: the key distinction is between a harmless administrative correction and a change that alters intended performance or operational readiness.
Apply it
During procurement, a department asks to add wireless connectivity to a previously standalone device. Reassess network compatibility, cybersecurity responsibilities, integration testing and support costs before accepting the change as an equivalent substitution within the approved project.
Common pitfall: Calling a change minor because its purchase-price effect is small overlooks interface, workflow and validation consequences that may be much more significant operationally.
2025 ACCE Body of Knowledge Survey Final Report · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
11.What must device integration planning establish before purchase?
Integration planning defines which information or control functions cross an interface, how they will be used and who is responsible for each component. Compatibility includes data meaning, timing, supported configurations and behavior during faults, not simply a matching connector or protocol name. Establish interface documentation and test responsibilities before purchase. The decisive cue is whether the combined system can support its intended clinical function safely under both expected conditions and foreseeable communication failures.
Apply it
A monitor exports observations to the record system. Before purchasing, require agreement on patient association, units, update timing, failure indication and end-to-end testing responsibilities across the device, middleware and record-system suppliers and their support teams.
Common pitfall: Assuming that two products using the same communication standard are automatically interoperable ignores optional implementations, data semantics and failure behavior in the assembled clinical system.
12.Why should acceptance evidence be agreed before contracting?
Acceptance planning converts important requirements into evidence that the purchaser and supplier agree will demonstrate satisfactory delivery. Specify the configuration, test conditions, responsibilities and handling of unresolved deficiencies before contractual leverage is reduced. Commercial milestones and operational release may require different evidence. The principle is to make expected performance observable in the intended setting, while avoiding a late dispute about whether installation, a factory certificate or a local demonstration fulfills the purchase obligation.
Apply it
A new imaging workstation must exchange studies with an existing archive. Include local exchange testing, supported configuration documentation and deficiency resolution in the acceptance plan before agreeing that delivery alone triggers final contractual acceptance and payment.
Common pitfall: Adding acceptance criteria after equipment arrives can create disputes and leave essential integration work outside the supplier’s agreed obligations or the project’s budget.
WHO: Procurement process resource guide · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
13.When does fleet standardization improve value?
Fleet standardization can reduce variation in accessories, training, spare parts and service procedures, but its value depends on meeting the needs of each clinical setting. Compare these operational benefits with dependence on one supplier and the consequences of a common product problem. Standardization should follow a requirements assessment rather than replace it. A defensible decision identifies where one configuration is suitable and where a justified exception prevents compromised clinical function or excessive support burden.
Apply it
Three wards can use a common monitor platform, while a transport team requires different environmental and mobility capabilities. Standardize shared functions and support where appropriate, then document the transport exception against its distinct clinical and operational requirements.
Common pitfall: Forcing identical equipment into every setting can create workarounds, while allowing unrestricted variation can multiply training and service costs without a clinical benefit.
WHO: Procurement process resource guide · 2025 ACCE Body of Knowledge Survey Final Report
14.How should usability influence product selection?
Usability assessment examines how intended users perform important tasks in the actual use context. A feature-rich device may still create risk if controls, displays or workflow conflict with user capabilities and environmental demands. Include representative users and realistic tasks rather than relying only on expert demonstrations. Selection should consider observed errors, confusion and recovery needs, especially for tasks with serious consequences, while distinguishing correctable training gaps from interface problems that persist despite reasonable preparation.
Apply it
During a device trial, experienced nurses repeatedly confuse two adjacent operating modes under realistic interruptions. Record the task failures and compare interface alternatives before concluding that a longer introductory lecture will make the product suitable for purchase.
Common pitfall: Treating user preference alone as usability evidence misses observable task performance; treating every error as inadequate training can conceal a recurring interface-related problem.
FDA: Human Factors Considerations · FDA: Applying Human Factors and Usability Engineering to Medical Devices
15.How should equipment retirement protect continuing operations?
Retirement is a controlled lifecycle transition that removes equipment from service while preserving necessary records and managing remaining dependencies. Confirm that replacement capacity is ready, update inventory status and identify associated accessories, support agreements and connected-system relationships. Responsibility for information handling and disposal should be assigned rather than assumed. The discriminating clue is that physically removing a device does not by itself end its financial, service, information or workflow obligations to the organization.
Apply it
A department replaces networked diagnostic workstations. Coordinate clinical cutover, authorized handling of stored information, inventory retirement and cancellation of obsolete support coverage, while retaining service records needed to explain the equipment’s history and any outstanding safety actions.
Common pitfall: Removing an asset from a room without updating its records can leave unnecessary contracts, misleading inventory counts and unresolved information or clinical-service dependencies.
WHO: Health technology management, section 3.4 · WHO: Computerized maintenance management system
Service Delivery Managementnot stated
16.What makes an equipment inventory useful for service decisions?
An effective inventory links a unique equipment identity with information needed to locate, support and manage the asset. Model, serial number, location, operational status and maintenance requirements allow service records to refer to the correct unit. Consistent naming and controlled updates prevent duplicate or obsolete entries from distorting workload and costs. The inventory becomes a management tool when it supports actions such as locating affected equipment, planning maintenance and distinguishing active assets from retired ones.
Apply it
A manufacturer notice applies to selected serial numbers. Use validated model and serial fields to identify potentially affected assets, then reconcile their current locations and status before assigning the required actions to named service staff.
Common pitfall: An inventory that counts purchases but lacks reliable identity and status can appear complete while failing to support recalls, maintenance scheduling or defensible resource planning.
17.How should a work order explain what actually happened?
A useful work order links the reported symptom, findings, action and verification to the correct asset and dates. It distinguishes the user’s observation from the technician’s diagnosis and records relevant parts, labor and unresolved restrictions. This preserves a service history that can reveal recurring problems and support cost analysis. Closing a ticket should mean the documented disposition is clear, not necessarily that a suspected cause was proved or that every reported fault was reproduced.
Apply it
A pump intermittently stops, but bench testing reproduces no fault. Record the original operating conditions, tests performed, results and agreed disposition. Preserve the symptom history so a later recurrence can be analyzed rather than treated as unrelated.
Common pitfall: Writing only 'checked, okay' loses diagnostic context and makes repeat failures look like independent events, weakening both troubleshooting and service-performance analysis over time.
18.How do performance inspection, safety inspection and preventive maintenance differ?
Performance inspection determines whether equipment functions within defined performance requirements. Safety inspection assesses relevant hazards and protective features. Preventive maintenance consists of scheduled actions intended to reduce failures or preserve operation, such as specified cleaning, lubrication or part replacement. These activities can occur during one visit but answer different questions. A service record should identify what was tested or performed, because completing one activity does not establish that all other relevant requirements have been satisfied.
Apply it
A technician replaces a scheduled filter and records the preventive task. The device also requires an output-performance check. Complete and document that check separately before concluding that the unit meets the full service procedure’s release criteria.
Common pitfall: A completed preventive task does not prove acceptable output, and a successful performance test does not establish that every relevant safety feature was inspected.
19.How should a preventive maintenance programme be designed?
A preventive maintenance programme defines tasks, intervals, resources and records using manufacturer recommendations as the baseline. Under CMS hospital guidance, departure requires an eligible alternative equipment maintenance (AEM) programme: qualified personnel must document a risk-based assessment, equipment eligibility, the selected maintenance strategy and monitoring of its effectiveness. Assess failure consequences, use conditions, backup availability and maintenance history. Equipment subject to federal or state requirements mandating manufacturer recommendations, imaging/radiologic equipment and medical lasers are excluded. New equipment without sufficient maintenance history is also excluded; relevant history for the same or similar equipment may support the eligibility assessment. Identify AEM assets in the inventory, document activities and frequencies, and monitor failures and adverse outcomes to revise the strategy when necessary. Managerial approval or a backlog alone does not establish eligibility or satisfy these requirements.
Apply it
A department proposes extending maintenance intervals for established general equipment and a newly purchased medical laser. Keep the laser on manufacturer recommendations because it is excluded from AEM. For the other equipment, qualified personnel must first establish eligibility and document the risk assessment, supporting history, proposed tasks and intervals, and effectiveness monitoring before any departure.
Common pitfall: A period without reported failures does not establish an adequate maintenance history or justify a blanket interval extension. Internal authorization cannot override AEM exclusions or another legal requirement to follow manufacturer recommendations.
WHO: Medical equipment maintenance programme overview · WHO: Computerized maintenance management system · qso-25-24-hospitals-original-release-date-2025-09-05.pdf
20.What makes equipment performance testing reproducible?
Reproducible performance testing defines the measured function, equipment configuration, test conditions, measurement method and acceptance limits. Record actual results when needed to distinguish a clear pass from a trend toward a limit. Test equipment must be suitable for the measurement being made, and the procedure should address important operating modes. The decisive issue is whether another competent person could repeat the assessment and understand why the device was accepted, restricted or removed from service.
Apply it
After a repair, two technicians obtain different output readings. Compare accessories, settings, test load, instrument suitability and procedure version before deciding whether the discrepancy represents device instability or an inconsistent measurement method requiring procedural correction.
Common pitfall: A pass mark without defined conditions can conceal inconsistent testing; checking only one convenient setting may miss a fault in another clinically relevant operating mode.
WHO: Medical equipment maintenance programme overview · WHO: Computerized maintenance management system
21.What should equipment acceptance establish before clinical release?
Equipment acceptance confirms that the delivered asset matches requirements and is ready for its intended local use. Check identity, configuration, condition, documentation and required performance or safety evidence, then resolve deficiencies affecting release. Connected equipment also needs relevant interface verification. Acceptance records establish a baseline for future service. Delivery paperwork or a supplier’s general certificate may contribute evidence, but neither automatically demonstrates that the installed local configuration satisfies the organization’s agreed requirements.
Apply it
A device arrives with the correct model number but an unapproved software configuration. Record the discrepancy and assess its effect on required functions and interfaces before permitting clinical release, even though the delivery note is accurate.
Common pitfall: Signing for receipt and authorizing clinical use are different decisions; a complete shipment may still have configuration, documentation or performance deficiencies that prevent release.
WHO: Procurement process resource guide · WHO: Medical equipment maintenance programme overview · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
22.How does calibration differ from checking performance?
Calibration has two stages under specified conditions. First, it establishes a relation between quantity values supplied by measurement standards, with their measurement uncertainties, and corresponding instrument indications, with associated uncertainties. Second, it uses that information to establish a relation for obtaining a measurement result from an indication, such as a calibration function, curve or correction with uncertainty. The reference must suit the quantity, range and conditions; its uncertainty contributes to the uncertainty of the resulting measurement. A conformity decision separately determines whether specified requirements are met using the applicable decision rule. Adjustment changes the instrument and is distinct from calibration; after adjustment, repeat the necessary measurements and verification before release.
Apply it
Compare a pressure display with a suitable reference at specified points, recording indications, reference values, conditions and uncertainties. Establish the relation used to interpret subsequent indications. If a result is near a tolerance limit, apply the specified conformity decision rule with the relevant uncertainty rather than treating the displayed difference alone as conclusive. If adjustment occurs, repeat the required measurements and verification across the specified range.
Common pitfall: Reference comparison alone omits calibration’s second stage. A current reference certificate does not establish suitability for every range or uncertainty requirement, and calibration alone does not constitute adjustment or a pass decision.
jcgm.bipm.org · WHO: Medical equipment maintenance programme overview · 2025 ACCE Body of Knowledge Survey Final Report
23.Which service contract terms determine operational value?
A service contract’s value depends on coverage, exclusions and the service outcome the organization needs. Distinguish response time from restoration time, and identify who supplies parts, software support, planned maintenance, loan equipment and after-hours assistance. Compare contract cost with internal capability and the consequences of downtime. A low price may provide poor value when important failures are excluded, while comprehensive coverage may be unnecessary if competent internal resources can manage the equipment effectively.
Apply it
A critical system’s contract promises a quick telephone response but no parts availability or restoration commitment. Compare that coverage with the department’s maximum tolerable interruption and negotiate support arrangements that address the actual service vulnerability.
Common pitfall: Treating a response-time promise as an uptime guarantee confuses acknowledgment of a problem with restoration of the clinical service affected by that problem.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Procurement process resource guide
24.How should spare-parts stock reflect service risk?
Spare-parts planning balances consumption, procurement lead time, equipment criticality and the consequences of stockout against holding cost and obsolescence. A rarely used component may justify stock when failure stops an essential service and replacement takes weeks. Conversely, high quantities of model-specific parts can become stranded after fleet changes. Link stock decisions to service history and replacement plans, and distinguish items needed routinely from contingency stock maintained for an explicitly identified operational risk.
Apply it
A low-cost component has failed twice and takes six weeks to obtain; either failure disables the only local unit. Compare holding one verified compatible spare with the expected interruption and available backup arrangements before choosing stock levels.
Common pitfall: Stocking only the most frequently consumed parts overlooks long-lead critical items, while buying every possible spare can consume funds and create obsolete inventory.
WHO: Computerized maintenance management system · 2025 ACCE Body of Knowledge Survey Final Report
25.Why must service procedures match the equipment configuration?
A controlled technical library gives staff access to current procedures, service information and relevant configuration details. Model names alone may be insufficient when software, accessories or hardware revisions change a test method or acceptance limit. Link the applicable procedure to the maintained asset and record the version used when necessary. The goal is reproducible, authorized work: a familiar procedure is useful only when it applies to the equipment and task actually being serviced.
Apply it
A technician finds two maintenance procedures for the same product family. Check the unit’s hardware and software configuration against the procedure applicability statements before testing, then resolve conflicting instructions through the responsible technical authority and document the resolution.
Common pitfall: Using the newest document without checking applicability can be as misleading as using an obsolete one; revision date alone does not establish configuration compatibility.
WHO: Computerized maintenance management system · 2025 ACCE Body of Knowledge Survey Final Report
26.How should maintenance indicators distinguish workload from reliability?
Maintenance indicators need clear definitions and denominators to answer a specific management question. Completion rate describes planned-work execution, while repeat failures, downtime and service costs address different aspects of performance. A high closure count may reflect activity rather than reliable equipment. Compare like assets and periods, examine missing records and separate waiting time from active repair time when relevant. Indicators are most useful when they trigger investigation and improvement rather than reward easy-to-close work.
Apply it
A team closes more tickets, but one equipment family has increasing repeat visits. Review recurrence, downtime and documented findings for that family instead of concluding that higher closure volume proves the maintenance programme has become more effective.
Common pitfall: Comparing raw failure counts across fleets of different sizes or use intensity can misidentify the least reliable equipment and misdirect improvement resources or replacement funding.
Information Technology (IT)/Telecommunications/Cybersecuritynot stated
27.How can correct transmission still produce incorrect clinical data?
An interface can transmit a value accurately while the receiving system interprets its meaning incorrectly. Patient identity, units, parameter labels, scaling and context all contribute to semantic correctness. Verification must follow data through the entire intended pathway, including its displayed or stored interpretation. The discriminating clue is whether the receiving user or application can use the information correctly, rather than whether packets arrive or a connectivity indicator shows success at either end.
Apply it
A device sends a measurement that appears numerically unchanged in the record, but the displayed units differ. Pause reliance on the interface and verify mapping, scaling and end-to-end interpretation with representative data before restoring intended use.
Common pitfall: A successful connection test establishes communication, not correct patient association or measurement meaning; these failures can persist without packet loss or visible network alarms.
28.Why do data timing and communication failure behavior matter?
The usefulness of device data depends partly on when it was measured, when it arrives and how stale or missing information is identified. A delayed value may be technically accurate yet inappropriate for a time-sensitive decision. Interface risk assessment should consider latency, update rate, interruption and recovery behavior in relation to intended use. Verification should include faults and boundary conditions so the combined system handles missing, delayed or resumed communication in an understandable and safe manner.
Apply it
After a network interruption, a display continues showing the last observation without a freshness indicator. Test how the interface marks outdated data and resumes updates, and assess whether the intended clinical workflow can detect the interruption.
Common pitfall: Testing only normal streaming can miss silent stale-data states; restoring connectivity does not prove that timestamps, queued values and recovery behavior are appropriate.
29.How should a medical-device cybersecurity vulnerability be prioritized?
Cybersecurity prioritization considers the vulnerability’s exploitability, the device’s exposure and the possible effect on patient harm. A technical severity score alone does not describe the clinical consequence in a particular deployment. Examine whether exploitation could compromise essential performance and whether existing controls reduce the risk. Coordinate with the manufacturer, security staff and clinical owners so the response addresses both cyber exposure and the consequences of interrupting a needed clinical service during mitigation.
Apply it
Two devices share a vulnerability score, but one permits remote access to a treatment function while the other is isolated and read-only. Compare reachable attack paths, patient consequences and verified controls before assigning remediation priority.
Common pitfall: Ranking solely by a generic score can ignore local exposure and clinical consequences; dismissing risk solely because exploitation has not been observed is equally weak.
FDA: Postmarket Management of Cybersecurity in Medical Devices
30.When is a compensating cybersecurity control credible?
A compensating control reduces a specific exposure or attack pathway when the underlying vulnerability cannot yet be removed. Its credibility depends on demonstrated effectiveness, preservation of required clinical function and monitoring for failure or changing conditions. Network restrictions, for example, help only if they block the relevant path without disabling necessary communication. Document residual risk, ownership and review conditions; a control is an interim risk treatment, not proof that the vulnerable device has become intrinsically secure.
Apply it
A patch is unavailable for a networked device. Restrict access to necessary endpoints, verify required clinical exchanges and test that the identified attack path is blocked, then assign monitoring and a review date with responsible teams.
Common pitfall: Calling a device segmented without testing actual allowed pathways can create false confidence, particularly when required connections still expose the vulnerable service to attackers.
FDA: Postmarket Management of Cybersecurity in Medical Devices · FDA: Cybersecurity
31.How should a security patch enter clinical service?
A patch changes a maintained configuration and can affect device operation, interfaces or availability. Assess urgency alongside manufacturer information, compatibility, testing and a controlled deployment plan. Define what constitutes successful installation, how essential functions will be checked and how service will be maintained if problems occur. The goal is timely risk reduction with evidence that the changed system remains fit for intended use; indefinite delay and indiscriminate installation both leave important risks unmanaged.
Apply it
A security update is available for a connected workstation. Confirm supported versions, test representative workflows and interfaces, arrange a clinical maintenance window and document recovery steps before rolling the change across all workstations in the department.
Common pitfall: Installing directly on every clinical unit can spread an incompatibility, while waiting for perfect certainty without interim controls can leave a significant exposure untreated.
FDA: Cybersecurity · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices · 2025 ACCE Body of Knowledge Survey Final Report
32.How should continuity planning address a connected-device outage?
Continuity planning identifies which clinical functions depend on networks, servers, interfaces and shared services, then defines how care continues when those dependencies fail. A device may still operate locally while documentation, alarms or remote access become unavailable. Plans should assign communication, fallback and recovery responsibilities and verify them through realistic exercises. Recovery includes confirming correct data flow and reconciling affected information; technical restoration alone does not establish that the clinical workflow is fully restored.
Apply it
A middleware outage stops automatic charting while bedside measurements remain available. Activate the agreed manual documentation process, inform users of missing integration and verify recovery and information reconciliation before declaring the workflow fully operational across affected units.
Common pitfall: Assuming that local device operation means the service is unaffected overlooks lost alarms, documentation or remote functions and can delay necessary clinical workflow changes.
FDA: Cybersecurity · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices · 2025 ACCE Body of Knowledge Survey Final Report
33.What information belongs in a controlled device configuration baseline?
A configuration baseline records the approved combination of hardware, software, settings and interfaces needed to explain and reproduce a system’s operation. It supports fault diagnosis, change assessment and recovery by showing what should be present before a change occurs. Record authorized deviations and their justification rather than silently allowing drift. The important distinction is between knowing an asset’s product name and knowing the actual configuration on which performance, security and interoperability evidence depends.
Apply it
Two nominally identical devices behave differently after an interface update. Compare their approved software, settings and connected components against the baseline, then determine whether an undocumented difference invalidates previous testing or requires a controlled configuration change.
Common pitfall: A model list is insufficient for change control when software versions or settings alter behavior; undocumented local fixes make later troubleshooting and recovery unreliable.
2025 ACCE Body of Knowledge Survey Final Report · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
Risk Management/Safetynot stated
34.What should guide the immediate response to a suspected device incident?
The immediate response should protect the affected patient and prevent further exposure while preserving information needed to understand the event. Coordinate safe clinical alternatives before isolating equipment when therapy depends on it. Communicate with responsible clinical and safety personnel, identify potentially affected units and avoid assuming that either the device or the user caused the event. The initial decision concerns containment and continuity; a definitive causal conclusion usually requires evidence that is not yet available.
Apply it
A monitor behaves unexpectedly during care. Have clinicians maintain required monitoring through an appropriate alternative, remove the suspect unit from further use when safe and notify the investigation team while preserving its configuration, accessories and relevant records.
Common pitfall: Immediately returning a suspect unit to service after a quick check can expose others, while disconnecting essential equipment without a clinical alternative can create additional harm.
AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events · 2025 ACCE Body of Knowledge Survey Final Report
35.How should incident evidence be preserved?
Incident evidence includes the device, configuration, accessories, relevant consumables, logs and accounts of the operating context. Preserve original information and document necessary handling so investigators can distinguish event conditions from later changes. Cleaning, resetting or destructive testing may erase clues, although immediate safety needs can require action. Record what was changed, by whom and why. The purpose is to maintain a reliable reconstruction rather than protect a preferred explanation or delay essential patient care.
Apply it
A device restarts after an event and its logs may be overwritten. Once clinical safety is secured, coordinate preservation of available logs, configuration and accessories before routine servicing, documenting any actions already taken and their timing.
Common pitfall: A well-intended reset may destroy transient evidence; preserving equipment alone is also insufficient when accessories, settings and the surrounding workflow influenced the reported event.
AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events
36.When is failure mode and effects analysis the appropriate method?
Failure mode and effects analysis is a prospective method for examining how a process could fail and what those failures could cause. Break the process into steps, identify failure modes and effects, consider existing controls and prioritize improvements. It is especially useful before introducing a workflow or after recognizing vulnerability without waiting for harm. Numerical rankings can organize discussion, but prioritization must still consider severe consequences and the limitations of subjective estimates rather than treating a score as a complete decision.
Apply it
Before launching automated device-to-record transfer, map patient association, measurement capture and error handling. Examine how each step could fail, determine possible consequences and strengthen the most important controls before the workflow enters routine clinical use.
Common pitfall: Using a calculated ranking as the sole decision rule can underemphasize a severe hazard; FMEA also does not replace investigation of an event that already occurred.
AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events
37.How does root cause analysis move beyond identifying an individual error?
Root cause analysis examines an event retrospectively to identify contributing system conditions and opportunities for prevention. Reconstruct the sequence using records, interviews and technical evidence, then examine how workflow, interfaces, staffing and defenses shaped the outcome. Finding an incorrect action does not explain why it was likely or why safeguards failed. A useful analysis leads to feasible corrective actions with accountable owners and measures, rather than ending with a label such as inattention or noncompliance.
Apply it
An alarm was not escalated during an event. Examine routing, role assignments, competing alarms, staffing and escalation design alongside individual actions, then choose changes that address demonstrated contributing conditions and can be evaluated after implementation in practice.
Common pitfall: Stopping at 'staff failed to follow policy' can conceal unusable procedures or weak defenses and tends to produce reminders without reducing the underlying vulnerability.
AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events
38.What makes a corrective action stronger than a reminder?
A corrective action should address the demonstrated failure mechanism and make safer performance more reliable. System changes that reduce ambiguity, constrain hazardous choices or improve detection generally depend less on memory than reminders alone. Choose actions that are feasible in the actual workflow and assess unintended consequences. Assign an owner, completion evidence and an outcome measure. Implementation is necessary, but effectiveness requires showing that the targeted risk or failure pattern has actually changed over time.
Apply it
Repeated selection errors arise from nearly identical options. Compare revising the interface or available choices with sending another email, then test task performance and monitor recurrence after the selected change is introduced into the working environment.
Common pitfall: Closing an investigation because training was delivered measures activity rather than risk reduction; an action can be completed on time yet fail to prevent recurrence.
AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events · FDA: Applying Human Factors and Usability Engineering to Medical Devices
39.Which U.S. user-facility events require reporting, to whom and by when?
A U.S. medical device user facility reports information reasonably suggesting that a device caused or contributed to a death or serious injury; definitive proof is unnecessary. Serious injury means an injury or illness that is life-threatening, results in permanent impairment of a body function or permanent damage to a body structure, or necessitates medical or surgical intervention to prevent such permanent impairment or damage. Report a death to FDA and the manufacturer, if known, as soon as practicable and no more than 10 work days after the day of awareness. Report a serious injury to the manufacturer, or to FDA if the manufacturer is unknown, no later than 10 work days after the day of awareness. User facilities generally do not have mandatory malfunction-only reporting obligations under these provisions.
Apply it
A hospital learns that a suspected device failure required intervention to prevent permanent bodily damage. This meets the serious-injury criterion even if permanent harm was successfully prevented. Record the awareness date, initiate reporting to the known manufacturer within the 10-work-day limit and continue investigating. If the event were a death, report to both FDA and the known manufacturer as soon as practicable within the applicable limit.
Common pitfall: Successful treatment does not exclude serious injury when intervention was needed to prevent permanent harm. Waiting for a completed technical investigation does not postpone the awareness-based reporting deadline, and manufacturer malfunction-reporting duties should not be transferred to user facilities.
Federal Register :: Request Access · Federal Register :: Request Access · Questions and Answers on the Medical Device Reporting (MDR) Regulation | FDA · FDA: Medical Device Reporting—How to Report Medical Device Problems
40.How should a product safety alert be translated into local action?
A safety alert requires determining whether the specified products and conditions exist locally, then implementing and documenting the applicable action. Match model, serial or other identifying criteria against a reliable inventory and confirm actual locations. Assess continuity needs when affected equipment must be restricted or removed. Closure requires evidence that each affected asset received the required disposition, not merely that an email was circulated or that the notice was acknowledged by a department.
Apply it
A notice identifies a subset of a device family. Validate affected serial numbers, locate units including loaned equipment, coordinate alternatives and document each required action before closing the alert in the organization’s tracking process and notifying stakeholders.
Common pitfall: Treating every product in a family as affected can disrupt care unnecessarily, while closing an alert after distribution leaves implementation and missing assets unresolved.
WHO: Computerized maintenance management system · 2025 ACCE Body of Knowledge Survey Final Report
41.Why can adverse-event report counts not establish comparative device risk?
Adverse-event reports can identify safety signals but have limitations including incomplete information, underreporting, possible duplicate reports and uncertain device involvement. Counts usually lack a reliable denominator describing how many devices or procedures were exposed. More reports therefore do not, by themselves, establish a higher event rate or prove causation. Use reports to generate questions and guide investigation, then seek exposure data, clinical context and corroborating evidence before making comparative safety claims or procurement decisions.
Apply it
A committee finds twice as many reports for device A as device B. Ask about installed base, use volume, reporting patterns and event details before concluding that device A has twice the risk or should be excluded.
Common pitfall: Dividing report counts by an unrelated denominator creates a misleading rate; a report’s presence also does not establish that the device caused the outcome.
FDA: Medical Device Reporting—How to Report Medical Device Problems
General Managementnot stated
42.How should staffing estimates reflect actual service demand?
Staffing estimates should connect required work with available productive capacity and the competencies needed to perform it. Include planned maintenance, corrective work, projects, documentation, coverage and foreseeable variation rather than counting assets alone. Distinguish total paid hours from hours available for assigned service tasks. A calculated staffing requirement is a planning estimate, not proof of safe coverage; review whether the schedule provides necessary skills and continuity when leave, training or urgent work occurs.
Apply it
A service estimates 4,800 annual task hours and 1,200 available task hours per full-time position. Four positions cover the arithmetic workload, but review specialist coverage, leave assumptions and concurrent urgent demands before finalizing the staffing proposal.
Common pitfall: Using nominal paid hours as productive capacity understates staffing needs; using an equipment-to-technician ratio alone ignores complexity, geography, service scope and required skill mix.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Computerized maintenance management system
43.How should a manager distinguish credentials from task competence?
Credentials and experience provide useful background, but task competence requires evidence that a person can perform assigned work correctly under relevant conditions. Define the task, required knowledge, practical skills and escalation boundaries, then choose an assessment suited to the consequences of error. A skills matrix can reveal gaps in team coverage and guide development. Authorization should reflect demonstrated capability and available supervision, while recognizing that competence must be maintained as equipment and responsibilities change.
Apply it
A newly hired technician has broad experience but has not serviced the hospital’s specialized system. Review prior evidence, provide model-specific preparation and observe required tasks before granting independent authorization for that work and its associated release decisions.
Common pitfall: Assuming that years employed establish competence for every device can assign work beyond capability; attendance at a course alone also does not demonstrate independent performance.
2025 ACCE Body of Knowledge Survey Final Report · ACCE Code of Ethics
44.How should a technology-service budget be constructed?
A service budget translates expected workload and responsibilities into resource requirements over a defined period. Build assumptions for staffing, parts, contracts, training, test equipment and planned changes, distinguishing recurring operating costs from capital investment. Historical spending provides a baseline but may not reflect new equipment, support changes or deferred work. A defensible proposal explains what service the funding enables, which assumptions drive cost and what consequences follow if essential resources are omitted or reduced.
Apply it
A new fleet reduces repair demand but adds annual software support and staff training. Update the budget by service category and timing rather than applying the previous year’s total with a uniform percentage increase across all expenses.
Common pitfall: Repeating last year’s spending can perpetuate underfunding or obsolete costs; separating purchase and support decisions can also leave necessary recurring expenses unfunded after installation.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Health technology management, section 3.4
45.How should a manager interpret a favorable budget variance?
Spending below budget is favorable only in relation to the service delivered and obligations remaining. Analyze whether the difference reflects efficiency, lower demand, delayed invoices, vacant positions or deferred maintenance. Separate price changes from workload changes when possible and examine safety and performance indicators alongside financial results. The managerial decision is whether resources were used responsibly to achieve objectives, not whether expenditure was minimized regardless of unmet work, future liabilities or clinical consequences.
Apply it
Parts spending is below plan while unavailable equipment and overdue work are rising. Investigate purchasing delays and deferred repairs before reporting a saving, and estimate the cost and service effect of the work still outstanding.
Common pitfall: Celebrating underspending without checking output can reward postponed obligations; forcing expenditure merely to exhaust a budget is also inconsistent with responsible resource management.
2025 ACCE Body of Knowledge Survey Final Report · WHO: Computerized maintenance management system · ACCE Code of Ethics
46.What makes a technology policy operationally usable?
An operational policy defines its scope, responsibilities and required decisions clearly enough that staff can apply it consistently. Supporting procedures should explain how work is performed, documented and escalated, including exceptions and unavailable resources. Assign ownership and review when equipment, regulations or workflows change. A policy is useful when it creates a reliable process with observable compliance, rather than simply stating a desirable outcome that staff cannot translate into action under real conditions.
Apply it
A policy says defective equipment must be removed promptly but names no replacement or escalation process. Add responsibilities for clinical continuity, isolation, service notification and release so staff can act consistently during an actual equipment problem.
Common pitfall: A comprehensive document can still be unusable if responsibilities conflict or required resources are absent; publication alone does not establish that staff understand or follow it.
2025 ACCE Body of Knowledge Survey Final Report · AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events
47.How should a multidisciplinary committee reach a defensible decision?
A multidisciplinary committee needs a defined decision, relevant evidence and clarity about who can authorize action. Clinical, engineering, IT, finance and operations representatives contribute different consequences and constraints. Record the alternatives considered, rationale, unresolved assumptions and accountable follow-up. Consensus is useful, but agreement without evidence does not establish soundness. Effective leadership makes tradeoffs explicit and ensures that a decision can be implemented and reviewed rather than allowing discussion to end without an owner or outcome.
Apply it
A committee disagrees about a replacement system. Restate essential requirements, compare verified options and identify the remaining decision authority, then document the chosen tradeoff and assign owners for integration, training and support before the meeting concludes.
Common pitfall: Seeking unanimous preference can obscure mandatory requirements or delay necessary action; recording only the final vote loses the rationale needed for implementation and later review.
2025 ACCE Body of Knowledge Survey Final Report · ACCE Code of Ethics
48.When must a conflict of interest change professional participation?
A conflict of interest exists when a personal or financial relationship could influence, or reasonably appear to influence, professional judgment. Disclose relevant interests before participating in a decision and follow appropriate arrangements for independent evaluation or recusal. Disclosure is necessary but may not by itself resolve the conflict. Protect confidential information and represent qualifications honestly. The guiding principle is that patient welfare and responsible resource decisions must remain credible to affected stakeholders and independent reviewers.
Apply it
An engineer evaluating bids has a financial interest in one supplier. Disclose the relationship before scoring begins and arrange an independent evaluation role or recusal under organizational rules so the purchasing decision has a credible, documented basis.
Common pitfall: Believing that personal confidence in one’s fairness eliminates a conflict ignores its perceived influence; disclosing only after the decision prevents timely independent management.
ACCE Code of Ethics · HTCC Certification Handbook—2026 Virtual Edition
Education of Othersnot stated
49.How should device-training objectives be written?
A useful training objective identifies an observable task, the conditions under which it is performed and the criterion for satisfactory performance. Start with the user’s responsibilities and the consequences of task failure, rather than organizing instruction solely around every menu or feature. Match language and examples to the intended audience and environment. Objectives guide both teaching and assessment, allowing the educator to distinguish exposure to information from the ability to use equipment appropriately.
Apply it
Instead of asking nurses to 'understand alarms,' require them to recognize a specified alarm state, assess the displayed information and carry out the approved response in a realistic scenario, using defined performance criteria during assessment.
Common pitfall: Objectives such as 'know the device' are too broad to assess; teaching every feature equally can consume time while leaving high-consequence tasks insufficiently practised.
FDA: Applying Human Factors and Usability Engineering to Medical Devices · FDA: Human Factors Considerations
50.Why is return demonstration stronger evidence than attendance?
Attendance establishes that a learner was present, while return demonstration shows whether the learner can perform specified tasks. Use representative conditions and explicit criteria, observe errors and provide targeted feedback before reassessment. A written quiz can assess supporting knowledge but may miss difficulties locating controls, interpreting displays or responding under realistic interruptions. Choose the assessment method according to the task and its consequences, and record the demonstrated capability rather than assuming it from participation alone.
Apply it
After teaching a new device, observe each user completing setup and responding to a representative alarm. If a learner omits a required check, provide focused practice and repeat the relevant assessment before independent use is authorized.
Common pitfall: A signed attendance sheet or high recall score can coexist with unsafe task execution; a coached demonstration also gives weaker evidence than unaided performance under defined conditions.
FDA: Applying Human Factors and Usability Engineering to Medical Devices · 2025 ACCE Body of Knowledge Survey Final Report
51.When is additional training an inadequate response to use error?
Training can address a genuine knowledge or skill gap, but it may be insufficient when the interface or use environment repeatedly induces error. Examine whether intended users can perform the task after realistic preparation and whether controls, labels, feedback or workflow create persistent confusion. Human factors analysis considers the interaction among user, device and environment. Select an intervention that addresses the demonstrated cause; repeated education should not substitute for evaluating a design problem or an impractical workflow.
Apply it
Users who passed training repeatedly select an unintended mode because labels are difficult to distinguish. Observe the task, assess interface and workflow changes and use targeted education as part of the response rather than the sole corrective action.
Common pitfall: Calling every error a training failure transfers responsibility to users and can leave an error-inducing design unchanged despite repeated courses and continuing incidents.
FDA: Applying Human Factors and Usability Engineering to Medical Devices · FDA: Human Factors Considerations
52.How should a technical staff development plan set priorities?
A staff development plan compares required service capabilities with demonstrated team competence and upcoming responsibilities. Prioritize gaps according to clinical consequence, workload, coverage and planned technology changes, then select education, supervised practice and assessment methods. Assign time and resources rather than treating development as an optional activity outside normal work. The plan should show how learning closes a service gap and how competence will be confirmed and maintained after the educational activity is completed.
Apply it
Only one technician can support a critical device family and is frequently unavailable. Develop a second qualified person through structured instruction, supervised tasks and observed assessment, then review whether the team can sustain the required service coverage.
Common pitfall: Choosing courses solely by availability or employee preference can leave essential capability gaps unresolved; completing a course does not automatically authorize independent work.
2025 ACCE Body of Knowledge Survey Final Report · ACCE Code of Ethics
53.How can educators determine whether learning transfers to practice?
Learning transfer means that required skills are used correctly in the work setting after instruction. Assess immediate task performance, then examine relevant practice observations, errors or service outcomes over time. Interpret results in context because workflow changes, equipment design and staffing can also affect performance. Feedback should lead to targeted improvement rather than merely repeating the same course. Satisfaction surveys describe the learner’s experience but do not establish competence or sustained improvement in clinical or technical work.
Apply it
A training programme improves immediate setup demonstrations, but support calls remain high. Review call reasons and observe actual use to determine whether retention, an unaddressed workflow or a device issue explains the continuing demand for assistance.
Common pitfall: Using positive course ratings as proof of effective training confuses satisfaction with performance; blaming instruction for every later problem also ignores environmental and design influences.
FDA: Applying Human Factors and Usability Engineering to Medical Devices · AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events · 2025 ACCE Body of Knowledge Survey Final Report
Facilities Managementnot stated
54.Why does emergency power require end-to-end verification?
Emergency power readiness depends on the complete path supplying an essential clinical function, not simply the presence of a generator. Consider transfer behavior, connected loads, distribution, device batteries and dependencies such as cooling or communications. A successful component test may not establish that the intended service continues through an outage. Coordinate facilities, clinical engineering and clinical teams to verify relevant behavior safely, document limitations and plan alternatives for functions that cannot tolerate an interruption or loss of supporting utilities.
Apply it
A generator test succeeds, but a connected clinical system also depends on a server and room cooling. Examine those dependencies and device behavior during transfer before concluding that the clinical service can continue during a power outage.
Common pitfall: Assuming that an emergency receptacle guarantees uninterrupted operation overlooks transfer intervals, battery condition, load limitations and supporting systems that may lose power elsewhere.
55.How should utility-outage plans identify hidden dependencies?
A utility-outage plan maps how electricity, water, medical gases, ventilation and communications support clinical services. Determine which functions fail immediately, which degrade over time and which depend on shared infrastructure. Define triggers for conservation, relocation or service reduction using local capability and verified resources. The important distinction is between owning backup equipment and sustaining the complete service: a device may remain powered while the utility or environment necessary for its intended operation is unavailable.
Apply it
A department plans to continue procedures on backup power during a water outage. Map water-dependent equipment, cleaning and environmental needs before approving continuity, then identify which services require restriction or relocation despite available electricity and functioning devices.
Common pitfall: Planning each utility in isolation can miss cascading failures; a backup device may provide little benefit if its gas, cooling, water or communication dependency is unavailable.
56.How should construction and emergency readiness be verified together?
Facility changes can alter equipment locations, access, electrical supply, environmental conditions and emergency routes. Review intended clinical workflows and equipment requirements before work begins, then verify affected services before occupancy or return to use. Coordinate temporary arrangements and escalation responsibilities during construction. Emergency preparedness should be exercised against the changed layout and dependencies, because a plan that worked in the previous configuration may no longer provide timely access, suitable backup power or an effective clinical alternative.
Apply it
A renovation relocates monitored beds and storage. Review power and network provision, access to backup equipment and emergency movement routes, then test the revised escalation and continuity arrangements before the area returns to routine clinical operation.
Common pitfall: Approving drawings without verifying the completed clinical environment can miss changed dependencies; assuming the previous emergency plan still fits may leave critical resources inaccessible.
ASPR TRACIE: Utility Failures · 2025 ACCE Body of Knowledge Survey Final Report
Product Development, Testing, Evaluation, and Modificationnot stated
57.What makes a user task critical in human factors engineering?
A critical task is a user task whose incorrect performance or omission would or could cause serious harm to the patient or user, including compromised medical care. Criticality therefore depends on the consequence of failure rather than how often the task occurs or how difficult it appears. Identify tasks through use-related risk analysis and examine the interface and workflow supporting them. This focuses evaluation on the parts of device use where misunderstanding, omission or incorrect action has the greatest safety significance.
Apply it
A rarely used control changes a therapy mode and incorrect selection could seriously harm a patient. Treat the task as critical during use-related risk analysis even if routine setup tasks occur far more frequently during daily operation.
Common pitfall: Ranking tasks only by frequency or visible complexity can exclude a simple, infrequent action with serious consequences when performed incorrectly or omitted entirely.
FDA: Applying Human Factors and Usability Engineering to Medical Devices
58.How does formative usability evaluation guide design?
Formative evaluation explores how users interact with an evolving design so problems can be identified and corrected before final validation. Methods can include observation, interviews and task-based testing appropriate to the development stage. The objective is to understand why difficulties occur and improve the interface, rather than demonstrate that a finished design is acceptable. Iterate after changes and connect findings to use-related risks, especially when users misunderstand feedback, confuse controls or fail to recover from foreseeable errors.
Apply it
Prototype testing shows that users overlook an important confirmation message. Examine visibility, wording and task flow, revise the interface and test again before treating the design as ready for validation with its intended users and operating context.
Common pitfall: Using early prototype success as final validation ignores later design changes; collecting preference ratings alone may miss task failures that require observation and investigation.
FDA: Applying Human Factors and Usability Engineering to Medical Devices
59.What makes human factors validation representative?
Human factors validation evaluates whether intended users can perform critical tasks safely and effectively with the final user interface under representative use conditions. Include relevant user groups, realistic environments and the training or information expected in actual use. Avoid coaching that masks difficulty. Analyze use errors, close calls and task problems to understand residual risk. A technically functional device or a demonstration by product experts does not establish that its intended users can operate it appropriately.
Apply it
A home-use device is tested only by development engineers in a quiet laboratory. Redesign the evaluation to include intended lay users, realistic conditions and expected instructions, observing critical tasks without assistance that ordinary users would not receive.
Common pitfall: Testing only expert users or giving extra coaching can hide real difficulties; representative conditions concern users, environment, interface and expected preparation, not just equipment function.
FDA: Applying Human Factors and Usability Engineering to Medical Devices · FDA: Human Factors Considerations
60.How should a device modification be justified and documented?
Begin by distinguishing servicing from remanufacturing. Servicing restores a finished device to the original manufacturer’s safety and performance specifications and original intended use. Activities that significantly change performance specifications, safety specifications or intended use can constitute remanufacturing, regardless of the activity’s local label. Compare the proposed result with the original specifications and intended use, assess individual and cumulative changes, and document the classification rationale and affected hazards. Internal authorization and successful testing do not resolve resulting manufacturer responsibilities or whether applicable marketing authorization is required. Determine those obligations before implementation. Verification demonstrates specified requirements were implemented correctly; validation evaluates affected intended-use needs. Both support the decision but do not replace the regulatory assessment.
Apply it
Replacing a failed pressure sensor with an equivalent component and demonstrating restoration of the original specified range and safety functions is servicing when original specifications and intended use remain intact. Reprogramming the same device to deliver substantially higher therapeutic pressure and changing its safety cutoff significantly alters performance and safety specifications and can be remanufacturing. For that proposal, stop routine service release, involve regulatory and manufacturer expertise, determine manufacturer and marketing-authorization obligations, and document risk analysis, required testing and the resulting release decision.
Common pitfall: A modification can pass locally selected tests while changing the device’s regulatory status. Calling work a repair, retaining the original enclosure or obtaining committee approval does not establish that original specifications and intended use have been preserved.
Remanufacturing of Medical Devices | FDA · FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices · FDA: Applying Human Factors and Usability Engineering to Medical Devices · 2025 ACCE Body of Knowledge Survey Final Report
What to focus on during revision
The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.
- Explain a decision in a consistent sequence: clinical objective, immediate risk, missing evidence, alternatives, recommendation, ownership and effectiveness measure. This is an educational response framework, not an official examination scoring rubric.
- Distinguish device performance from whole-system performance, especially for interfaces, emergency utilities and clinical workflows.
- Compare acquisition price, ownership cost, service resilience and supportability using explicit assumptions and a common time horizon.
- Separate preventive tasks, performance inspection, safety inspection, calibration and operational acceptance.
- Connect cybersecurity exposure to patient consequences and verify that mitigation preserves essential clinical functions.
- Choose prospective FMEA or retrospective RCA deliberately, then propose corrective actions with measurable follow-up.
- Practise explaining a recommendation to clinical, financial and technical stakeholders without overstating certainty.
- Use the full official BOK responsibility lists to extend this selective guide, including subjects receiving fewer examples here.
A practical preparation plan
1. Map the full scope
Create a personal coverage map from all eight official BOK work categories and their responsibilities. Mark which duties you can explain with evidence and which require study beyond these 60 concepts.
2. Build decision comparisons
Practise short comparisons of repair versus replacement, contract versus internal service, and immediate patching versus controlled mitigation. State the deciding evidence and the assumptions that would change your recommendation.
3. Work the quantitative cases
Calculate ownership cost, simple payback and workload capacity with units and defined boundaries. Then explain which clinical or operational considerations the calculation does not capture.
4. Rehearse oral scenarios
Use original cases involving an incident, integration failure, procurement dispute or utility outage. Explain immediate containment, investigation, stakeholders and follow-up aloud, then challenge your own assumptions. Use the worked responses below to practise a complete recommendation through competing constraints. Their response framework is an educational approach, not an official scoring rubric.
5. Worked oral case: vulnerable connected monitors
Case: A hospital’s monitors continue bedside monitoring, but a network service has a serious vulnerability. No patch is available for two weeks. Disconnecting all monitors would also remove central alarm delivery. The security team proposes restricting connections; nursing reports insufficient staffing for continuous bedside observation. Model response: 'My immediate objective is to preserve effective monitoring while reducing the attack exposure. I would bring nursing, clinical engineering, IT security and the manufacturer together immediately, preserve relevant logs and avoid an abrupt disconnection that removes required alarms. I assume bedside performance is intact, no compromise has been demonstrated and the manufacturer supports the proposed configuration; I would verify each assumption. The severity score establishes urgency, but reachable attack paths, possible effects on monitoring and current controls determine local risk. I would compare complete isolation, restricted connectivity and temporary replacement. Isolation removes connectivity but creates an alarm and staffing deficit; unrestricted operation retains the known exposure. I recommend a time-limited restriction only if testing demonstrates that it blocks the identified attack path while preserving required central alarms, patient association and outage indication. IT security owns enforcement and monitoring, engineering verifies device and interface behavior, nursing validates the clinical fallback, and the manufacturer supplies compatibility and remediation information. The accountable clinical and security leaders should document residual risk and review it daily until patch deployment. Effectiveness measures are successful attack-path blocking tests, successful end-to-end alarm tests and monitoring for failed or delayed alarm delivery; absence of a reported incident alone is insufficient.' Follow-up challenge: Testing shows that a connection required for central alarms still exposes the vulnerable service. Revised response: 'The proposed control fails its essential criterion, so I would not accept it as sufficient mitigation. I would activate the clinical continuity plan, obtain replacement monitoring or relocate patients to an area with verified monitoring capacity, and isolate affected units through a clinically coordinated transition. If replacement capacity is inadequate, clinical leadership must reduce or transfer the affected service rather than assume unavailable bedside staffing can compensate.'
6. Worked oral case: maintenance backlog and replacement pressure
Case: A U.S. hospital has a maintenance backlog and limited capital. A manager proposes doubling every maintenance interval. An established general-equipment fleet has usable service records, while an imaging system has repeated interruptions and unavailable essential parts. A newly acquired medical laser has little local history. Model response: 'I would first triage overdue work by patient consequence and arrange clinical alternatives for unreliable equipment. I would retain existing maintenance requirements while the proposal is assessed. I assume the records identify actual tasks, failures, use and downtime; qualified personnel must check completeness before relying on them. A backlog demonstrates a capacity problem, not that current maintenance is unnecessary. CMS AEM permits eligible departures only through a documented risk-based programme with qualified assessment, a defined strategy and effectiveness monitoring. Imaging/radiologic equipment and medical lasers are excluded; insufficient history also prevents treating new equipment as eligible merely because a manager approves it. For eligible general equipment, I would compare retaining the existing schedule with a specifically justified AEM strategy using failure consequences, history, use and backup availability. I recommend targeted AEM assessment alongside temporary service capacity, rather than a blanket extension. Separately, I would prioritize the unsupported imaging system for replacement because parts unavailability and interruption consequences weaken continued-service resilience even if it currently passes a performance test. Engineering owns the inventory, history review and maintenance strategy; clinical leaders establish backup needs; procurement and the supplier verify replacement and parts options; finance and the capital committee authorize resources. I would monitor risk-stratified overdue work, fleet-normalized repeat failures and downtime, with reassessment if failures or adverse outcomes increase. The laser and imaging system continue under manufacturer recommendations.' Follow-up challenge: An audit finds that the general fleet’s apparent low failure rate excludes outsourced repairs. Revised response: 'The evidence is incomplete, so I would defer the proposed interval change, reconcile contractor records and continue the existing schedule with added capacity. If verified parts support and adequate backup later become available for the imaging system, I would reconsider the urgency of replacement against other capital needs; its age alone would not settle the decision.'
7. Use drills diagnostically
Answer the 20 MCQs and explain why each alternative is less suitable before reading the explanation. Convert errors into a specific rule, such as distinguishing response time from restoration time.
8. Verify readiness and current rules
Review the current HTCC handbook and your authorized pathway, then complete the required virtual readiness checks. Keep administration details separate from your substantive study of clinical engineering judgment.
Use your sample score as a starting point
The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.
Start the free sampleOfficial sources and updates
- ACCE: Get Certified
- HTCC Certification Handbook—2026 Virtual Edition
- 2025 ACCE Body of Knowledge Survey Final Report
- WHO: Procurement process resource guide
- WHO: Health technology management, section 3.4
- WHO: Medical equipment maintenance programme overview
- WHO: Computerized maintenance management system
- FDA: Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices
- FDA: Postmarket Management of Cybersecurity in Medical Devices
- FDA: Cybersecurity
- FDA: Medical Device Reporting—How to Report Medical Device Problems
- AHRQ PSNet: Strategies and Approaches for Investigating Patient Safety Events
- FDA: Applying Human Factors and Usability Engineering to Medical Devices
- FDA: Human Factors Considerations
- ACCE Code of Ethics
- ASPR TRACIE: Utility Failures
- qso-25-24-hospitals-original-release-date-2025-09-05.pdf
- jcgm.bipm.org
- Questions and Answers on the Medical Device Reporting (MDR) Regulation | FDA
- Federal Register :: Request Access
- Federal Register :: Request Access
- Remanufacturing of Medical Devices | FDA
- Mandatory Reporting Requirements: Manufacturers, Importers and Device User Facilities | FDA
- download
- Energy and Cost Analysis Methodology | Building Energy Codes Program
Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.