Closed KevinMayfield closed 4 years ago
From @DaveBarnett
a lot of these errors you point to are from the SNOMED ECL statements (for example "CareConnect-AllergyCertainty-1 | error | Error from server: The filter "constraint = (385434005 | Improbable diagnosis | OR 2931005 | Probable diagnosis | OR 255545003 | Definite | OR 410605003 | Confirmed present |)" was not understood in the context of http://snomed.info/sct"
If you take the constraint (385434005 | Improbable diagnosis | OR 2931005 | Probable diagnosis | OR 255545003 | Definite | OR 410605003 | Confirmed present |) and run this through a URL encoder you get
(385434005%20%7CImprobable%20diagnosis%7C%20OR%202931005%20%7CProbable%20diagnosis%7C%20OR%20255545003%20%7CDefinite%7C%20OR%20410605003%20%7CConfirmed%20present%7C)
you get the results back as expected from the ECL. So I'm not sure it's fair to call this an error on the valueSet definition?
Many of the active errors have not yet been triaged, they were created during the IgPublisher process. It's likely this error (and others like it) are caused by limitations on tx.fhir.org which is detailed here. https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/SNOMED.20ecl.20-.20server.20errors
Tried disabling error. Seems to not be possible https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/ignorewarnings