The BF classification describes how a medical device’s applied part touches the patient — and that classification drives the isolation and leakage requirements of the power supply behind it. B, BF and CF are not features; they are design targets confirmed in documentation. This guide explains the three patient-contact types, why BF matters for an adapter, how BF interacts with MOPP requirements, and how to verify the classification before sourcing.
Key takeaways
- B, BF and CF describe patient-contact types; BF applies to parts that contact patients.
- The classification drives isolation and leakage expectations for the power design.
- Verification is documentary: the certificate and report must name the classification and configuration.
Content updated: August 2026 — confirm current standards editions and model-specific details before ordering.
Scope note: This article is industry information about power-supply engineering, not regulatory, legal or certification advice. Standards applicability is decided by the buyer’s QA or regulatory team per configuration.
Patient Contact Types: B, BF and CF
The IEC 60601 framework classifies applied parts by how they contact the patient:
| Type | Contact | Typical example |
|---|---|---|
| B | Body, no direct patient contact intended | Handles, some external surfaces |
| BF | Contacting the patient, not directly conductive to the heart | Patient-contact sensors and pads |
| CF | Directly conductive to the heart | Cardiac-related connections |
The letter sets the expectation: CF carries the strictest requirements, BF sits in the middle, and B the least. For a power supply, the classification of the applied part determines the isolation and leakage limits the design must meet.
The classification is not a property of the power supply alone; it is a property of the device’s applied part as designed. The same adapter can support a B application or a BF application depending on the device it powers, which is why the certificate names the classification the configuration was tested against. A buyer who reads a “BF” label without checking the device design has read half the story.
The three types also explain a common confusion in sourcing: the classification letter is often mistaken for a product grade. It is not a quality ranking. A B-class design is not “worse” than a BF design; it is built for a different patient-contact situation. The requirement comes from the device program, and the design matches it — or it does not.
Why BF Matters for an Adapter
A BF-rated adapter is designed for applications where the applied part contacts the patient without being directly conductive to the heart. The practical consequences for the power supply:
- Leakage limits are tighter than for B-class applications.
- Isolation expectations are higher because the patient is part of the circuit path.
- Documentation must name the classification to make the design claim verifiable.
The adapter alone does not create the classification — the device design and its applied part do. The adapter must be specified to match the device’s classification, which is why the device program, not the adapter catalog, sets the requirement.
How BF Interacts With MOPP Requirements
BF and MOPP answer different questions. The classification (B, BF, CF) describes the patient-contact type; MOPP describes how many means of patient protection the design provides. A BF device can require one or two MOPP depending on the applicable requirements, and the isolation design must satisfy both the classification-driven limits and the MOPP count.
For buyers, the interaction means the document set must state both: the patient-contact classification and the MOPP level. A certificate that names one without the other leaves the design claim incomplete.
The interaction also affects how the power supply is reviewed when the device changes. If a device program moves an applied part from B to BF, the isolation and leakage expectations change, and the power supply’s documentation should be re-reviewed against the new classification. The same applies when a configuration moves from one MOPP count to another. Change management is part of the compliance story, and it is cheaper to review the document set than to discover the gap after shipment.
For the engineering team, the interaction is a design input rather than a label: the isolation barrier, the spacing and the leakage design are chosen to satisfy the classification and the MOPP count together. The certificate records the result, and the test report shows the measured values. Both are needed to verify the design claim, and both must name the same configuration.
Verifying the BF Classification
Verification follows the same documentary discipline as the rest of the medical power cluster:
- Confirm the device classification with the QA or regulatory team.
- Read the certificate — does it name the patient-contact classification and configuration?
- Check the test report — do the leakage and isolation results match the classification?
- Keep the batch records so reorders match the tested design.
The classification is a design claim until the certificate and report establish it. A “BF” label without documents is marketing.
The verification is only as strong as the standard edition it cites. Standards are revised, and the edition named on the certificate must match the edition the market requires and the device program expects. A certificate citing a previous edition should trigger a conversation about currency before the configuration is accepted, because the classification requirements can change between editions.
Verification also has a practical rhythm. The certificate is checked at selection, the test report at sample approval, and the batch records at every shipment. Running the three checks at three different moments, instead of once at the start, is what keeps the classification claim true for the units that actually arrive.
Sourcing Checklist for BF-Rated Power
- “Which patient-contact classification does the device program require?”
- “Does the certificate name that classification, the MOPP level and the exact configuration?”
- “What are the leakage and isolation values in the test report?”
- “Which standard edition applies, and does it match the market requirement?”
- “What batch documentation travels with the order?”
The checklist converts the classification question into a document question — and the document question is where sourcing decisions should be made.
The answers worth accepting follow a consistent shape: the certificate names the classification and configuration, the report contains the measured values, and the batch records connect the design to the shipment. Answers that describe intent without naming documents are not answers yet. Running the same five questions against every candidate keeps the shortlist comparable, which is the point of a checklist rather than a conversation.
For the supplier side, the same five questions serve as a self-check. A supplier that can answer them with documents has a program; one that cannot has a label. Buyers who insist on the documents from the first exchange set the tone for the rest of the relationship.
The BF discussion fits into a larger sourcing rule that applies across the medical power cluster: the classification and the MOPP count are confirmed before the configuration is compared, not after. Buyers who fill in the device program’s requirements first find that the shortlist shrinks quickly and the document review becomes a verification rather than an exploration. The classification question is the cheapest question in the program, and it is the one most often asked last.
For the power platform itself, the BF requirement shapes the design review even before the certificate exists. The isolation barrier, the leakage design and the test plan are chosen to meet the classification, and the certificate records the result. A buyer who understands the interaction can read the design’s intent from the documents and can push back when the evidence does not match the claim. That understanding is what separates a document review from a document browse.
The GaN Charger Category at WECENT organizes the platform lineup by power and ports, a practical map for programs that confirm patient-contact classification separately, and the WECENT FAQ answers the certification questions that come up during selection. For a program evaluating patient-contact classification and documentation, submit the device list and target markets to WECENT’s project engineering team — the review returns the document set and configuration options that apply to your exact program.
Frequently Asked Questions
What is the difference between B, BF and CF?
They describe patient-contact types: B for no direct patient contact, BF for patient contact without direct heart conduction, and CF for direct heart conduction. The stricter the type, the tighter the leakage and isolation expectations.
Does a BF adapter make the device BF?
No. The device design and its applied part create the classification; the adapter is specified to match it. The device program sets the requirement, and the adapter documents confirm the match.
How do I verify a BF classification?
Ask for the certificate and test report that name the classification, the isolation rating and the exact configuration. Documents, not labels, establish the claim.
Can one adapter serve both B and BF applications?
Possibly, if its design meets the stricter BF requirements and the documentation names both classifications. Confirm the certificate and the device programs before reusing a configuration.
What happens if the classification changes after sourcing?
The document set should be re-reviewed, because a different classification can change the isolation and leakage expectations. Change management and re-certification are part of the program, not an afterthought.