I am not sure I understand how you see this used then. Are you suggesting to ‘decouple’ the value from the code (or preferred term)? How should we ensure that the meaning of the code matches semantically the value entered? how should any validation work if the code is saying ‘A’ but the value is rather a ‘B’ - which one is ‘wrong’, if you get to a point of validating?
sebastian.iancu
(Sebastian Iancu)
31
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Coding element and event names | 59 | 1522 | 28 August 2026 | |
| Storing codes of two external terminologies | 37 | 2054 | 19 July 2024 | |
| Why is value not optional for DvCodedText | 27 | 1152 | 20 October 2021 | |
| LOCATABLE name with a SNOMED code | 18 | 1287 | 18 March 2024 | |
| [EHRbase] Storing and querying data without an standalone archetype | 38 | 1222 | 17 April 2024 | |
| SNOMEDCT - correct representation | 49 | 352 | 20 May 2017 | |
| Option to record free text as choice against DV_CODED_TEXT - do we need DV_PLAIN_TEXT | 72 | 2740 | 5 January 2023 | |
| What happens once the Pulse/Heart beat archetype is replaced? | 48 | 593 | 2 October 2025 | |
| New ADL/AOM proposals to solve some old problems | 15 | 73 | 29 April 2013 | |
| Terminology_id name list | 63 | 885 | 16 October 2026 |