# How to make mappings easier to query and to document in openEHR

**URL:** <https://discourse.openehr.org/t/how-to-make-mappings-easier-to-query-and-to-document-in-openehr/5063>\
**Category:** Terminology\
**Created:** [3 April 2024 08:49 UTC](https://discourse.openehr.org/t/how-to-make-mappings-easier-to-query-and-to-document-in-openehr/5063 "2024-04-03T08:49:43Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [17 April 2024 19:05 UTC](https://discourse.openehr.org/t/how-to-make-mappings-easier-to-query-and-to-document-in-openehr/5063/31 "2024-04-17T19:05:59Z")

</div>

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?

---

_[View the full topic](https://discourse.openehr.org/t/how-to-make-mappings-easier-to-query-and-to-document-in-openehr/5063)._