<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FHIRfly Blog</title>
    <link>https://fhirfly.io/blog</link>
    <description>Healthcare interoperability, FHIR APIs, and developer tools from FHIRfly.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Apr 2026 19:49:13 GMT</lastBuildDate>
    <atom:link href="https://fhirfly.io/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Information Blocking Fines Are Real Now</title>
      <link>https://fhirfly.io/blog/information-blocking-enforcement</link>
      <guid>https://fhirfly.io/blog/information-blocking-enforcement</guid>
      <description>ONC is issuing nonconformity letters to EHR vendors. OIG can stack $1M fines per violation. Nearly 1,600 complaints are in the queue. Here&apos;s what health IT developers need to know.</description>
      <pubDate>Tue, 28 Apr 2026 14:00:00 GMT</pubDate>
      <category>compliance</category>
      <category>information-blocking</category>
      <category>onc</category>
      <category>cures-act</category>
      <category>fhir</category>
    </item>
    <item>
      <title>Agentic Prior Auth: Grounding the 72-Hour Clock</title>
      <link>https://fhirfly.io/blog/agentic-prior-auth-mcp-cms-0057</link>
      <guid>https://fhirfly.io/blog/agentic-prior-auth-mcp-cms-0057</guid>
      <description>CMS-0057-F puts payers on a 72-hour clock for expedited prior auth. LLM agents can close the gap — but only if they&apos;re grounded against NCCI, MUE, coverage, and terminology data they can trust.</description>
      <pubDate>Thu, 16 Apr 2026 16:00:00 GMT</pubDate>
      <category>prior-authorization</category>
      <category>cms-0057</category>
      <category>mcp</category>
      <category>agents</category>
      <category>ncci</category>
    </item>
    <item>
      <title>What Rural Hospitals Actually Need for Interoperability</title>
      <link>https://fhirfly.io/blog/what-rural-hospitals-actually-need</link>
      <guid>https://fhirfly.io/blog/what-rural-hospitals-actually-need</guid>
      <description>The $50B is flowing and September&apos;s deadline looms. Rural hospitals don&apos;t need another framework — they need tools that work today.</description>
      <pubDate>Wed, 08 Apr 2026 14:00:00 GMT</pubDate>
      <category>rural-health</category>
      <category>interoperability</category>
      <category>fhir</category>
      <category>cms</category>
      <category>terminology</category>
    </item>
    <item>
      <title>Azure API for FHIR Retires in September — Your Options</title>
      <link>https://fhirfly.io/blog/azure-api-for-fhir-retirement</link>
      <guid>https://fhirfly.io/blog/azure-api-for-fhir-retirement</guid>
      <description>Microsoft is shutting down Azure API for FHIR on September 30, 2026. Here&apos;s what breaks, what the migration looks like, and what your realistic options are.</description>
      <pubDate>Tue, 07 Apr 2026 16:00:00 GMT</pubDate>
      <category>fhir</category>
      <category>interoperability</category>
      <category>azure</category>
      <category>migration</category>
      <category>infrastructure</category>
    </item>
    <item>
      <title>Introducing @fhirfly-io/fhir-builder v1.0.0</title>
      <link>https://fhirfly.io/blog/fhir-builder-v1-fluent-fhir-resource-builder</link>
      <guid>https://fhirfly.io/blog/fhir-builder-v1-fluent-fhir-resource-builder</guid>
      <description>Build valid FHIR R4 resources in TypeScript with a fluent API. Zero dependencies, 13 resource builders, build-time validation, and bundle reference resolution.</description>
      <pubDate>Mon, 06 Apr 2026 16:00:00 GMT</pubDate>
      <category>fhir</category>
      <category>sdk</category>
      <category>open-source</category>
      <category>typescript</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Build a FHIR Enrichment Service with AI and an Afternoon</title>
      <link>https://fhirfly.io/blog/ai-coding-assistant-fhir-enrichment</link>
      <guid>https://fhirfly.io/blog/ai-coding-assistant-fhir-enrichment</guid>
      <description>How a solo developer can use AI coding assistants to discover the FHIRfly SDK and build production-quality FHIR data enrichment in a single session.</description>
      <pubDate>Thu, 26 Mar 2026 19:19:23 GMT</pubDate>
      <category>sdk</category>
      <category>fhir</category>
      <category>ai</category>
      <category>tutorial</category>
      <category>rural-health</category>
    </item>
    <item>
      <title>AI Agents for Drug Interaction Screening: An API-First Approach</title>
      <link>https://fhirfly.io/blog/ai-agents-drug-interaction-screening</link>
      <guid>https://fhirfly.io/blog/ai-agents-drug-interaction-screening</guid>
      <description>How AI agents can use FDA-approved drug interaction text and RxNorm enrichment to screen medication lists — with working code and architecture patterns.</description>
      <pubDate>Wed, 25 Mar 2026 23:01:21 GMT</pubDate>
      <category>ai</category>
      <category>ddi</category>
      <category>agents</category>
      <category>clinical-safety</category>
      <category>api</category>
    </item>
    <item>
      <title>$50B for Rural Health IT: What Developers Need to Know</title>
      <link>https://fhirfly.io/blog/50b-rural-health-it-opportunity</link>
      <guid>https://fhirfly.io/blog/50b-rural-health-it-opportunity</guid>
      <description>CMS is distributing $50 billion to modernize rural healthcare — and interoperability is a scored funding priority. Here&apos;s what the program means for health IT.</description>
      <pubDate>Fri, 20 Mar 2026 19:49:12 GMT</pubDate>
      <category>rural-health</category>
      <category>interoperability</category>
      <category>cms</category>
      <category>fhir</category>
      <category>policy</category>
    </item>
    <item>
      <title>FHIRfly Now Supports UK Health Terminology</title>
      <link>https://fhirfly.io/blog/uk-health-terminology-dmd-opcs4</link>
      <guid>https://fhirfly.io/blog/uk-health-terminology-dmd-opcs4</guid>
      <description>FHIRfly adds dm+d and OPCS-4 APIs — bringing NHS medicines and procedure classifications to the same platform as NDC, RxNorm, and ICD-10.</description>
      <pubDate>Thu, 19 Mar 2026 15:32:53 GMT</pubDate>
      <category>fhir</category>
      <category>uk-health</category>
      <category>dmd</category>
      <category>opcs4</category>
      <category>interoperability</category>
    </item>
    <item>
      <title>The 98% Problem: What Healthcare AI Teams Actually Build Before Writing a Single Prompt</title>
      <link>https://fhirfly.io/blog/the-98-percent-problem</link>
      <guid>https://fhirfly.io/blog/the-98-percent-problem</guid>
      <description>The API call is 2% of the work. The other 98% — LOINC normalization, FHIR conversion, compliance — is where healthcare AI teams actually spend their time.</description>
      <pubDate>Wed, 18 Mar 2026 16:07:39 GMT</pubDate>
      <category>ai</category>
      <category>terminology</category>
      <category>loinc</category>
      <category>fhir</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Why Payer Interoperability Deadlines Keep Slipping — and What Developers Should Do About It</title>
      <link>https://fhirfly.io/blog/payer-interoperability-deadlines-slipping</link>
      <guid>https://fhirfly.io/blog/payer-interoperability-deadlines-slipping</guid>
      <description>CMS pushed the prior authorization API deadline to 2027 — and a new WEDI survey shows zero providers have reported implementation progress. Here&apos;s what developers building against these APIs should plan for.</description>
      <pubDate>Mon, 16 Mar 2026 21:58:44 GMT</pubDate>
      <category>cms</category>
      <category>interoperability</category>
      <category>prior-authorization</category>
      <category>fhir</category>
      <category>policy</category>
    </item>
    <item>
      <title>A Developer&apos;s Starting Point for FHIR</title>
      <link>https://fhirfly.io/blog/developer-starting-point-for-fhir</link>
      <guid>https://fhirfly.io/blog/developer-starting-point-for-fhir</guid>
      <description>David Hay&apos;s latest guide distills FHIR into its essential concepts. Here&apos;s what it means for developers building healthcare apps today.</description>
      <pubDate>Fri, 13 Mar 2026 22:33:48 GMT</pubDate>
      <category>fhir</category>
      <category>interoperability</category>
      <category>api</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>NPI Lookup in 5 Minutes: Search 9 Million Providers From Your App</title>
      <link>https://fhirfly.io/blog/npi-lookup-search-providers-tutorial</link>
      <guid>https://fhirfly.io/blog/npi-lookup-search-providers-tutorial</guid>
      <description>Every healthcare app needs provider data. Here&apos;s how to search, look up, and filter the NPI registry from TypeScript — with code you can ship today.</description>
      <pubDate>Fri, 13 Mar 2026 15:53:46 GMT</pubDate>
      <category>npi</category>
      <category>tutorial</category>
      <category>sdk</category>
      <category>provider-directory</category>
      <category>api</category>
    </item>
    <item>
      <title>MCP or API? Let Your Tools Decide</title>
      <link>https://fhirfly.io/blog/mcp-or-api-how-your-tools-should-shape-your-integration</link>
      <guid>https://fhirfly.io/blog/mcp-or-api-how-your-tools-should-shape-your-integration</guid>
      <description>MCP or REST API? The right integration for healthcare AI depends on what you&apos;re building. Here&apos;s how to choose — and why FHIRfly supports both.</description>
      <pubDate>Thu, 12 Mar 2026 15:04:16 GMT</pubDate>
      <category>mcp</category>
      <category>api</category>
      <category>sdk</category>
      <category>ai-agents</category>
      <category>interoperability</category>
    </item>
    <item>
      <title>AI Tools Don&apos;t Fail — Data Infrastructure Fails Them</title>
      <link>https://fhirfly.io/blog/ai-tools-dont-fail-data-infrastructure-fails-them</link>
      <guid>https://fhirfly.io/blog/ai-tools-dont-fail-data-infrastructure-fails-them</guid>
      <description>More than 85% of healthcare AI pilots never scale. The reason isn&apos;t the models — it&apos;s the fragmented, unstandardized data underneath them.</description>
      <pubDate>Wed, 11 Mar 2026 14:53:36 GMT</pubDate>
      <category>ai</category>
      <category>interoperability</category>
      <category>fhir</category>
      <category>data-infrastructure</category>
      <category>healthcare-it</category>
    </item>
    <item>
      <title>Share Patient Records With a QR Code: SMART Health Links in Node.js</title>
      <link>https://fhirfly.io/blog/smart-health-links-qr-code-tutorial</link>
      <guid>https://fhirfly.io/blog/smart-health-links-qr-code-tutorial</guid>
      <description>Build encrypted, patient-controlled health records that anyone can scan. A step-by-step guide to SMART Health Links with the @fhirfly-io/shl SDK.</description>
      <pubDate>Tue, 10 Mar 2026 19:35:08 GMT</pubDate>
      <category>shl</category>
      <category>tutorial</category>
      <category>sdk</category>
      <category>fhir</category>
      <category>patient-access</category>
    </item>
    <item>
      <title>Getting Your Healthcare API Into AI Agent Toolchains</title>
      <link>https://fhirfly.io/blog/healthcare-apis-ai-agent-toolchains</link>
      <guid>https://fhirfly.io/blog/healthcare-apis-ai-agent-toolchains</guid>
      <description>AI agents discover healthcare APIs through Context Hub, MCP, and typed SDKs — not your marketing site. Here&apos;s how to make your API agent-ready.</description>
      <pubDate>Mon, 09 Mar 2026 19:13:57 GMT</pubDate>
      <category>ai</category>
      <category>mcp</category>
      <category>agents</category>
      <category>sdk</category>
      <category>tool-use</category>
    </item>
    <item>
      <title>Validating FHIR Code Systems for the CMS Patient Access API Deadline</title>
      <link>https://fhirfly.io/blog/validating-fhir-code-systems-patient-access-api</link>
      <guid>https://fhirfly.io/blog/validating-fhir-code-systems-patient-access-api</guid>
      <description>How to validate NDC, ICD-10, LOINC, and NPI codes in your Patient Access API before the March 31 CMS reporting deadline.</description>
      <pubDate>Fri, 06 Mar 2026 17:31:22 GMT</pubDate>
      <category>fhir</category>
      <category>cms</category>
      <category>sdk</category>
      <category>compliance</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Build a Medication Lookup Agent with Claude and FHIRfly</title>
      <link>https://fhirfly.io/blog/build-medication-agent-with-claude</link>
      <guid>https://fhirfly.io/blog/build-medication-agent-with-claude</guid>
      <description>Build a TypeScript agent that uses Claude&apos;s tool-use protocol to query verified medication data from FDA and NLM sources — no hallucinated drug codes, no invented interactions.</description>
      <pubDate>Thu, 05 Mar 2026 17:31:27 GMT</pubDate>
      <category>tutorial</category>
      <category>ai</category>
      <category>sdk</category>
      <category>tool-use</category>
      <category>medications</category>
    </item>
    <item>
      <title>RAG Alone Won&apos;t Fix Healthcare AI Hallucinations — Here&apos;s What Will</title>
      <link>https://fhirfly.io/blog/rag-vs-mcp-grounding-healthcare-ai</link>
      <guid>https://fhirfly.io/blog/rag-vs-mcp-grounding-healthcare-ai</guid>
      <description>RAG helps with unstructured knowledge, but structured clinical data needs a different approach. MCP tool-use gives LLMs direct access to authoritative sources.</description>
      <pubDate>Mon, 23 Feb 2026 22:40:15 GMT</pubDate>
      <category>mcp</category>
      <category>rag</category>
      <category>hallucinations</category>
      <category>healthcare-ai</category>
      <category>clinical-data</category>
    </item>
    <item>
      <title>The $50 Billion Rural Health Bet: Why Interoperability Is the Linchpin</title>
      <link>https://fhirfly.io/blog/rural-health-transformation-interoperability</link>
      <guid>https://fhirfly.io/blog/rural-health-transformation-interoperability</guid>
      <description>The Rural Health Transformation Program commits $50B over five years to modernize rural healthcare. Health IT interoperability is the mandate that makes it work.</description>
      <pubDate>Fri, 20 Feb 2026 21:31:17 GMT</pubDate>
      <category>rural-health</category>
      <category>interoperability</category>
      <category>cms</category>
      <category>fhir</category>
      <category>policy</category>
    </item>
    <item>
      <title>The CMS ACCESS Model: What FHIR Developers Need to Know</title>
      <link>https://fhirfly.io/blog/cms-access-model-fhir-requirements</link>
      <guid>https://fhirfly.io/blog/cms-access-model-fhir-requirements</guid>
      <description>CMS&apos;s ACCESS model mandates FHIR-based outcome reporting for chronic care. With 15 payers and 165M members aligned, here&apos;s what it means for developers.</description>
      <pubDate>Thu, 19 Feb 2026 16:13:39 GMT</pubDate>
      <category>fhir</category>
      <category>cms</category>
      <category>interoperability</category>
      <category>compliance</category>
    </item>
    <item>
      <title>SSA Joins TEFCA: What Federal FHIR Adoption Means for Developers</title>
      <link>https://fhirfly.io/blog/ssa-joins-tefca-federal-fhir-adoption</link>
      <guid>https://fhirfly.io/blog/ssa-joins-tefca-federal-fhir-adoption</guid>
      <description>The Social Security Administration is joining the TEFCA network via FHIR APIs. Here&apos;s what this milestone means for healthcare developers.</description>
      <pubDate>Wed, 18 Feb 2026 22:28:59 GMT</pubDate>
      <category>fhir</category>
      <category>tefca</category>
      <category>interoperability</category>
      <category>federal</category>
      <category>api</category>
    </item>
    <item>
      <title>Why Terminology Is the Real AI Differentiator in 2026</title>
      <link>https://fhirfly.io/blog/terminology-is-the-differentiator</link>
      <guid>https://fhirfly.io/blog/terminology-is-the-differentiator</guid>
      <description>The winners in healthcare AI won&apos;t have the best models — they&apos;ll have the cleanest data. Here&apos;s why terminology management is the competitive edge.</description>
      <pubDate>Tue, 17 Feb 2026 21:20:27 GMT</pubDate>
      <category>ai</category>
      <category>terminology</category>
      <category>data-quality</category>
      <category>fhir</category>
      <category>interoperability</category>
    </item>
    <item>
      <title>Healthcare AI&apos;s Real Problem Isn&apos;t AI</title>
      <link>https://fhirfly.io/blog/integration-is-the-bottleneck</link>
      <guid>https://fhirfly.io/blog/integration-is-the-bottleneck</guid>
      <description>The most advanced AI becomes useless when it can&apos;t access patient data. The real bottleneck in healthcare AI isn&apos;t models — it&apos;s integration.</description>
      <pubDate>Mon, 02 Feb 2026 21:46:51 GMT</pubDate>
      <category>ai</category>
      <category>integration</category>
      <category>infrastructure</category>
      <category>healthcare-it</category>
    </item>
  </channel>
</rss>
