<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bonfireDB — Building on FHIR, explained</title>
    <link>https://bonfiredb.dev/blog</link>
    <atom:link href="https://bonfiredb.dev/rss.xml" rel="self" type="application/rss+xml" />
    <description>Plain-English guides for developers and clinician-founders shipping FHIR-safe outpatient healthcare apps.</description>
    <language>en-us</language>
    <item>
      <title>What is a SMART-on-FHIR app — and how to make your app interoperable</title>
      <link>https://bonfiredb.dev/blog/smart-on-fhir-interop</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/smart-on-fhir-interop</guid>
      <pubDate>Thu, 18 Jun 2026 15:00:00 GMT</pubDate>
      <description>Plain English: FHIR is the data layer, SMART is the auth layer. EHR launch vs standalone, scopes and PKCE, and the playbook for interoperability — without hand-rolling a FHIR server.</description>
    </item>
    <item>
      <title>How to build an outpatient app in an afternoon (behavioral health)</title>
      <link>https://bonfiredb.dev/blog/build-outpatient-app</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/build-outpatient-app</guid>
      <pubDate>Tue, 16 Jun 2026 15:00:00 GMT</pubDate>
      <description>End to end: create a patient, capture a PHQ-9 as a QuestionnaireResponse, write notes, and render a fresh timeline — on typed clinical primitives with FHIR underneath.</description>
    </item>
    <item>
      <title>Why build on FHIR (and when you shouldn't)</title>
      <link>https://bonfiredb.dev/blog/why-build-on-fhir</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/why-build-on-fhir</guid>
      <pubDate>Tue, 16 Jun 2026 15:00:00 GMT</pubDate>
      <description>The custom-schema trap, the interoperability expectation, and why FHIR makes you agent-ready — plus an honest look at when FHIR is the wrong call.</description>
    </item>
    <item>
      <title>The backend for an AI medical scribe: architecture &amp; the part you can’t fake</title>
      <link>https://bonfiredb.dev/blog/ai-scribe-backend</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/ai-scribe-backend</guid>
      <pubDate>Mon, 15 Jun 2026 15:00:00 GMT</pubDate>
      <description>Where transcripts and SOAP notes actually go, the data model a scribe needs, and the regulated parts (BAA, audit, signed-note provenance, FHIR export) you cannot vibe-code.</description>
    </item>
    <item>
      <title>Build an AI scribe in a weekend (without a HIPAA lawyer)</title>
      <link>https://bonfiredb.dev/blog/build-ai-scribe-weekend</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/build-ai-scribe-weekend</guid>
      <pubDate>Sun, 14 Jun 2026 15:00:00 GMT</pubDate>
      <description>Step by step: capture audio → transcribe → AI draft → clinician signs with provenance → store as a FHIR DocumentReference → export → audit.</description>
    </item>
    <item>
      <title>Can you vibe-code a HIPAA-compliant app?</title>
      <link>https://bonfiredb.dev/blog/vibe-code-hipaa</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/vibe-code-hipaa</guid>
      <pubDate>Fri, 12 Jun 2026 15:00:00 GMT</pubDate>
      <description>AI tools can build the app — but a BAA on your coding tool doesn't make the app compliant, and they emit compliant-looking code that isn't. Where the line really is.</description>
    </item>
    <item>
      <title>FHIR, explained for app developers</title>
      <link>https://bonfiredb.dev/blog/fhir-explained</link>
      <guid isPermaLink="true">https://bonfiredb.dev/blog/fhir-explained</guid>
      <pubDate>Wed, 10 Jun 2026 15:00:00 GMT</pubDate>
      <description>The no-jargon guide: what FHIR actually is, why it exists, why building your app directly on it hurts, and what to do instead.</description>
    </item>
  </channel>
</rss>
