Is it possible to rename the tab ‘Layout Based’ in an encounter?
The perfect place for this would be when I create a layout based form and have a field ‘Category’ and whatever I enter there would be the name of the tab.
This way I could group layout based forms into different categories like the regular forms. For a user of the the system it is very uninteresting how I have created a form, but much more important what kind of form it is.
I have seen the trick to use the translation table to rename the tab and it would work - but is a hack (sorry and would still not allow to sort these forms into different categories.
The tab is generated from the List Editor, where the names of the new forms are entered. Have a look at openemr/interface/super/edit_list.php.
There is already a LBF folder in openemr/interface/forms which is required for the Patient Summary, therefore it should not be tampered with. Copy the content of that folder and name it something else. Hopefully the renamed folder will appear in Administration/Other/Forms so that a new category (tab) can be assigned. Code found in openemr/interface/forms_admin/forms_admin.php.
You could name the same Category-forms with the same beginning. First sort the names in the order you wish in Administration => LIST Next sort the forms in Group names in Administration => Layouts After that you still can sort the created groups in the Layout based forms.
No hack needed as with next examples of doing it another way.
Example can be found in weekly Demo for Ann Boleyn for her allergy LB-name-approach and for Infection Group-approach
Sometime ago we had provided code that lets you recorder all forms based on administrator defined order. Time of creation of a form is irrelevant to md looking at all observations.
Thank you all for your hints and suggestions!
In comparing the effort of creating a form as LBF or using the XML form generator, there is not too much of a difference.
So, I might end up creating my forms the old fashioned way and just register them. It’s a pity but that unchangeable tab in the encounter is a kind of a deal breaker for me - brings too much programming internals into the user interface.
Is there a way to communicate this to the people actively developing to possibly get this changed?