TLDR
Our public repository provides a database-centric approach to implement modifications to standard emr.
Like windows registry or linux package managers, dev_obj table stores various “things”. The dev_component table implements the relationship between defined objects. All “objects” are then supported by specific code that implements specific actions. As an example, DevFile object can be leveraged to control actions of standard scripts. Object versioning implements ability to support custom behavior for different emr versions or specific installations. guids implement integrity of objects globally.
Currently the code includes objects that works for MySQL or compatible engines. Interested developers can also look at the stored functions that use dbengine to generate guids as an alternative to emr code.
Changes needed to standard code:
- Review and install tables in database.
Depending on your dbengine version, you may need to set uuid default to null and use the polyfill + trigger mechanism to manage uuid values. - Modify composer.json and globals.php
- Review changes in mdpubapps branch to see how external content can be included in emr screens.
If any questions, please post in its own thread. Optionally refer to this post.