Stream: hapi
Topic: Validation of post-coordinated SNOMED CT codes
Morten Ernebjerg (Aug 12 2021 at 08:52):
I am working on a validation service that builds on HAPI & the HAPI JPA starter. I am loading SNOMED CT on start-up using the termLoaderService.loadSnomedCt method. I additionally load several IGs on start-up. When validating resources against profiles from the IGs, validation of individual SNOMED codes seems to work fine, but I am getting errors for (what I believe are) correct post-coordinated codes, e.g.
Unknown code {http://snomed.info/sct}417662000:246090004=22298006 for 'http://snomed.info/sct#417662000:246090004=22298006'
Should validation of post-coordinated codes be working out-of-the-box or is it something that needs to be separately configured? Conversely, if it is a known limitation, is there some way to avoid this causing errors (without dropping validation of normal SNOMED codes)?
Morten Ernebjerg (Aug 17 2021 at 11:23):
@Patrick Werner Do you happen to have experience with this?
Patrick Werner (Aug 17 2021 at 11:24):
yes and no :-)
Patrick Werner (Aug 17 2021 at 11:24):
post-coordination and validation is a nightmare (one of the reasons we changed the icd10 profile recently)
Patrick Werner (Aug 17 2021 at 11:26):
From my perspective you have to implement a IValidationSupport Module which does the magic on post coordination and add this to the ValidationChain BEFORE the other TermValidationModules.
Patrick Werner (Aug 17 2021 at 11:27):
Naive approach: split the post-coordinated codes into singleSNOMED-CT codes and validate these. Ignoring the post-coordination syntax
Patrick Werner (Aug 17 2021 at 11:29):
Or, trigger an existing SNOMED-CT capable Termserver. You could try integrating SNOWSTORM (https://github.com/IHTSDO/snowstorm) as a ValidationModule, outsourcing the actual Validation of the post-cord code
Morten Ernebjerg (Aug 17 2021 at 11:36):
Ouch, but thanks for the info! - I guess I was expecting smt. like this :sweat_smile: Maybe a first modest step will be to tell my terminology validation support to ignore post-coordinated codes for now.
@Julian Sass FYI, in case others have validation issues, too: I met these in the sample resources from the GECCO project
Julian Sass (Aug 19 2021 at 06:57):
@Morten Ernebjerg Thanks for the info. I haven't tried SNOWSTORM yet. We have an Ontoserver handling the validation of the post-coordinated codes.
Last updated: Apr 12 2022 at 19:14 UTC
