# Lifecycle\_state in EHRbase

**URL:** <https://discourse.openehr.org/t/lifecycle-state-in-ehrbase/1567>\
**Category:** Platform\
**Tags:** ehrbase\
**Created:** [19 May 2021 15:35 UTC](https://discourse.openehr.org/t/lifecycle-state-in-ehrbase/1567 "2021-05-19T15:35:02Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![borut.jures](https://discourse.openehr.org/user_avatar/discourse.openehr.org/borut.jures/32/1391_2.png) [@borut.jures](https://discourse.openehr.org/u/borut.jures)\
**Post date:** [2 November 2021 09:10 UTC](https://discourse.openehr.org/t/lifecycle-state-in-ehrbase/1567/32 "2021-11-02T09:10:54Z")

</div>

> [@Seref](#):
>
> don’t worry. In the sprit of openEHR, we’ll first invent an acronym mapping language, then develop an information model and add both to the specs. Problem solved.

Please don’t provoke another discussion about the validity of reference models (may I as a newcomer even ask such a thing 😳).

An important step forward happened over the past few days regarding them.

Check [this thread](https://discourse.openehr.org/t/where-to-find-aom2-bmm-for-the-latest-stable-release-2-3-0/2006/28) to see what @thomas.beale and @pieterbos achieved:

> [@Where to find AOM2 BMM for the latest stable release (2.3.0)](https://discourse.openehr.org/t/where-to-find-aom2-bmm-for-the-latest-stable-release-2-3-0/2006/28):
>
> Teamwork rules 😉

---

_[View the full topic](https://discourse.openehr.org/t/lifecycle-state-in-ehrbase/1567)._