Regulatory guidance and project coordination

Singapore Hsa Medical Device Registration Service

Scope and evidence must be confirmed before any paid tests or filings.

What an HSA filing project actually has to control

A Singapore HSA medical device registration filing is not just a portal upload. Before submission, the applicant should lock the device scope, risk class, evaluation route, grouping, Singapore-labelled use, configurations, product owner and Singapore registrant. The dossier then has to tell the same regulatory story across approvals, labels, technical evidence, manufacturing information and declarations.

For current filings, new product registration applications are submitted through HSA's Singapore Health Product Access and Regulatory E-System (SHARE). HSA's guidance library was updated on 30 September 2026 and lists GN-15-R15 and GN-17 R5 as October 2026 documents. A filing team should therefore work from the current HSA material rather than legacy MEDICS instructions.

Filing-readiness matrix

The quickest way to prevent a weak application is to resolve route and scope questions before building the upload set.

Control pointWhat to freeze before filingEvidence to have readyWhy it matters
Regulatory scopeMedical-device status and HSA risk classIntended use, device description and classification rationaleRisk class drives the available registration route and evidence depth.
Evaluation routeFull, abridged, expedited or immediate route only where the HSA criteria are metReference approvals, comparison of labelled use, marketing history and safety evidence where applicableA foreign approval does not by itself prove eligibility for every reliance route.
Application scopeSingle, Family, Group, System or other permitted groupingConfiguration/model matrix and grouping rationaleGrouping determines what may be included in one application; HSA determines the final SMDR listing, which may differ from the grouping submitted in the application.
Registrant authoritySingapore registrant and its authority to actCurrent Letter of Authorisation and consistent legal namesThe authority chain must match the applicant and product owner shown in the dossier.
Dossier basisCurrent submission format and route-specific document setCSDT/accepted dossier structure, declarations, QMS and technical evidenceSubmitting the wrong depth or obsolete templates creates avoidable deficiencies.
Singapore commercial versionExact intended use, labels, sites and configurations to be suppliedSingapore labels/IFU and reconciliation against reference-market approvalsThe Singapore application should not silently exceed the scope supported by the evidence.

Class A is different: HSA states that Class A devices are exempt from product registration, but a product notification in SHARE is required for Class A devices that are manufactured or imported. Classes B, C and D follow product-registration routes.

Who is responsible for what

PartyCore filing responsibilityExecution risk to control
Product ownerProvides controlled technical, clinical/performance, manufacturing, labelling and post-market information and authorises the registrant.Source documents must describe the same device and commercial scope submitted to HSA.
Singapore registrant / applicantCreates and submits the application in SHARE, makes authorised declarations, receives HSA correspondence and coordinates responses.Portal data, attachments and responses must stay version-controlled throughout review.
Manufacturer, importer or wholesalerMaintains the HSA dealer's licence required for the relevant Singapore activity and the associated quality/distribution controls.Dealer licensing is a separate regulatory workstream from product registration; one does not automatically replace the other.
HSAAssesses route eligibility and the submitted evidence, and may issue Input Requests for clarification or additional information.HSA turnaround time excludes the applicant's response time when the applicant stop-clock is running.

Dossier structure and pre-submission control

For Class B-D general medical devices, HSA's registration guides use the ASEAN Common Submission Dossier Template (CSDT) framework. The required depth depends on the class and route. Depending on the application, the dossier can include an executive summary, Essential Principles checklist and Declaration of Conformity, device description, design verification and validation evidence, clinical evaluation, labels, risk analysis, manufacturing and sterilisation sites, quality-management evidence and manufacturing information. Full evaluation normally requires the deepest evidence set, while reliance routes add proof that their specific eligibility conditions are satisfied.

Before upload, perform a cross-document consistency check:

  • product owner, device name, model and configuration logic are identical across forms, certificates, labels and technical evidence;
  • the Singapore intended use and labelled claims do not exceed the scope supported by the relied-on approvals or evidence;
  • manufacturing and sterilisation site names and addresses reconcile across QMS certificates and dossier sections;
  • clinical/performance, risk, software/cybersecurity, biocompatibility, sterilisation and shelf-life evidence is included where applicable to the device;
  • declarations use current HSA templates where required and are signed by the correct authorised party;
  • submission documents are in English, as specified in HSA registration guides.

IVD dossiers have their own HSA submission guidance. For IVD-specific execution, use the dedicated Singapore HSA IVD registration service page rather than applying general-device dossier assumptions.

Seven-step SHARE filing workflow

  1. Freeze the regulatory baseline. Confirm class, route, grouping, product owner, registrant, Singapore intended use and configurations before dossier assembly.
  2. Build the dossier map. Map each HSA requirement to a controlled source document, identify gaps and assign an owner and version for every file.
  3. Confirm applicant access and authority. Ensure the Singapore applicant can access SHARE through CorpPass and that the Letter of Authorisation supports the filing relationship.
  4. Create and submit the application. Enter the application data, upload the route-specific documents, perform a final portal-versus-dossier reconciliation and complete the required payment steps.
  5. Control HSA Input Requests. Treat each request as a deficiency package: identify the question, regulatory issue, evidence owner, response document and consequential updates to other dossier sections.
  6. Close the decision and listing. After approval, verify the registered particulars and Singapore Medical Device Register (SMDR) listing against the intended commercial scope and any approval conditions.
  7. Hand over to lifecycle control. Maintain retention, change assessment, post-market obligations and registrant/dealer alignment so the approved state remains controlled.

How to manage HSA Input Requests without creating new inconsistencies

Typical issueResponse packageControl check before replying
Route eligibilityReference approval evidence, labelled-use comparison, marketing-history and safety evidence as applicableDo not rely on evidence for a different indication, model or commercial version.
Technical evidence gapTargeted report, summary or justification answering the precise deficiencyUpdate the dossier index and identify whether the new evidence changes any earlier statement.
Label/configuration mismatchCorrected labels, configuration table and a reconciliation noteCross-check against approvals, Letter of Authorisation and the application scope.
Manufacturing/QMS questionSite-specific QMS evidence, manufacturing information or clarificationLegal names and addresses must match every affected dossier section.
Administrative clarificationCorrected application fields plus corporate/authorisation evidence where neededMake sure the correction does not unintentionally expand the registered product scope.

A response should be complete enough for HSA to close the question without reconstructing the answer from unrelated attachments. Because HSA's published TAT excludes the applicant's stop-clock, slow or fragmented responses can materially extend calendar time even when the authority's review clock is unchanged.

Common delay and rejection triggers

Unsupported route eligibility
Reference-market approval, marketing history or safety conditions do not satisfy the selected route.
Wrong classification or grouping
The risk class or application grouping does not match HSA rules, causing the dossier and route assumptions to unravel.
Reference-market scope does not match Singapore scope
The Singapore indication, claims, models or configurations are broader or materially different from the evidence used for reliance.
Defective authority chain
The Letter of Authorisation, applicant identity or product-owner details are outdated or inconsistent.
Cross-document identity mismatch
Model numbers, legal entities, manufacturing sites or labels differ across the portal, certificates and technical dossier.
Evidence depth does not match the route
A summary is filed where the route or device risk requires fuller underlying reports, or required route-specific declarations are missing.
Uncontrolled Input Request response
The reply fixes one document but leaves conflicting data elsewhere, or arrives slowly in multiple fragments.

What continues after registration

Approval is not the end of the regulatory file. Class B-D registrations listed in the SMDR are subject to annual retention. Changes to a registered device should be assessed against HSA's Change Notification framework before implementation where required. Companies dealing in medical devices also have applicable adverse-event and field-safety obligations.

A change of registrant is a distinct SHARE transaction and should be managed as a controlled handover of the listing, authority documents, open HSA matters and post-market responsibilities. Do not assume that changing an importer, distributor or corporate arrangement automatically changes the registrant shown in HSA records.

Where this filing-execution page stops

This page owns the mechanics of preparing, submitting and maintaining an HSA registration. For upstream decisions on classification, route selection, grouping strategy and gap analysis, use the Singapore HSA medical device registration consultant page.

For IVD-specific dossier execution, use the Singapore HSA IVD registration service page. For a wider country-level map covering product compliance and other Singapore market-access workstreams, use the Singapore product compliance and market access hub.

Official HSA sources to verify before filing

FAQ

Can an overseas manufacturer file directly with HSA?

The filing needs an appropriate Singapore applicant/registrant setup and an authority chain from the product owner. The registrant role should not be confused with the separate dealer's licences required for manufacturing, importing or wholesaling activities in Singapore.

Does a Class A device follow the same product-registration route?

No. HSA exempts Class A devices from product registration. For Class A devices manufactured or imported in Singapore, HSA requires product notification in SHARE instead.

Does an FDA, EU, Canadian, Australian or Japanese approval automatically qualify the device for a faster HSA route?

No. Prior approval can be relevant, but HSA route eligibility also depends on the device class and the criteria of the specific route, including matters such as the same labelled use, marketing history and safety record where applicable.

Should a new application still be prepared for MEDICS?

No. HSA's current e-service for new medical-device product registration is SHARE. Legacy documents or third-party pages that still describe MEDICS should be checked against current HSA instructions before they are used operationally.

What should be controlled after the device appears in the SMDR?

Maintain annual retention where applicable, assess proposed changes before implementation, meet post-market reporting duties, and keep registrant and dealer responsibilities aligned with the actual Singapore supply chain.

Responsible for publication: Khachatrian Razmik

Last updated: 2026-10-16

Related guidance