Product Classification

Recording access to hidden service programs

A device may have maintenance, debugging or engineering programs beyond its ordinary interface.

A device may have maintenance, debugging or engineering programs beyond its ordinary interface. The Chinese search terms “non-medical certification” and “non-medical notice” should be understood through medical-device classification and the exact wording of the relevant document. They do not describe a general product-safety certification. This article concerns evidence preparation and business decisions; it does not establish that any particular device has received a decision not to be regulated as a medical device. Establish whether these functions exist, who can activate them and what activation changes; screenshots of the normal user interface are insufficient.

Facts to establish

Start version control from identifiable deliverables, not a product name alone. Link main unit, handpieces, software, modes, accessories and key outputs. Explain how development, test, application and sales versions correspond. Similar appearance does not prove identical functions; a different name does not prove changed action.

How to move the project forward

For each change, review operating principle, method, body contact, output and intended purpose before assessing existing evidence and the scope of a classification conclusion. Record date, affected models, impact and documents to update. This is a review method, not a universal requirement to reapply for every change.

Service and supply-chain changes also need review. Replacing components, restoring programs or altering settings may change the installed configuration. Define permitted actions and records jointly with engineering and regulatory staff. Assess configurations that cannot be linked to the original; an unchanged nameplate is insufficient.

Decision boundaries

Ask the manufacturer to explain access, permissions and parameter changes, linking verified records to the relevant version. Effective access separation requires evidence; a salesperson’s claim that customers will not use a feature cannot exclude it from review.

For a concrete assessment, collect the model, current instructions, intended scenario and unresolved questions. Separate verified facts from assumptions before prioritising documentation, verification or actual product changes. An individual assessment does not replace a formal decision or guarantee an outcome, completion date or acceptance by every sales channel.

This article provides general compliance information and cannot replace a formal assessment of a specific product. Regulations, classification catalogues, guidance, and enforcement practice may change; each project should rely on the rules then in effect, the actual product, and formal documents.
Digital Project PortalCompliance Center Submit Assessment