I tried to export a NationNotes Eye form via Export Configuration last month. In the process all sets of Components were missing in action, see first attachment. The second attachment is the result of importing the .sql file back via the 4.1.1 Demo’s phpMyAdmin, exporting the layout_option tables and deleting the non-Eye tables. The 4 lists survived without difficulty.
Is the problem that Database does not have the adequate structure for the Components (a place to place these values) or is it that I don’t know where to look? The Insert scripts seem to make no provision for the Components.
In Admin there is lists:
Layout-Based Visit Forms
Cylinder
Spheres
Visual Acuity
lbf-data tabel is not included in de sql file, could this cause the problem? This said, not all tables are exported.
Not in:
ophthalmic_nt_lbv.sql
and not in:
non typist eye form.sql
Did you follow the correct export import steps? My suggestion would be you made a export file with exclusions of some tables, with the first export. Due to the new import all choice were set back to default and this made the correct export for the second exportation (or during the second export you choose to export more options than just the obvious table.
I just added a set of Components under Chief Complaint in the 4.1.1 Demo. The entry for Phil Belford in the WYSIWYG editor is in the lbf_data table but not the set of Components. They must be stored elsewhere. Sequential export sounds like a good idea, but first I would have to know where the stuff is hiding.
Another possible etiology may come from the use of Internet Explorer. Firefox works more reliably but I hate to use it, while experimenting, because of the business with third party cookies.
I followed Tony’s direction in the construction of the original .sql file meticulously and even he had difficulties with that file. At that point he suggested that I create a package of the lists with the lbf_data table, then import via a mysql command line (of which Kevin gave instructions) or via phpMyAdmin (which I figured out myself).
The reason you were unable to import, via phpMyAdmin, the Eye files into the Dev. Demo’s had been explained to us by Brady. Import/Export is possible in the 4.1.1 Demo, albeit erratically. The Import function in the 4.1.2 and 4.1.3 Demo’s is nestled in the Settings Tab (of all places). They are truly whacked.
There is a clean install. If you try to import your sql file you know what was added, since we can see that in the sql file examination.
Than we start filling the Opthalm-NN-forms and the detectives have to find the answer for you "missing-"question.
If the Components are filled and can be retraced after LOGOUT, they are stored somewhere and we have to be able to find all changed tables and these have to be inserted in the sql.
I find in layout-options -> LBFcompexamnt for FORM-ID
this form-ID is stored in lbf-data (all data are stored per field used. So next thing to do is make an export sql from lbf_data, restore lbf_data and see if you get what you want.
All tables are included for Ophthalmic-forms, but lbf_data is used to store the patient related information.
The forms table makes the connection between Opthalmic-form and the current-encounter.
The following queries should import the NationNotes components. First test it in a backup db.
insert into database_to.customlists select * from database_from.customlists where cl_list_type in(3,4);
insert into database_to.template_users(tu_user_id,tu_template_id,tu_active_id) select (select id from users where username=‘username_in_openemr’),cl_list_slno,1 from database_to.customlists where cl_list_type in (3,4);
The following queries should import the NationNotes components. First test
it in a backup db.
insert into database_to.customlists select * from database_from.customlists
where cl_list_type in(3,4);
insert into
database_to.template_users(tu_user_id,tu_template_id,tu_active_id) select
(select id from users where username=‘username_in_openemr’),cl_list_slno,1
from database_to.customlists where cl_list_type in (3,4);
I just added a set of Components under Chief Complaint in the 4.1.1 Demo.
The entry for Phil Belford in the WYSIWYG editor is in the lbf_data table
but not the set of Components. They must be stored elsewhere. Sequential
export sounds like a good idea, but first I would have to know where the
stuff is hiding.
Another possible etiology may come from the use of Internet Explorer.
Firefox works more reliably but I hate to use it, while experimenting,
because of the business with third party cookies.
I followed Tony’s direction in the construction of the original .sql file meticulously and even he had difficulties with that file. At that
point he suggested that I create a package of the lists with the lbf_data
table, then import via a mysql command line (of which Kevin gave
instructions) or via phpMyAdmin (which I figured out myself).
The reason you were unable to import, via phpMyAdmin, the Eye files into
the Dev. Demo’s had been explained to us by Brady. Import/Export is
possible in the 4.1.1 Demo, albeit erratically. The Import function in the
4.1.2 and 4.1.3 Demo’s is nestled in the Settings Tab (of all places). They
are truly whacked.
Hi Pimm,
Serial export/import via phpMyAdmin was a great idea.
Hi Eldo,
There is nothing like getting it from the horse’s mouth. I did find the Components that I had created in the 4.1.1 Demo in customlists. Sneaky little critters.
If I could trouble you for one more piece of advice. How do I strip out the script of the attached files so that they would not overwrite the pre-existing tables? The purpose of this exercise is to provide users with Eye Forms but not wipe out their own data.
It turns out the 2 .sql files in my original post had the “wipe-out” scripts because they were products of the Export Configuration module.
The files posted today were exported from phpMyAdmin; therefore they are “safe” scripts. The only thing a user needs to do before importing is to add the title of these forms to Adminstration/Lists. Then they’re good to go. No deletion of personal files and no pounding on the keyboard to get these forms in manually.
I’ll get all this stuff in the pertinent thread and into the Wiki.
Dear Flor,
in an earlier post you did include two sql files. The longer one does also include the content in Lists for layout-based Visit-forms, no need to include it by hand.
To be sure you could do another install of the sql tomorrow AFTER RESET OF THE 4.1.1 Demo.
BTW I was pissed of to pay for any program since the earliest version of Windows 3.1 and Quickbooks. Just when I bought the latest version there was a complete update, even better and more options compared to the one I payed for. Till today they make me pay for the latest version, but since the last version was incomplete and MS did say this was the greatest release ever, I do not want to pay for the new version. Thus I try to use free versions and if they work I pay for them, but only if they really give more options needed and included.
The ophthalmic_nt_lbv.sql does enter the form into Administration/Lists/Layout Based Forms, but the nt_eye_form.sql does not while the 8 eye forms.sql have only the Lists for Add, Axis, Cylinder, Sphere and Visual Acuity. As a result the LBV forms associated with the .sql files, even when clearly in the tables, will not show up as forms that can be used for recording a H & P.
I found out the hard way as I experimented on the 4.1.1 Demo, doing a couple of deletions of the lbv_options tables and re-importing the .sql files. Best way to learn is to get your hands dirty and wading in the weeds. Probably should read the Help section instead of all this fooling about. Thank goodness I did not crash the Demo again.
This is a little embarrassing. Harley’s NationNotes article, part 3, did say that the Components are stored in customlists. Of course, I noticed this after starting this thread.