Skip to main content

Schedule H1 Register Format: Fields, Supply Rows and Corrections

For supplies to which Rule 65(3)(h) applies, the Schedule H1 register records the prescriber’s name and address, patient’s name, medicine name and quantity actually supplied, at the time of supply. Keep those required particulars distinct from additional event, batch and correction fields. Build rows around real handovers, then test partial supplies, downtime entries and inspection retrieval; a template alone does not establish compliance.

By Bractis · Updated · 9 min read

Indian clinics and authorised dispensaries that have established the applicability of H1 supply records and now need a practical register structure and review method.

Start with the applicable supply process, not a blank PDF

The useful question is not simply which spreadsheet columns to copy. It is which activity the register records, who performs it, which medicines are classified for that event and how the records can be produced for inspection. Confirm the clinic's actual dispensing arrangement before configuring any statutory register.

The existing H1 overview explains the legal and classification boundary. This guide goes further into the working row: how a specific handover becomes a record, how errors are amended and how a reviewer follows the evidence. It does not duplicate a fixed list of H1 medicines.

An issued prescription and an actual supply are different events. A clinic that prescribes an item bought entirely from an outside pharmacy must not fabricate its own supply row. An abandoned draft, a cancelled order and a stock reservation likewise do not establish a handover.

Use a copyable working outline only after checking the accepted record format and relevant obligations for the actual arrangement. A vendor's export called 'H1 register' is a starting point for inspection, not evidence that the authority has approved the system.

Separate the rule particulars from the traceability columns

Rule 65(3)(h) specifies the separate register, recording at supply, the named particulars, three-year maintenance and inspection access. Other applicable rules or licence conditions may also matter. Keep the cited requirement and the additional design choices distinguishable.

The table maps the provision's core particulars to an original event model. Do not replace a prescriber's address with a registration number or assume a patient phone number supplies the patient's name. Extra identifiers can help matching, but do not replace the specified information.

On a narrow screen, scroll the table horizontally to read all columns.

H1 register particulars and additional working fields
Field groupBasisHow to use it
Prescriber name and addressNamed in Rule 65(3)(h)Retain the particulars applying to the source prescription.
Patient nameNamed in Rule 65(3)(h)Match the supply to the correct patient; add internal identity links separately.
Drug name and quantity suppliedNamed in Rule 65(3)(h)Use the actual item and unambiguous supply unit.
Event date and referenceOriginal operational traceability proposalConnect one real handover to its order, receipt and source.
Batch and responsible personAdditional traceability proposalFollow the physical item and the attributable action.
Correction and downtime linksAdditional history proposalExplain changes without presenting transcription as another supply.

Source: CDSCO: Drugs Rules, 1945, compilation amended through July 2024

Write one traceable record for each real supply event

Consider a fictional training item whose H1 classification and supply authority have already been confirmed. The current prescription is for ten tablets. The dispensary supplies six on 3 November and four on 5 November, after confirming the later supply is permitted. There are two real events totalling ten tablets.

Do not copy the prescribed quantity of ten into both rows. That would falsely report 20 tablets supplied. Keep the event quantity with its date and source, and connect the second event to the original prescription and first supply.

If the four-tablet balance is merely planned, it must not appear as a completed second event. A reminder to collect, an advance payment and a promised delivery date are not substitutes for handover evidence. The working queue may show them, while the actual supply register remains factual.

For multiple medicines handed over together, preserve the distinct item quantities and a common handover reference if useful. Do not combine unlike products into 'ten medicines' or use a billing total as the quantity. A register must let the reviewer identify what was actually supplied.

Keep classification decisions tied to dates and operative sources

Medicine classification is a controlled catalogue decision. Record the exact item, official source, applicable commencement and person approving the classification. The same source list may contain a consultation draft, a final notification and an amendment that starts later.

The CDSCO notifications register checked on 24 October 2026 includes an August 2026 draft concerning additional H1 medicines. A draft listing is not, by itself, authority to treat a proposed addition as an operative rule. This guide deliberately does not reproduce an exhaustive current medicine list.

If classification changes, preserve what was applied to historical events and why. Do not rewrite every old row to the newest category without a trace. Review how the change affects new supplies, stock labels, staff instructions and exports under the applicable requirements.

An uncertain catalogue flag should be routed to the designated reviewer before the actual supply decision. A receptionist should not be expected to settle legal classification from a warning colour, and software should not silently treat an unknown state as unrestricted.

Source: CDSCO: Gazette notifications

Correct a register entry without erasing the handover

A correction should identify the original event, erroneous field, corrected value, reason, supporting evidence, responsible person and time. Preserve the earlier value in the accepted record system. A neat final screen is not enough if an inspector cannot understand what changed.

Suppose the first fictional supply was six tablets but was typed as eight. The original record and the amendment should remain reconstructable. The correction changes the recorded quantity to match the evidence; it does not represent a new handover of minus two tablets.

A physical return after supply is another event. If two of the ten tablets are returned, retain the original gross supplies of ten and a separate two-tablet return with its reason and disposition. Do not rewrite history to say only eight were originally supplied.

Stock, finance and the patient record may each need linked action, but the correct action differs. A financial refund is not evidence that returned stock can be reissued. A technical correction is not evidence that the patient returned medicine. Use the event type that matches reality.

Make the register usable during an outage and after an export

Use the approved downtime source with the actual supply time, particulars and responsible person. During reconciliation, retain the paper reference and distinguish the event time from the later electronic-entry time. Decide who marks a source as reconciled so two staff do not create duplicate rows.

An export should preserve the information necessary to read each event without opening a hidden screen. Check that long prescriber addresses and medicine names are not cut off, quantity units remain attached and corrections can be followed. A file that opens successfully may still be incomplete.

Confirm retention and inspection access for this record category. Do not apply the H1 period as a universal deletion rule for every clinical note, invoice or backup. Likewise, retaining only screenshots may make search and inspection difficult even when the images look correct.

Restrict routine access to people who need the register for their role, and use an appropriate process for authorised inspection or export. A shared spreadsheet link can expose patient names well beyond the counter. The ability to retrieve records should coexist with controlled disclosure.

Run a retrieval exercise using events that are easy to get wrong

Choose a sample that includes a normal supply, a partial supply, a correction, a downtime entry and a return. Ask the responsible person to identify the source prescription, actual quantity, applicable classification evidence and amendment history for each.

In a fictional sample of 12 events, ten can be reconstructed completely. One lacks a usable prescriber address and another has an unexplained quantity correction. Report two unresolved events out of 12, with their owners and actions. Twelve populated rows are not evidence of 12 satisfactory records.

Repeat the exercise from the exported material. If a correction is visible only in the live system, document that dependency and resolve how records will be available after migration or during an outage. This is particularly important when changing software vendors.

Use the findings to improve the real process: unclear responsibility, missing source particulars or a misleading quantity default. Adding more mandatory fields will not fix a staff member who cannot tell whether the patient actually collected the item.

A return does not rewrite two earlier supplies

In the fictional ten-tablet example, six tablets are supplied first and four later. Two are subsequently returned. The record preserves two supplies totalling ten, the separate return of two and the authorised stock and financial outcomes. A report labelled 'gross supplied' shows ten; a separate net-material calculation may show eight. Neither view should conceal what was originally handed over or imply a new clinical instruction.

H1 Register Row and Retrieval Worksheet

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Applicable particulars
Compare the accepted register with the cited rule and any other requirements for your arrangement.
Actual events
Follow a partial supply without copying the prescribed total into every row.
Amendment evidence
Distinguish an error correction, physical return and cancelled plan.
Inspection retrieval
Reconstruct a corrected and downtime event from both the live record and its export.

Questions doctors ask

Which fields belong in a Schedule H1 register?

The cited provision names the prescriber and address, patient, drug and actual quantity supplied. Confirm its applicability and other requirements for the arrangement. Event, batch and correction links are useful additions, not substitutes for those particulars.

How should two partial supplies be entered?

Record the actual quantity at each permitted handover and link both to the prescription. A six-tablet supply followed by four totals ten; copying the ten-tablet prescribed quantity into each row would double the record.

Is a printable H1 template enough to establish compliance?

No. The actual activity, current classification, complete event records, applicable format, retention and inspection arrangements matter. The outline here is an original working model, not an officially approved statutory form.

Should an incorrect register quantity be deleted and re-entered?

Use the accepted correction process that retains the original event, changed value, reason and attributable evidence. Do not create a fictional return or second supply merely to make the final total look right.

Sources and scope

Updated on . This guide provides an original working register model and retrieval exercise. It does not certify a format, medicine classification, electronic-register acceptance or the legal status of a particular clinic. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Bring the register format confirmed for your arrangement and fictional partial, corrected and downtime events to inspect record history and usable exports.

Request a clinic demo