Repository Validation Support

Repository Validation provides another way to validate against the core FHIR specification and the resource against it.

The default implementation uses the built-in official FHIR definitions to validate the resource against it and, in many cases, this is good enough. However, if you have needs beyond validating against the core FHIR specification, you may want to use another validation method called Repository Validation.

When using a HDR FHIR JPA server as a FHIR Repository, it is often desirable to enforce specific rules about which specific FHIR profiles can or must be used.

For example, if an organization created a FHIR Repository for the purposes of hosting and serving US Core Data, that organization might want to enforce rules that data being stored in the repository must actually declare conformance to US Core Profiles such as the US Core Patient Profile and US Core Observation Profile.

In this situation, it would also be useful to require that any data being stored in the repository be validated, and rejected if it is not valid. The Repository Validating method can be used for this purpose. The HDR-FHIR server will be able to configure to validate resources based on external profiles or implementation guides.

• Configuration
  The required configuration properties are added to the hdr_fhir.yaml file.