Inquiry on Medical Device Certification Support for .NET MAUI

[spulverail]

Dear .NET MAUI Team,

I hope this message finds you well.

I am writing on behalf of a medical device development company that is currently exploring cross-platform mobile frameworks for the next generation of regulated medical devices (Class IIa under MDR and FDA guidelines).

We are particularly interested in understanding whether .NET MAUI could meet the stringent requirements of medical device software certifications (IEC 62304, ISO 13485, FDA 510(k), MDR CE Marking).

Specifically, could you kindly clarify:

• Whether .NET MAUI provides or plans to provide documentation or support that could assist in certifying a medical application developed with your technology?
• Are you aware of any existing or in-progress projects where .NET MAUI has been successfully used to develop software for Class II or Class III medical devices?
• Does your roadmap include features, documentation, or services oriented towards high-assurance or regulated industries, particularly healthcare and medical devices?

Any available technical documentation, case studies, or contacts for further discussion would be greatly appreciated.

Thank you very much for your time and consideration. We would be delighted to continue the conversation should there be opportunities for deeper collaboration.

Looking forward to your reply.

Best regards,
Sébastien Pulvérail
TechnoConcept France

[ghost]

In case you will not get any answer, check Copilot AI. It gave me a good answer for your question that might get you into the right direction.

[MerSpyro]

I dont really think asking a hallucinating AI bot is a good idea when dealing with anything medical including ISO certification.

[ghost]

@MerSpyro CoPilot found Medical Device Software Development (MDSW), maybe you can search for relevent links to find more information.

I was searching for "Medical Device Certification Support + Xamarin" and found Software as a Medical Device (SaMD) Compliant: 25+ years of experience and Approval & certification of software medical devices (MDR).

[clarkstephen619-bot]

As an ISO professional, I’ve worked closely with teams navigating the complex world of medical device certification. Integrating certification requirements with modern frameworks like .NET MAUI can be challenging, especially ensuring compliance while maintaining efficient development cycles. From my experience, having a clear roadmap and expert guidance makes a huge difference in avoiding common pitfalls. For those looking to streamline the certification process and align it with industry standards, this approach proved invaluable. If you’re exploring similar challenges, I highly recommend checking out resources that bridge technical implementation with compliance. Learn More

[adhyan1991-hue]

Hi Sébastien,

This is a great question and something many teams in regulated industries are actively evaluating.

From what I’ve seen, .NET MAUI itself is not a certified medical framework, but it can be used as part of a compliant system if the overall development lifecycle is aligned with standards like IEC 62304 and ISO 13485. The key point is that certification typically applies to the entire software system and process, not just the UI framework.

A few practical considerations:

Regulatory compliance is process-driven

1. Even if you use .NET MAUI, you’ll still need validated SDLC processes, risk management (ISO 14971), traceability, and detailed documentation to satisfy MDR/FDA requirements.
2. Separation of concerns
3. Many medical device teams use frameworks like MAUI primarily for the UI layer, while keeping safety-critical logic isolated, rigorously tested, and easier to validate.
4. Documentation & validation
5. Since MAUI doesn’t provide certification-ready artifacts, teams usually generate their own technical documentation, validation reports, and testing evidence to support audits.
6. Ecosystem & real-world usage
7. While there’s limited public evidence of Class II/III certified apps built on MAUI, earlier Microsoft technologies (like Xamarin) have been used in regulated environments with proper compliance frameworks.
8. End-to-end system considerations
9. If your application interacts with physical devices, aspects like hardware reliability, integration protocols, and even manufacturing quality such as precision medical device stamping used in components also play a role in overall regulatory approval.

Overall, MAUI could still be a viable option depending on your architecture and risk classification—but it requires a strong compliance strategy around it rather than relying on the platform itself.

Curious to hear if anyone here has taken a MAUI-based solution through MDR or FDA certification?