FHIR R4 JSON examples
Valid FHIR R4 resources you can copy, each next to the mistakes that break it and the exact error a validator returns. Every example on these pages is run through the FHIR R4 validator when the page is built.
- FHIR R4 Patient resource exampleA valid FHIR R4 Patient in JSON with identifier, name, gender, birth date, contact details, address and language, plus the mistakes validators report most often.
- FHIR R4 Observation example: blood pressureA valid FHIR R4 blood pressure Observation with systolic and diastolic components, LOINC codes and UCUM units, and the errors validators report for common mistakes.
- FHIR R4 Observation example: laboratory resultA valid FHIR R4 laboratory Observation (serum glucose) with LOINC code, UCUM unit, reference range, interpretation, performer and issued time, checked against a lab profile.
- FHIR R4 DiagnosticReport example: lab panelA valid FHIR R4 DiagnosticReport for a lipid panel that groups four result Observations, with LOINC codes, status, dates and performer, plus common validation errors.
- FHIR R4 Condition resource exampleA valid FHIR R4 Condition (type 2 diabetes) coded with SNOMED CT and ICD-10-CM, with clinical and verification status, category and onset, plus common errors.
- FHIR R4 MedicationStatement exampleA valid FHIR R4 MedicationStatement (metformin) coded with RxNorm and ATC, with status, period and dosage, plus the medication[x] mistakes validators report.
- FHIR R4 AllergyIntolerance exampleA valid FHIR R4 AllergyIntolerance (penicillin) with SNOMED CT codes, clinical and verification status, criticality and reaction, plus common validation errors.
- FHIR R4 Immunization resource exampleA valid FHIR R4 Immunization (seasonal influenza) with a CVX vaccine code, status, occurrence date, lot number and dose, plus the errors validators report.
- FHIR R4 Encounter resource exampleA valid FHIR R4 Encounter (outpatient check-up) with status, class, type, period, participant and reason, plus the R5 habits that fail R4 validation.
How to read the examples
Each page shows a complete resource, the elements that matter most with their cardinality from the FHIR R4 specification, and a short list of mistakes. The mistakes are real edits of the valid example; the error under each one is what the validator answers for it, not a paraphrase.
The examples use one synthetic patient, Patient/example, and US code systems where there is a choice (RxNorm, CVX, ICD-10-CM) next to international ones (LOINC, SNOMED CT, ATC). Codes are real, but check them against your terminology source before you depend on them.
POST /fhir/R4/Observation and $validate.Related guides
- How to store medical records using FHIR R4Tutorial: create a Patient, a blood-pressure Observation and a Condition, use a transaction, search, update with history and read provenance — every request with curl and the real response, on the free sandbox.
- FHIR code systemsWhich code systems each FHIR resource type uses: LOINC for measurements and lab results, ICD-10 for conditions, ATC for medications, UCUM units, and SNOMED CT behind a licence flag.
- How to normalize medical dataTutorial: turn medical data from many sources into one comparable form — LOINC and ATC lookup, UCUM units, ISO dates, reference ranges, no duplicates on retry, and validation against the European lab profile.