-
Notifications
You must be signed in to change notification settings - Fork 70
Open
Description
I'm attempting to use itiRequestValidator to validate MHD 4.x requests (IPF version: 5.1.0). My route looks like this:
from("mhd-iti65:mhdservice?audit=true")
// ...
.setHeader(VALIDATION_MODE, constant(MODEL | SCHEMA))
.process(itiRequestValidator())
// ...As a result, I get errors for everything related to the new MHD specification, e.g.:
- Unknown extension https://profiles.ihe.net/ITI/MHD/StructureDefinition/ihe-designationType
- Unknown extension https://profiles.ihe.net/ITI/MHD/StructureDefinition/ihe-sourceId
- Profile reference 'https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Comprehensive.SubmissionSet' has not been checked because it could not be found
In Iti65Validator I found that it has a separate bundle consistency validation based on MHD version:
if (transactionBundle instanceof Mhd421) {
validateBundleConsistency421(transactionBundle);
} else {
validateBundleConsistency320(transactionBundle);
}But then validates using only the instance validator for MHD 3.2:
var validator = fhirContext.newValidator();
validator.setValidateAgainstStandardSchema(false);
validator.setValidateAgainstStandardSchematron(false);
var instanceValidator = new FhirInstanceValidator(validationSupportv320);
instanceValidator.setNoTerminologyChecks(false);
instanceValidator.setErrorForUnknownProfiles(true);
instanceValidator.setBestPracticeWarningLevel(BestPracticeWarningLevel.Hint);
validator.registerValidatorModule(instanceValidator);
var validationResult = validator.validateWithResult(transactionBundle);Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels