It is possible to validate FHIR resources and bundles using a NHS Digital service.
The service can be used with tools such as postman by POSTing the resource (xml or json) to
http://data.developer.nhs.uk/ccri-fhir/STU3/{resource}/$validate
Replace {resource} with the type of resource you wish to validate. So if you want to validate a FHIR Document (as used with transfer of care), you would post your Bundle to
http://data.developer.nhs.uk/ccri-fhir/STU3/Bundle/$validate
Alternatively you can use a web app which does the same. This is available here:
Both return a FHIR OperationOutcome with a list of issues (if any!).
The validation service currently doesn’t validate codes (see note below). The errors can be a bit cryptic but feel free to post here and I’m sure someone will post replies.
For more details on validation see https://www.hl7.org/fhir/validation.html#op
This service currently doesn’t support the profile parameter, if you wish the validate a resource against a specific CareConnect profile you will need to include it the profile section of the meta tag. e.g. In the sample below, the CareConnect-Condition-1 profile is specified.
{
"resourceType": "Condition",
"id": "1",
"meta": {
"profile": [
"https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Condition-1"
]
},
This is not the same validator used in transfer of care, both are based on HAPI and use the official HL7 validation engine.
A newer version of this validation software which can be built from the (open source) code here CCRI 3.8 version. This is currently being worked on and is likely to include SNOMED code + ValueSet validation and message validation.