Evidence for systems that carry regulated work.
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
Kivo documents submission structures, content placeholders, a blinded-or-unblinded toggle, tracking spreadsheets, and export to publishing partners or software. A handoff still needs an approved content inventory, artifact-level blinding state, immutable transfer manifest, and receiver reconciliation before it can be treated as complete or appropriately disclosed.
Generis presents CARA as one governed platform spanning regulatory, quality, safety, and clinical processes, with shared records and audit trails. The same underlying record can reduce re-entry, but each configured process still needs intended-use, migration, access, workflow, calculation, report, interface, and exception evidence before the organization can rely on it for regulated work.
EMA says the PLM web-based electronic Application Form becomes mandatory for human Centrally Authorised Product variation submissions on September 1, 2026, with justified technical exceptions for continued interactive-PDF use. Regulatory operations need to preserve the applicable form path, impediment, support evidence, submission package, and receipt outcome as separate controlled facts.
ArisGlobal presents LifeSphere Regulatory as an end-to-end environment for regulatory data, content, submissions, labeling, planning, tracking, and health-authority interactions. Connecting those records can improve oversight, but an incoming question, an outgoing response, a promised action, and completion evidence still need distinct identities, owners, dates, and approval states.
Rimsys presents regulatory intelligence, product data, approvals, submissions, UDI, and change management as a connected regulatory information environment for medtech. Connection can speed impact analysis, but a new signal or proposed change should not silently rewrite the product and registration state that was actually approved.
Veeva describes a single cloud platform spanning quality assurance, quality control, and training. Connected records can reduce handoff friction without making a document approval, investigation conclusion, laboratory result, and training completion interchangeable.
Veeva documents one shared platform and data model across four regulatory applications. That connection should preserve the different states of a registration, submission plan, published dossier, authority correspondence, and historical archive.
Regulation (EU) 2017/746 connects scientific validity, analytical performance, clinical performance, post-market follow-up, and lifecycle updates. One completed study or stored report cannot stand in for that maintained evidence chain.
The July release carries bug fixes and sits inside a broader transition toward structured application data, new MAA forms, and mandatory PLM web-based eAF use for centrally authorised product variations.
The July package refresh adds forward-compatibility samples and revises regional vocabulary, conformance, and transmission materials for a standard FDA already accepts for new applications.
The transition moves actor, device, certificate, and market-surveillance records from voluntary use into required EU operating workflows, increasing the cost of disconnected regulatory data.
The rule now incorporates ISO 13485:2016 by reference and replaces QSIT with a new inspection process, shifting the questions device manufacturers should ask of quality systems and evidence.
The January transition changes classification and procedure rules for post-authorisation changes, forcing regulatory operations teams to align systems, forms, content, and implementation dates.
