Stream: terminology
Topic: USA Dental Code System Canonical URLs
Robert McClure (Oct 18 2019 at 00:29):
Folks,
Just spoke with Jean Narcissi about determining the canonical url's for the ADA's CDT and SNODENT code systems. These are the official decisions:
CDT for dental procedures. Used for claims and clinical care.
Owned by ADA and there is a small cost.
HL7 official symbolic name: cdt-ADAcodes
OID: 2.16.840.1.113883.6.13
Defining url (just decided today): http://ada.org/cdt
SNODENT for dental conditions, findings, disorders. Used for claims and clinical care.
Owned by ADA and I think there is now cost, not sure.
HL7 official symbolic name: ada-snodent
OID: 2.16.840.1.113883.3.3150
Defining url (just decided today): http://ada.org/snodent
Robert McClure (Oct 18 2019 at 00:30):
@Grahame Grieve @Rob Hausam Can you add those the terminology page build?
Grahame Grieve (Oct 18 2019 at 02:36):
yes but can you please make a task in gForge to make it official?
Rob Hausam (Oct 18 2019 at 03:49):
yes, can be added to the page (and need a task)
Robert McClure (Oct 18 2019 at 17:52):
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=25029
Eric Haas (Oct 19 2019 at 17:58):
OK this is so late-breaking. we have this table below for US Core table below and I think we should keep it as is for CDT in R4 and change for R5.
I keep bringing this up but we keep publishing some US code systems in the FHIR spec but its not complete so we have to publish this table in US Core (and yes there is overlap with icd-10-cm since we give a little more background. ) We don't seem to have a clear strategy on this. Can we consolidate this list in the future in one place as the source of truth?
Robert McClure (Oct 25 2019 at 14:52):
First let me highlight the value of meaningless identifiers - because as we see here, the thing that is consistent is the thing humans tend to not mess with - OIDs!
What we see here is what I think will be what I suspect will be our best _standard_ approach to uri/url identifiers for code systems upon our initial need to identify one in FHIR: (@Julie James and @Carol Macumber )
- If the code system authority is immediately engaged and crafts a url they want and own - use that and stop
- If we need to create something because above is not happening fast enough, use the http://hl7.org/fhir/sid/xxx (or some tbd better base) where the xxx is an established (at HL7 OID site or other) short symbolic name
- Publish this via UTG
- Understand that this url can change when the steward decides to establish something that is better aligned with their domain. Obviously this is a big deal with implications, but it's a fact, as we see here. So we need a defined process to manage this and I'd except this is something HTA, with our help, will craft as the responsible entity in HL7 for external code systems. I'd like better clarity on how we technically help folks go through a transition like we see here. For now, @Eric Haas seems to describe the result of this process.
Grahame Grieve (Oct 25 2019 at 20:50):
Publish this via UTG
I don't know what that means
Grahame Grieve (Oct 25 2019 at 20:51):
There's some technical support at that end point for sids. So I'm not clear on what is being proposed here.
Robert McClure (Oct 27 2019 at 17:01):
@Grahame Grieve I suspect we're talking past each other. I'm about to head out of the country but will reach out via skype next week.
Last updated: Apr 12 2022 at 19:14 UTC
