01 · Generic framework
RequirementDocument control
Define controlled versions, approval and access to the records used by a system.
Quality · evidence control
Quality system development and evidence
Quality claims are useful only when they identify the product, system, site, evidence and status they actually support.
Evidence positionQuality
Requirements are identified. Implementation needs evidence.
This page describes programme requirements and evidence logic. It does not certify an operating pharmaceutical quality system, laboratory, validated process or released batch.
- Facility evidence basis
- Dated project-development record; present operating status unverified
- Operational PQS or GMP status
- Not asserted
- Public document availability
- Confirmed only case by case
- Status reviewed
- Project update
01 · Quality position
Quality position at the current project stage.
The controlled website record places the Boten project in development. The implementation programme identifies documentation, training, qualification-related work, trial activities, analytical work, stability and quality-release decisions as workstreams to be completed or evidenced as the project advances.
Claim boundary
No current GMP certificate, operating pharmaceutical quality system, qualified utility, validated production process, testing laboratory capability or released commercial batch is asserted by this page.
A system of connected responsibilities
Generic process context: a proposed way to organise the requirements already discussed in the public record. This framework does not assert implemented systems.
02 · Generic framework
RequirementTraining & responsibility
Connect role-specific work to competence, documented training and accountable decisions.
03 · Generic framework
RequirementSupplier & material quality
Keep material identity, supplier assessment and traceability connected.
04 · Generic framework
RequirementQualification & validation
Define systems, protocols, acceptance criteria and executed evidence.
05 · Generic framework
RequirementDeviation & corrective action
Record events, investigate causes and evaluate corrective and preventive actions.
06 · Generic framework
RequirementChange control
Assess the impact of a proposed change before it is approved and implemented.
07 · Generic framework
RequirementData integrity
Retain attributable, complete and reviewable records throughout their lifecycle.
08 · Generic framework
RequirementAnalytical & stability work
Tie methods, specifications and study conclusions to the exact product and container.
09 · Generic framework
RequirementReview & release decisions
Define responsibilities and the evidence needed for any future batch decision.
02 · Product evidence
The product evidence chain.
A useful evidence chain begins with an identified product and ends with a defined review or regulatory use.
Evidence should remain connected to the exact product and use for which it was generated. A defensible chain identifies the active substance, formulation, strength, container/closure, manufacturing site, process version, specification, methods, batch records, stability package and intended market.
Defined product→Controlled process→Generated evidence→Quality review→Regulatory use
A certificate of analysis is not a manufacturing authorisation; a development result is not a marketing authorisation; and a guideline link is not evidence that an authority has inspected or certified the Boten project.
03 · Qualification & validation
Make dependencies visible.
Facility, utility, equipment and process evidence must remain specific to the system being assessed. Photographs or planned equipment lists do not establish qualification.
Analytical and stability conclusions similarly depend on the material, formulation, strength, container, methods and study. Testing availability cannot be inferred from a catalogue entry.
| Workstream | Required definition | Evidence question |
|---|---|---|
| Qualification | System, intended use and acceptance criteria | Which approved protocol and executed result support the claim? |
| Validation | Process, product and defined operating conditions | Does the documented evidence cover this exact scope? |
| Analytical work | Methods and specifications for the material | Are methods, laboratories and responsibilities established? |
| Stability | Presentation, pack and study design | Is there a relevant controlled study and reviewed conclusion? |
04 · Programme status
Programme status must be stated at the correct evidence level.
Facility / utilitiesRequirement identified
Qualification and validation concepts belong to a defined system, protocol, acceptance criteria and executed evidence. Construction photographs do not establish completion.
Documentation / trainingDevelopment workstream
Procedures, role assignments, training records and controlled-document status require approved records. A project plan is not proof of implementation.
Analytical / stabilityProduct-specific requirement
Methods, specifications and stability conclusions depend on the exact material, formulation, strength, container and study. Availability is not assumed.
ReleaseFuture governed decision
A batch-release decision requires authorised responsibilities and the required manufacturing and quality evidence. No public stock or released batch is claimed.
05 · Lifecycle governance
Responsibilities and decision rights.
A functioning quality system requires accountable roles for document control, change control, deviations, complaints, supplier/material controls, qualification and validation, analytical/stability work, batch review and release. The website does not invent names or appointments for those roles because controlled evidence has not been supplied.
Before publication of role-specific claims, the website record should identify the approved role, scope, delegated authority, effective date and supporting controlled document.
Generic process context
Complaints, defects and recall preparedness belong in the proposed lifecycle framework. Their appearance here is a content requirement, not a claim that a commercial procedure is in operation.
06 · Documentation & references
Requesting quality documentation.
For a professional request, identify the portfolio reference or generic product, proposed presentation, target jurisdiction and the exact document or evidence class required. Availability, current revision, disclosure permission and relevance to the proposed transaction are confirmed individually.
Do not assume that certificates, validation packages, stability reports, specifications, batch documents or audit records exist or can be disclosed because a generic category is mentioned on the website. Use professional contact to define the request.
External technical frameworks
WHO GMP main principles, ICH Q9(R1) and ICH Q10 are useful external frameworks for understanding manufacture, quality risk management and lifecycle quality systems.
They are referenced for technical context only. Applicable Lao requirements, product category, destination requirements and the competent authority determine what is legally required. Reference to WHO or ICH does not constitute certification, inspection status or regulatory approval.
07 · Quality concerns
Quality concerns and safety reports.
A product-quality concern should identify what was observed, the product wording, strength/presentation, batch or lot if available, country and source of supply. If patient harm or a suspected adverse event is involved, use the safety-reporting guidance as well.
The current public intake is the company contact form. It is not represented as a continuously monitored hotline or a secure clinical-record transfer system.
No Luang Pharma product is on the market yet. A medicine offered under the company’s name is covered by the notice on falsified products and misuse of our name.
08 · Project roadmap
The wider project sequence.
Quality-system evidence is generated in sequence with the facility. Qualification follows installation, and validation follows qualification; none of these steps is complete until the company confirms it.
Project milestones provide context; they are not evidence of completed quality-system work.
- 01Completed
Facility design
Facility design is recorded as complete. No completion date is supplied.
- 02In progressTarget Q4 2026 · indicative
Construction and fit-out
Construction is in its final stage; completion is an indicative target.
- 03PlannedTarget Q1 2027 · indicative
Equipment installation and qualification
Installed systems would require documented qualification.
- 04PlannedTarget Q2 2027 · indicative
Process and system validation
Process and system evidence would need to be established.
- 05PlannedTarget Q3 2027 · indicative
Manufacturing licence application
Submitting an application does not establish permission to manufacture.
- 06PlannedTarget Q4 2027 · indicative
Regulatory inspection
Inspection is a separate stage from any resulting authorisation.
- 07PlannedTarget Q1 2028 · indicative
First commercial batch
Dependent on applicable permissions and demonstrated readiness.
Project roadmap reviewed . These are indicative project targets, subject to progress and applicable permissions. They are not service launch dates or commitments to supply. A milestone is marked completed only when the company confirms it.
Read the project roadmap09 · Professional reading
Explore the related evidence questions.
Guide
GMP, manufacturing authorisation and product approval
Read the guideGuide
How to read a certificate of analysis
Read the guideGuide
Pharmacopoeial standards explained
Read the guideProfessional enquiries
Define the documentation question.
Specify the product or system, the evidence class and the purpose of your request. Availability and disclosure are confirmed individually.