Let’s be honest — regulatory updates don’t usually make it to your “interesting reads” list.
But MIR 7.3.1 is different.
Why? Because this isn’t just another version update. It’s a fix to real problems that manufacturers were struggling with — from broken XML exports to confusing validation rules and unclear signature requirements.
If you’ve ever felt frustrated while preparing an MIR… this update is for you.
🚀 What is MIR 7.3.1 (And What It Is Not)
The Manufacturer Incident Report (MIR) is the standard form used to report:
- Serious incidents
- Follow-up reports
- Final reports
under MDR and IVDR.
Now here’s the important part:
👉 MIR 7.3.1 does NOT change regulations
👉 It improves how you report, not what you report
No new timelines. No new obligations. No new data fields.
Just a much-needed technical and usability upgrade.
😬 The Rocky Start: What Went Wrong in 2025
When MIR 7.3.1 was first released, it didn’t land well.
Many teams faced issues like:
- Data not saving correctly (especially market distribution)
- Mandatory fields not clearly indicated
- Mismatch between PDF behavior and XML validation
- Confusing IMDRF coding rules
And then came one of the most overlooked — yet impactful — issues…
🔐 The XML Signature Confusion (The Silent Blocker)
This wasn’t a system bug. It was worse — a clarity problem.
Teams across organizations were asking:
- Do we need to digitally sign the XML before submission?
- Does signing the PDF automatically validate the XML?
- Why does XML export fail — is it because of missing signature?
Even though the help text clearly states:
👉 “The signature is optional.”
…in practice, things weren’t so clear.
- Some systems blocked XML export due to security settings
- Signing locked the document, making users hesitant
- Lack of clear guidance led to inconsistent internal processes
👉 Result?
- Delays in submission
- Dependency on IT teams
- Overcomplicated workflows for something that wasn’t even mandatory
This became a hidden inefficiency across many organizations.
✅ The Turning Point: December 2025 Fix
This is where MIR 7.3.1 finally became usable.
The December 2025 update didn’t add anything new — it fixed what was broken.
🧾 A Better, Cleaner PDF Experience
- Fixed-size free text fields (no more hidden or cut-off content)
- All text duplicated at the end for easy review and printing
- Mandatory fields clearly highlighted
- Simplified submission buttons
- Electronic signature made optional
👉 Less confusion. Faster completion. Better review experience.
🔐 XML is Finally Reliable (and Less Stressful)
- XML export issues resolved
- Security restrictions removed
- No dependency on signature for XML generation
👉 This directly reduces the earlier XML signature confusion
Now:
- You don’t need to “guess” if signing is required
- XML works independently
- Less back-and-forth between regulatory and IT teams
🧩 IMDRF Coding — Now Logical
- Correct enforcement of coding rules
- Annex C no longer incorrectly mandatory
- Alignment across PDF, Helptext, and XML
👉 Fewer validation errors. Fewer rejections.
⚙️ Stronger XML/XSD Foundation
- Obsolete fields removed
- Mandatory rules corrected
- Better PDF ↔ XML alignment
👉 Your automated systems finally behave predictably.
📘 Better Guidance for Users
- Clear helptext improvements
- Instructions for handling PDFs
- Better visibility of free-text sections
👉 Easier audits and internal reviews.
🔍 A Small Detail That Caused Big Confusion
Let’s pause on something simple — but powerful.
The help text clearly says:
👉 “The signature is optional.”
Yet many teams treated it as mandatory.
Why?
- Fear of submission rejection
- Confusion between PDF signing and XML submission
- Concern about data getting locked after signing
👉 The result was over-complication of workflows.
The updated version fixes this by making the process clearer:
- Signature = optional
- XML = independent of signature
- Signing = only if your internal SOP requires it
Bottom line:
👉 Don’t over-engineer your process for something that isn’t required.
🆕 March 2026 Update: Final Polishing Touches
Just when things stabilized, a March 2026 update (Version 7.3.1 – SB-11010) added a few important refinements.
What was fixed:
- Error in Field 1.2.e (linked to risk class 2.4) when changing document type
- Removed “Align form after import” button (UI glitch fix)
- Fixed incorrect validation in Field 4.3.1.a (Annex A issue when “Other” selected)
👉 And importantly:
- No changes to XML/XSD
💡 Why This Matters
These are small fixes — but high impact:
- Fewer false errors
- Cleaner UI experience
- Less frustration during form completion
👉 This is the kind of polish that makes a system truly usable.
📅 Deadline You Cannot Ignore
🗓 1 May 2026
From this date:
- MIR 7.3.1 becomes mandatory
- Older versions may be rejected
No transition cushion here — you need to be ready.
🧠 What You Should Do Now
Don’t wait until the last minute — that’s where most teams fail.
Start now:
- Update MIR templates and tools
- Align XML validation files
- Test PDF ↔ XML workflows
- Train teams on updated behavior
- Clarify internally that signature is optional
- Remove confusion around XML signing
👉 The biggest risk now is not technical — it’s misunderstanding.
💡 Final Thought
MIR 7.3.1 had a rough start.
But today?
It’s stable. It’s clear. It’s usable.
- December 2025 fixed the foundation
- March 2026 refined the experience
- Signature confusion? Resolved
- XML issues? Stabilized
👉 This is the version you can trust.
Now the only question is: Will you prepare early — or deal with avoidable chaos in April 2026?
You must be logged in to post a comment.