UUID v4 is the workhorse — 122 bits of randomness in a fixed layout, cryptographically strong when generated with a proper RNG, no ordering information. UUID v7 is newer — it embeds a millisecond timestamp in the high bits so ids sort by...
Popular Posts
-
-
Bundle.entry.fullUrl is where a Bundle assembles entries that reference each other atomically. The urn:uuid: prefix in that field is what makes cross-entry references work in a transaction Bundle where the resource ids do not exist yet. It...
-
FHIR has two id-shaped fields on almost every resource, and they do different jobs. Resource.id is the server's logical id — where the resource lives. Resource.identifier[] is the business identity — the MRN, order number, or external...
-
Every FHIR resource has a logical id. It can be a UUID, a sequential integer, a natural business key, or anything else that satisfies the id datatype rules. The choice is not academic. A resource id is what every reference in the graph...
-
SMART on FHIR app reviewers (the people running app-store-style review programs for SMART apps inside EHR vendor marketplaces) have a validation workload that looks nothing like a developer's IDE pass. The review has to check conformance, s
-
The FHIR validator market has a strong open-source baseline and a meaningful commercial layer on top, and most procurement decisions get framed as either-or when the honest answer is usually both. The cost story, the support story, and the
-
Bulk data submissions are the validation use case where single-resource validators show their limits. An NDJSON file with a million Patient and Observation resources is a throughput problem before it is a validation problem, and a validator
-
Plenty of validators claim to validate against FHIR profiles. Far fewer actually catch the profile errors that matter in production, where a missed must-support violation or a silently-accepted invalid coded value is the kind of bug that su
-
A vendor publishing a benchmark that includes their own product is one of the oldest tensions in software procurement, and FHIR is no exception. Health Samurai, the company behind Aidbox, just released an open-source performance benchmark…
-
The FHIR specification defines $validate as a standard operation on every resource type, and the validators that expose it through a REST surface are the ones that fit cleanly into modern integration patterns. A $validate call is the standa