I am new developer and trying to run the example_patient_data.sql to test my install and learn openemr at the same time. However when I run this sql it has less than the number of columns expected. Is there an updated version that I can use? If not I can fix the sql to make the inserts successful as well. Just want to know if there is a work around out there already.
hey,
That file is outdated (about 4 years or so), so would take modifications to get it to work. There has been lots of talk about creating sample datasets, but nothing has materialized yet.
-brady
Code patches for review can be submitted in the sourceforge tracker here in either ‘Code Review’ or ‘Patches’ (note you can upload a file with your new artifact). Important to also post it on the forums heres so we know to look for it. Best way is to create a patch (via ‘diff’ command) from most recent cvs version, however full files will also suffice for new developers (especially in this case where the original file is 4 years old).
Looking forward to reviewing/committing your contribution. Don’t hesitate to ask if have any more questions or unclear about the process.
would it be possible to do something as Translations? I could send you a Curacao table with 50.000 names and anybody could add or delete. In my opinion we could also start with a lot less names woul making them unrelated a bit easier.
Some mock Pharmacies and Insurance companies.
Real medication list and what else…… if we do it via Google and import them with your script or some else’s???
A sample dataset of 50-100 patients and with a mixture of encounter, history, billing data and some supporting, mock users in different roles, insco, pharmacies, referring providers, etc would be more than adequate.
-Tony
I will be more than happy to collect and compile all the input files and
create a sample data set. Let me know where to retrieve your input
files. Csv format is preferable since I can manipulate and create SQL
statemens easily
If I do it it would directly into OpenEMR and then I would do a backup dump creating the SQL inserts. No need to create CSV or write import scripts, just restore the SQL test data dump and go…
Anybody willing to sit and type for a few hours could do this. I have a 50+ person dataset for this, but it’s version 3.1 and I haven’t tried upgrading it yet to 4.0+, maybe this week.
you do the thing, but if you do this in the Demo’s of OpenEMR you have to make a script to insert the data every morning after the automatic renewals of Brady about 11:00 hrs am West time.
Seems a bit awkward. This could mean that everybody has to import their own SQL with data to be happy at test time if you can not do the auto refill just after the Brady renewals.
I would like to start a new total minimla fill every mourning with relevant initial data. These could be rather lengthy or just basic like Demographs, Facility, Pharmacy and Insurance. Copay en ICD9 codes and some to be invoiced amounts.
I am willing to help but not every morning……… It should be a lasting thing. But I am not a programmer, CSV ok. Fill with data and make a SQL basic Querries via PHP MyAdmin OK. But that is about what I can do to support.
Pimm,
The official release demos contain sample data. Pre-loading the cvs demos would defeat some of the purpose of these things, which are to identify bugs. Every time you or somebody types in low-level info, you are doing a check for bugs. Previous to these demos, many official releases of openemr contained a sucky bug. Plus, the sample set would have to be continually updated with development of code (ie. adding a new patient_data column would require the developer to modify the sample data set stuff); to much of a burden for the few developers whom need to instead focus on pumping out as many new features as possible.
-brady
what you are telling me is that if I want to check a new feature in Demo versions:
I have to include my own new data in Demo versions, so I have to upload my own Backup SQL and see if the in depth feature, something like Layout based forms, is working?
For superficial testing your solution is OK, but in depth testing need lots of input to find the bugs and manual input every time of the needed information to test only one feature is a headache.
Why have some tables filled with a lot of stupid information. Names of all Countries in this world, except for the Netherlands Antilles? And others are prohibited, States contain only your State, “California” and not all US States? Take once more a close look at the different tables incorporated in the latest working version and you know there is discussable difference of opinion here.
But you are far more involved and much more active in OpenEMR. I only know that quite often, I refrain from testing, just because I do not want to type in names again and again, to be followed by some mock information of some patients to see the feature and my idea is not working in real life Demo.
YOU ARE THE BOSS and I do not intend to discuss your authority, I rest my case…… ;-))
(I go for my own SQL uploadfile)
Like I did when Rod did NOT want to have the ICD9 in some config.file to be translated , I made my own translation of that file. (00OOoops I mentioned it again, sorry Rod)
Decisions are made by the community with developer/technical guidance. To do what you ask requires constant maintenance (to keep the datasets compatible with developing database), which takes away from development resources towards other areas. I have no interest in doing this (I focus on bugs and stuff that expands the userbase, which this project doesn’t fulfill), Another developer, if interested, can always take it on, so it never hurts to keep asking