Data Matrix Readability vs Verification: What Medical Device Buyers Should Specify
A scanner result, a data match and a DPM quality report answer different questions. Use this decision matrix to specify the functions your medical marking project actually needs.
Read the guideOn this page
“The camera read the code” is not the same statement as “the encoded data matched the approved order” or “the direct-part mark met the agreed symbol-quality criteria.” Specify those three outputs separately. Then decide which must run on every production part and which require a defined verification or audit method.
This guide helps medical-component buyers choose inspection functions and interpret supplier demonstrations. For laser source, material and station selection, use the medical UDI marking and traceability pillar. For the wider sample handoff, use the six-gate marking acceptance checklist.
1. Ask three different questions
| Function | Question answered | Output to request |
|---|---|---|
| Code reading | Can this configured reader decode this mark under the tested conditions? | Decoded string, read/no-read result and relevant setup |
| Approved-data comparison | Does the decoded information match the expected part and work order? | Expected value, actual value and match/mismatch decision |
| Symbol-quality verification | What result does the mark achieve using the agreed measurement method? | Quality report, method, settings and acceptance decision |
A system can combine these functions, but its interface should not collapse them into one unexplained pass flag. Ask which results are measured, which are calculated, and which are merely imported from another device.
The GS1 DataMatrix Guideline distinguishes scanning from verification and addresses both encoded data and symbol quality. Use the applicable issuing-agency and application requirements for your project, not an assumption that every Data Matrix is a GS1 UDI.
2. Specify the reading environment, not just a camera model
Describe the actual part surface, curvature, mark location and allowed presentation variation. Identify fixture orientation, working distance, illumination, expected viewing direction and the time available for a read. Include whether the part is stationary or moving and whether another operation can shadow the mark.
For a production reading trial, retain the reader configuration and the tested part conditions. Deliberately include agreed variation rather than repeatedly reading one favorable sample. Report no-reads and retries, not only the final successful decode. If manual repositioning was needed, preserve that fact because it changes the proposed automation task.
A production reader's performance result applies to that tested configuration. It should not be presented as a universal quality grade or as proof that all downstream readers will behave identically.
3. Compare decoded content with an independent expected value
Define who supplies the expected record and when it becomes authoritative. Keep the reference independent of the marking output: copying the decoded string into both “expected” and “actual” fields cannot detect a wrong identifier.
Agree the comparison rule for each field, including formatting and any meaningful separators or leading characters. If the system parses a structured message, request the raw decoded string as well as the interpreted fields. That makes an interface-format issue distinguishable from a physical marking defect.
Use controlled tests for wrong work orders, repeated identifiers where prohibited, absent input and malformed messages. State the allowed response and the authority needed to resume. These are proposed challenge cases; the project team chooses those relevant to its identifier-management policy.
4. Define a verification method and a report
For a direct-part mark, identify the required specification and edition, verifier configuration, measurement conditions and acceptance criteria in the project document. ISO's public ISO/IEC 29158:2025 scope identifies DPM symbol-quality measurement and reporting as distinct concerns. The appropriate project criteria cannot be inferred from the standard's title.
Ask the supplier what is included in a claimed verification function: instrument, software option, setup checks, report export and linkage to the physical sample. If a camera offers a proprietary quality score, label it accordingly and assess whether it satisfies the specified task. Do not silently rename a vendor-specific score as a standards-based verification grade.
Retain the report's relevant settings alongside its outcome. A number without a method, setup and sample identity is difficult to compare or reproduce.
5. Decide how to handle disagreeing results
Plan for a code that reads successfully but contains the wrong approved data. The data mismatch should remain visible even if the optical reading is easy. Likewise, a correct decoded value should not erase an unacceptable verification result where verification is required.
When a production reader fails but a separate verifier produces a result, investigate the reader presentation and settings without rewriting the mark history. When verification is inconclusive, retain the incomplete state and route it to the designated reviewer. Define containment and any permitted retest; do not allow repeated attempts to hide the first result.
6. Turn the distinction into a purchasing specification
- List reading, data comparison and verification as separate scope lines.
- State which parts are inspected, at which process stage and under which setup.
- Define record fields, report formats and the physical-sample reference.
- Include controlled exception tests and the decision owner for each outcome.
- Ask for included functions, options and customer-supplied interfaces separately.
Use this list to review the medical UDI laser-marking and vision-traceability system. Specify the inspection configuration your workflow needs rather than assuming one camera performs every role. Explore the medical manufacturing application hub, or send your code examples and inspection specification for an equipment proposal.