Schedule H1 Register for Clinic Pharmacies in India: Prescription, Dispensing, and Record Workflow

Software does not create permission to stock or sell a medicine. Before configuring a Schedule H1 workflow, confirm the pharmacy's current retail licence, approved premises, responsible persons, State-level requirements, and the medicines the clinic is authorised to handle.

Rule 65 of the Drugs Rules, 1945 states that retail supply on the prescription of a registered medical practitioner must be effected by, or under the personal supervision of, a registered pharmacist. The same rule contains the Schedule H1 register and prescription conditions discussed in this guide. CDSCO consolidated Drugs Rules, 1945.

Assign a named owner for each part of the workflow:

• The clinic owner confirms licence and premises scope
• The prescriber issues a complete prescription
• The registered pharmacist verifies and dispenses
• An authorised stock operator records inward and adjustment movements
• A reviewer reconciles the register, invoices, prescriptions, and stock
• The clinic's qualified adviser interprets current Central and State requirements

A shared login labelled 'pharmacy' cannot prove who acted. Individual accounts are part of an inspection-ready record.

Schedule classifications can change, and a draft proposal is not a final rule in force. Use the official CDSCO Drugs Rules repository for consolidated rules and the Gazette Notifications page for later amendments. Record the source, notification number, publication date, and effective date used for each classification decision.

Rule 65 provides that Schedule H1 drugs may be sold by retail only on and in accordance with the prescription of a registered medical practitioner. It also states that, for this purpose, the prescription must be written, signed and dated, identify the person for whose treatment it is given by name and address, and indicate the total amount to be supplied and the dose.

Before the medicine leaves the pharmacy, the pharmacist's review should answer:

• Is the prescription legible and attributable to the prescriber?
• Is it signed and dated?
• Does it state the medicine, total amount, and dose?
• Is the prescribed product classified correctly on the dispensing date?
• Has this prescription already been dispensed?
• Does it expressly permit a repeat, and if so, how many times or at what intervals?

The software can make missing information visible, but it should not invent a dose, infer permission to repeat, create a prescriber signature, or turn an incomplete order into a compliant prescription.

Rule 65(3)(h) requires supply of a Schedule H1 drug to be recorded in a separate register at the time of supply. The rule specifies the name and address of the prescriber, the name of the patient, the name of the drug, and the quantity supplied.

Treat those as the stated particulars, not the complete design of a digital workflow. Also preserve context needed to reconstruct the transaction:

• Supply date and time
• Unique register entry number
• Prescription reference
• Prescriber name and address
• Patient name
• Medicine name and strength
• Quantity supplied and unambiguous unit
• Batch number and expiry date
• Dispensing pharmacist
• Correction, cancellation, or return status

Clearly label which fields come directly from the separate-register rule and which are additional operational controls. That distinction makes the register easier to review and prevents product documentation from overstating the law.

The Schedule H1 clause says the records must be maintained for three years and remain open for inspection. This specific period is longer than the general two-year record period stated elsewhere in Rule 65 for records without another specified period.

A separate register does not necessarily require an isolated application. It does require a clearly identifiable Schedule H1 record set that can be searched, reviewed, exported, and retained without mixing it into an undifferentiated sales report.

Define the retention start, archive method, access controls, backup coverage, and deletion block. Confirm additional State or licence expectations with the authority or a qualified adviser.

Trace every entry back to inward stock and forward to physical balance. Rule 65 requires retail purchase records to show the purchase date, supplier name and address, supplier licence number, drug, quantity, batch, and manufacturer. Purchase bills or memos should be serially numbered and chronological.

For each Schedule H1 dispense, the system should connect:

• Supplier and purchase document
• Inward date
• Product, strength, and form
• Manufacturer
• Batch and expiry
• Pack, strip, and loose-unit conversion
• Prescription and register entry
• Current book and physical balance

If inward stock is recorded as boxes but dispensing is recorded only as '1', nobody can reliably tell whether one box, strip, blister, or tablet left the shelf. Unambiguous units are essential for both the patient-facing supply and the stock reconciliation.

Schedule H1 and Schedule X controls are not identical. Schedule H1 has its separate register and three-year retention requirement. Schedule X has additional provisions for duplicate prescriptions, preservation of one copy, restricted storage, and a bound, serially page-numbered register with separate pages for each drug.

A generic 'controlled medicine' label is too broad. The catalogue and dispensing screen should show the actual classification and triggered controls.

When classification is unclear, stop and obtain authoritative advice. Software should preserve the decision source, not choose the least restrictive category.

Rule 65 states that a prescription containing a Schedule H or Schedule H1 drug must not be dispensed more than once unless the prescriber states that it may be dispensed more than once. If the prescription specifies a number of repeats or intervals, dispensing must follow those directions. The seller's name and address and the dispensing date must be noted on the prescription.

Build repeat status around the prescription, not the patient or medicine alone:

• No repeat authorised
• Repeat authorised for a stated number
• Repeat authorised at stated intervals
• Dispense count and dates
• Quantity supplied on each occasion
• Quantity or repeats remaining
• Rejected attempt and reason

Partial dispensing can create additional questions about how the original quantity, remainder, prescription notation, and later supply should be documented. The clinic should agree its procedure with the registered pharmacist and licensing adviser. Software should record exactly what was supplied on each occasion and should never convert an unfulfilled balance into an assumed repeat authorisation.

Rule 65(11A) says that a person dispensing a prescription containing a Schedule H, Schedule H1, or Schedule X substance may not supply another preparation in lieu of it.

A search result that suggests a similar brand, strength, formulation, or ingredient can be operationally useful, but it must not silently replace the prescribed preparation. The dispensing record should preserve the prescribed item and the supplied item as separate facts.

If the requested product is unavailable, route the decision through the authorised clinical and pharmacy process. Do not let stock availability, margin, a barcode match, or a staff shortcut rewrite the prescription.

During a demonstration, deliberately select a different preparation. Ask what warning appears, whether dispensing is blocked, and what evidence remains.

A misspelled prescriber address, wrong batch, duplicate transaction, or incorrect quantity may need correction. Replacing the old value without history makes the register look clean while weakening the evidence.

A correction workflow should preserve:

• Original entry
• Corrected value
• Reason
• Person approving it
• Date and time
• Related prescription, invoice, and stock adjustment
• Whether a printed or exported register was already produced

Voiding a duplicate should not delete the underlying event. A quantity correction should create the corresponding stock movement. If patient identity is wrong, treat it as both a pharmacy-record correction and a potential confidentiality issue.

The medical-record correction workflow provides a broader framework for preserving original entries and downstream document history.

The pharmacy workflow involves sensitive records, so access should follow responsibility. A receptionist may only need readiness status, while a pharmacist needs the prescription, medicine, batch, stock, and prior dispense status. System administration should not confer authority to make professional dispensing decisions.

Use individual accounts for prescribing, dispensing, stock adjustments, classification changes, exports, and corrections. Review access after staff changes and preserve audit history after an account is disabled.

CliniKite describes role-based access and audit logs on its public pages. Clinics should map the product roles to their own legal and professional responsibilities. The role-based access checklist offers a practical starting point.

A three-year archive is not enough if errors remain unnoticed. Build a daily control and periodic review.

A daily Schedule H1 review can compare:

• Every H1 invoice against a register entry
• Every register entry against a prescription
• Medicine, strength, quantity, and unit across all three records
• Dispensing date against prescription and repeat conditions
• Batch movement against the selected inward
• Physical quantity against book balance for selected medicines

Record the reviewer, date, exceptions, action owner, and closure evidence. An empty exception report is meaningful only if the underlying checks actually ran.

The clinic pharmacy stock and dispensing guide explains the wider inward, batch, expiry, pack-conversion, return, and adjustment workflow.

Rule 65 requires registers and records to be produced for inspection on demand. The clinic should know whether it can do so without giving an inspector unrestricted access to the live application or exporting unrelated patient information.

Prepare a documented retrieval path for:

• Schedule H1 register for a selected date range
• Search by medicine, patient, prescriber, and entry number
• Connected prescriptions
• Connected invoices or memos
• Purchase bills and supplier licence details
• Batch and stock movement history
• Corrections, voids, and user attribution
• Readable export and backup restoration

Restrict output to the authorised request. Record who generated and received it, when, and which filters were used.

Use fictional data and a non-production environment.

Create an inward for 100 tablets with supplier, batch, expiry, pack conversion, and purchase invoice details. Create a complete fictional prescription, then dispense 20 tablets through a registered-pharmacist test account.

Then verify that staff can:

• Find the transaction in the separate H1 register
• Trace it to the prescription, invoice, inward, batch, and pharmacist
• Reject an unauthorised second dispense
• Warn against a different preparation
• Correct a deliberately wrong batch without erasing history
• Reconcile opening, inward, dispensed, adjusted, and closing quantities
• Export only the selected H1 records
• Read the export without access to the application

Repeat the exercise after a schedule-classification update and after a staff-role change. This tests whether the controls are part of the workflow rather than a one-time configuration.

CliniKite's public feature page describes prescription-linked dispensing, batch and expiry tracking, pack and loose-unit sales, inwards, suppliers, returns, adjustments, statutory registers, role-based access, audit logs, backups, and exports. CliniKite features.

These statements provide relevant evaluation context. They do not, by themselves, prove that a clinic's licence, medicine catalogue, Schedule H1 interpretation, prescription, register format, retention policy, or inspection process is compliant.

During a demonstration, ask:

• How is a medicine classified as Schedule H1, and who can change it?
• Can a classification have a future effective date?
• Does the system distinguish draft, final, and effective notifications?
• Which prescription fields are required before dispensing?
• Is the H1 supply recorded at the time of supply?
• Can the separate register be filtered and exported?
• How is three-year retention protected?
• Are repeat conditions enforced from the prescription?
• What happens when a different preparation is selected?
• Can batch, expiry, invoice, inward, and pharmacist be traced?
• Do corrections preserve old and new values?
• Can an older register be restored from backup?
• Which controls are automatic and which remain clinic procedures?

Ask for the answers to be demonstrated using the synthetic workflow above and obtain written confirmation for any requirement essential to the clinic's licence or State inspection process.

A dependable Schedule H1 workflow starts before the sale. Confirm the current classification and effective date, verify the prescription, dispense through the responsible pharmacist, create the separate register entry at the time of supply, and connect it to purchase, batch, invoice, stock, and user history.

Keep Schedule H1 distinct from Schedule X, prevent unauthorised repeats and silent substitutions, retain H1 records for the required period, and correct mistakes through attributable amendments rather than deletion.

The practical standard is reconstruction. Years later, the clinic should be able to show what was prescribed, what was supplied, from which batch, under whose supervision, against which stock and invoice, and what changed afterward.