validate FHIR resources against profiles using the $validate operation and US Core

Steps

1. POST the resource to {base}/{ResourceType}/$validate with the resource as the request body (or wrapped in a Parameters resource with a 'resource' parameter); include ?profile={profile-canonical-URL} to validate against a specific profile.
2. Parse the returned OperationOutcome resource: check issue[].severity for 'error' and 'warning' entries; 'error' issues indicate non-conformance that must be fixed.
3. For offline or CI validation, use the HL7 FHIR Validator CLI (validator_cli.jar) with the -ig flag pointing to US Core or other implementation guide packages from the FHIR package registry (packages.fhir.org).
4. Download US Core profiles as an npm-style FHIR package (e.g. hl7.fhir.us.core) and supply them to the validator so it can resolve profile URLs and value set bindings.
5. Address common US Core violations: missing must-support elements, unbound or incorrectly bound code values, and missing required identifiers or category codings.
6. Integrate $validate calls into your data ingestion pipeline to catch non-conformant resources at the boundary rather than letting invalid data propagate into your store.