Now it only works fully for the patient’s encounter. This is the Trail commit for getting the approval from the community to continue further. (By ViSolve for MI2)
This requires code changes in all over the code base (where ever required this change).
This appears to work very nicely. so basically need three items to work (correct me if mistaken):
1.Precede display to screen with oeFormatShortDate()
2.Calendar.setup javacript item with ifFormat:“useGlobals”
3.Precede save to database with DateToYYYYMMDD()
Looks like ready to integrate into the codebase and for you to begin the code walk through. One more quick question is how it will manage date and time entries?
We have modified to change the date and also the time format based on the setting in Globals. There is no need for specifying anything different in the ifFormat for the time format changes. We have implemented this in the encounter form for testing.
This looks and tests really nicely. Kudos on coming up with a elegant solution that has eluded us developers for many years. I think your code is ready to implement. I suggest placing an entry in the following wiki page going over the above three steps to implement (along with including the formatting.inc.php script) for developers: http://www.open-emr.org/wiki/index.php/Development_Policies
(could create a ‘Localization’ section or something like that)
Just point us towards your code when your ready to start committing code to the official codebase (above is basically almost ready, except just need to remove the time example you have in the encounter form; when you do this just let me know and I’ll package up the commits into one and commit it).
