Stream: conformance
Topic: FHIR 3.0.2. Invalid eld-16 constraint
Ardon Toonstra (Jan 17 2020 at 13:05):
The .NET validator triggers eld-16 error using FHIR 3.0.2. This turns out to be an error in the FHIR specification.
The double backslashes in the regex of the eld-16 constraint are incorrect here. It has been solved in FHIR standard 4.0.1, but unfortunately not in FHIR standard 3.0.2.
This was reported in august 2017, but unfortunately not solved for STU3. See the original ticket here: https://jira.hl7.org/browse/FHIR-13771 and our ticket for the .NET API https://github.com/FirelyTeam/fhir-net-api/issues/1219
The reason the Simplifier .NET validator now triggers the eld-16 is because it uses package 3.0.2 as the source which is in JSON format. The summary is that the eld-16 RegEx doesn’t need backslashes for escaping the underscore in range, but if backslashes are used it should have been 4 backslashes for JSON.
Ardon Toonstra (Jan 17 2020 at 13:05):
@Grahame Grieve , is this something for a 3.0.3 release?
Grahame Grieve (Jan 17 2020 at 19:47):
presumably yes
Ward Weistra (Feb 04 2020 at 03:27):
Captured as J#25776 and just approved.
Last updated: Apr 12 2022 at 19:14 UTC
