How to match a medical-device model to a certificate schedule
Read the certificate together with its model schedule: match the legal holder, exact model, device category, issue, printed period and assessment conditions. A valid-looking company certificate does not establish coverage of every product, and a model absent from an appendix must remain unconfirmed.
| Document example | What the supplied copy shows | What it does not establish |
|---|---|---|
| ISO 13485 CN15/30545 | A quality-management scope and listed sites for COMEN | Registration or approval of every device in this catalogue |
| SGS FI23/1008002 Issue 11 | V8 on page 5, EV3 on page 6, ME660 on page 7 | Coverage of ME600 by similarity to ME660 |
| SGS CN23/00001577 Issue 21 | MN family, C20/C21/C22 and NC5 on page 3 | Interchangeability of configurations or patient-group instructions |
| BSI MDR record | An issued record and a separately identified invalid draft | A draft becoming an issued certificate because its number looks plausible |
Start with document identity and holder
Use the original PDF rather than a cropped badge. Record the certificate number, issue, holder, pages and source-file hash. The supplied records name Shenzhen Comen Medical Instruments Co., Ltd. as holder. Abyssalmed/WANLIN publishes these copies; the records do not establish that the website publisher owns the certificates or has distributor authorization.
Find the exact model in the appendices
Read every relevant schedule page and retain the model spelling, grouping and stated conditions. FI23/1008002 lists ME660; that is not evidence for ME600. For EV3, the stated patient-weight scope must remain attached to the entry. Do not turn a broad device category or a family-like name into an unsupported exact-model match.
Separate documentary review from issuer verification
A printed validity period and a matching hash describe the supplied copy. They do not independently establish current issuer status or validate a cryptographic signature. Use the issuer route linked in the register and request the applicable model-specific declaration, instructions and destination documentation. The current site registry explicitly distinguishes these verification states.
Maintain the evidence record when documents change
Retain the prior document and its hash, record the new issue and compare the schedules. Recheck affected model pages and quotations rather than simply changing an expiry date in a badge. An invalid draft or an internal audit record must not be substituted for an issued public certificate; this site does not publish those originals as product certifications.
Does an ISO 13485 certificate prove device registration?
It describes the stated quality-management scope. Check model-specific and destination requirements separately; do not infer universal product approval.
Can an expired or superseded copy simply be removed from the record?
Keep an internal history and clearly identify which copy supports the current claim. Request the replacement evidence before changing the public status.