This message is addressed to you because I think you are the right person to approach with this information. I have been working with a Dr. East a cardiologist on creating a printable office note. The above link is what we have finally gotten to in about 6 months of development. Dr. East has spent a considerable amount of money on this project and he is ready to turn it over to the community for futher development and inclusion in the base code.
We approached the office note from the LBF direction. We had no real clue what the under taking would really cost. It has been a laborous task in getting this far. I am going to try to get the LBF out of the production server for you to review on the demo server. I just need to get Rakesh, the programmer that built the PDF print out to show me where those files are located and move those to the demo server. I don’t know how to submit to the grub.
Dr. East was wanting to know if there are other cardiologist that are in the community that could use this office note. Dr. East is a part of the Sentara Heart Hospital in Norfolk VA.
If you could send me some feedback that would be greatly appreciated.
Doc looks nice; pretty cool to see something like that from the LBF engine. Definitely should try to integrate this into OpenEMR. It’s hard to say how difficult(or easy) it will be integrating this until we get a look at the code. Probably the most efficient thing to do here is to get the code and then figure out how to best integrate it. Does Rakesh know git(aka grub ) or can he make you a patch of the code he developed?
I am waiting now on Dr. East to approve the upload of the code. Since he did sponsor the creation of the code. I have looked at the GIT and I think I can create an upload. I created an account on the GIT and will upload the code as soon as Dr. East approves it.
Dr East has approved the release of the code. However, i have had problems with configuring the .git to work from my server and making a patch has proved to be a challange as well. So here is the next best thing. I have made a copy of the entire folder with all the code in it. It can be downloaded here http://www.openmedpractice.com/openemr-4.0.zip.
I will keep workinig on making a patch and/or the git.
Hi,
It looks like that is an entire OpenEMR package? Are you able to send the files you only modified and keep it in the openemr directory structure (ie. how the openemr official patches are). If you can do this and give me the OpenEMR version you based the changes on, then I should be able to quickly get it into a git commit.
thanks,
-brady
Brady,
I offered to help Sherwin sort this out in to a package that could be committed… Gonna give it a shot this weekend
Tony www.mi-squared.com / @tonymi2 oemr.org / @OEMR_org
I took a moment and did the patch file. https://www.openmedpractice.com/PatchOfficeNote.zip has all the changes.
I included and sql of the layout_option table incase it would help since this is all based on the LBF that was designed to capture all the data needed for the output. Since the output is only reflecting what is in the database tables.
The other thing was done so that the reports can be printed separately was the in order to generate the office note. Only the HPI has to be selected in the reports generator. Selecting HPI tells the system to grab all the other form data to generate the note.
Thanks to Tony and Ken for helping get this integrated into the next release!
The modifications are functional, but the code is not acceptable at this time for inclusion in the main project. The implementation is, odd, at best. While it works fine, it is too purpose built. I think it will most likely be a good prototype of what could be done. The forms themselves could be pealed off for cardiology use. The code we ported to version 4.1 is available at https://github.com/kchapple/openemr/tree/gaddis-merge-410. The forms are all LBF so you need import the SQL files layout_options41_Orig.sql and list_options41_Orig.sql to try it. And pay very close attention to the Video training Sherwin posted.
Some of the issues are just poor design. Simple things like, the PDF output should work for ALL forms, not just the specific Cardio forms you created and their should be a button that says “Print/Sign/Save” rather than the really kludgy “uncheck all then check HPI” to create the PDF…
The other is that the way the PDF creation was done. It is a big pile of interspersed IF blocks… It would be better to have a separate module that can create PDF from forms.
On my looking through this in the past, also came to the same general conclusions as Tony; not really giving up on it, but realizing there is likely lots of work to do to get this into a less invasive format… Is there any way we can get all of this code rebased into one commit, though; then can look at the code in its entirety and see if can figure out a way to get it to work (such as localize all the list_options and layout_options to the form, such as what the xmlformgenerator forms do).
This thread, and the discussions about migrating LBF InnoDB has me thinking that I could probably build an engine that would generate reports that are far more customizable. Rather than generate a .PDF file, I would generate a Word .DOC file (well really I would use LibreOffice because of licensing issues, but it would be compatible with M$).
How this would work is a user could format their report in Word, defining sections of the document to be filled in with data from LBF. You’d upload it to your OpenEMR server and define it as a template to use, indicating which forms correspond with which templates.
Then anytime you brought up a LBF which had a corresponding template I can add a “print to .DOC” button or something like that. Or alternately I could add a link next to the edit button on the encounters page for forms which have this.
) or can he make you a patch of the code he developed?