Specify method for DV_CODED_TEXT to support IHTSDO URI for terminology_id and code_string
Raise
Analysis
Raise
Analysis
Description
PR is addressed in
Activity
Show:
Diego Bosca December 26, 2018 at 12:37 PMEdited
...
<value xsi:type="DV_CODED_TEXT">
<defining_code xsi:type="CODE_PHRASE">
<terminology_id>http://snomed.info/id/900000000000207008/version/20160731 </terminology_id> <!-- international release, 20160731 version-->
<code_string>http://snomed.info/id/900000000000207008/version/20160731/id/404684003 </code_string>
</defining_code>
</value>
...
wrote that xml by hand, so it may not be perfect
Bjørn Næss October 25, 2016 at 6:32 PM
I think this looks fine.
Could someone provide an example in openEHR xml format?
Diego Bosca October 25, 2016 at 9:04 AM
I support this
Details
Details
Created October 24, 2016 at 8:11 PM
Updated September 29, 2020 at 12:07 PM
Codes from terminologies, value sets, and terminologies themselves can all be identified by IHTSDO standard URIs. Use of these may proliferate in the future. We need to describe how DV_CODED_TEXT should be populated to use them. Possibly the best approach is to consider terminology_id a namespace string that maps to a standard URI for each terminology, which will be published by openEHR in a table. Code strings could be treated the same way.