deschel wrote on Sunday, July 29, 2012:
Some of what was expressed in this post is concerning to me.
Please verify that what I am interpreting is correct:
“Administration->Layouts” does not just change the layouts, but it changes the database tables.
If so, then the word “Layouts” is misleading. Additionally, giving the user this ability is kind of dangerous (even if they do have admin priviledges.)
Plus, new updates to the software risk breaking the database customizations done in “Administration->Layouts”. If someone, needs to add new fields, they should probably use the already existing “usertext” or “userlist” fields. I really doubt many people add new fields by this method anyway.
Can we remove the ability for users to make database changes from “Administration->Layouts”?
The layout customization should just effect the layout, not the database. If someone does not want to use a field, they can just delete it from the layout. The field should still exist in the database after this deletion (there is really no need to delete the table field) and the user should be able to add it back later if they change their mind. This would alleviate the risk of users messing up the database by modifying the layout. And, also eliminate the need to back up the database prior to layout changes.
If someone really does need to track other data, requiring database changes, this should be done by using the phpMyAdmin database module embedded in OpenEMR to add new table fields. This the more appropriate way to modify the database. The phpMyAdmin database module can be accessed from: “Administration->Other->Database”.
“Administration->Other->Database” for database changes.
“Administration->Layouts” for layout changes.
We really need to keep these two things separate!
Brady, would you agree to this change?
-david