Stream: hapi
Topic: ValueSet expansion with snomed ct codes for JPA 5.1.0
Oliver Egger (Aug 20 2020 at 12:45):
I'm trying to work with the NpmJpaValidationSupport validation functionality and I stumble upon the handling of ValueSets. In a ValueSet I have a compose with 2 snomed ct codes inside. SNOMED CT is not directly supported so the expanded ValueSets are not containing these 2 codes (the IG Publisher can handle this with the terminology server). An option would be to upload the snomed ct codesystem directly, however I would like to have a quicker development solution:
Is it possible to connect tx.fhir.org to hapi for testing purpose? And if yes has somebody a sample how to add that to JpaValidationSupportChain?
Jens Villadsen (Aug 20 2020 at 20:44):
well ... using https://hapifhir.io/hapi-fhir/docs/validation/validation_support_modules.html#remoteterminologyservicevalidationsupport for LOINC and SNOMED could be a solution
Jens Villadsen (Aug 20 2020 at 20:44):
and then default to the local valuesets and codesystems for all other codes
Jens Villadsen (Aug 20 2020 at 21:09):
Maybe @James Agnew has a better suggestion
Oliver Egger (Aug 21 2020 at 20:12):
thanks @Jens Villadsen , i was hoping somebody has already connected remoteterminologyservicevalidationsupport with tx.fhir.org but I put it up on my :working_on_it: list. I found out that you can defer the ValueSet Expansion by not setting setDeferIndexingForCodesystemsOfSize. Then the InMemoryTerminologyServerValidationSupport expands the ValueSet and is not validating the codes and in addition it is possible to disable the task expanding the ValueSets. I have the example ig jpa validation server up here and can now validate with the $validate operation, time for the weekend :tada:
Last updated: Apr 12 2022 at 19:14 UTC
