That is true, did not think about that.
That is correct Bert,
There is no need to remove the SNOMED CT bindings from the archetypes.
Ian
When we have a DvCodedText and we want to express a List Of Values with term-bindings, then we need SNOMED post-coordination in term-bindings.
Example:
Excision of lymph node: Procedure context (attribute)
58347006:408730004=410534003 <-- Not indicated
58347006:408730004=262008008 <-- Not performed
58347006:408730004=385671000 <-- Unsuccessful
Take into account I differentiate “name” from “code”. Ian is referring to that I think.
Terminology id should use the code, not the name IMHO. Erik in the other thread shared a nice reference using URIs as codes (ids really).
Hi Gerard,
I don’t have a strong opinion on that area, we have too many cases to state MUST rules that might apply just to a subset of cases.
I think a more generic rule is to use term / concept codes that are at the semantic level of the archetype node being defined / disambiguated.
If a SNOMED CT code is at the same semantic level as a no-leaf node of an archetype, IMO it is OK to bind it to the node.
The basic case is the blood pressure, SNOMED has the blood pressure reading code, then specific systolic and diastolic readings.
Also, there might be LOINC codes that might apply it those codes are on the same semantic level as archetype nodes. If are too generic or too specific, might not at the right definition / disambiguation.
Not sure if this is correct or not, it just feels right.