<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DEXPRA</title>
    <link>https://dexpra.com</link>
    <description>Healthcare interoperability, data platforms, and applied AI.</description>
    <language>en-CA</language>
    <atom:link href="https://dexpra.com/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Wed, 21 Oct 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Monitoring clinical AI after it goes live</title>
      <link>https://dexpra.com/insights/clinical-ai-monitoring</link>
      <guid isPermaLink="true">https://dexpra.com/insights/clinical-ai-monitoring</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>A clinical model is validated once. After go-live its patients, devices and users change, and the organisation running it is usually the only one placed to notice. What to watch, and what it costs.</description>
      <category>Applied AI</category>
      <category>Data platforms</category>
    </item>
    <item>
      <title>Monitoring Clinical AI After Deployment</title>
      <link>https://dexpra.com/resources/clinical-ai-monitoring</link>
      <guid isPermaLink="true">https://dexpra.com/resources/clinical-ai-monitoring</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
      <description>What changes after a clinical model goes live, who is asked to watch it, the signals and what each costs, how long a fall takes to see, and what the platform has to record.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>Healthcare Data Platform Architecture</title>
      <link>https://dexpra.com/resources/healthcare-data-platform-architecture</link>
      <guid isPermaLink="true">https://dexpra.com/resources/healthcare-data-platform-architecture</guid>
      <pubDate>Thu, 15 Oct 2026 16:38:07 GMT</pubDate>
      <description>What a healthcare data platform is made of: six components, two shared services, the standards that govern each, and the four questions that decide its shape.</description>
      <category>Data platforms</category>
    </item>
    <item>
      <title>What a healthcare data platform is made of</title>
      <link>https://dexpra.com/insights/healthcare-data-platform-architecture</link>
      <guid isPermaLink="true">https://dexpra.com/insights/healthcare-data-platform-architecture</guid>
      <pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate>
      <description>The same two words describe an integration engine and a cloud lakehouse. Naming the parts, six components and two shared services, is what makes two very different platforms comparable.</description>
      <category>Data platforms</category>
    </item>
    <item>
      <title>On-Premises &amp; Hybrid Clinical AI</title>
      <link>https://dexpra.com/resources/on-prem-hybrid-clinical-ai</link>
      <guid isPermaLink="true">https://dexpra.com/resources/on-prem-hybrid-clinical-ai</guid>
      <pubDate>Sat, 10 Oct 2026 18:32:00 GMT</pubDate>
      <description>What crosses a hospital’s site boundary when the model runs on local hardware: five topologies, eleven paths, the standards on each, and the rules that follow.</description>
      <category>Data platforms</category>
    </item>
    <item>
      <title>On-Premises &amp; Hybrid Clinical AI Framework</title>
      <link>https://dexpra.com/insights/on-premises-hybrid-clinical-ai</link>
      <guid isPermaLink="true">https://dexpra.com/insights/on-premises-hybrid-clinical-ai</guid>
      <pubDate>Sat, 10 Oct 2026 12:00:00 GMT</pubDate>
      <description>Running the model on hospital hardware answers latency, bandwidth and residency. It does not stop the data moving. The inference stays; the evidence, the updates and the accountability travel.</description>
      <category>Data platforms</category>
    </item>
    <item>
      <title>AI Agents on FHIR</title>
      <link>https://dexpra.com/resources/ai-agents-on-fhir</link>
      <guid isPermaLink="true">https://dexpra.com/resources/ai-agents-on-fhir</guid>
      <pubDate>Sun, 04 Oct 2026 02:28:56 GMT</pubDate>
      <description>How an autonomous agent reaches a patient record: the three SMART subjects, the two-token bridge, and the audit question nobody can answer afterwards.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>Clinical AI Regulation</title>
      <link>https://dexpra.com/resources/us-medical-ai-regulation</link>
      <guid isPermaLink="true">https://dexpra.com/resources/us-medical-ai-regulation</guid>
      <pubDate>Sat, 03 Oct 2026 22:17:55 GMT</pubDate>
      <description>A 33-page map of US regulation for AI in medical software and hardware, and the four rules that are not the FDA’s.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>An AI agent is a client, not a user</title>
      <link>https://dexpra.com/insights/ai-agent-is-a-client-not-a-user</link>
      <guid isPermaLink="true">https://dexpra.com/insights/ai-agent-is-a-client-not-a-user</guid>
      <pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate>
      <description>SMART defines three subjects and an agent is none of them. What a record actually sees when a model asks it a question, and why the answer is usually one service account doing everything.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>Clinical AI regulation: intended use determines the path</title>
      <link>https://dexpra.com/insights/clinical-ai-regulation-intended-use</link>
      <guid isPermaLink="true">https://dexpra.com/insights/clinical-ai-regulation-intended-use</guid>
      <pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate>
      <description>Intended use decides, not the architecture and not the accuracy. FDA rewrote the four criteria in January 2026, and three of them now read differently.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>Imaging AI Standards: Everything Is Optional</title>
      <link>https://dexpra.com/resources/imaging-ai-standards</link>
      <guid isPermaLink="true">https://dexpra.com/resources/imaging-ai-standards</guid>
      <pubDate>Fri, 18 Sep 2026 04:37:39 GMT</pubDate>
      <description>A 26-page audit of every standard governing AI in medical imaging, and what each one declines to cover.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>Imaging AI: six handoffs between the scanner and the chart</title>
      <link>https://dexpra.com/insights/imaging-ai-six-handoffs</link>
      <guid isPermaLink="true">https://dexpra.com/insights/imaging-ai-six-handoffs</guid>
      <pubDate>Thu, 17 Sep 2026 12:00:00 GMT</pubDate>
      <description>An imaging AI deployment is not one integration. It is six, each governed by a different standard, and the two nobody scopes are the last two: what the radiologist did with it, and who pays.</description>
      <category>Applied AI</category>
    </item>
    <item>
      <title>MADO 101: The Manifest Becomes Its Own Document</title>
      <link>https://dexpra.com/resources/mado-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/mado-101</guid>
      <pubDate>Sat, 12 Sep 2026 22:07:43 GMT</pubDate>
      <description>A 21-page guide to IHE Radiology MADO for engineers and architects, checked against the supplement Rev. 1.2, 20 August 2026.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>MADO: the imaging manifest becomes its own document</title>
      <link>https://dexpra.com/insights/mado-imaging-manifest</link>
      <guid isPermaLink="true">https://dexpra.com/insights/mado-imaging-manifest</guid>
      <pubDate>Sat, 12 Sep 2026 12:00:00 GMT</pubDate>
      <description>IHE Radiology published MADO in March and revised it in August. It takes the retrieve address out of the signed report, gives the manifest two encodings, and asks less of a server than XDS-I.b did.</description>
      <category>IHE</category>
    </item>
    <item>
      <title>The data platform is the evidence package</title>
      <link>https://dexpra.com/insights/data-platform-evidence-package</link>
      <guid isPermaLink="true">https://dexpra.com/insights/data-platform-evidence-package</guid>
      <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
      <description>Of 691 AI devices the FDA cleared through July 2023, 95.5% never said who was in the training data. That is not a paperwork failure. It is a platform that could not produce the answer.</description>
      <category>Data platforms</category>
    </item>
    <item>
      <title>DICOMweb 101: Three Services, Four Gaps</title>
      <link>https://dexpra.com/resources/dicomweb-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/dicomweb-101</guid>
      <pubDate>Sun, 06 Sep 2026 23:13:23 GMT</pubDate>
      <description>A 23-page orientation to DICOMweb for engineers and architects, checked against DICOM PS3.18, edition 2026c.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>DICOMweb: three services, four gaps</title>
      <link>https://dexpra.com/insights/dicomweb-three-services-four-gaps</link>
      <guid isPermaLink="true">https://dexpra.com/insights/dicomweb-three-services-four-gaps</guid>
      <pubDate>Sun, 06 Sep 2026 12:00:00 GMT</pubDate>
      <description>Three services, ordinary HTTP, JSON on the wire. DICOMweb is the most approachable thing in medical imaging, and the four things it declines to specify are where the schedule goes.</description>
      <category>Interoperability</category>
      <category>DICOM</category>
    </item>
    <item>
      <title>FHIR 101: The API Is the Easy Part</title>
      <link>https://dexpra.com/resources/fhir-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/fhir-101</guid>
      <pubDate>Fri, 04 Sep 2026 18:58:44 GMT</pubDate>
      <description>A 26-page orientation to FHIR for engineers, checked against R4, R5, SMART App Launch 2.0.0 and US Core STU 9.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>FHIR: the API is the easy part</title>
      <link>https://dexpra.com/insights/fhir-the-api-is-the-easy-part</link>
      <guid isPermaLink="true">https://dexpra.com/insights/fhir-the-api-is-the-easy-part</guid>
      <pubDate>Fri, 04 Sep 2026 18:00:00 GMT</pubDate>
      <description>A FHIR server answers its first request in an afternoon. Profiles, terminology and the implementation guide are the actual project, and none of them is the API.</description>
      <category>Interoperability</category>
      <category>FHIR</category>
      <category>HL7</category>
    </item>
    <item>
      <title>HL7 101: Four Standards, One Name</title>
      <link>https://dexpra.com/resources/hl7-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/hl7-101</guid>
      <pubDate>Fri, 04 Sep 2026 12:45:59 GMT</pubDate>
      <description>A 24-page orientation to HL7 v2, v3, CDA and FHIR, checked against v2.9.1, C-CDA Edition 5 and FHIR R4.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>HL7 is four standards, and none of them has been retired</title>
      <link>https://dexpra.com/insights/hl7-four-standards-one-name</link>
      <guid isPermaLink="true">https://dexpra.com/insights/hl7-four-standards-one-name</guid>
      <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>
      <description>Ask three engineers in a hospital what HL7 is and you get three answers, all correct. Pipe-delimited text, an XML document, a JSON API: four generations, one name, none switched off.</description>
      <category>Interoperability</category>
      <category>HL7</category>
    </item>
    <item>
      <title>DICOM 101: The Standard That Runs Medical Imaging</title>
      <link>https://dexpra.com/resources/dicom-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/dicom-101</guid>
      <pubDate>Mon, 31 Aug 2026 22:24:25 GMT</pubDate>
      <description>A 32-page orientation to DICOM for engineers and data scientists, checked against the current edition, PS3 2026c.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>IHE 101: Two Conformant Systems, One Broken Department</title>
      <link>https://dexpra.com/resources/ihe-101</link>
      <guid isPermaLink="true">https://dexpra.com/resources/ihe-101</guid>
      <pubDate>Mon, 31 Aug 2026 22:24:25 GMT</pubDate>
      <description>A 29-page walk through IHE Radiology and Scheduled Workflow.b, transaction by transaction. Checked against RAD TF Rev 23.0.</description>
      <category>Interoperability</category>
    </item>
    <item>
      <title>IHE Radiology: how imaging systems are made to work together</title>
      <link>https://dexpra.com/insights/two-conformant-systems-one-broken-department</link>
      <guid isPermaLink="true">https://dexpra.com/insights/two-conformant-systems-one-broken-department</guid>
      <pubDate>Mon, 31 Aug 2026 13:00:00 GMT</pubDate>
      <description>DICOM and HL7 define the words. They do not define the conversation. IHE writes the conversation down, and Scheduled Workflow.b is the one running almost every radiology department.</description>
      <category>Interoperability</category>
      <category>IHE</category>
    </item>
    <item>
      <title>DICOM: not just a file format for medical images</title>
      <link>https://dexpra.com/insights/dicom-is-not-a-file-format</link>
      <guid isPermaLink="true">https://dexpra.com/insights/dicom-is-not-a-file-format</guid>
      <pubDate>Mon, 31 Aug 2026 12:00:00 GMT</pubDate>
      <description>Every scanner, archive and viewer on earth speaks DICOM. Almost every team building AI on medical images discovers, painfully, that it is a four-layer stack and not a header.</description>
      <category>Interoperability</category>
      <category>DICOM</category>
    </item>
  </channel>
</rss>
