Good to hear from you Sinte and I hope to help - we definitely need to sort this out together for our overall O3 i18n strategy.
From a quick review - the scope of implementing a single config component might be big-ish, given there are many different O3 apps leveraging date-type fields: >30 in esm-core, >180 in esm-patient-chart and >140 in esm-patient-management. Mind you maybe it’s just a refactoring challenge, once the component has been built.
It looks like omrsDateFormat could be the component to focus on but I’m not sure.
@sinte or @dagimm is your team interested in partnering with an org to build this config out? I might be able to find some OMRS Inc resource to help with the Architecture but we’ll most likely need help with manpower when it comes to implementing it. I’ll also raise this with the whole tech team in next week’s TAC call.
Minor Clarifications:
- Would you also expect config for hourCycle? E.g. do you find that your users sometimes require a 12hr cycle instead of a 24hr cycle?
- You would expect this Date-config to be separate and unaware of this browser-based i18n feature, right?
- Did you have any thoughts/replies to this thread: O3: Config to set a standard date/time convention throughout App?
Pinging also @mogoodrich & @mseaton & @dkayiwa b/c they’ve suffered through so much of OMRS’ i18n history and may have some sage advice here - e.g. Mark & Mike, do you guys have a Date locale config you use for PIH EMRs?