Note that you should always use the current validator (see above), irrespective of which FHIR Release you are validating.
You need a current version of java to run the validator: The params control how the validator works, and are documented here.
Looking at the ANT documentation for the task you are using: https://ant.apache.org/manual/Tasks/it seems to have a disable DTD attribute but I'm not sure if it would help you or not.
Regards, Radu Hello Radu, It seems that it is not possible to use xerces parser to do that (see https://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-4).
The validator can validate against an implementation guide.
Do this involves 2 steps: The -profile parameter is the canonical URL for the profile you wish to validate against.
If the parameter -output is defined, a file will be created to contain the output.
There are other validation parameters that affect validation: The validation engine uses a terminology server to validate codes from large external terminologies such as SNOMED CT, LOINC, Rx Norm, etc.By default, this is the current build version of the specification.You probably don't want to validate against that version, so the first thing to do is to specify which version of the spec to use.The behavior of this can be controlled by the -questionnaire parameter: Possible values: - hints - report all hints, warnings and errors.(same as if not present) - warnings - report all warnings and errors, but not hints - errors - report all errors, but not warnings and hints note: this parameter is not presently supported note: this parameter is not presently supported There are a few contraints in the specification that are warnings but marked as 'best practice'.
Possible value are Ignore, Check, Check Case And Space, Check Case, Check Space note: this parameter is not presently supported By default, the validation engine only validates using the FHIR structures and profiles.