hl7-v2-validation 1.5.0 https://hit-nexus.nist.gov/repository/public/gov/nist/hl7-v2-validation/1.5.0/hl7-v2-validation-1.5.0.jar
hl7-v2-parser 1.5.0 https://hit-nexus.nist.gov/repository/public/gov/nist/hl7-v2-parser/1.5.0/hl7-v2-parser-1.5.0.jar
hl7-v2-profile 1.5.0 https://hit-nexus.nist.gov/repository/public/gov/nist/hl7-v2-profile/1.5.0/hl7-v2-profile-1.5.0.jar
Under to correct context, this is the XML script to add:
<Constraint ID="ELR-40">
<Description>INSERT DESCRIPTION HERE</Description>
<Assertion>
<Plugin QualifiedClassName="gov.nist.hit.elr.quest.plugin.cs.ELR_040" />
</Assertion>
</Constraint>
It is important that:
- The constraint is added under the correct context.
- The QualifiedClassName is the full name (package + class name) of the plugin's code.
When using in validation, check for spec errors. If there is a spec error, something is wrong either in the plugin Java code, or in the XML script (wrong context or wrong QualifiedClassName)
Under the correct context, add a Free Text conformance statement.
Fill in the Identifier, the conformance statement Strength, the Description and the XML Script.
The XML script is the assertion part. Again, the QualifiedClassName is important. Check for spec errors in the NIST validation!
<Assertion>
<Plugin QualifiedClassName="gov.nist.hit.elr.quest.plugin.cs.ELR_040" />
</Assertion>
