Stream: terminology
Topic: AdverseEvent.category
Michaela Ziegler (Feb 16 2021 at 10:23):
AdverseEvent.category has a binding to http://hl7.org/fhir/ValueSet/adverse-event-category
If I use the code "product-problem" (http://terminology.hl7.org/CodeSystem/adverse-event-category) in my instance, i get the following error:
Unknown Code http://terminology.hl7.org/CodeSystem/adverse-event-category#product-problem in http://terminology.hl7.org/CodeSystem/adverse-event-category for 'http://terminology.hl7.org/CodeSystem/adverse-event-category#product-problem'
Robert McClure (Feb 16 2021 at 17:33):
The code "product-problem" does not exist in the code system. Why do you think it does? The CI build (which has any completed changes to THO terminology, like this, is here
Michaela Ziegler (Feb 16 2021 at 17:47):
Because the FHIR Structure Definition says this for AdverseEvent.category:
product-problem | product-quality | product-use-error | wrong-dose | incorrect-prescribing-information | wrong-technique | wrong-route-of-administration | wrong-rate | wrong-duration | wrong-time | expired-drug | medical-device-use-error | problem-different-manufacturer | unsafe-physical-environment
and the link goes to AdverseEventCategory (Extensible), where the code is also shown
Lloyd McKenzie (Feb 16 2021 at 21:30):
Looks like the codes got yanked from the proposed code system before it was migrated to terminology.hl7.org. So, while the codes might once have been valid, they're not anymore. What should have happened is that the codes should have been marked as deprecated rather than being removed outright - because obviously they're part of the R4 value set. @Ted Klein - is this something that happened prior to migration?
Ted Klein (Feb 16 2021 at 21:42):
Sigh. The policy of HL7 Vocabulary WG is that codes are never removed (except under very extreme and deliberate circumstances) but are marked deprecated or retired. If they were yanked from the resources that happened prior to the import of the FHIR content rooted in THO. We can absolutely put them back in properly as a technical correction. I did not make any editorial changes to FHIR content for that import (I did not even do the import myself). If it needs to happen prior to R4B please let us just do it; pick a time for the four of us and I will just make it happen.
Last updated: Apr 12 2022 at 19:14 UTC
