SNOMED in CKM
bert.verhees at rosa.nl
Tue Apr 25 06:04:14 EDT 2017
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.
Excision of lymph node: Procedure context (attribute)
58347006:408730004=410534003 <-- Not indicated
58347006:408730004=262008008 <-- Not performed
58347006:408730004=385671000 <-- Unsuccessful
On 25-04-17 09:57, GF wrote:
> I agree.
> Attaching codes to nodes in the archetype is in order to disambiguate
> that archetype node concept/name.
> In addition.
> I think that we should NOT use SNOMED-CT codes for that purpose.
> As far as I know this is the realm of LOINC. So we need LOINC codes to
> disambiguate nodes in an archetype.
> In general LOINC is used to disambiguate the ‘Question’.
> And SNOMED is used to disambiguate the ‘Answer’; the ‘Result'
> This implicates that LOINC must be used in all Archetype nodes that
> are NO leaf-nodes.
> SNOMED must be used in Leaf-nodes and stored as results and queried
> for as results.
> Gerard Freriks
> +31 620347088
> gfrer at luna.nl <mailto:gfrer at luna.nl>
> Kattensingel 20
> 2801 CA Gouda
> the Netherlands
>> On 25 Apr 2017, at 06:23, Pablo Pazos <pablo.pazos at cabolabs.com
>> <mailto:pablo.pazos at cabolabs.com>> wrote:
>> Hi Bert,
>> Maybe my wording is the issue here since I don't disagree with what
>> you said.
>> Take into account that I use the word "might" on every sentence, as
>> the indication of an ability. Never said that 1. applies to all
>> contexts, or 2. that those are hard rules. In those cases I would use
>> "must" instead of "might".
>> With that being said, when a SNOMED CT code is referenced directly as
>> a bind to an archetype node, the purpose is to add definition to the
>> archetype, not to use the code as part of the record. That can be
>> done, but is not the purpose of having term bindings on the
>> archetype. That is explained on the specs somewhere, is not my idea :)
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openEHR-clinical