FOR QUALITY AND DOCUMENT MANAGEMENT TEAMS

Every revision.A controlled release.

IFU revision management & controlled publishing

Manage instructions for use through preparation, independent review, approval and publication. Check products, audiences, markets and language coverage with each revision, while keeping versions and decision records connected to the same product.

Public preview · Sales are not yet open

From preparation to a published version

  1. 01

    Prepare the revision

    Map the new document version to its products. Define document type, audience, market and language coverage. Check for missing language versions before publication.

  2. 02

    Complete independent review

    Reviewers assess content and scope. Separate preparation from review and keep your team’s decision process recorded.

  3. 03

    Approve and publish

    The authorised team makes the publication decision. Connect the published version to product access and track previous versions and decision history through the same record.

How do current, previous and withdrawn IFUs differ?

IFU revision management is more than uploading a new PDF. Separate the current publication from version history by product, document type, audience, country and file language. Finding an earlier version in a portal does not mean it is the current IFU for use today.

Example: SAMPLE-001 from Rev. A to Rev. B

In this fictional example, the same product’s English IFU is published as Rev. A and then Rev. B for the same audience and country scope. This is not a customer record or a country-specific regulatory rule.

  1. 01

    Rev. A is published

    Rev. A appears in the current document list for the selected scope. Check product reference, document type, file language and revision together.

  2. 02

    Rev. B is published

    The later publication, Rev. B, appears in the current list for the same document and language; Rev. A is separated as a previous version in history. The product QR can continue to provide access if its link to the same product record is retained.

  3. 03

    Rev. B is withdrawn

    Rev. B is removed from the current published list; history shows its withdrawn status and reason. Rev. A does not automatically become current again. If no current document is available, follow the manufacturer’s support process.

Three distinct document states

Current published version
The latest document/language record for the selected product, audience and country is offered in the current list when it is published. File language and document type selections also apply.
Previous published version
History identifies it as a previous version. A file that remains published can be viewed if it meets the access conditions; it is not presented as current.
Withdrawn version
History shows its withdrawn label and reason, without a file viewing link for that record. File access also checks that the revision is published.

Direct answers about IFU version history

Is a previous IFU the same as a withdrawn IFU?

No. A previous version is outside the current list because a newer publication exists. Withdrawal is a separate publication status. The portal distinguishes these records in history with different labels and access behaviour.

Does the old IFU become current again if the latest version is withdrawn?

Not automatically. eIFU Systems checks the publication status of the latest document/language record for the selected scope; it does not automatically reinstate an earlier version as current. Your authorised team must assess the publication decision and the resulting portal display.

Does publishing a revision require changing the printed product QR?

If the QR points to the same product record rather than a PDF file and the product link is retained, a new version can be offered through the same product access. Test the domain, link, product mapping and relevant language/scope publication after release.

Does withdrawing an IFU delete PDFs already downloaded?

No. Changing portal access does not remove a file a user previously saved on their device. Handle earlier copies and any required user communication separately within the manufacturer’s document and safety processes.

Records to check in your demonstration

  • Compare the same product, document type, file language, audience and country for Rev. A and Rev. B.
  • After publishing Rev. B, check the current file through the product QR and the previous-version label for Rev. A in history.
  • In a test environment, withdraw Rev. B and separately check the current list, withdrawal reason and file access.
  • Confirm that withdrawal does not automatically present the earlier version as current.
  • Assess publication decisions separately from user communication and delivery records.

Explore product QR link continuity →

Explore publication and withdrawal workflows →

Discuss your revision and version history scope ↗

Keep version history connected to products

A product can be associated with several document types and language versions. Assess a new file version together with its publication scope: products, intended audiences, markets and languages. Previous versions and decision records help your team follow changes over time.

Permanent access, controlled document changes

Connect QR links to product access. When a new version is published, visitors can reach the relevant documents through the same product link. Check product mappings and the version visible in the portal after publication. Manage revision follows and user requests alongside your document workflow.

Explore product document access →

Check multilingual document coverage →

Read the IFU publication workflow guide →

Revision management questions

Is a new revision published immediately?

Preparation, independent review and the publication decision are separate steps. Your team completes review and approval using the appropriate permissions.

Does one revision cover every language?

Language versions and market coverage are assessed by product and document. Uploading a file in one language does not establish that the other language versions are ready.

Does a new version require a new QR code?

The permanent product link is managed separately from the document file. A new revision can be available through the same product link. Check mappings and document access after publication.

Does this workflow guarantee regulatory compliance?

No. The platform provides tools for controlled publication and traceability. Your quality and regulatory teams remain responsible for content accuracy, product eligibility and market obligations.

LET’S DISCUSS YOUR REQUIREMENTS

See the platform with your team.

We will walk through document access, revision management and multilingual publishing around your product range and markets.

Chat on WhatsApp ↗

DEMO REQUEST

Tell us what you need.

This form prepares a WhatsApp message. Your request is sent only when you send it in WhatsApp. Do not include patient information or confidential documents. Privacy information (Turkish)