A charging connector has to fit the PCB footprint, mate through the enclosure and withstand the loads expected in use. Checking the footprint alone will not answer all three questions. Medical device PCB design starts by assigning the relevant device requirements to board features and identifying which checks need the assembled product.
The device manufacturer owns the broader design decisions; PCB and assembly teams need enough information to implement and verify their assigned portions. For supplier evidence and release considerations, see the high-reliability medical and aerospace PCB and PCBA guide.
Start with the device, not a generic PCB checklist
Before selecting materials or drawing the stackup, the hardware team and device owner should agree on the operating context and design assumptions:
- How is the device powered, charged and used?
- What connects to the board, and what mechanical loads might those connections impose?
- Which functions are sensitive to electrical noise, interruption or component variation?
- What enclosure features constrain the board, connectors and assembly sequence?
- Which risks require controls at board level, device level or both?
- What documentation and verification must accompany a design change?
The answers become board-level constraints: component ratings selected against the intended operating conditions, connector locations and retention features, mounting clearances, layout boundaries, test access and approved component choices. Record the rationale and owner for each constraint rather than treating the layout as the only source of design intent.
Standards inform allocation; they do not replace it
The FDA’s Quality Management System Regulation (QMSR) took effect on February 2, 2026 and incorporates ISO 13485:2016 by reference. It applies to finished-device manufacturers. The device manufacturer and its regulatory team should determine applicable obligations and how supplier work fits its quality system.
Other sources are conditional on the product and its use:
- FDA’s Electromagnetic Compatibility (EMC) of Medical Devices guidance addresses EMC information for medical devices. Board design and board tests can support that evidence, but the integrated device remains important.
- IEC 60601-1, Medical electrical equipment — Part 1: General requirements for basic safety and essential performance, applies to medical electrical equipment and systems when relevant. It is not a blanket specification for every medical product.
- FDA’s guidance Use of International Standard ISO 10993-1, “Biological evaluation of medical devices — Part 1: Evaluation and testing within a risk management process” concerns relevant devices with direct or indirect body contact. It should not be applied indiscriminately to every PCB material.
For a closer look at safety context, see IEC 60601 and electrical safety. These sources are not a substitute for product-specific regulatory assessment. There is likewise no single IPC class that can be assigned to all medical products; the device team should select and document applicable acceptance criteria.
Use a requirement-to-board allocation matrix
A matrix makes it easier to see where a board check ends and integrated-device evidence begins. Use requirement identifiers from the device design records, and add references to the relevant drawings, risk controls and verification plans.
| Requirement or risk control | Layout or assembly implementation | Board verification | Remaining integrated-device evidence | Accountable owner |
|---|---|---|---|---|
| Device requirement or identified risk control, with rationale | Specific features, component choices or process instructions | Inspection, measurement or test proposed for the board or assembly | Checks that require the enclosure, software, accessories or complete device | Named role responsible for the requirement and disposition |
A board verification entry should identify the method, acceptance criteria, revision and record location. The criteria come from the device design and risk assessment. An inspection result can show that a feature matches a drawing; it does not automatically show that the feature controls the device-level risk.
Hypothetical example: a battery-powered external monitor
Consider a proposed external monitor with a sensor interface, a battery, a charging connector and an enclosure. Its team uses revision-controlled component substitution. This example does not assume patient contact, a regulatory classification, a particular isolation architecture or test thresholds.
The following are proposed allocations and checks, not test results.
| Requirement or risk control | Layout or assembly implementation | Board verification | Remaining integrated-device evidence | Accountable owner |
|---|---|---|---|---|
| Preserve sensor-interface performance during intended operation | Define sensor routing and placement constraints, reference paths and separation from potentially noisy circuits based on the design analysis | Inspect layout against the constraints; plan an assembly-level functional check if suitable test access is available | Evaluate sensor performance in the assembled device under relevant operating and charging conditions | Device hardware lead |
| Support the intended charging interface | Specify the connector, footprint, orientation, mating geometry and relevant electrical ratings in controlled design files and BOM | Inspect connector placement and assembly; plan electrical checks against documented board criteria | Check charging behavior and connector use with the enclosure and intended mating accessory | Charging subsystem lead |
| Maintain board fit and connector alignment | Define board outline, mounting features, keepouts and connector position relative to the enclosure datum | Measure or inspect the board and assembly against controlled mechanical requirements | Assess fit, access and connector engagement in the assembled enclosure | Mechanical lead |
| Control an approved component substitution | Identify the approved part and alternatives by revision; record any footprint, electrical or assembly constraints | Confirm the assembled part and revision against the released BOM; perform applicable checks from the change plan | Reassess device-level verification affected by the substitution | Device manufacturer’s change owner |
The matrix helps the team avoid two common handoff errors: asking an assembler to infer the intended control from a drawing, and assuming a board-level pass closes a device-level requirement.
Turning the matrix into layout decisions
The matrix should influence design reviews while changes are still manageable.
For the sensor interface, identify the signals and circuits whose performance matters, then document routing, placement and return-path constraints that support the design. If charging or digital activity could affect measurements, plan how to examine the interaction. A board functional test may be useful, but the enclosure and operating configuration can change the result.
For charging, review the connector and its surrounding circuitry together. Electrical ratings, footprint dimensions, orientation and mating access all matter. The team should also consider how repeated connection forces reach the board and enclosure. The appropriate mechanical design and verification depend on the product, not on a universal connector rule.
For enclosure fit, exchange controlled mechanical data early. Board thickness, component height, mounting points and connector position can affect assembly and use. A dimensional board inspection is useful evidence, while an assembled-device fit check addresses interactions the bare-board drawing cannot show alone.
For test access, decide which board functions need to be checked before the enclosure is closed. Document accessible nodes, fixtures or interfaces needed by the proposed test approach, along with the limits and ownership of the test. The PCBA functional test planning guide provides further context.
A DFM review should complement these design decisions. It can surface fabrication and assembly questions about features such as spacing, component placement and access, but it should not silently replace a risk control. See the PCB layout DFM guidelines.
When a DFM recommendation affects a design requirement
Suppose the assembler reviewing the hypothetical monitor says that a test point beside the charging connector is difficult to reach with the proposed fixture and asks to move it. The device team can use the following record to resolve the question:
| Record | Example decision to make |
|---|---|
| Finding | Identify the test point, board revision and fixture-access problem. Ask for the access constraints or a drawing of the proposed location. |
| Affected requirements | Check the test plan and circuit design to establish what the point measures and whether the proposed location still accesses the intended net. Review any effect on nearby routing and enclosure clearance. |
| Proposed disposition | Accept a specified new location, propose a different fixture approach, or retain the original location with an agreed alternative test. A DFM suggestion alone does not authorize a layout change. |
| Evidence and release | The responsible design and test owners review the decision. If the design changes, update the affected board and test documents, then verify the new revision against the approved criteria. |
If the supplier cannot reach an agreed test point and no alternative check has been approved, leave that test requirement open. A board can be manufacturable while a required verification step is still unresolved.
Evaluate a prospective charging-connector change
Suppose the team proposes a different charging connector because the specified component is difficult to obtain. The alternative should not enter production merely because it has a similar description or appears to fit the footprint.
A controlled review could proceed as follows:
- Identify the change. Record the current and proposed manufacturer part numbers, affected BOM and drawing revisions, reason for the change and any open questions.
- Compare the design attributes. Review electrical ratings, pin assignment, footprint, height, orientation, mating interface and retention or mounting features against the device’s documented needs. Check the proposed part against the board and enclosure data.
- Assess affected requirements and risks. Update the allocation matrix to identify which charging, fit, assembly and user-interface assumptions may change. Determine whether the proposed part changes any prior verification assumptions.
- Define verification before use. Depending on the impact assessment, the plan might include footprint and assembly inspection, board-level charging checks, enclosure fit and mating checks, and relevant integrated-device testing. Record acceptance criteria and responsible owners.
- Approve or reject through the device manufacturer’s change process. Capture the decision and required evidence. If approved, release the updated BOM, drawings and instructions together; if not approved, retain the original requirement or assess another option.
- Verify the implemented revision. Confirm that the build uses the released component and complete the checks required by the approved plan. Record actual results separately from the proposal.
The hardware, mechanical, manufacturing and quality representatives can each contribute to the assessment. The device manufacturer’s designated change owner remains accountable for the final disposition and for deciding whether integrated-device evidence must be repeated or supplemented.
For BOM structure and substitution controls, see assembly BOM best practices.
Prepare the manufacturing handoff
A useful handoff package lets the manufacturing team identify the intended revision, build it without guessing and raise exceptions before an unapproved change occurs. Agree the exact package and deliverables with the prospective supplier.
| Handoff item | What to make clear |
|---|---|
| Fabrication data and drawings | Board revision, stackup intent, dimensions, applicable fabrication requirements and specified acceptance criteria |
| Assembly data | Assembly revision, component placement and orientation, assembly notes and relevant mechanical constraints |
| Controlled BOM | Manufacturer part numbers, approved alternatives if any, revision and substitution approval route |
| Test and inspection plan | Proposed checks, access requirements, acceptance criteria, responsibilities and required records |
| Change and deviation instructions | Who can approve a departure, how questions are raised and which documents must be updated |
| Traceability expectations | The identifiers and records needed to connect the build to its applicable design and material revisions |
Traceability requirements should be specific enough to be actionable: state what must be identified, what record is expected and who retains it. See PCB traceability and lot control.
When reviewing supplier feedback, distinguish a proposed manufacturing change from an approved design update. Assess its effect on allocated controls and verification before releasing it.
Use supplier evidence within its limits
Supplier documentation, inspection and board-level test records can support the device manufacturer’s design history and release decisions. They can show what was built or checked against agreed criteria. They do not, on their own, establish final device safety, regulatory compliance, clearance or suitability for the intended use.
For a manufacturing discussion, share the controlled design package and identify open decisions such as connector alternatives, inspection criteria and proposed functional checks. Confirm what the supplier can provide rather than assuming a particular capability or test result.
Explore medical PCB manufacturing information, request a quote, or contact APTPCB to discuss the proposed handoff.