Engineering resource
Patient monitor PCBA: documenting isolation requirements
A patient monitor PCBA release should describe where isolation is required, what each barrier is intended to achieve and which controlled requirements govern its implementation. A note saying “medical isolation” does not give a manufacturer enough information to inspect a board, evaluate a substitution or execute a test. The design authority must translate the system safety assessment into specific drawings, material identities and approved verification instructions.
This article concerns that engineering handoff. It is not a table of universal spacing or test-voltage values, and it does not establish product certification. Requirements depend on the intended equipment, interfaces, environment and applicable evaluation framework. The purpose of the release packet is to preserve those decisions so that procurement, fabrication, assembly and testing implement the same approved design.
Start with a system connection map
Draw the monitor’s major electrical domains and every external connection relevant to the assessment. Include the patient-connected circuitry where present, processing electronics, power sources, communications, displays and accessories. Show grounds and shields explicitly. A block diagram that hides power connections behind a generic arrow may omit the path that matters most to the isolation review.
Include normal accessory combinations and service connections in the design review. An interface that is unused during a simple bench demonstration may be connected in the intended product configuration. The responsible system engineer should decide how it is treated, and the drawing should record that decision. The assembly team cannot determine the intended safety boundary merely by looking for a visible isolator on the PCB.
Analog Devices’ CN-0571 reference design illustrates isolation in an HDMI interface and includes a healthcare system barrier example. It considers more than the main video data path, including auxiliary signals and power. The relevant lesson for a release review is to account for the complete interface; the reference design’s ratings and topology do not automatically apply to another patient monitor.
Assign an identity and owner to every barrier
Give each required boundary a stable identifier that appears in the schematic review, layout notes and test documentation. For example, a project might label the boundary between an acquisition domain and a processing domain as B1, while a separate external interface is B2. These names are organizational examples, not a recommendation for how many barriers a product needs. The approved system architecture determines that.
For each identifier, record the domains on both sides, the reason for the isolation, the governing requirement reference and the engineer responsible for approval. Include the operating and environmental assumptions used in the assessment. If an assumption changes, the team can identify which boundary needs review rather than searching the entire project history for an informal explanation.
Keep unresolved decisions visible. If the accessory configuration or operating environment has not been finalized, mark the affected requirements as pending. Do not fill a missing value with a convenient component rating or a value from a different project. A controlled open item gives purchasing and manufacturing a clear hold point; an invented requirement can create a board that looks complete but cannot be accepted.
Record what each isolation parameter means
Use the parameter names from the applicable component documentation and approved design requirements. A withstand test rating, a working-voltage specification and a transient capability describe different conditions. Preserve their units, waveform assumptions and duration where relevant. Avoid reducing a collection of ratings to a single “isolation voltage” column that makes unlike quantities appear equivalent.
TI’s creepage and clearance training distinguishes the two spacing concepts and identifies working voltage and operating environment as inputs to their determination. For the manufacturing handoff, record the requirements that the responsible engineer has established and how they are implemented on the actual assembly. Do not let a layout measurement substitute for the earlier decision about what spacing is required.
The comparison should be explicit: requirement reference, implemented feature, supporting evidence and disposition. If the design uses a slot, a particular material or a mechanical separation feature, identify it in the drawings and state its approved purpose. The reviewer should be able to trace the requirement into the released data without relying on the original designer’s memory.
Keep component evidence tied to the exact ordering code
List the full manufacturer part number and package for every component whose identity is important to the boundary. Include the applicable certificate or manufacturer evidence and its scope. Similar functional descriptions are insufficient when packages or variants differ. A device that performs the same data-transfer function may not carry the same isolation evidence or physical construction.
Analog Devices’ isolation certification directory, updated September 2026 when reviewed, organizes ratings and certificate links by product. Use the underlying document for the selected device and its conditions rather than relying only on a family-level marketing statement. Component evidence supports the design review; it should not be described as certification of the complete PCBA or monitor.
Define who reviews a proposed alternate before procurement. The request should include the original and proposed identities, the affected barrier and the relevant evidence comparison. If approval is limited to an evaluation build, keep that restriction on the purchase and assembly records. A shortage should not silently convert a controlled safety-related item into an unrestricted equivalent-parts line.
Make the boundary visible in fabrication data
Provide the fabricator with unambiguous layer data, board outline and the specific features needed to implement the approved design. Reconcile dimensions and notes across drawings. Where material properties are part of the requirement, identify the approved specification and how substitutions are handled. A generic board material description may not preserve the assumptions used by the design authority.
Review the final copper data around the boundary after pours and manufacturing outputs are generated. Check that later edits to test points, mounting features or connectors have not changed the reviewed implementation. The release checklist should identify which data set was inspected. A screenshot from an earlier layout is weak evidence if the actual fabrication files have a different revision.
Ask for clarification when the quoted construction differs from the drawing. Resolve the discrepancy before manufacture and preserve the disposition. The manufacturer should not have to choose between two inconsistent documents, especially where a feature’s purpose is not obvious from appearance. Clear release-file readiness checks help expose these conflicts before they become physical boards.
Carry the requirement into assembly instructions
Identify placement, lead preparation, hardware and wiring details that can affect the implemented boundary. A correct bare board does not guarantee that every later assembly operation preserves the intended separation. Show the approved routing and retention of wires or other added items where relevant. Instructions should describe an inspectable condition instead of asking operators to apply their own interpretation of isolation.
Define any cleaning, coating or encapsulation process that the design actually relies upon. Record the material identity, controlled process and acceptance evidence. Do not assume that adding a coating resolves an unspecified spacing issue, and do not substitute a different material without review. The design authority must decide what role the process plays in the approved construction.
Include repair restrictions and escalation points. If an assembly defect occurs near a controlled boundary, the repair instruction should state what may be done and which verification follows. Preserve the original failure and the repair history. A successful functional retest alone may not answer the question raised by a change to the physical construction.
Separate design evaluation from routine production testing
The product’s evaluation plan and the factory’s routine acceptance test serve related but distinct purposes. The responsible engineer should specify which checks are required during development or qualification and which are performed on production units. Manufacturing needs an approved procedure with defined connections, equipment, limits, sequence and handling of abnormal results. It should not derive those settings from a headline device rating.
Describe the unit’s configuration during each check. Identify attached cables, accessories, shields and any temporary test connections. If a fixture changes how domains are connected, review that arrangement rather than assuming it is neutral. The record should state what was actually tested so that the result can be interpreted against the requirement it is meant to support.
Keep functional performance results separate from isolation-related evidence. Communication across an isolator demonstrates a functional path under the test conditions; it does not establish every insulation requirement. Similarly, a specified electrical acceptance check does not establish all aspects of signal integrity or application behavior. The release report should connect each result to a specific requirement without expanding its meaning.
Use an interface example to check for omissions
Consider a hypothetical monitor with an acquisition board, processing board and external display connector. The engineering team marks the acquisition boundary and records its approved components. During a later review, the display interface is added to the connection map along with its auxiliary signals and power. The team then checks whether the new configuration changes the original assessment before releasing the updated assembly.
The important output is not a generic instruction to isolate every connector in the same way. It is a documented decision for the particular architecture. The resulting release might update a schematic, an approved component list, a mechanical instruction or a verification procedure. Each changed document should refer to the same revision and have an owner responsible for confirming that the implementation matches the decision.
Use this walkthrough at a design transfer meeting. Ask one participant to follow the boundary from the system map through procurement evidence, PCB data, assembly instructions and test records. Any point that depends on an unwritten assumption becomes a concrete action item. This is often more useful than checking that a folder contains many documents without verifying how they relate.
Retain evidence that can be retrieved for a specific build
The finished record should connect the board revision, approved component identities, relevant material lots, process records and acceptance results to the build or serial range. Agree the retention and retrieval expectations in the project quality plan. The purpose is to make the implemented configuration knowable if a later change notice or field investigation requires review.
Discuss quality and traceability planning before production so the required data can be collected at the appropriate steps. A requested record cannot always be reconstructed after material has been mixed or labels discarded. Define the evidence needed for this product rather than promising an unspecified level of traceability.
Before you request a project review, assemble the boundary map, approved requirements, exact component evidence and manufacturing test scope. Identify open decisions and the person authorized to close them. That packet gives the supplier concrete instructions while preserving product-level evaluation and approval with the responsible design organization.