reddit · SideProject · 09-13 15:50 55 分 ← 返回列表

I'm not a developer. I built a medical app anyway. Here is everything that broke.

Eighteen months ago I started building a medical pre-consultation tool in France. I am not a developer. I had an idea and I had AI, and that was enough to get something working. Getting it to work was the easy part. Here is what nobody warned me about. The analytics were logging health data and I had no idea. I had set up a tracker so I could show real numbers to the doctor reviewing my work. Sensible, right? Except it was recording symptoms and vital alert triggers. No names, no emails

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：非技术开发者构建医疗/健康类应用时，容易无意收集健康数据、违反GDPR等法规，并因无法合规接入AI而被医生和健康网络拒绝。

目标用户：法国/EU的独立医疗健康应用开发者、非技术创始人，以及需要合规接入AI的小型诊所/健康网络。

证据：Under EU rules that is still health data, and it should never have been sitting in a general analytics tool. ... their own rules forbid sending patient data to an AI

变现：订阅制合规扫描与脱敏SDK/API；按扫描次数或年费收费；一次性合规审计报告。

MVP：2周内做一个浏览器插件或API，扫描前端/后端发往analytics和AI的字段，识别健康/患者数据，自动脱敏并生成GDPR风险清单，内置医疗术语替代表述建议。

竞品：OneTrust、Transcend、Dastra、AWS Comprehend Medical、Google Cloud Healthcare NLP、Azure Health Data Services

摘要：一位非开发者用18个月在法国做出医疗预诊工具，发现analytics在记录健康数据、医疗术语构成合规问题，且自由文本字段导致医生/健康网络因禁止将患者数据发给AI而拒绝合作。这暴露了健康AI数据合规与脱敏工具的需求，但帖中无明确付费意愿或收入验证。