When I activate a Form it creates a table in MySQL. (This is my observation)
Question: are these forms in one way or another related to other tables of information and how can I find these possible relationships?
Is complete change of just the form specific directy and import into and activate enough to get them working in OpenEMR?
Example:
I make the Intake_verslag in …/interface/forms/intake_verslag, use the copy of the Dutch and rename into intake_report and continue to change the field names in English. Than change all Dutch in comparable English words and keep these English fieldnames, database fields and *.php files consistent, and activate this new intake_report.
Would this give rise to serious problems somewhere else in OpenEMR? (p.e. reports general, statistics, referral etc?)
Or could I assume it works as flawless as changing Vitals into VitalsMetric?
I am unaware of any ways except as you note in which that would be a problem, except for anyone who is currently using intake_verslag itself. If you recall, that opinion is based on my wife (bless her little heart somehow thinking she could merely change the database and its field names to english with phpMyAdmin and it would all be hunky-dory. Which led to my making the dutch - english labels in the *.php files, restoring all the original configuration to intake_verslag, and then locking her out of phpMyAdmin in the ACL (as well as the ACL edits themselves
And I would say that was also true for the other two Dutch Psyche forms included in the distribution as well.
That said, there are a number of other forms which DO have relational linkages for which I have not found any formal maps, but most assuredly they exist as they caused problems when I tried to populate Insurance Companies, for example, from our prior process data, then found they were listed, but unable to be accessed in the Admin - Practice process.
I wandered into the deep and dark forest of OpenEMR forms a few months ago. Take a look at the sample form in <oemr>/contrib/forms/example2. I created it as a basic template for those who’d like to hand edit their own forms. The other approach is to use the <oemr>/contrib/forms/formmaker tool called formscript.pl. It’s pretty easy.
In the ‘example2’ form folder you’ll find a README.TXT file that I put together. Here’s the basic content of that file:
A few words of wisdom:
1) The folder name you create is important
When you create a new form, copy this whole folder to a new name. If you’d like to create a form for Eye Exams then make a new folder called ‘eye_exam’ with the contents of this sample inside of it.
2) Stick with the same name once you’ve created the form
Every file and database reference in these PHP and SQL scripts refer to your form name explicitly. Once you’ve chosen a name STICK WITH IT because if you change it half way through then your form won’t work.
3) Normally a form requires it’s own database table. Be sure to edit the table.sql file appropriately.
=======================
Forms are finicky things and can have odd dependencies. Take extra caution when working with them as they are easily prone to copy-and-paste or typographical errors.
Do you know of a standard set of forms? In Connecticut we seem to have new and different forms every year and they aren’t the same as other behavioral health agencies in our area.
somehow thinking she could merely change the database and its field names to english with phpMyAdmin and it would all be hunky-dory. Which led to my making the dutch - english labels in the *.php files, restoring all the original configuration to intake_verslag, and then locking her out of phpMyAdmin in the ACL (as well as the ACL edits themselves