# Coding element and event names

**URL:** <https://discourse.openehr.org/t/coding-element-and-event-names/1998>\
**Category:** Specifications\
**Tags:** template\
**Created:** [28 October 2021 11:14 UTC](https://discourse.openehr.org/t/coding-element-and-event-names/1998 "2021-10-28T11:14:21Z")\
**Posts on this page:** 1\
**Showing post:** 53

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [3 December 2024 18:17 UTC](https://discourse.openehr.org/t/coding-element-and-event-names/1998/53 "2024-12-03T18:17:47Z")

</div>

> [@sebastian.garde](#):
>
> We should probably deprecate this assumed value…You have given the main, maybe even the only example for it that I have ever heard, and even there it seems of dubious value to me.

It was an idea of Sam’s (and maybe Dipak), from close to 20y ago. It was something I think they thought would generalise across medicine, but over time the only examples that have ever emerged always seem to have been patient position during BP measurement and exertion during heart rate measurement.

For good or bad, we have engineered the capability to have ‘assumed values’ in any primitive data type. This could potentially be used as is to implement some sort of default values, but since default values need to be definable for larger granularity objects (potentially even up to whole Observations) it might be better to deprecate it.

---

_[View the full topic](https://discourse.openehr.org/t/coding-element-and-event-names/1998)._