<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CT_NOOO</title>
    <description>The latest articles on DEV Community by CT_NOOO (@cto_nooo_41914ad55905b).</description>
    <link>https://dev.to/cto_nooo_41914ad55905b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2494859%2F3c96cf86-b223-42d6-bfe7-81360a4b8d64.png</url>
      <title>DEV Community: CT_NOOO</title>
      <link>https://dev.to/cto_nooo_41914ad55905b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cto_nooo_41914ad55905b"/>
    <language>en</language>
    <item>
      <title>I shipped a health app without knowing it was regulated. Here are the tools I used to fix it</title>
      <dc:creator>CT_NOOO</dc:creator>
      <pubDate>Fri, 24 Apr 2026 16:36:34 +0000</pubDate>
      <link>https://dev.to/cto_nooo_41914ad55905b/i-shipped-a-health-app-without-knowing-it-was-regulated-here-are-the-tools-i-used-to-fix-it-lck</link>
      <guid>https://dev.to/cto_nooo_41914ad55905b/i-shipped-a-health-app-without-knowing-it-was-regulated-here-are-the-tools-i-used-to-fix-it-lck</guid>
      <description>&lt;p&gt;TL;DR: Most developers building health apps don't realise they might be building a regulated medical device. Here's how to check, and the tools that can help if you are.&lt;/p&gt;

&lt;h2&gt;
  
  
  A question worth asking early
&lt;/h2&gt;

&lt;p&gt;I'm a former CTO of a medtech startup. The question that blindsided us - and that I see catch developers out constantly - is this:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;"Is what we're building actually a medical device?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Most developers assume the answer is no. Often they're wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to tell if your software is regulated
&lt;/h2&gt;

&lt;p&gt;The category is called SaMD, Software as a Medical Device. It covers standalone software that performs a medical function without being part of a physical device.&lt;br&gt;
The line is blurrier than you'd expect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Is a mental health app a medical device?&lt;/em&gt; A mood journal or meditation app -  probably not. An app that screens for depression, tracks symptoms to inform clinical decisions, or recommends treatment, almost certainly yes.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Is a fitness tracker a medical device?&lt;/em&gt; General step counting, no. Detecting arrhythmia or monitoring blood oxygen for clinical purposes, yes.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Is a symptom checker a medical device?&lt;/em&gt; Usually yes. If it influences what a user does next about their health, regulators treat that as a medical function.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Is a mental health chatbot a medical device?&lt;/em&gt; If it's therapeutic or diagnostic in intent, likely yes.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Is a hospital management app a medical device?&lt;/em&gt; Administrative software, no. Clinical decision support that affects patient care, the line blurs fast.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The rule of thumb&lt;/strong&gt;: if your software influences a clinical decision, monitors a health condition, or assists in diagnosis or treatment: assume you're regulated until confirmed otherwise. This applies whether you're building for the EU, the US, or elsewhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tools that actually help
&lt;/h2&gt;

&lt;p&gt;The ecosystem has improved a lot. Here's what's worth knowing across the different compliance layers:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Getting started / qualification&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;OpenRegulatory's classification wizard — walks you through the EU MDR classification logic and produces a risk class. Free to use.&lt;/li&gt;
&lt;li&gt;Greenlight Guru's &lt;a href="https://www.greenlight.guru/eu-mdr-gap-analysis-tool" rel="noopener noreferrer"&gt;EU MDR gap assessment&lt;/a&gt; — a free tool for teams who already know they're building a medical device and want to assess their compliance posture against EU MDR requirements.&lt;/li&gt;
&lt;li&gt;QualiHQ's &lt;a href="https://qualihq.com/tools/is-my-product-a-medical-device" rel="noopener noreferrer"&gt;Is My App a Medical Device?&lt;/a&gt; — a free five-question checker that gives you a preliminary answer based on your software's intended use.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;HIPAA compliance (US)&lt;/strong&gt;&lt;br&gt;
If you're handling protected health information, HIPAA is a parallel concern. &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Google Workspace: Google signs a Business Associate Agreement, meaning there's a legitimate pathway to using Google Workspace as part of a HIPAA-compliant setup if configured correctly.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://compliancy-group.com/the-guard-compliance-dashboard/" rel="noopener noreferrer"&gt;Compliancy Group (The Guard)&lt;/a&gt; — dedicated HIPAA compliance platform covering policy management, risk assessments, staff training, and incident management.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;QMS platforms&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Formwork (OpenRegulatory) — QMS with strong template coverage, AI Assistant in Paid Tiers. Relatively cheap but best for teams that already understand the regulatory framework.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.qualio.com/compare" rel="noopener noreferrer"&gt;Qualio&lt;/a&gt; — full-featured, built for teams with a dedicated QA function and budget to match. Strong if you have a regulatory/QA hire. &lt;/li&gt;
&lt;li&gt;
&lt;a href="//qualihq.com"&gt;QualiHQ&lt;/a&gt; — Built for small-medium SaaS teams, free to start, no credit card required. AI generates documentation drafts based on your product, onboarding teaches the framework as you go, scoped to software compliance only.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most regulated health app founders find out late, usually when they're close to launch or talking to their first healthcare customer (but definitely not afterwards ;)). Finding out early is cheaper in every sense.&lt;/p&gt;

&lt;p&gt;If you're not sure whether your app is regulated, start with the classification wizard or the free checker above. If you are regulated, the tools listed here are what I'd reach for first. no three-month detour, no valuable consultant (read: expensive).&lt;/p&gt;

&lt;p&gt;I'm sure there are other tools in this space I haven't covered. If you've been through this process and found something useful, drop it in the comments, would love to build out the list.&lt;/p&gt;

</description>
      <category>software</category>
      <category>devops</category>
      <category>product</category>
      <category>deved</category>
    </item>
  </channel>
</rss>
