Skip to content
Per Square Metre

Per Square Metre

Payer-side FHIR architecture: Da Vinci IG adoption, analytics stacks, and payer platform engineering notes.

  • Terminology server
  • Medical form builder
  • Master patient index

Author: Alessandro Ricci

Payer-side FHIR architect in Newport Beach. Writes about Da Vinci IG adoption and payer platform engineering.
FHIR Search Performance Across 4 Servers: A First Look at the Numbers

FHIR Search Performance Across 4 Servers: A First Look at the Numbers

FHIR search is where most production payer workloads actually live. Patient Access calls, panel queries, analytics extracts, and prior-auth bundle…

Top 5 Risk Adjustment Patterns Using FHIR Clinical Data

Top 5 Risk Adjustment Patterns Using FHIR Clinical Data

Risk adjustment is the financial mechanism that compensates Medicare Advantage and ACA marketplace payers for the clinical risk in their…

Top 5 FHIR-Based Stars Rating Measurement Patterns for 2026

Top 5 FHIR-Based Stars Rating Measurement Patterns for 2026

CMS Stars ratings drive Medicare Advantage bonuses, market positioning, and member growth. The measures depend on clinical and administrative data…

Top 5 Claims Analytics Modernization Patterns Using FHIR

Top 5 Claims Analytics Modernization Patterns Using FHIR

Claims analytics at US health payers has decades of accumulated infrastructure. Data warehouses built years ago. Custom claim line fact…

STU 2.0.0 vs STU 2.0.1: How Da Vinci IG Versions Differ in Production

STU 2.0.0 vs STU 2.0.1: How Da Vinci IG Versions Differ in Production

Da Vinci IG versioning looks subtle on the surface. STU 2.0.0 versus STU 2.0.1 sounds like a minor patch. In…

Da Vinci CRD vs PDex: Which IG Drives Which Workflow

Da Vinci CRD vs PDex: Which IG Drives Which Workflow

Coverage Requirements Discovery (CRD) and Payer Data Exchange (PDex) are two Da Vinci IGs that sometimes get confused in early…

Best Multi-Tenant FHIR Hosting Models for Payer Workloads in 2026

Best Multi-Tenant FHIR Hosting Models for Payer Workloads in 2026

Multi-tenant FHIR hosting matters for any health plan that supports multiple lines of business, multiple delegated entities, or multiple regulatory…

5 Patterns for Using FHIR Data to Train Payer LLM Applications

5 Patterns for Using FHIR Data to Train Payer LLM Applications

LLM applications at US health payers are growing in 2026. Care management note summarization. Prior auth narrative generation. Member service…

FHIR Adoption Roadmap: How Payer-Side Deployments Actually Ship

FHIR Adoption Roadmap: How Payer-Side Deployments Actually Ship

Payer-side FHIR adoption follows a specific roadmap driven by CMS-0057 requirements. Understanding the sequence shapes investment. Phase 1: Foundation (months…

Digital Forms for Healthcare: Adoption Patterns in Payer Ops

Digital Forms for Healthcare: Adoption Patterns in Payer Ops

Digital forms in payer operations serve specific workflows: prior authorization, appeals, member surveys, provider credentialing. Understanding adoption patterns shapes deployment.…

Posts navigation

Older posts

Fixing broken refs?

Fixing broken refs?

Debugging a Bundle full of broken references? a Bundle reference walker parked here will find the culprits.

Recent Posts

  • Designing a Reference Resolver That Survives Partial Outages
  • Reference Resolution in Bulk Data: What the Spec Allows
  • Batching Resolution to Reduce Round Trips
  • Circular References and How to Detect Them Safely
  • Version-Specific References: When You Need Them, When You Don't

Categories

  • Da Vinci Ecosystem
  • Fhir Platform Architecture
  • Master patient index
  • Medical form builder
  • Payer Side Analytics Ai
  • Reference Resolver
  • Terminology server

Copyright © 2025