Close

Clinerion received ISO 27001:2013 certification

Note* - All images used are for editorial and illustrative purposes only and may not originate from the original news provider or associated company.

Related stories

Managing Quality and Regulatory Risks in Pharmaceutical Technology Transfer

Technology transfer moves more than manufacturing instructions. It moves process knowledge, supplier dependencies, labeling requirements, packaging specifications, and the evidence needed to demonstrate control. For medical device manufacturers, including those supporting drug-device combination products, these interfaces can become recurring sources of compliance gaps during site transitions, acquisitions, and remediation. The central problem is often not a missing procedure. It is a quality system that allows connected activities to change independently. A label revision may be approved while packaging artwork, supplier instructions, or production-system data still reflect an obsolete version. Staying inspection-ready requires manufacturers to manage these dependencies as one controlled system. Why Compliance Gaps Keep Recurring Findings are treated as documentation defects Revising a procedure can resolve an immediate discrepancy without changing the behavior that caused it. If unclear decision rights, weak escalation, or ineffective training remain, the same failure may surface elsewhere. Corrective and preventive action should distinguish the observed finding from its underlying cause and establish how effectiveness will be demonstrated. Ownership is divided across connected functions Quality, Regulatory Affairs, labeling, packaging engineering, operations, suppliers, and digital-system owners often maintain separate workflows. Each team may complete its assigned task while an interface remains uncontrolled. For example, changing an instruction for use can affect packaging configuration, translations, technical documentation, inventory disposition, and release controls. Transitions expose unresolved weaknesses Acquisitions and site transfers can introduce conflicting procedures, incomplete knowledge transfer, or different assumptions about validated processes. Regulatory changes add further demands. When these events coincide with CAPA or change-control backlogs, teams may prioritize administrative closure over risk reduction. Without a coordinated impact assessment, local fixes can create new gaps downstream. Establish the Regulatory Baseline Inspection readiness starts with knowing which requirements apply to the product, activity, and market. Pharmaceutical, device, and combination-product obligations are not interchangeable; transfer planning should identify the applicable requirements rather than assume one quality framework covers every operation. According to FDA’s Quality Management System Regulation overview and FAQs, the QMSR became effective on February 2, 2026, incorporates ISO 13485:2016 by reference, and introduced the updated device inspection process under Compliance Program 7382.850. ISO 13485 certification does not exempt a manufacturer from FDA inspection or guarantee compliance with FDA requirements. For devices marketed in the European Union, Regulation (EU) 2017/745, Annex I, Section 23, provides the primary requirements for information supplied with devices, including labels and instructions for use. Teams should assess the applicable provisions alongside relevant language, product-specific, and market requirements. A labeling review should therefore evaluate required content and consistency with the device’s intended purpose and supporting documentation—not merely artwork accuracy. How to Identify the Real Gaps Begin with a cross-functional assessment that follows actual product and information flows. Select representative transfers, label changes, supplier changes, and CAPAs, then trace each from initiation through implementation and effectiveness review. Map dependencies: Identify affected specifications, suppliers, packaging components, systems, validation activities, and training. Compare records with practice: Check whether approved procedures match what operators and reviewers actually do. Test traceability: Follow a requirement through technical documentation, labeling, production instructions, and release evidence. Examine recurrence: Look for repeated deviations, reopened actions, overdue changes, and findings shared across sites. Assess capacity: Determine whether qualified owners have enough time and authority to complete corrective work. Prioritize gaps by potential patient or user harm, regulatory impact, likelihood of recurrence, and detectability. Document the rationale; an old overdue item is not automatically more important than a newly identified high-risk weakness. Align Quality, Labeling, Packaging, and Change Control Create a coordinated remediation plan with one accountable owner for each action, named contributors, acceptance criteria, and required evidence. Separate immediate containment from systemic correction. Containment might prevent obsolete labels from being issued; correction might redesign approval and implementation controls so obsolete versions cannot return. Use change control as the integration point. Before approval, evaluate effects on regulatory submissions or notifications, technical documentation, supplier controls, packaging performance, validation, electronic master data, inventory, and training. Record both identified impacts and justified decisions that particular activities are unaffected. During technology transfer, define readiness gates before production or release responsibilities move. These should address the transfer of process knowledge, acceptance criteria, receiving-site capability, required qualification or validation, approved documents, and personnel competence. The appropriate evidence depends on the product and process; a generic checklist cannot replace a documented assessment. Finally, verify implementation where the work happens. Confirm that current instructions are available, suppliers received approved requirements, systems contain correct versions, and affected personnel can perform their tasks. A signed approval is not evidence that every downstream change took effect. Mistakes That Undermine Inspection Readiness Closing CAPAs on task completion alone: Effectiveness checks should test whether the underlying failure has been controlled. Updating labels in isolation: Assess packaging, supplier, system, documentation, and inventory consequences. Counting closures instead of evidence: Dashboards need defensible records behind their status indicators. ...

State of API & Peptide CDMO Capacity

Pharmaceutical companies planning peptide or complex small-molecule launches are...

Improving Therapeutic Development with Female Clinical Endpoints

The pharmaceutical industry faces growing pressure to refine how...
- Advertisement -

Clinerion has gained ISO 27001:2013 certification, the international standard that describes best practice for an information security management system (ISMS).

ISO 27001:2013 is a standard set by the International Organization for Standardization (ISO), the independent, non-governmental international organization of national standards bodies. ISO 27001:2013 is the international standard that describes best practice for an information security management system (ISMS). This International Standard can be used by internal and external parties to assess an organization’s ability to meet the organization’s own information security requirements.

To quote the ISO:

“ISO/IEC 27001:2013 specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. It also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization.”

“The information security management system preserves the confidentiality, integrity and availability of information by applying a risk management process and gives confidence to interested parties that risks are adequately managed.”

Clinerion was assessed by and received ISO 27001:2013 certification from the certification organization DSR.

“We are very pleased to receive this certification, which reflects the fact that Clinerion’s information security management system is part of and integrated with our processes and overall management structure,” says Ian Rentsch, CEO of Clinerion. “For Clinerion, information security is considered in the design of processes, information systems, and controls. Our implementation of our information security management system can be scaled in accordance with the needs of the organization.”

About Clinerion

Clinerion accelerates clinical research and medical access to treatments for patients. We use proprietary technologies for analysis of patient data from our global network of partner hospitals. Clinerion’s Patient Network Explorer radically improves the efficiency and effectiveness of clinical trial recruitment by offering data-driven protocol optimization, site feasibility evaluation and real-time patient search and identification to match patients to treatments. Our technology solution provides real-world evidence analytics for medical access. Clinerion facilitates the participation of partner hospitals in leading-edge, industry-sponsored trials and time savings in patient recruitment. We create innovative and disruptive fit-for-purpose solutions which enable pharmaceutical companies to shorten patient recruitment and save costs by streamlining operations and leveraging strategic intelligence. Clinerion’s proprietary Big Data analytics technologies leverage real-time data from electronic health records which comply with international patient privacy and data security regulations. Clinerion is a global data technology service company headquartered in Switzerland.

Never miss a pharmaceutical headline

The pharmaceutical industry moves fast – stay on top of it with our must - read briefings.

  • The top pharma and life sciences stories, straight to your inbox
  • The biggest news, features, interviews, and analysis
  • Dedicated coverage of the key developments driving the global pharmaceutical sector

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access the Media Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Latest stories

Related stories

Managing Quality and Regulatory Risks in Pharmaceutical Technology Transfer

Technology transfer moves more than manufacturing instructions. It moves process knowledge, supplier dependencies, labeling requirements, packaging specifications, and the evidence needed to demonstrate control. For medical device manufacturers, including those supporting drug-device combination products, these interfaces can become recurring sources of compliance gaps during site transitions, acquisitions, and remediation. The central problem is often not a missing procedure. It is a quality system that allows connected activities to change independently. A label revision may be approved while packaging artwork, supplier instructions, or production-system data still reflect an obsolete version. Staying inspection-ready requires manufacturers to manage these dependencies as one controlled system. Why Compliance Gaps Keep Recurring Findings are treated as documentation defects Revising a procedure can resolve an immediate discrepancy without changing the behavior that caused it. If unclear decision rights, weak escalation, or ineffective training remain, the same failure may surface elsewhere. Corrective and preventive action should distinguish the observed finding from its underlying cause and establish how effectiveness will be demonstrated. Ownership is divided across connected functions Quality, Regulatory Affairs, labeling, packaging engineering, operations, suppliers, and digital-system owners often maintain separate workflows. Each team may complete its assigned task while an interface remains uncontrolled. For example, changing an instruction for use can affect packaging configuration, translations, technical documentation, inventory disposition, and release controls. Transitions expose unresolved weaknesses Acquisitions and site transfers can introduce conflicting procedures, incomplete knowledge transfer, or different assumptions about validated processes. Regulatory changes add further demands. When these events coincide with CAPA or change-control backlogs, teams may prioritize administrative closure over risk reduction. Without a coordinated impact assessment, local fixes can create new gaps downstream. Establish the Regulatory Baseline Inspection readiness starts with knowing which requirements apply to the product, activity, and market. Pharmaceutical, device, and combination-product obligations are not interchangeable; transfer planning should identify the applicable requirements rather than assume one quality framework covers every operation. According to FDA’s Quality Management System Regulation overview and FAQs, the QMSR became effective on February 2, 2026, incorporates ISO 13485:2016 by reference, and introduced the updated device inspection process under Compliance Program 7382.850. ISO 13485 certification does not exempt a manufacturer from FDA inspection or guarantee compliance with FDA requirements. For devices marketed in the European Union, Regulation (EU) 2017/745, Annex I, Section 23, provides the primary requirements for information supplied with devices, including labels and instructions for use. Teams should assess the applicable provisions alongside relevant language, product-specific, and market requirements. A labeling review should therefore evaluate required content and consistency with the device’s intended purpose and supporting documentation—not merely artwork accuracy. How to Identify the Real Gaps Begin with a cross-functional assessment that follows actual product and information flows. Select representative transfers, label changes, supplier changes, and CAPAs, then trace each from initiation through implementation and effectiveness review. Map dependencies: Identify affected specifications, suppliers, packaging components, systems, validation activities, and training. Compare records with practice: Check whether approved procedures match what operators and reviewers actually do. Test traceability: Follow a requirement through technical documentation, labeling, production instructions, and release evidence. Examine recurrence: Look for repeated deviations, reopened actions, overdue changes, and findings shared across sites. Assess capacity: Determine whether qualified owners have enough time and authority to complete corrective work. Prioritize gaps by potential patient or user harm, regulatory impact, likelihood of recurrence, and detectability. Document the rationale; an old overdue item is not automatically more important than a newly identified high-risk weakness. Align Quality, Labeling, Packaging, and Change Control Create a coordinated remediation plan with one accountable owner for each action, named contributors, acceptance criteria, and required evidence. Separate immediate containment from systemic correction. Containment might prevent obsolete labels from being issued; correction might redesign approval and implementation controls so obsolete versions cannot return. Use change control as the integration point. Before approval, evaluate effects on regulatory submissions or notifications, technical documentation, supplier controls, packaging performance, validation, electronic master data, inventory, and training. Record both identified impacts and justified decisions that particular activities are unaffected. During technology transfer, define readiness gates before production or release responsibilities move. These should address the transfer of process knowledge, acceptance criteria, receiving-site capability, required qualification or validation, approved documents, and personnel competence. The appropriate evidence depends on the product and process; a generic checklist cannot replace a documented assessment. Finally, verify implementation where the work happens. Confirm that current instructions are available, suppliers received approved requirements, systems contain correct versions, and affected personnel can perform their tasks. A signed approval is not evidence that every downstream change took effect. Mistakes That Undermine Inspection Readiness Closing CAPAs on task completion alone: Effectiveness checks should test whether the underlying failure has been controlled. Updating labels in isolation: Assess packaging, supplier, system, documentation, and inventory consequences. Counting closures instead of evidence: Dashboards need defensible records behind their status indicators. ...

State of API & Peptide CDMO Capacity

Pharmaceutical companies planning peptide or complex small-molecule launches are...

Improving Therapeutic Development with Female Clinical Endpoints

The pharmaceutical industry faces growing pressure to refine how...

What Goes Into Synthetic Urine? The Chemistry Behind Replicating a Biological Fluid

Synthetic urine sounds simple until you look closely at...

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access theMedia Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Translate »