Validate resources against US Core profiles and check must-support field compliance

Steps

1. Identify the relevant US Core profile for the resource type (e.g., US Core Patient, US Core Observation Lab) from the US Core Implementation Guide at hl7.org/fhir/us/core.
2. Invoke the server's $validate operation: POST [base]/[ResourceType]/$validate with the resource as the body and profile parameter set to the US Core profile canonical URL.
3. Review the returned OperationOutcome for issues with severity 'error' (profile violations) vs. 'warning' (recommendations); must-support fields that are absent generate warnings, not errors, unless populated with a value.
4. Check that must-support fields are present when data is available; must-support means senders must populate the field if the data exists, and receivers must handle it if present.
5. For US Core Patient, verify that at minimum identifier, name, gender, and birthDate are present; for US Core Observation Lab, check status, category, code, subject, and effective[x] are present.
6. Use a FHIR validator tool (e.g., the HL7 FHIR Validator JAR) locally to pre-validate before submitting to production servers, reducing rejected resource errors.