FHIR JSON checker

FAQ

What does this FHIR JSON checker actually verify?

It checks that the text is valid JSON, that the root is an object, and that resourceType is a non-empty string. It optionally reports an id if present and counts top-level keys. It does not validate cardinality, coded values, references, Bundles or Implementation Guide profiles.

What is resourceType in HL7 FHIR R4?

In FHIR JSON, every resource instance includes a resourceType string naming the resource (for example Patient, Device, Observation, Bundle). That field is how parsers know which resource definition to apply. Missing or non-string resourceType means the payload is not a recognizable FHIR resource instance.

Is this a substitute for the HL7 FHIR validator?

No. Use the official HL7 FHIR validator (or your IG’s tooling) for structure definitions, ValueSets, references and US Core / national profiles. This page is a syntax and resourceType smoke test for pasted payloads.

Do Bundles need special handling?

Yes. A Bundle still has resourceType “Bundle”, but clinical content lives in entry.resource elements. This checker will say the Bundle looks like FHIR JSON; it will not walk entries or validate nested resources.

How does FHIR exchange relate to HIPAA BAAs?

If a vendor creates, receives, maintains or transmits ePHI while hosting or transforming FHIR resources for you, a HIPAA BAA analysis usually applies in the US, separate from FHIR technical validity. Use the BAA vs DPA picker for the contracting first pass.

Does the tool send my JSON to a server?

Parsing runs in the browser on the text you paste. Treat PHI-bearing examples according to your own privacy policies before pasting them into any online tool.