Closed oliveregger closed 7 months ago
There are multiple issues causing this.
One of them will be hard to fix: the validator wants to know if http://snomed.info/sct|10828004
is contained in http://hl7.org/fhir/uv/ips/ValueSet/results-blood-group-uv-ips
, which looks like this:
{
"name": "valueSet",
"resource": {
"resourceType": "ValueSet",
"url": "http://hl7.org/fhir/uv/ips/ValueSet/results-blood-group-uv-ips--0",
"version": "1.1.0",
"status": "active",
"compose": {
"include": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/900000000000207008",
"filter": [
{
"property": "concept",
"op": "descendent-of",
"value": "365636006"
}
]
}
]
}
}
}
We could change the default value, but then we would give the wrong answer when the validator wants to know if it's part of http://hl7.org/fhir/uv/ips/ValueSet/results-coded-values-laboratory-uv-ips
. The slice evaluation is probably not possible without a way to expand that kind of value sets.
do you have an idea why the behaviour changed between the version? because before this error was not happening, and we did not change the ips / or eu lab version?1
can we solve it with making the expanded ValueSet's available?
It seems it was not needed :)
fixed in versin 3.8.1
There seems to be a difference in tx validation with the new matchbox version:
FHIR IG Publisher Version 1.6.3 (Git# 58fd9ba64d35) returns only display warnings for [Bundle-1c-TxProblem.json]( https://build.fhir.org/ig/ahdis/ch-elm/branches/oe_validationcmp/qa.html#_scratch_repo_input_resources_Bundle-1c-TxProblem}
With matchbox 3.8.0 there are mutliple errors when configured with the internal terminology server, especially two:
matchbox 3.6.0 with ch-elm did not show this validation error behaviour (there is a constraint failing there but not validation issues but a constraint in the valueset)
OperationOutcome with machbox-ch-elm v.3.6.0