How to modify "Add Issue" form

[rdh61]

Hi,

I am using openemr version 3.2.0 on Ubuntu 10.10.

Where do I go to modify the "Add New Issue" form?

Many thanks.

[zhhealthcare]

The add issue form is critical in terms of the new certification. Are you implementing OpenEMR within the US?
Shameem

[Aethelwulffe]

Hi RDH,

This form is only modifiable by changing the code outside of a setting or two I think exists in Globals Admin. As Shameem states, that is an important part of the new versions that should not be messed with too much, but since you are running 3.2.0, you MIGHT consider upgrading a few versions (all the way to 4.1 might be nice) and see if THAT takes care of your issue first. It's a lot easier to get help with a newer version (hey it IS free).
I am not sure where the file was in 3.2, but now some of the file names associated with "issues" are add_edit_issue.php, left_nav_issues_ajax.php, link_issue_to_encounter.php, and ippf_isues.inc.php...and naturally all their include files. They are in various locations, but you can search them out with those file names.
Mind if we ask what your goal is? Maybe we can help better.
-ARt

[rdh61]

The Issues form (in 3.2.0) contains a box labelled "Diagnosis" which is bound to an installable list of diseases (ICD codes). I do not wish to use this. I wish to add a box where I can add my own text for the diagnosis.

I am not in the US, I am in Spain.

To upgrade or not to upgrade? I have concerns here. I have modified various forms (e.g. the symptom review form has been extensively changed) and added other, layout-based forms of my own creation. Can I somehow import these (and their data) to a new install of the latest version of openemr?

Many thanks for your help.

[drbowen]

Dear rdh61:

Are you going to make up your own codes?

Or are you going to use ICD-10?

Most of OpenEMR allows the use of the translation xml mechanism to rename practically anything to what you want but applies mostly to text labels. I am not sure that this is possible using the codes table per se.

It is certainly possible to load your own code definitions in the codes table. This is a very flexible structure that comes empty when you first install. Most of the code ontologies are owned by somebody and their licensing is almost always incompatible with the GPL licensing that we use.

In the codes table you would need to set up:

ID code_text code code_type active
45097 UPPER STOMACH-INTESTINE SCOPE, SIMPLE 43234 1 1

If you want to use the ICD-9 code but rename it to some thing else easy to remember you could just change the "code_text" to what you want.

If you want to use ICD-10 you would need to load the ICD-10 codes into the table. The ICD-10 codes are owned by the World Health Organization so you would need to own a licensed copy.

None of this involves changing the software - just manipulating the codes table.

Sam Bowen, MD

[rdh61]

Thanks for your reply, but I don't want the codes table. All I want is a simple text box! Please can anybody tell me how to add one?

[Aethelwulffe]

We'll get you a file. You want to be able to write in there...no list or any of that junk. Right? Simple, and then it saves the data...right? I will get you a file from 3.2, but you likely would benefit from newer versions.
-Look for it first thing in the morning tuesday, your time. I will get something out for you tomorrow evening.

[rdh61]

That's exactly what I want - thank you very much for your efforts.

Any chance you could also respond to my concerns about upgrading to a higher version of openemr, expressed previously:

"To upgrade or not to upgrade? I have concerns here. I have modified various forms (e.g. the symptom review form has been extensively changed) and added other, layout-based forms of my own creation. Can I somehow import these (and their data) to a new install of the latest version of openemr?"

Again, thanks.

[drbowen]

The problem with custom forms that have not been contributed back to the project is that you have to import all of your custom changes to the new version every time you upgrade.

Advantages of upgrading:

Loads of new features.
Multiple new bug fixes.
Multiple security fixes.

Not upgrading. You have to learn how to find and apply all the fixes yourself.

The longer you wait to upgrade the more painful it becomes.

Sam Bowen, MD

[Aethelwulffe]

Sorry RH,
I need to get into the office to run my 3.2 changes for testing. I'll be a little delayed. It's mostly just an add-option box change.