MedVertical
Open menu

Blog

FHIR in practice.

Practical guides, product updates and lessons from building Records.

Latest articles

Explore by topic
6 min read

Introducing the Records Public Demo

Understand FHIR® data. Verify the change. Explore resources, follow findings and test a correction in the Records public demo — no account required.

recordsfhirpublic-demo
Read article
Records with a synthetic Patient list, the selected Patient's identifier.use field and terminology findings side by side, in a dark frame cropped at the bottom and right.
7 min read

Claude Should Not Guess FHIR: Validation Guardrails for AI-Assisted Development

Claude can generate plausible FHIR JSON. Trust requires a validation loop that identifies the runtime, protects data boundaries, explains the evidence, and revalidates every change.

fhirclaude-codecodex
Read article
Abstract agentic FHIR workflow showing resources moving through runtime planning, validation, issue explanation, controlled repair, and revalidation
3 min read

Beyond the Fixture Gate: FHIR Validation in Operation

A fixture gate answers a bounded question. Choose the data, triggers and retained evidence needed to review a delivery and verify its correction.

fhirvalidationci-cd
Read article
Abstract FHIR validation visual showing resources passing through a CI quality gate into structured profile, terminology, baseline, and evidence checks
5 min read

ePA für alle: What Germany's National Health Record Means for Your FHIR Data

Since October 2025, Germany's ePA has entered mandatory everyday use for healthcare providers. It's the largest FHIR deployment the country has attempted — and it moves German healthcare from documents to structured data, at a scale where conformance stops being optional.

epafhirgermany
Read article
Abstract ePA FHIR data quality visual showing healthcare source systems flowing into a national patient record service, structured medication data, validation checks, and continuous evidence outputs
Auf Deutsch lesen
5 min read

How to Add a FHIR Validation Gate to GitHub Actions

A FHIR validation gate should be boring: run on every pull request, fail clearly, produce machine-readable output, and leave a path from local checks to reviewable Records evidence.

fhirvalidationgithub-actions
Read article
Abstract GitHub Actions validation gate visual showing local FHIR resources flowing into CI checks, structured reports, and reviewable evidence
3 min read

ISiK: What Confirmation Covers and How Teams Check Changes

ISiK requirements, formal confirmation and a checked data delivery have distinct scopes. Connect the applicable basis with findings, ownership and follow-up.

isikfhirgematik
Read article
Abstract ISiK conformance visual showing German hospital FHIR systems flowing into validation, certification evidence, and continuous monitoring
Auf Deutsch lesen
6 min read

The German FHIR Landscape: ISiK, MII, gematik, and Why It's More Complex Than It Looks

Germany has one of the densest and most overlapping FHIR landscapes in Europe. ISiK, MII, DiGA, KHZG — they're not the same thing, they don't share the same profiles, and hospitals may need to work with several of them simultaneously.

fhirgermanyisik
Read article
Abstract map of Germany with parallel FHIR profile streams converging into validation and evidence outputs
Auf Deutsch lesen
3 min read

FHIR Terminology Drift: Explain What Changed

A changed terminology result can come from the data, the selected requirement or the validator. Preserve both contexts before deciding what needs correction.

fhirterminologydata-quality
Read article
Abstract terminology drift visual showing code systems, value set expansion, and validation changes over time
3 min read

Three Questions Every FHIR Team Should Be Able to Answer

What did we check, what changed between comparable observations, and what can the next reviewer verify? Three practical questions for a FHIR handover.

fhirdata-qualityvalidation
Read article
Timeline visual showing three FHIR data quality questions leading to historical evidence
5 min read

Why We Built Records

Records didn't start as a data quality layer. It started while I was designing clinical research systems and ran into a problem many healthcare UX teams face: interfaces are only as reliable as the FHIR constraints behind them.

recordsfhirhealthcare-ux
Read article
Abstract Records workflow from raw FHIR resources to profile constraints and reproducible evidence

Explore by topic

Suggested reading orders for a closer look at operations, implementation and the German FHIR landscape.

Records

Turn FHIR validation into operational evidence.

Records supports recurring checks of a selected FHIR scope, compatible run comparisons, and recorded findings for release and handover decisions.

Explore RecordsFind your use case