# Call for Suggestions: OpenMRS Platform 3.0.0

**URL:** <https://talk.openmrs.org/t/call-for-suggestions-openmrs-platform-3-0-0/46965>\
**Category:** Development\
**Tags:** platform, platform-3x\
**Created:** [August 28, 2025, 11:21am UTC](https://talk.openmrs.org/t/call-for-suggestions-openmrs-platform-3-0-0/46965 "2025-08-28T11:21:42Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![mksd](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mksd/32/11729_2.png) [@mksd](https://talk.openmrs.org/u/mksd)\
**Post date:** [September 29, 2025, 6:14am UTC](https://talk.openmrs.org/t/call-for-suggestions-openmrs-platform-3-0-0/46965/33 "2025-09-29T06:14:30Z")

</div>

> [@ibacher](#):
>
> For fields in the database that store a timestamp, we should convert to using fields that use timestamp with timezone information, so that datetimes are representable unambiguously in the database.

+1 to that!

Having dealt with the timezone issue in the past, I can say it is essential, especially for centralized (cloud) deployments, which are becoming increasingly common.

---

_[View the full topic](https://talk.openmrs.org/t/call-for-suggestions-openmrs-platform-3-0-0/46965)._