We are officially in testing phase, so please test these out and report any bugs. Plan is to only fix bugs and internationalization fixes in this branch. Hopefully with these tools we can avoid a embarrassing release.
Just committed a nifty css-html printing mechanism for immunization records. Looks better than the pdf variant, and also put a paging mechanism in it (15 shots per page). At this point, now done with new features, and will only be focusing on bug fixes (so far, got a couple reported by Pimm and the above bug to look into).
-brady
(I also committed this css-html immunization printing feature to the development tip)
(both demos use following login credentials user:admin pass:pass )
The goal right now is to just focus on the above 3.1.0 branch demo or the 3.1.0 daily builds in this thread which can be downloaded from the oemr.org download page. If you’re still having bug, give some more details so I can reproduce it.
hey,
can’t think of anything (unless you were using the development tip demo maybe related to the multiple recent bug fixes to layouts and custom forms layouts). we’ll chalk it up to a successful bug fix…
-brady
Still planning to release this version near end of August. Please keep testing the 3.1.0 development demo and the daily 3.1.0 development builds. Specific things to test:
1) 3.1.0 Development demo
Anything you can think of. Bugs also include any english words noted in the "dummyUTF8" language. Also, any users proficient in chinese or greek, please test your language everythwere in forms, names, apssword, calendar, and let know if character issues: http://opensourceemr.com:2093/openemr user:admin pass:pass
I tried to install with all your instructions OpenEMR version CVS 3.1 on a computer with a working version 2.09. All seemed to go smooth. Except that I can’t login with the usual user/password. Could see the Login screen and enter my Username and password, but could NOT enter OpenEMR V3.1.0…
Changing all back to Version 2.09 (RENAME OpenEMR directories) also was easy, and login V2.0.9 again, was without any problems.
Question (if needed):
Can I use upgrade instructions V2.09 (to V3.01 to go direct without an extra step) to V3.1,
following your instruction, so do it without the extra step via 3.0.1?
hey,
Over last several days, have made extensive internationalization bug fixes to admin->language module and the calendar(default and outlook views). Calendar stuff won’t show up in cvs demo until this AM. Plan to add another 39 english constants to the spreadsheet this weekend.
Please keep testing the 3.1.0 development demo and the daily 3.1.0 development builds. Specific things to test:
1) 3.1.0 Development demo
Anything you can think of. Bugs also include any english words noted in the "dummyUTF8" language. Also, any users proficient in chinese or greek, please test your language everythwere in forms, names, apssword, calendar, and let know if character issues: http://opensourceemr.com:2093/openemr user:admin pass:pass
It just hit me that the user manual needs to be revised for 3.1.0 .
Tony, don’t make me beg.
Looking through, only minor mods are required. Can go the 1)easy route or 2)difficult route.
1) Just change the version number, the new patient screen, and give a text sentence how to navigate the tree view in each section (since already introduced tree view, no need to change every image)
2) Just change the version number, the new patient screen, and give a text sentence how to navigate the tree view, and crop every image to the view of interest (hence, image works for both radio and tree view, sort of like unisex but would be "uniview")
hey,
Just looked through 3.0.1 manual in more detail; for option 1) above, would actually only need to mention tree view instructions in several places. And basically would remove the new patient image. So option one should be entitle the 1)even easier route.
-brady
Smile … I already told my tech writer to start on it and use the opportunity to do some QA as well. Also Justin Doeil of Youthbridge is going to do some merge work that includes things he has written that are missing from the setup process and things from new IPPF user guide that was presented at the FOSS Conference, that may just be wiki based, however.
Dummy translation showed:
Misc Billing Options for HCFA-1500; amount Charges; STATE; Additional Notes; SAVE; Don’t Save Changes
In Form Review of Systems:
SUBMIT
In Fee Sheet Form many Fields are not translated. In the screen but also in the defaults.
The word "category" comes back in many screens as category and not as dummy…
Some: Save, View, etc are not translated, but could not find them back also these are self explaining in any language. Should be somewhere in reports, but checking the Dummy actually, needs two OpenEmr versions one in English and one in Dummy language… and that is to much for this amateur.
Thanks for testing. Remember to focus on the 3.1.0 demo, since I’m not paying attention to the development tip right now (in development tip, the “checkbox w/text” and “listbox w/add” labels were altered for cosmetic reasons, hence no longer mapped to their translations).
The "with selected:" constant was just added to the spreadsheet.
I didn’t quite figure out a clever way to deal with the ICD9, CPT4, and CHCPS labels, and since US based were low priorities. I plan to try to deal with these, the other fee sheet stuff. and the Misc billing sheet. Thanks for finding it and reminding me.
Also will do the submit button in ros form.
‘category’ is not straightforward since hard-coded into database from admin->forms. Likely try to deal with after release.
Unclear about the some: stuff. If you can, give me pages, so can fix.
hey,
Over last several days, have made extensive bug fixes to the calendar, so please test away.
Please keep testing the 3.1.0 development demo and the daily 3.1.0 development builds. Specific things to test:
1) 3.1.0 Development demo
Anything you can think of(calendar, access controls, everything). Bugs also include any english words noted in the "dummyUTF8" language. Also, any users proficient in chinese or greek, please test your language everythwere in forms, names, password, calendar, and let know if character issues: http://opensourceemr.com:2093/openemr user:admin pass:pass
YES, it works, see my former remark just before this one.
I did it in my own Experimental Version 3.1.0 and it came out as I expected. Now if you make the Constants in this file xl( ) translatable, there will be in future releases no hassle about how to change from IDC9 to IDC10 or to ICPC. Or for international use who do NOT use CPT4 codes change to "Fee" or "Declarable"; and HCPCS to "Lab and/or X-ray". It might be of help if there was a small something like "// Note:" to indicate that IDC9, CPT4 and HCPCS are default and should only be changed into something different if the local use of OpenEMR makes different coding for encounters/users or facilities and billing necessary.
All related ICD9, CPT4 and HCPCS codes are imported after installation and NOT through Update. The DEFAULT values for New Patient or Established Patient default to ZERO via CPT4 codings and should be created via Admin Services or direct into phpMyAdmin IMPORT SQL or CSV file for the right tables and/or can be made through Admin => List => Fee Sheet
Also a remark about Modifier and Justified could be of importance for OEM-Newbies. (Although they might be in somewhere in OpenEMR already…)
Please include this in the new V3.1.0 release since I like to have it available as a regular option for new installations.