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: Jacob Berkowitz

Health IT consultant in Boston. Writes about patient access APIs and the operational gap between FHIR specs and member experience.
Top 6 FHIR Data Store Patterns for Reusable Compliance Investment

Top 6 FHIR Data Store Patterns for Reusable Compliance Investment

The FHIR data store is the architectural decision that determines whether CMS-0057-F compliance becomes a reusable platform investment or stays…

Top 5 PostgreSQL-Based FHIR Engines for 2026

Top 5 PostgreSQL-Based FHIR Engines for 2026

PostgreSQL has become the default storage substrate for production FHIR platforms in 2026. The JSONB column type stores FHIR resources…

Top 5 Da Vinci HRex Use Cases for Payer Implementations

Top 5 Da Vinci HRex Use Cases for Payer Implementations

Health Record Exchange (HRex) is the Da Vinci foundation IG that other Da Vinci IGs build on. Most payer implementations…

The Complete Guide to the Da Vinci Ecosystem for CMS-0057-F

The Complete Guide to the Da Vinci Ecosystem for CMS-0057-F

The HL7 Da Vinci Project produces the FHIR Implementation Guides that CMS-0057-F relies on. The ecosystem covers Coverage Requirements Discovery,…

FHIR-Native vs Compliance Gateway: Architectural Trade-Offs for CMS-0057-F

FHIR-Native vs Compliance Gateway: Architectural Trade-Offs for CMS-0057-F

The architectural choice between a FHIR-native stack and a compliance gateway determines what the CMS-0057-F investment becomes three years from…

Cloud-Hosted vs Self-Hosted FHIR Platforms for CMS-0057-F

Cloud-Hosted vs Self-Hosted FHIR Platforms for CMS-0057-F

The deployment model for the CMS-0057-F FHIR platform is one of the choices that gets less attention than vendor selection…

Best FHIR Profile Development Tools for Da Vinci IG Authoring

Best FHIR Profile Development Tools for Da Vinci IG Authoring

Most payers do not author Da Vinci IGs directly. They consume the IGs HL7 publishes and customize at the profile…

5 FHIR Storage Anti-Patterns That Hurt CMS-0057-F Performance

5 FHIR Storage Anti-Patterns That Hurt CMS-0057-F Performance

FHIR storage design has predictable failure modes that surface under production CMS-0057-F load. The anti-patterns below produce systems that pass…

My Unexpected Journey into Healthcare Data with a FHIR Store

My Unexpected Journey into Healthcare Data with a FHIR Store

Have you ever felt completely overwhelmed by a new subject, like staring into a black hole of jargon and acronyms?…

7 Steps to Digitize Paper Forms in Payer Operations

7 Steps to Digitize Paper Forms in Payer Operations

Digitizing paper forms in payer operations follows a specific sequence. Seven steps cover essentially every project. Step 1: Inventory current…

Posts navigation

Older posts
Newer 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