The OperationOutcome a validator returns is the sender's only tool for fixing the payload. A well-designed outcome tells them what is wrong, where in the resource it is wrong, how to fix it, and how to correlate it with logs if support...
Resource Vetter
Resource Validation in a Batch Pipeline
Validating one resource on a REST write is a lightweight operation. Validating a million resources in an import pipeline is a different shape entirely. Cache warmth, batching semantics, per-resource result accounting, and downstream...
Resource Vetter
Terminology Validation and the Tradeoffs of Enabling It
Terminology validation is the FHIR check that catches "this coded value is not in the value set the profile bound." It is the layer that catches soft-typing bugs that structural validation cannot see. It is also the slowest, most brittle,...
Resource Vetter
When Structural Validation Is Enough for Your Risk Profile
Not every FHIR endpoint needs profile validation. Not every endpoint needs terminology validation. Some workloads are served fully by structural validation — checking that the JSON is well-formed, that elements have the right cardinality,...
Resource Vetter
Validating Incoming Resources on an Existing Endpoint
Adding validation to an existing FHIR endpoint is not usually a greenfield decision. There is already an endpoint, already producers sending to it, already downstream systems consuming from it. Introducing validation means picking a place...
Resource Vetter
meta.profile: What It Claims and What It Costs to Enforce
Resource.meta.profile is the sender's assertion of conformance. It says "this resource conforms to these profiles." That claim is powerful and unenforced by the spec — receivers may honor it, ignore it, or dispute it. Deciding how your...
Resource Vetter
Profile-Based Validation Without a Full IG Deploy
Profile-based validation requires a StructureDefinition, some terminology, and enough of the surrounding IG to interpret cross-references. In practice teams reach for the full-IG deploy as if it were the only option — and it is not. A...
Resource Vetter
Single-Resource Validation vs Bundle Validation: Knowing the Boundary
FHIR validation looks like one topic and is really two. Validating a single resource — is this Patient well-formed? — and validating a Bundle — do these entries reference each other correctly? — share tooling and vocabulary and diverge...