如今，团队如何加速 MDR IIa 合规软件的开发？
1 分•作者: peppernub•7 个月前
我们正在进行一个数字健康项目，并遇到了 MDR IIa 常见的瓶颈问题——文档、质量管理、基础设施、安全工作流程等。
我最近一直在研究不同的团队是如何处理这个问题的。一些团队似乎在使用预认证平台，而不是在内部构建所有东西（我遇到的一个例子是 Actimi (https://actimi.com/en/signals)），我正在努力理解这是否真的能节省时间，或者只是转移了工作。
我很想听听有以下经验的人的看法：
* 在内部构建符合 MDR 标准的软件
* 使用预构建的框架或平台
* 自动化合规流程的某些部分
* 或采取混合方法
哪些有效，哪些无效？
如果你们在 2025–2026 年重新开始，你们会怎么做？
我不是想推广任何东西——只是想真正了解当前生态系统的现状。
查看原文
We’re working on a digital health project and running into the usual bottlenecks with MDR IIa — documentation, quality management, infrastructure, safety workflows, etc.
I’ve recently been researching different ways teams are approaching this. Some appear to be using pre-certified platforms instead of building everything internally (Actimi (https://actimi.com/en/signals) is one example I came across), and I’m trying to understand whether this actually saves time or just shifts the work around.
I’d love to hear from people who have:<p>built MDR-compliant software in-house<p>used pre-built frameworks or platforms<p>automated parts of the compliance process<p>or taken a hybrid approach
What worked and what didn’t?
What would you do differently if you were starting again in 2025–2026?
Not trying to promote anything — genuinely trying to understand the current state of the ecosystem.