Stream: terminology
Topic: URI for MedDRA?
Jean Duteau (Apr 13 2020 at 21:37):
I am trying to find a CodeSystem URI for MedDRA. It's not listed on the main FHIR page and my google-foo has let me down if it actually already exists. Does anyone know if there an already defined URI for MedDRA?
Rob Hausam (Apr 13 2020 at 21:46):
I think we need to ask HTA about this. @Julie James? @Carol Macumber?
Grahame Grieve (Apr 13 2020 at 23:08):
I haven't heard of one
Carol Macumber (Apr 14 2020 at 13:12):
Me either. HTA will add this to our agenda for tomorrow (4/15) @Julie James
John Snyder (Apr 14 2020 at 13:23):
@Jean Duteau
Not certain if this helps or is accurate, however, I did find a reference and Example using MEDRA on https://build.fhir.org/ig/HL7/UTG/branches/master/NamingSystem-v3-mdr.json.html
The URI listed at the bottom of the example is: http://terminology.hl7.org/CodeSystem/v3-mdr
For OID based systems, the OID is: 2.16.840.1.113883.6.163
Julie James (Apr 14 2020 at 17:35):
I know the MedDRA folk quite well, I'd like to put this through the new HTA process, even though we don't have JIRA to work with yet. Which MedDRA would you like? It has one major version and one minor version each year, and knowing which version is really important for analysis etc. so it is really version sensitive. Also, which language? There are several :)
Jean Duteau (Apr 14 2020 at 17:41):
I'm assuming that the various versions and languages would work similar to how SNOMED's URI does.
Jean Duteau (Apr 14 2020 at 17:41):
but, for right now, I need the english v23.0 :)
Rob Hausam (Apr 15 2020 at 01:44):
Yes, echoing what I think Jean is saying, I believe we need a single canonical url for Medra (for Coding.system), and then the individual versions, including languages, would be handled in the version element (for Coding.version) (with the specific convention for the version string presumably still needing to be determined).
Michael Lawley (Apr 15 2020 at 11:27):
Surely language aspects are better handled with displayLanguage etc rather than version? SNOMED does not handle languages via version.
Rob Hausam (Apr 15 2020 at 12:18):
That is a very good point, @Michael Lawley. I haven't looked into the details of how Medra deals with this in their publications, but presumably and hopefully we can handle it similar to the way it's done with SNOMED, as you say.
Jean Duteau (Apr 15 2020 at 15:28):
Michael Lawley said:
Surely language aspects are better handled with displayLanguage etc rather than version? SNOMED does not handle languages via version.
well, actually it does. The SNOMED URI is 'http://snomed.info/sct/[sctid]/version/[YYYYMMDD]' and the sctid tells us what edition we want:
Canadian English edition 20621000087109. http://snomed.info/sct/20621000087109
Canadian French edition 20611000087101 http://snomed.info/sct/20611000087101
Rob Hausam (Apr 15 2020 at 19:15):
I'm trying to recall if that's the only case where SNOMED CT does that (possibly so)? But, either way, it is one way that they have done it and it is something that we can deal with on the FHIR side of things. Again, I need to get a considerably better feel for the Medra side of things and what their typical publication and versioning practices are.
Julie James (Apr 15 2020 at 20:08):
Guys - MedDRA doesn't work like SNOMED does! It is a different terminology for a different purpose. The HTA tonight have agreed to put the the URI process into action for MedDRA to MSSO for a single canonical URI, then you can add version information (it's currently 23.0 for the major version) as you need to. We are waiting for our JIRA process, but in the meantime, Jean, if you could raise a JIRA ticket and assign to HTA or to me, please do.
Jean Duteau (Apr 15 2020 at 20:12):
J#26858 is created for this
Peter Jordan (Apr 15 2020 at 20:29):
Jean Duteau said:
Michael Lawley said:
Surely language aspects are better handled with displayLanguage etc rather than version? SNOMED does not handle languages via version.
well, actually it does. The SNOMED URI is 'http://snomed.info/sct/[sctid]/version/[YYYYMMDD]' and the sctid tells us what edition we want:
Canadian English edition 20621000087109. http://snomed.info/sct/20621000087109
Canadian French edition 20611000087101 http://snomed.info/sct/20611000087101
There can be multiple languages and dialects within a single edition - e.g. English and Maori within the NZ Edition.
Grahame Grieve (Apr 15 2020 at 20:35):
I don't know any other snomed language edition that works the same way
Peter Jordan (Apr 15 2020 at 20:40):
Do you mean any other SCT edition that works the same way as the NZ one - or any edition that works in the same way as another one? As another example of multiple language editions - the International one comes with 2 languages - US English and UK English.
Grahame Grieve (Apr 15 2020 at 21:00):
usually, one edition has multiple languages
Michael Lawley (Apr 15 2020 at 22:50):
Sorry @Jean Duteau I wrote the SNOMED URI spec :-) It manages different Editions (roughly, national releases) of SNOMED CT. These often contain languages other than English, but that is not how they are managed in SNOMED or in the mapping of SNOMED to FHIR. Rather, SNOMED descriptions include a language tag, and then additional reference sets allow you to group sets of descriptions together for different contexts.
To use different languages with SNOMED in FHIR, you use the normal FHIR language mechanisms. The version of SNOMED only affects which languages may be in scope.
A quick look at the MedDRA translation documentation (https://www.meddra.org/basics) suggests that they are all included in a common release version, so I would expect the normal FHIR language parameters & features would be used.
Last updated: Apr 12 2022 at 19:14 UTC
