Your Clinical Evaluation Exists, but Does It Support the Device Claims?

Start with the decision

Turn labelling, the IFU and scientific material into a reviewable claim inventory. Define the evidence type needed for each claim instead of treating the evaluation as one block.

The source basis is MDS-REQ 1 Medical Devices Marketing Authorization. Regulatory statements come from those sources; the workflow and review tools are Basier professional recommendations.

Build the evidence chain

1. Turn labelling, the IFU and scientific material into a reviewable claim inventory.
2. Define the evidence type needed for each claim instead of treating the evaluation as one block.
3. Test whether populations, device versions, comparators and outcomes apply to the submitted product.
4. Record gaps, uncertainty and limitations that must flow into risk management and labelling.
5. Maintain traceability when literature, design or intended purpose changes.

Run the method on a live case before treating it as established. A procedure or certificate does not prove that records align, responsibilities are understood or the decision was executed. A real sample exposes handoff and version failures that a generic checklist often misses.

Three reviews before approval

First confirm the facts: current source, version, device or establishment scope, and the data behind the decision. Time-bound information or opportunity-specific assumptions should carry a date and should not become a permanent rule by accident.

Then run a cross-functional review. Regulatory, quality, product, operations or channel owners should participate according to the subject. The purpose is to expose any gap between the controlled record and what the organisation can actually execute while keeping one accountable decision owner.

Finally assess downstream impact. Identify the documents, records, versions and systems that must change, together with the evidence that will demonstrate implementation and outcome. A decision without follow-through usually reappears as the next change, audit or tender gap.

Questions that slow down a weak decision

• Is the scope tied to a known product, establishment or opportunity?
• Is one approved version used by every relevant owner?
• Does each gap have an owner, date and closure evidence?
• What new information would reopen the decision?

Where control is usually lost

Breakdowns tend to start with unverified inputs, different versions across functions or an exception with no owner and closure date. Records also lose value when they describe the event without showing who decided, why the decision was justified and what evidence would cause it to change.

The operating deliverable

A claim-evidence matrix and clinical-evaluation gap register.

The deliverable should state scope, assumptions, sources, versions, owners and closure criteria. That structure lets the team update a decision when new evidence appears without rebuilding the file from the beginning.

Basier scope and limits

Basier supports this work through Technical documentation and product compliance by reviewing evidence, structuring the operating record and testing gaps with the team. Basier does not issue authority decisions or guarantee acceptance, certification, qualification or award. Relevant service: Technical Documentation and Product Compliance

References: [1]