This project is classed as skunkworks it is not built for operational use.
See FHIR Development and Testing (FHIR Validation) Skunkworks for a demonstration of this service can be found on
An application using this service: FHIR Development and Testing Tools (skunkworks)
This project has three purposes:
- To provide a FHIR Validation Service which runs via AWS ECS and provides a FHIR /$validate operation. See deploy-notes
- To provide a FHIR Validation Service which runs via Docker and provides a FHIR /$validate operation. See docker-image
- To provide a FHIR Validation service for GitHub Actions to test FHIR Conformance. See IOPS-FHIR-Test-Scripts for example github actions using this service.
This service is built using HL7 Validation and HAPI FHIR Libaries with additional support for
- NHS England Terminology Server to handle the security layer.
- FHIR Message validation using a FHIR MessageDefinition.
- validation-service-fhir-r4 is used to perform operational FHIR Validation Service by Electronic Prescription Service - FHIR API. This provides FHIR Validation via a AWS Lambda and is optimised for performance (it doesn't perform coding validation).
It has several configuration options:
- To validate against a supplied set of FHIR Implementation Guides (NPM packages are supplied).
- To validate against a configured FHIR Implementation Guide (NPM package are retrieved by the service and configured via environment variables)
- Optionally validate using the NHS England Ontology Service (configured via environment variables).
The configuration is aimed at supporting different use cases. For example the lambda version with no ontology support is aimed at performing basic FHIR validation checks. This may just be FHIR core and schema validation but can also test against UKCore profiles.
See Environmental Variables for configuration options.
The latest version og HAPI-FHIR can be found at https://github.com/hapifhir/hapi-fhir and with the respective changelog at https://hapifhir.io/hapi-fhir/docs/introduction/changelog.html
Change the <fhir.version>
value (line 20) in the pom.xml to the latest version. The github action 'FHIR-Validation-Test' will run, ensure it passes before merging to main.
To update the packages that are validated against refer to src/main/resources/manifest.json. The packages need to be published on https://registry.fhir.org/ and need to be in the format
{
"packageName": "<package name>",
"version": "<version number>"
}
Follow updating-validator.md to push the latest version of the validation service to AWS