Spanish Language Requirements for Labels and IFUs in Peru

Regulatory information verified as of October 29, 2026.

1. Key takeaways

Spanish is not a translation step that can be remedied later; it is a formal requirement of the Peruvian sanitary registration dossier. The mandatory elements of labels and instructions for use must be presented in Spanish, the core chapters of the technical file must be provided in Spanish, and the translations must remain consistent with the submitted dossier. The statutory anchor of the language obligation is the packaging and labeling chapter of D.S. N° 016-2011-SA, published on 2011-07-27, listing the mandatory content (specific article numbers pending verification; official publication controls), under which the simplified label contains at minimum 5 elements. Scheduling translation after the certificate is granted simply adds an unnecessary round of observations to the review. The language duty also extends to controlled consistency: a Spanish version that diverges from the technical file in scope statements, warnings or performance claims is treated as an inconsistency between documents, not as a minor editorial issue, and it must be corrected within the same correction window as any other deficiency. Labeling is the surface the regulator and the market actually see, so it carries the highest exposure of any translation defect.

2. Legal basis

Regulatory information verified as of October 29, 2026.

3. Expert insights

Insight 1: The language obligation and the label elements are coupled, so one translation error triggers two rejection grounds.

The 5 mandatory elements of the simplified label, namely name or code, batch number, expiry date, storage and transport conditions, and registration number, plus ESTERIL where applicable, must each be legible and verifiable in Spanish. Mechanically, the reviewer checks two dimensions: whether the elements are complete, and whether each element is correctly expressed in Spanish consistent with the dossier. A missing element constitutes incompleteness; an element present but inconsistent with the dossier constitutes information inconsistency. A single translation slip can hit both rejection grounds at once, and the correction window is only 30 working days (practical estimate).

Insight 2: Terminological consistency is an invisible defense of scope.

The Spanish terms, such as lote, fecha de vencimiento and condiciones de almacenamiento, must stay consistent with the technical terminology in the dossier. Synonym drift caused by machine translation is not a cosmetic flaw; it can change how the reviewer reads the product scope. When the same component appears under three different names in the label, the instructions for use and the technical report, the review will demand clarification of the product composition, which in turn triggers supplementary data requests. The step GRZAN performs first in its projects is building a Spanish terminology table and locking the rendering of key components before batch translation begins.

Insight 3: Language capability is the precondition for executable vigilance duties.

R.M. N° 539-2016/MINSA, published on 2016-07-27, requires the designation of an in-country responsible party and the performance of reporting duties: serious adverse events within 24 hours, moderate and mild suspected adverse events within 20 calendar days, and field safety notices (Nota de Seguridad en Campo) executed within Peru. All of these actions take place in a Spanish-language context: communication with health facilities, distributors and the regulator is in Spanish. A foreign manufacturer without Spanish capability or local language support cannot operationally meet the 24-hour line, and the duty remains unexecuted on paper. Field safety notices illustrate the point concretely: drafting, distributing and confirming receipt of a Nota de Seguridad en Campo all run through distributors and health facilities in Spanish, so the language plan is part of the vigilance plan, not a separate marketing function.

4. Practical recommendations

1. Build the terminology table first: lock the Spanish terminology covering product names, components, warnings and storage and transport wording before translation starts.
2. Pre-review label proofs: produce Spanish label proofs against the 5 mandatory elements and compare them item by item with the technical parameters in the dossier before finalizing.
3. Translate the core chapters of the technical file: provide Spanish versions of the technical report, the essential principles checklist and the instructions for use, controlled in step with the originals.
4. Staff vigilance roles with Spanish capability: the in-country responsible party must be able to communicate in Spanish so the 24-hour and 20-calendar-day lines are executable.
5. Add the IVD-specific labeling: state specificity and sensitivity on the label per D.S. N° 020-2001-SA, published on 2001-07-16, and render them in Spanish at the same time.

5. Verification checklist

□ Established and locked the Spanish terminology table, with consistent wording across labels, instructions for use and the technical report, and version-controlled under the same document system as the dossier

□ Produced and pre-reviewed Spanish label proofs against the 5 mandatory elements

□ Confirmed that applicable sterile products carry the ESTERIL marking

□ Confirmed that the core chapters of the technical file exist in Spanish under document control

□ Confirmed that the in-country vigilance responsible party can communicate in Spanish

□ Confirmed that in vitro diagnostic device labels state specificity and sensitivity in Spanish

Regulatory information verified as of October 29, 2026.

GRZAN Regulatory Team

GRZAN provides medical device registration support in Peru for manufacturers, importers and authorized representatives. For inquiries, contact info@grzanglobal.com.