Peru, the Dominican Republic and Uruguay: why one Spanish device dossier does not fit all three

"We already have the Spanish dossier from Mexico. Can we just send it to Peru, the Dominican Republic and Uruguay?" I hear some version of that question every month. The honest answer is that you can reuse a lot of the translated content, but not the dossier. Each of these three regulators asks for a differently shaped file, with different rules for foreign documents, different labeling fields and different authentication steps. A single "pan-Latin American Spanish dossier" usually means three observation letters.

I'm Julio Martinez-Clark, co-founder of Amavita Sciences™ and CEO of bioaccess®, the First-in-Human CRO for medical devices in Latin America since 2010. This article is the translation and dossier-assembly view of three markets that often get bundled together late in a launch plan: Peru (DIGEMID), the Dominican Republic (DIGEMAPS) and Uruguay (MSP). If you need the commercial registration and holder strategy for each country, bioaccess® covers that in separate guides for Peru, the Dominican Republic and Uruguay. Here I focus on what has to change in the documents.

Spanish is the official language in all three countries, so it is tempting to think of language as solved once you have a good Spanish version. But a regulator does not review language in the abstract. It reviews a file against its own regulation, and the three regulations below were written at different times, on different templates, with different assumptions about foreign documents.

What carries across well is the technical translation itself: device description, intended use, warnings, the risk management narrative and test summaries, as long as they are built from one controlled term list. What does not carry across is the wrapper: which documents must be in Spanish, which can stay in English, what kind of translation each one needs, what must be authenticated, how old a certificate can be, and which local fields go on the label.

Peru regulates devices under Ley N° 29459 and its regulation, Decreto Supremo N° 016-2011-SA (published 27 July 2011), with DIGEMID acting as the national authority for pharmaceutical products, medical devices and health products. Device classification and essential principles were updated by Decreto Supremo N° 003-2020-SA, which ties the "descripción de la eficacia y seguridad" requirement to a checklist of essential principles of safety and performance.

Three Peru-specific points shape the Spanish file.

The technical core is the informe técnico. Article 130 of DS 016-2011-SA sets out what the device technical report must contain: a detailed description of the device, including its operating principle, composition and accessories; the indication or intended use; precautions, restrictions, warnings and storage and transport conditions; presentation forms; and, where it applies, a basic manufacturing flow diagram. Briefs and vendors sometimes call this a "ficha técnica." For devices, plan around the informe técnico structure in Article 130, and build your Spanish translation to that outline rather than to your US or EU table of contents.

Technical studies are summarized, not dumped. DIGEMID's published requirements for Class II and Class III registration ask for "estudios técnicos y comprobaciones analíticas," satisfied by manufacturer documents such as a summary of design verification and validation, a declaration of conformity with international reference standards, and a certificate of analysis of the finished device where one exists. Translating 400 pages of raw test reports is usually the wrong move. Translating accurate summaries that trace back to those reports is the right one.

Foreign documents need a simple translation and must be fresh. Article 28 of DS 016-2011-SA, as amended, says documents issued abroad must be no more than two years old from issue unless they state a different validity, and must be accompanied by a simple Spanish translation (traducción simple). DIGEMID may also designate by comunicado which documents can be filed in English. Peru is therefore more permissive than its neighbors on translation tier, and less forgiving on currency. Our DIGEMID translation guide goes deeper on this point.

Labeling follows Article 137: labels and IFUs in Spanish, with other languages allowed alongside if the information matches the sanitary registration.

DIGEMAPS (Dirección General de Medicamentos, Alimentos y Productos Sanitarios) was created by Decreto 82-15 of 6 April 2015. The substantive rule set operators file against is Decreto 246-06 of 9 June 2006. Its title refers to medicines, but Article 1 extends its principles and requirements to productos sanitarios, which is why device files in the Dominican Republic are still prepared against this regulation.

Three provisions change the shape of the Dominican file compared with Peru.

Legal documents go to an intérprete judicial. Article 32 states that documents not in Spanish must be translated by an intérprete judicial, and names certificates of free sale, GMP certificates and powers among them. A simple translation that works in Lima does not satisfy this. Separate those documents in your plan early, because they follow a different route and a different timeline from the technical translation.

Foreign documents must be authenticated. The text of Article 32 calls for legalization by the Dominican consular authority in the country of origin and by the Dominican foreign ministry. The Dominican Republic acceded to the Hague Apostille Convention, which entered into force for it on 30 August 2009, so documents from other contracting states are generally authenticated by apostille rather than by consular legalization. Confirm the route DIGEMAPS currently accepts for your document type before you order apostilles.

Technical reports must be in Spanish and clean. Article 39 requires chemical, pharmaceutical, biological, toxicological, pharmacological and clinical reports to be written in Spanish, or accompanied by a translation if they are in another language, and states that they must not show strikeouts, erasures, stains or signs of alteration. That last clause is easy to miss. A scanned report with handwritten corrections can be a problem regardless of translation quality.

The Dominican file also has a representation element. Article 31 requires a power of representation from the foreign manufacturer to the Dominican establishment that applies for, and holds, the registration. That power is a legal instrument, so it falls under the Article 32 translation and authentication rules. Articles 31 and 32 are drafted around pharmaceutical products, so confirm with DIGEMAPS how they are applied to your device class before you finalize the legal track. Our DIGEMAPS translation guide covers the forms and tiers in more detail.

Uruguay regulates diagnostic reagents, medical equipment and medical devices under Decreto N° 3/008 of 2008, which updated the earlier 1999 device decree (Decreto 165/99). The decree's structure is different from both Peru and the Dominican Republic, and it changes who signs and what the label must say.

Only enabled companies register products. Under Articles 2 and 6, companies that manufacture, import, store, distribute or service these products must be enabled (habilitadas) by MSP, and only enabled companies can register products. Registration is valid for five years. Article 7 lists what the registrant files, including proof of enablement, technical specifications, the documentation that ships with the product (leaflets, instructions, user manuals, warranties) and a certificate of free sale from the competent authority of the country of origin. If the origin country does not issue one, MSP may accept a quality certificate from a recognized body instead.

Signatures are local. Article 7 also requires the application to be signed by the company's legal representative and its Director Técnico. Your translated documents need to be ready for those local signatories, not just for the manufacturer.

The technical report mirrors Peru's, with a twist. Article 8 describes a technical report with a familiar outline: detailed description, intended use, precautions and warnings, presentation forms, a manufacturing flow diagram and a description of safety and efficacy. It adds that if that description does not demonstrate safety and efficacy, MSP may ask for clinical investigation at the importer's or manufacturer's cost. Sterile devices add sterilization and sterility-control protocols under Article 9. The overlap with Peru's Article 130 is useful: a well-built Peruvian informe técnico is a strong starting point for Uruguay, but it still needs the Uruguayan wrapper.

Labels carry Uruguayan registration data. Article 15 requires Spanish labeling that includes, among other items, the product name, lot, manufacturer and importer details, the MSP registration number and the name of the responsible Director Técnico, plus sterilization date and method where relevant. Article 16 lists IFU content such as performance, service life, possible side effects and maintenance. A label reused from Peru or Mexico will be missing these fields.

Registration is by product family. Article 32 organizes registration by families classified by product type, complexity and risk, and Article 11 sets the clock: up to 180 days, suspended when MSP raises observations, with 90 days to cure them before the file is archived.

The way out is not three separate translation projects. It is one master technical file, translated once, wrapped three ways.

1. Build the core once. Device description, intended use, warnings, risk narrative and verification and validation summaries, translated from source into Spanish against one approved term list. This core should map cleanly to the Peru Article 130 and Uruguay Article 8 outlines, because they are close.
2. Write country labels, not a regional label. One master label text, then a Peru variant, a Dominican variant and a Uruguay variant with that country's mandatory fields.
3. Split legal instruments out early. Certificates of free sale, GMP certificates and powers follow different rules in each country: simple translation and a two-year limit in Peru, judicial translation and authentication in the Dominican Republic, local enablement and local signatories in Uruguay. Plan them as a separate track.
4. Track document currency against the filing date. Know the issue date of every foreign certificate and the date you expect to file in each country. A certificate that is current for one filing can be stale for the next.
5. Keep one version log. When the source changes, you need to know which country packages it affects.

The Amavita Sciences™ regulatory translation matrix lists the instrument behind each language rule for the regulators we cover, and our apostille vs. sworn translation guide helps you sort the legal-instrument track.

We translate device files directly from the origin language into Latin American Spanish, with clinical review and a country-by-country regulatory check, and each document ships with a signed certificate of accuracy. Amavita Sciences™ is not a sworn translator or an intérprete judicial. Where a document needs that tier, we identify it at scoping and route it to a licensed professional, so the legal track does not surprise you at filing.

If Peru, the Dominican Republic and Uruguay are on your launch list, send us your master technical file and the order you plan to file in. You can start with a one-document pilot or see how we handle full files on our medical device translation services page.

Julio Martinez-Clark, co-founder, Amavita Sciences™, and CEO, bioaccess®. Operator guidance based on the published instruments cited above; not legal advice. Forms and practice change, so confirm current requirements with each regulator before filing.