LEGAL STANDARDS FOR VERSION CONTROL OF DIGITAL LABELS

1. INTRODUCTION

Version control of digital labels refers to the systematic identification, review, approval, publication, modification, and archival of electronic product labels and instructions for use. In biotechnology and healthcare, digital labels may contain dosage information, contraindications, storage conditions, expiry dates, warnings, product identifiers, batch details, and instructions for operating medical devices.

Incorrect or outdated digital labels can cause medication errors, improper device use, product recalls, patient injury, and regulatory non-compliance. A legally defensible version-control system must therefore ensure that the correct, approved label is associated with the appropriate product, market, batch, and intended user.

Although legislation does not universally prescribe a particular software version-control method, applicable product-labeling, quality-management, electronic-record, and change-control requirements establish important legal foundations.

2. LEGAL AND REGULATORY FRAMEWORK

A. INDIA: MEDICAL DEVICES RULES, 2017

Chapter VI of the Medical Devices Rules, 2017, governs medical-device labeling. Rule 44 specifies prescribed labeling particulars, while Rule 48 addresses devices intended for clinical investigations, evaluations, demonstrations, and training. Rule 46 addresses unique device identification requirements.

Where digital labels or electronic instructions for use are used, manufacturers should establish whether the applicable regulatory requirements permit that format and whether additional conditions apply. CDSCO has expressly confirmed in its medical-device FAQs that electronic instructions for use are permitted under the Medical Devices Rules, 2017. <Cite refs={["turn406500search25","turn406500search3","turn406500search8"]}/>

B. DRUGS AND COSMETICS LEGISLATION

The Drugs and Cosmetics Act, 1940, and applicable Drugs Rules, 1945, establish requirements relating to drug labeling, packaging, and product information. Digital publication does not automatically replace mandatory physical labeling or other prescribed disclosures. Pharmaceutical manufacturers must assess the rules applicable to the particular product and any approved labeling variation.

C. INTERNATIONAL QUALITY AND LABELING STANDARDS

For medical devices marketed in the United States, 21 CFR § 820.45 requires documented procedures controlling labeling and packaging, including accuracy checks, release documentation, and prevention of mix-ups. The FDA also identifies formal review and authorisation of labeling changes as important quality-system controls. <Cite refs={["turn406500search2","turn406500search1"]}/>

ISO 13485 provides a quality-management framework for medical-device manufacturers, including document control, records, and production controls. Its relevance depends on applicable regulatory requirements, certification arrangements, and contractual obligations.

3. CORE LEGAL STANDARDS FOR VERSION CONTROL

A. UNIQUE VERSION IDENTIFICATION

Each controlled digital label should have a unique version identifier, approval date, effective date, product identifier, jurisdiction, and document owner. Where appropriate, the system should associate the label with the product's unique device identifier, catalogue number, or batch information.

B. FORMAL CHANGE CONTROL

Every material change should be documented through a controlled change request explaining the reason, affected products, regulatory impact, risk assessment, and implementation plan. Changes to dosage, contraindications, warnings, storage conditions, or intended use require heightened review.

C. AUTHORISED REVIEW AND APPROVAL

Label changes should be reviewed by the appropriate regulatory, quality, medical, safety, and technical personnel. Approval responsibilities should be defined, and the system should prevent unapproved versions from being published as current instructions.

D. TRACEABILITY AND AUDIT TRAILS

The system should preserve the previous version, the identity of the person making the change, the reviewer and approver, timestamps, reasons for modification, and the distribution or publication history. Electronic records and signatures must meet any applicable legal requirements.

E. PUBLICATION AND WITHDRAWAL

When a revised label becomes effective, controlled publication processes should ensure that authorised channels display the correct version. Superseded versions should be withdrawn from active use while remaining retrievable for audit, investigation, and historical traceability. Where physical stock remains in circulation, the manufacturer should assess whether relabeling, notification, corrective action, or recall is required.

F. VALIDATION AND CYBERSECURITY

Digital-label platforms should be validated for accuracy, permissions, change tracking, backup, recovery, and reliable publication. Access controls should prevent unauthorised edits. Hashes, digital signatures, and controlled repositories may strengthen integrity assurance, but do not replace regulatory review and approval.

4. RELEVANT CASE LAWS

A. DONOGHUE v. STEVENSON (1932) — ANALOGOUS PRODUCT-SAFETY AUTHORITY

The House of Lords recognised a manufacturer's duty of care toward the ultimate consumer. The decision provides a foundational principle for preventing foreseeable injury caused by defective products. In digital labeling, inaccurate or outdated safety instructions may contribute to negligence claims, depending on the facts and applicable law. The case did not address electronic version control.

B. GRANT v. AUSTRALIAN KNITTING MILLS LTD. (1936) — ANALOGOUS AUTHORITY

The Privy Council considered manufacturer responsibility for a defective consumer product. The decision illustrates the importance of product safety and the consequences of defects reaching end users. Its application to digital labels is indirect.

C. BOLAM v. FRIERN HOSPITAL MANAGEMENT COMMITTEE (1957) — ANALOGOUS PROFESSIONAL-STANDARD AUTHORITY

The English court considered the standard of care expected of medical professionals. Its reasoning may be relevant when assessing professional reliance on product instructions, although it does not establish a manufacturer's specific electronic-labeling obligations.

D. CAPARO INDUSTRIES PLC v. DICKMAN (1990) — ANALOGOUS NEGLIGENCE AUTHORITY

The House of Lords articulated principles concerning the duty of care, including foreseeability, proximity, and whether imposing a duty is fair, just, and reasonable. These principles may inform disputes involving foreseeable harm from inaccurate digital product information, subject to the applicable jurisdiction.

E. M.C. MEHTA v. UNION OF INDIA (OLEUM GAS LEAK CASE, 1986) — ANALOGOUS SAFETY AUTHORITY

The Supreme Court of India developed the principle of absolute liability for enterprises engaged in hazardous or inherently dangerous activities. The case reinforces the importance of stringent precautions in hazardous operations but does not directly govern digital-label versioning.

F. INDIAN MEDICAL ASSOCIATION v. V.P. SHANTHA (1995) — ANALOGOUS CONSUMER-PROTECTION AUTHORITY

The Supreme Court examined the application of consumer-protection law to medical services. The judgment illustrates the importance of accountability for healthcare-related harm. It is not a direct precedent on digital labeling or document version control.

5. PRACTICAL COMPLIANCE CHECKLIST

Maintain a controlled repository of approved digital labels.

Assign unique version numbers and effective dates.

Require documented regulatory and quality approval before publication.

Preserve complete change histories and archived versions.

Validate product, market, language, and batch associations.

Prevent unauthorised editing and accidental publication.

Establish procedures for urgent safety updates and withdrawal of obsolete labels.

Periodically audit the system and investigate discrepancies.

6. CONCLUSION

Version control of digital labels is a critical component of product safety, regulatory compliance, and quality assurance. Applicable laws may require accurate labeling, controlled changes, documented release, and prevention of mix-ups, even where they do not prescribe a specific software tool. Manufacturers should combine formal approval workflows, reliable version identification, audit trails, validated publication systems, and effective withdrawal procedures. Judicial decisions on product safety and professional responsibility provide supporting principles, but they should not be misrepresented as direct precedents establishing electronic-label version-control requirements.