Medical sensor PCBA: defining traceability before sourcing

A medical sensor PCBA quotation should define what can be traced before anybody purchases the first reel. A supplier’s invoice identifies a transaction; a board serial number identifies an assembly. Neither automatically connects the sensor fitted to that board with its original package, programming history and measurement record. That connection must be designed into the manufacturing handoff.

This article proposes a practical component-to-board record structure for an engineering team preparing a sensor assembly. It addresses procurement and production evidence, not approval of a finished medical device or a claim that a particular assembler holds a certification. The product owner must establish the applicable product requirements and the records needed for its own quality system.

Write the question that the record must answer

Start with concrete retrieval questions. Given a returned board serial number, can the team identify the fitted sensor part number, incoming material record, firmware revision and final test result? Given a suspect incoming lot, can it identify the assemblies that might contain that material? These forward and reverse questions reveal gaps that a long list of retained documents can conceal.

Decide the resolution needed for each component group. Some records may be associated with a manufacturing lot, while selected devices require an individual identifier. Explain why that resolution is adequate and what uncertainty remains. If production cannot determine exactly where a reel change occurred, the affected assembly range must include that uncertainty instead of presenting an unjustifiably precise boundary.

Record this scope in the quality and traceability plan before requesting prices. The quotation should distinguish ordinary material identification from additional scanning, record retention, unit-level association and retrieval exercises. Otherwise, two suppliers may offer materially different evidence while both describe their service as traceable assembly.

Separate material traceability from measurement traceability

Material traceability concerns the identity and history of what was fitted. Measurement traceability concerns the basis of a measured result. A board can have excellent purchasing records but an inadequate calibration record, or a well-documented measurement without a clear link to the installed sensor. Specify the two chains separately and then identify where they join.

Texas Instruments’ April 2025 overview NIST Traceability for Temperature and Humidity Sensors describes different traceability tiers in its sensor portfolio. Some use shipment-label lot information; others provide a device identifier, and label requirements differ by tier. Check the exact selected product and required retrieval process. Do not assume that every sensor in a manufacturer’s catalog exposes an individual identifier or the same supporting information.

For a product that offers an electronic identifier, specify the readout procedure and how the result is linked to the assembly serial number. For a label-dependent product, specify when the original label is captured and which record preserves that association after parts leave the package. Establish these steps while the material is still identifiable; reconstructing them after assembly may be impossible.

Capture supplier identifiers without inventing a universal format

Keep the manufacturer’s label fields in their original form and record the supplier and purchase reference alongside them. TI’s quality and packaging FAQ distinguishes its Ship Trace Code on the shipping label from its Lot Trace Code on the device. This illustrates why a single spreadsheet column called “date code” is an inadequate substitute for identifying the actual field being captured.

Do not apply one manufacturer’s code interpretation to another. Let the manufacturer documentation define the meaning, and store a readable label image when it forms part of the agreed evidence. Preserve leading zeros and punctuation in identifiers. A spreadsheet that automatically converts a code into a number or a date can destroy the value needed for a later lookup.

At incoming inspection, compare the ordered manufacturer part number with the supplied label and the approved BOM. Record discrepancies separately from accepted stock. If the distributor repackages a small quantity, ask what traceability documentation accompanies the repacked material and whether it meets the project requirement. A supplier statement should be linked to the received material record rather than stored in an unrelated purchasing folder.

Preserve the relationship when a reel becomes several kits

Splitting material is a common point at which the physical item and its history separate. Give each issued container or kit an identifier connected to its parent receipt. Record the quantity issued, destination build and any returned balance. The purpose is not to create paperwork for every movement; it is to avoid an unidentified container entering production with no defensible origin.

For feeder changes, define the event that closes one material interval and starts the next. If the process associates material at panel level, include the panel identifier and how individual boards inherit it after separation. If the association is only at work-order level, state that limitation. Do not describe work-order tracking as exact component-to-unit tracking unless the process really establishes that relationship.

Plan for interruptions. A partially used reel returned to stores should retain its identity and required handling record. Material removed from a feeder should not be merged with an indistinguishable balance merely because the part number matches. The released process should tell operators when merging is allowed, how the record is updated and who resolves uncertain identity.

Use a retrieval exercise before accepting the process

Consider an illustrative pilot build using two sensor receipts, called A and B. The assembler starts with A, changes to B during the build and replaces one sensor during rework. Ask the team to retrieve the history of a selected finished board without relying on the memory of the person who assembled it.

The retrieved record should identify the board revision, the applicable material receipt or bounded set of possible receipts, the programming configuration, the measurement result and any replacement event. Then reverse the exercise: choose receipt A and ask which boards require review if that receipt becomes suspect. Include the reworked board in the exercise so that the team must distinguish the removed sensor from the installed replacement.

If the records cannot answer these questions, document the missing association and improve the process before increasing the batch size. Do not fill the gap with an assumption that the first half of the serial numbers used the first reel unless that sequence was actually controlled and recorded. A candidly bounded population is more useful than a precise-looking list based on inference.

Attach test data to the configuration actually tested

A result file should identify the assembly, procedure revision and relevant programming state. Where calibration or adjustment is performed, record the parameter set and the approved method of associating it with the device. Separate the original measurement from any calculated correction and retain the information needed to interpret both. An isolated “pass” entry may be insufficient for an engineering investigation.

Decide what happens when the firmware changes after testing. The release owner should specify whether the earlier result remains applicable and which checks must be repeated. The same applies when a sensor is replaced or a configuration file is restored. A unit should not inherit an acceptance result from a materially different configuration simply because its label did not change.

Keep patient information out of routine manufacturing examples and test fixtures unless a specifically approved process requires it. Engineering reference inputs and controlled test data can establish the intended checks without attaching personal records to a production traveler. Define the test evidence that is necessary for the manufacturing decision and avoid collecting unrelated data.

Make change notifications part of purchasing review

Assign an owner to monitor manufacturer notices for the controlled BOM. Analog Devices describes its Product Change Notices and Product Discontinuance Notices on its product life-cycle information page. Receiving a notice is only the start of a review; the product team still needs to determine which part, revision and planned purchases it affects.

Link the decision to the approved BOM and purchasing instructions. If a change requires evaluation, identify the material that can continue to be used and the material that is held pending approval. Do not replace a technical review with a blanket rule that all newer date codes are better or that all older inventory is unacceptable. The relevant manufacturer information and the product’s defined requirements should drive the decision.

For alternatives proposed during a shortage, require the full manufacturer part number and written disposition. The traceability record should show the approved substitution at the affected references, not merely record what happened to be available. Where approval is limited to a particular build, prevent that exception from becoming an unrestricted BOM change.

Agree retention and retrieval before the order

Specify the format in which records will be supplied and how the customer can retrieve them later. Include access responsibility, retention expectations and the treatment of corrected entries. Avoid an arrangement in which only one operator can open a proprietary station file and nobody can associate it with a shipped board after that operator changes roles.

Test the correction process with a deliberately identified clerical error in a sample record. The corrected version should preserve the original entry, the reason for correction and the responsible approver according to the agreed system. Do not demonstrate this by altering a real production result. The exercise should show how a user distinguishes a corrected association from an unexplained overwrite, and how the corrected information reaches everyone who received the earlier record.

Also define the response when an expected label image or station file cannot be recovered. Identify who assesses the gap and what evidence can legitimately resolve it. A missing record should remain an explicit exception until disposition, rather than being replaced with a similar record from another receipt. This preserves the difference between known manufacturing history and assumptions introduced during a later investigation.

Require a sample delivery package during the pilot. Check that identifiers are readable, links between files work, revisions are explicit and the customer can answer the agreed retrieval questions. Record any missing evidence as an acceptance issue with an owner and due date. The number of uploaded files is not a useful completion measure if the files cannot be reconciled.

Before you request a project review, prepare the BOM, board revision, proposed traceability fields, test scope and a sample record layout. Use the release-file checklist to identify incomplete inputs. A clear handoff lets the supplier quote the actual recordkeeping work and lets engineering verify that the delivered assembly history answers the questions the product requires.