Bhutan DRA (Drug Regulatory Authority) and the Bhutan Food and Drug Authority
Understand Bhutan DRA and BFDA’s published responsibilities while distinguishing official information from practical manufacturer-side preparation.

On this page · 11 sections
- 1Bhutan DRA: former authority, legal basis and the BFDA merger
- 2BFDA’s published divisions and services: who handles which subject
- 3Product scope in Bhutan: distinguish historical coverage from enquiry routing
- 4Drug-RIMS: the official access point and a controlled handoff
- 5Agency, division, portal and decision: terms that are not interchangeable
- 6A manufacturer-side lifecycle from product scoping to ongoing follow-up
- 7What manufacturers keep ready: product records, quality evidence and versions
- 8Internal system handoffs and recovery when a submission is uncertain
- 9Three worked cases: shared evidence, conflicting descriptions and uncertain transmission
- 10Failure modes that leave a regulatory case difficult to review
- 11A practical readiness review before the next authority interaction
How does DRA (Bhutan) apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Bhutan DRA: former authority, legal basis and the BFDA merger
Bhutan DRA means Bhutan’s former Drug Regulatory Authority. In this article, “DRA” refers only to that Bhutanese authority. The historical name remains useful when interpreting older correspondence and product records, but it should not be treated as the name of a separate present-day agency alongside the Bhutan Food and Drug Authority (BFDA).
BFDA’s account of DRA describes it as an autonomous agency instituted under the Medicines Act of Kingdom of Bhutan 2003. This is BFDA’s description of the former authority’s legal basis, not an interpretation of individual provisions of that Act. It establishes the institutional background; it does not, by itself, establish a manufacturer’s obligations for a particular product.
BFDA describes three predecessor agencies as merged into the Bhutan Food and Drug Authority: the Drug Regulatory Authority, the Bhutan Agriculture and Food Regulatory Authority, and the Bhutan Narcotics Control Authority. Its Background page places that merger in line with the provisions of the Civil Service Reform Act of Bhutan 2022. Here, 2022 belongs to the Act’s title; it should not be used as an effective merger date.
Handling the historical name in manufacturer records
As a document-provenance practice, retain the agency name appearing on an original letter, certificate or other record. Separately record the current enquiry contact and the subject of the enquiry. Do not silently replace “Drug Regulatory Authority” with “Bhutan Food and Drug Authority” inside historical correspondence: that would obscure who issued or received the document at the time.
For example, an internal index can preserve “Drug Regulatory Authority” in an original-addressee field while maintaining a separate current-contact field for follow-up. This is a recommended records convention, not a Bhutanese legal requirement. For exporters working across markets, also label the jurisdiction explicitly: keep Bhutan’s agency history separate from records concerning Pakistan’s DRAP, rather than grouping authorities by similar acronyms.
02BFDA’s published divisions and services: who handles which subject
BFDA’s Divisions page provides a starting directory for identifying the subject of an enquiry. The main entries below preserve its displayed headings. Read their descriptions as regulator website guidance, not as a complete legal allocation of powers or a product-specific routing decision.
| Displayed entry | What BFDA states |
|---|---|
| Controlled Substance and Medical Device Division (CSMDD) | BFDA describes its coverage as narcotics, psychotropics and medical devices. |
| Food Quality and Safety Division (FQSD) | BFDA describes a food standards role involving regulation, inspection and quality control. This describes the function; it is not a finding that any particular food product complies. |
| Medical Product Division (MPD) | BFDA identifies pharmaceuticals, vaccines and related products, with evaluation, approval and post-market surveillance functions directed at safety, efficacy and quality. |
| Plant and Animal Biosecurity Division (PABD) | This is the displayed heading. The name alone should not be used to infer additional powers or settle a product’s classification. |
| Certifications Services (CS) | BFDA describes official certification of regulated products against national safety, quality and compliance standards. Agency product certification is distinct from any claim about manufacturing software. |
| National Food Testing Laboratory (NFTL) | A laboratory service entry: BFDA describes food-product testing for safety, quality and compliance with regulatory standards. Not every entry in this directory is a division. |
For manufacturer-side enquiry preparation, use the closest subject description as a starting point and ask BFDA to confirm the responsible contact where scope overlaps. State the product’s identity, intended use and the question requiring an answer; do not substitute an internal department name for a clear product description.
Keep supporting quality-system topics, such as ISO 13485 readiness or cGMP, separate from the routing question. As a practical filing convention, record the selected directory entry and any subsequent routing confirmation together so colleagues can distinguish an initial assumption from an authority response.
03Product scope in Bhutan: distinguish historical coverage from enquiry routing
BFDA’s historical account of DRA describes coverage of human allopathic medicines, vaccines, veterinary medicines, blood and blood products, traditional medicines, health supplements and medical devices. This is DRA’s described scope, not a complete current product-classification rule. Use the division descriptions above for orientation; distinguish that directory from an authority-confirmed answer about a particular product.
The table separates official descriptions from questions worth resolving before choosing a route. Historical entries refer to the Background account; the pharmaceutical entry uses BFDA’s Medical Product Division description.
| Destination jurisdiction | Product or subject | Official mapping | Question to resolve |
|---|---|---|---|
| Bhutan | Pharmaceuticals and vaccines | Medical Product Division | Which product category and enquiry contact apply? |
| Bhutan | Medical devices | DRA’s historical scope | How should this device be classified? |
| Bhutan | Food | Historical BAFRA food-safety remit | Which current contact handles this food enquiry? |
| Bhutan | Health supplements | DRA’s historical scope | Does the proposed description match BFDA’s classification? |
| Bhutan | Veterinary or traditional products | Veterinary and traditional medicines in DRA’s historical scope | Is this product a medicine or another category? |
| Bhutan | Narcotics or psychotropics | Historical BNCA controlled-substance remit | Which current controlled-substance contact should review the enquiry? |
As manufacturer-side preparation, keep the manufacturer’s proposed category separate from any authority-confirmed classification. For supplements and other boundary products, assemble intended use, composition, presentation and labelled claims. These are useful enquiry inputs, not a statutory Bhutanese classification test. Record the question, the response and the product version it concerns so a later formulation or claim change does not silently inherit an earlier answer.
Keep country of manufacture and existing foreign authorisations in separate fields. An overseas category—such as UK traditional herbal registration—should not substitute for Bhutanese classification. Do not infer a Bhutanese reliance pathway, recognition arrangement or market permission from origin-country approval. Likewise, do not assign general industrial chemicals to a medical-product route merely because their manufacturer operates in a regulated sector; seek product-specific routing instead.
04Drug-RIMS: the official access point and a controlled handoff
BFDA’s Drug-RIMS Portal page is the official entry point displaying the name “Drug Regulatory Information Management System” and the link “Click Here to Access Drug RIMS”. This identifies where to access the system; it should not be read as instructions for a particular registration procedure.
For the applicable task, follow current authority instructions rather than inferring account roles, required attachments, fees, processing times, registration validity or the meaning of portal labels from the access page.
Keep a manufacturer-side handoff record
As an internal traceability practice—not a stated Drug-RIMS requirement—prepare a short record linking the intended task to its accountable owner and approved material. Include:
- Task owner and product or internal case identifier.
- Approved document manifest: filenames, revision identifiers and approval dates.
- Access date and a factual note of the action observed.
- Any reference actually received, recorded exactly; if none was received, say so.
Record observations, not intended outcomes. A planned upload is not evidence of completed transmission, and an internal case number should not be presented as an authority-issued reference. Have the task owner review the handoff record before another person relies on it.
Retain the approved document set in the manufacturer’s controlled repository, with its manifest and related correspondence linked to the same case. Preserve that copy separately from later working revisions. This supports subsequent audit review: a reviewer can identify what was prepared, what transmission evidence exists and what response was received without relying on an operator’s recollection. It is a manufacturer-side recordkeeping recommendation, not a statement about Drug-RIMS storage or official retention rules.
05Agency, division, portal and decision: terms that are not interchangeable
Use these terms to distinguish organisational identity from case status:
| Term | Level | What it identifies | What it does not establish |
|---|---|---|---|
| Bhutan DRA | Historical agency | Former Drug Regulatory Authority | Current case status |
| BFDA | Authority | Bhutan Food and Drug Authority | Approval of a particular product |
| Medical Product Division | Division | BFDA organisational unit | A contact’s response is a regulatory decision |
| Drug-RIMS | Portal | Portal entry in BFDA’s navigation | Transmission evidence is an authority decision |
| Internal dossier approval | Manufacturer governance | Approval of specified documents for a stated purpose | Authority approval or batch release |
| Authority decision | Regulatory case | Authority’s determination for its stated scope | Manufacturer’s internal quality disposition |
The Medicines Act of Kingdom of Bhutan 2003, named in BFDA’s background, is legislation. BFDA’s background, division descriptions and portal information are official website guidance, not substitutes for provision-specific legal duties. The document-control arrangements recommended here are industry practice, not prescribed Bhutanese filing requirements.
Keep agency identity, division contact, transmission evidence, authority decision and internal quality disposition as separate records or statuses. An internal approval should identify exactly what was approved, by whom and for which purpose. Within the quality assurance process, distinguish permission to send a dossier from a batch release disposition; neither substitutes for an authority decision.
Software belongs only in the internal record-support layer of this comparison. Authorised people remain responsible for internal approval and release; the relevant authority remains responsible for its regulatory decisions.
06A manufacturer-side lifecycle from product scoping to ongoing follow-up
BFDA’s account of DRA’s mandate identifies product registration, post-marketing surveillance, testing of medical products, and inspection of sale, storage and manufacturing premises as core functions. That account provides context for preparation and ongoing follow-up; it does not establish a detailed submission or inspection checklist.
The following is a suggested manufacturer-side workflow, not an official Bhutanese registration or import pathway or sequence of approvals. Assign one accountable case owner and named contributors for product information, quality records, labelling and authority correspondence.
- Scope the product. The product-information contributor uses the intended use, composition and presentation to prepare a dated product description, recording unresolved classification questions.
- Route the enquiry. The case owner uses that description to identify the relevant authority subject area and retains the enquiry, routing rationale and any clarification received.
- Prepare documents. Quality and labelling contributors use the agreed description to assemble a version-indexed document set. Identify supporting records, such as a relevant batch record, where useful to the case.
- Reconcile descriptions. The case owner compares contributors’ outputs, assigns discrepancies to named people and retains the agreed corrections before authorising the next handoff.
- Access the relevant channel. The correspondence contributor uses the reconciled set and the channel identified for the matter, retaining the communication and any acknowledgement separately.
- Track correspondence. The correspondence contributor logs incoming questions against the affected product, assigns response owners and retains the approved reply with its attachments.
- Assess subsequent changes. Following correspondence or a decision, the case owner links each resulting action to the affected product and document versions, with an assigned action owner.
Define each handoff by its input, responsible person and retained output—not an assumed turnaround time. Ongoing assessment can consider changed composition, sites, specifications, labels or safety information. Record the impact assessment without assuming that every change follows a particular Bhutanese notification route; applicable authority procedures remain product- and case-specific.
- ScopeRecord product identity, intended use and Bhutan as destination.
- RouteIdentify an enquiry contact from BFDA’s published descriptions.
- PrepareIndex applicable documents, owners and approved versions.
- ReconcileResolve discrepancies before authorised internal sign-off.
- AccessUse BFDA’s Drug-RIMS entry point where applicable.
- TrackRetain actual correspondence, references and decisions.
- MaintainAssess changes and preserve the case history.
07What manufacturers keep ready: product records, quality evidence and versions
Use this internal readiness matrix as a preparation framework, not a universal BFDA dossier checklist. Its purpose is to make enquiries coherent and document sets reproducible. Applicability differs between medicines, food, devices and other products; select records for the product and question, and document why a category is inapplicable.
| Record group | Useful contents | Accountable owner | Version or applicability check |
|---|---|---|---|
| Product identity and intended use | Name, form, presentation, use; applicable instructions for use | Product lead | Match the case’s product description |
| Manufacturing-site identity | Site name, address, manufacturing activities | Manufacturing lead | Confirm site and activity mapping |
| Composition or configuration | Ingredients and quantities, or device configuration | Technical lead | Identify formula or configuration revision |
| Specifications and methods | Limits, units, test-method references | Quality lead | Match specification and method versions |
| Stability or shelf-life evidence | Applicable studies, conclusions, packaging studied | Technical lead | Check product and packaging relevance |
| Storage information | Conditions and supporting rationale | Quality lead | Reconcile with shelf-life evidence |
| Controlled labels | Artwork, claims, language variants | Labelling lead | Identify approved internal version |
| Relevant correspondence | Enquiries, replies, attachments, unresolved questions | Case owner | Retain dates and original meaning |
These are suggested owners, not prescribed roles. Reconcile related records rather than merely collecting attachments: for example, distinguish a label claim from a release limit when comparing artwork with specifications.
Connect records through five entities
Use Product, Market Case, Document Version, Submission Set and Correspondence as suggested internal entities—not official Drug-RIMS fields. A Market Case concerns a Product. Each Submission Set belongs to that case and identifies a fixed document set. Correspondence links back to the case and the evidence it discusses.
Keep a stable document identifier separate from its version identifier. The submission manifest should resolve to exact document-version pairs, never a moving “latest version” pointer. Record each version’s owner, internal approval status and supersession relationship; link unresolved discrepancies to affected records and assign a resolution owner.
Keep the authority reference empty until one is actually received. Preserve original correspondence and its qualifications: an internal status label may summarise progress, but must not replace the message’s meaning or imply a decision it does not contain.
Product
Stable identity and intended use.
- product_id
- product_name
- intended_use
- label_version
Market Case
Destination and accountable owner.
- case_id
- product_id
- destination_country
- case_owner
Document Version
Controlled content and supersession.
- document_id
- version_id
- approval_status
- supersedes_version_id
Submission Set
Fixed manifest and observed reference.
- submission_id
- case_id
- manifest_id
- portal_reference
Correspondence
Responses and accountable follow-up.
- correspondence_id
- case_id
- action_owner
- closure_evidence_id
08Internal system handoffs and recovery when a submission is uncertain
Manufacturers can connect internal product, quality and document records through controlled handoffs rather than a direct technical integration. A reconciliation sheet or approved manifest can relate the product record to its quality records and selected document versions. These are manufacturer-side design options, not Bhutanese filing requirements or descriptions of Drug-RIMS interfaces. The same approach supports MES–QMS reconciliation: make relationships explicit before moving records.
Define what each handoff proves
Give each handoff a product identifier, document-version references, an accountable owner and a reconciliation result. Record whether the receiving internal record set matches the intended set, and identify unresolved differences. A successful internal export establishes only that an internal transfer step completed; it is not evidence that an external transmission was received. Keep internal acceptance and external receipt as separate conclusions, each supported by its own records.
Recover without guessing
For a hypothetical interrupted session or uncertain transmission, use a recovery procedure such as the following. This is general transaction-recovery practice, not a description of Drug-RIMS behaviour.
- Preserve the intended document set and available observations, including any messages or receipt evidence actually encountered.
- Assign an owner to establish what occurred. Avoid an unexamined duplicate submission while receipt remains uncertain.
- Log the event, affected case, evidence reviewed, reconciliation outcome and authorised next action. Keep an unresolved outcome explicit rather than marking the case complete.
If internal systems disagree, compare the underlying records and their provenance using an audit-trail review workflow. Do not let the latest displayed timestamp decide which status is correct. The accountable owner should document the resolution and obtain authorisation for the next action before the case proceeds.
09Three worked cases: shared evidence, conflicting descriptions and uncertain transmission
These hypothetical cases illustrate manufacturer-side preparation, not BFDA filing requirements. Each ends with a record that lets an accountable person understand the evidence and decide the next action.
Case one: shared documents, separate strength manifests
Assumption: A manufacturer prepares records for two medicine strengths. Each strength has two product-specific documents; three site documents are shared. These assumed counts are not BFDA requirements.
Reasoning: There are 2 × 2 + 3 = 7 unique documents. Each strength’s manifest references its two specific documents and all three shared documents, giving 2 × (2 + 3) = 10 document references across the manifests. Unique documents count distinct records; references count their appearances in the indexes. Reusing a site document does not create another unique document.
Retained-record outcome: Keep both manifests with document identifiers and fixed revision references under document control. If a shared document changes, the case owner reviews its effect on both manifests rather than silently replacing the earlier version.
Case two: conflicting product descriptions
Assumption: One product’s commercial description calls it food, while its controlled label calls it a health supplement.
Reasoning: Compare intended use, composition and claims across the two records. Log the exact conflict and identify the versions compared. Assign a named owner to prepare and pursue the classification enquiry. Neither the marketing term nor an internal preference should settle the legal classification; this example assumes no classification outcome.
Retained-record outcome: Preserve the comparison, enquiry, correspondence and eventual clarification with the case. The responsible reviewer records which descriptions need correction and why, keeping the original conflicting records traceable rather than overwriting them.
Case three: uncertain online transmission
Assumption: A browser session ends during an attempted online transmission, and the team has no clear receipt evidence. This is a generic scenario, not a statement about Drug-RIMS behaviour or recovery features.
Reasoning: Apply the recovery controls above: preserve the selected document versions, record the uncertainty through contemporaneous recording, and reconcile available transmission and receipt evidence. Do not treat the interrupted session as proof of either success or failure. An accountable person decides whether another attempt is appropriate after reconciliation.
Retained-record outcome: Keep the attempted manifest, available event evidence, reconciliation notes and authorised next-action decision together, including any unresolved uncertainty.
10Failure modes that leave a regulatory case difficult to review
For a manufacturer’s Bhutan regulatory case, the controls below are suggested internal practice, not a list of Bhutanese regulatory offences. They address accountability and evidence gaps behind the naming, classification and transmission examples above.
| Failure mode | Review consequence | Preventive control | Retained evidence |
|---|---|---|---|
| Enquiry without an accountable owner | Follow-up may stall or be duplicated. | Ownership register with a named owner and accepted responsibility. | Owner acceptance and assignment history. |
| Decision not linked to its product scope | Reviewers cannot establish which product or version it covers. | Product-and-version linkage for each decision. | Decision record linked to the assessed product description and document versions. |
| Unresolved discrepancy marked closed | An unsupported conclusion appears settled. | Require closure evidence; otherwise retain an open status. | Resolution rationale, supporting records and reviewer acceptance. |
| Internally scheduled review passes without assessment | Changed circumstances may remain unexamined. | Record a review disposition: completed, deferred with reason, or escalated. | Dated assessment or deferral rationale, responsible person and next action. |
Use observable closure criteria: a named person accepted the action, the relevant record is linked, and the reason for closure can be reconstructed. A closed status alone is insufficient.
Keep internally chosen review dates distinct from legal deadlines. Record unresolved risks in a quality risk register, and route overdue internal assessments to management review when escalation is warranted.
11A practical readiness review before the next authority interaction
Use three internal review moments—not an official Bhutanese approval sequence.
- Before an enquiry: confirm product identity, intended use, destination, the unresolved question and the responsible contact.
- Before transmitting documents: check applicability, approved versions, reconciliation against the document manifest and authorised internal sign-off.
- After correspondence: link the response to the case, assign actions and record the next review trigger. Route subsequent revisions through change control.
Can I reuse another market’s dossier?
Treat it as candidate evidence; apply the applicability check above.
What if product descriptions conflict?
Resolve the discrepancy internally before relying on either description.
What if classification remains uncertain?
Make that the enquiry’s explicit question, as discussed under scope.
Can a draft accompany an enquiry?
Obtain internal authorisation and identify its draft status.
What if transmission is uncertain?
Use the recovery approach above before attempting another transmission.
What if a colleague takes over?
Record the new owner and transfer open actions.
What if evidence changes afterwards?
Assess its effect on the case before replacing documents.
When is the team ready?
When it can explain the product, evidence used, unresolved issues and next-action owner. Readiness is an internal management conclusion, not regulatory approval.
Frequently asked questions
Q.Does an older document addressed to DRA prove a product’s current status?+
Treat an older DRA-addressed document as part of the product’s history, not conclusive evidence of its current status. As a document-control practice, distinguish an application, acknowledgement, decision and later correspondence. Match the product identity, manufacturer, document reference and any stated conditions against the decision being relied on. Preserve the original and an audit trail of subsequent clarification. If the records conflict, ask BFDA to clarify the specific product and reference rather than interpreting the agency name alone.
Q.Where should a query about a medicine–device combination begin when BFDA lists different product functions?+
Begin with a product-specific routing enquiry to BFDA, identifying both the medicinal and device functions. The Divisions page describes the Medical Product Division as regulating pharmaceuticals, vaccines and related products; that description should not be treated as a combination-product classification decision. A useful enquiry package includes composition, mechanism, intended purpose, presentation and the proposed instructions for use. Ask which function should coordinate the enquiry and retain the response with the product case.
Q.Can approval in the country of manufacture settle a product’s Bhutan market status?+
For internal decision-making, do not use home-country approval as a substitute for evidence addressing the product’s Bhutan status. Retain that approval with its product identity, holder, scope and stated conditions, then record separately the Bhutan correspondence and decisions on which the team relies. A requirements-traceability matrix can distinguish supporting documents from unresolved market-status questions. If a distributor asserts that foreign approval is sufficient, request the applicable Bhutan basis and have the responsible regulatory person assess it before proceeding.
Q.What should change in the internal case record when a label is revised after documents have been sent?+
Open a change-control entry linking the transmitted label to the proposed replacement. Record the revision identifier, reason, changed text or artwork, affected presentations and the person responsible for assessing the impact. Preserve the earlier transmission package unchanged. Track whether clarification or further communication with BFDA is needed, without recording the replacement as accepted prematurely. For recall readiness, identify any printed stock or distributed packs carrying the earlier version, and document the authorised disposition separately.
Q.How can a food exporter use the BFDA division map without borrowing medicine-specific assumptions?+
Use the BFDA division map as a contact-routing aid, then frame the enquiry around the actual food: ingredients, processing, intended use, packaging, storage and origin. As an export-planning practice, maintain a food-specific checklist rather than copying a medicine dossier template. Ask which services and documents apply to that product and transaction. Connect the answer to inbound receiving planning so the importer can reconcile product identity and accompanying records, while keeping unresolved questions visible.
Q.Which review and release decisions should remain with authorised people when software manages the records?+
Assign authorised people to approve classification positions, submission content, responses to BFDA, label changes and any decision to supply product. Keep the regulatory assessment distinct from the quality decision for batch release. As a governance practice, a completed workflow, uploaded file or recorded acknowledgement should not itself authorise either decision. Record the decision-maker, supporting documents, scope and date, with unresolved conditions visible. Configure permissions and review steps around those responsibilities rather than treating a software status as an approval.
Primary sources
Want to see how DRA (Bhutan) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
