You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The validator currently reports an error when an element with a cardinality of 1...1 is missing , however this is allowed when there is a "data-absent-reason" extension present instead.
To Reproduce
Run the RunSingleTest() test method in ValidationManifestTest.cs using allergy.json in the R4 branch for a test that checks for this.
Expected behavior
Don't throw an error on a missing element when the data-absent-reason extension is present.
Version used:
FHIR Version: STU3, R4, R5
Additional context
This issue/feature has come to light comparing the Java validator against the .NET validator.
The text was updated successfully, but these errors were encountered:
After investigating this.
No error is thrown when providing for a missing element, but only for not providing a code for an element that has a required binding. Just like the java validator does. No fix needed.
Describe the bug
The validator currently reports an error when an element with a cardinality of 1...1 is missing , however this is allowed when there is a "data-absent-reason" extension present instead.
To Reproduce
Run the
RunSingleTest()
test method inValidationManifestTest.cs
usingallergy.json
in the R4 branch for a test that checks for this.Expected behavior
Don't throw an error on a missing element when the data-absent-reason extension is present.
Version used:
Additional context
This issue/feature has come to light comparing the Java validator against the .NET validator.
The text was updated successfully, but these errors were encountered: