terminology expression cannot accept SNOMED expressions or READ-codes with DOT's
Raise
Analysis
Raise
Analysis
Description
Activity
Show:
Koray Atalag May 2, 2017 at 9:58 AM
yeah this is pretty important - we really need to sort out a reasonable way to bind valuesets using EQL and/or FHIR terminology service.
Bert Verhees April 25, 2017 at 10:03 AM
An example:
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
Details
Details
Reporter
Bert VerheesLabels
Components
Affects versions
Priority
MajorCreated January 19, 2017 at 6:28 PM
Updated June 30, 2017 at 8:12 AM
The problem is that the code part of the terminology binding:
V_QUALIFIED_TERM_CODE_REF
consists of two parts, the part for the code is of type NAMECHAR which does not accept the characters needed to construct a SNOMED expression.
SNOMED expressions can serve in situations where no concept is available. In this way it is possible to construct any clinical term in SNOMED.
Also I found out that RAED2 codes containing dots are not accepted, like this:
["READ2"] = <
items = <
["at0004"] = <[READ2::9x2..]>
["at0005"] = <[READ2::9NgG.]>
["at0022"] = <[READ2::9NgG0]>
["at0027"] = <[READ2::9NgK.]>
>
>