leecrites wrote on Friday, January 21, 2011:
Y’all;
I am making the changes that allows (a subset of the) BBCodes in the CAMOS reports. Here is what I am trying to accomplish:
1) You put the BBCodes in the actual report item. When you do the “Submit All Content” routine, it will pull the form, with BBCodes and all, into the Encounter. So the actual item that is saved includes the BBCodes.
2) The display function calls a routine that replaces the BBCodes with HTML, so what is actually displayed in the Encounter is the “final product.”
3) When you do one of the print functions, it will process the BBCodes as needed (either the HTML or some equivalent PDF command).
That is my intention. At this time, I have the function working so that most of the BBCodes I allow are being translated into HTML for the Encounter display. Once I have that part working, I’m going to go on to fix the HTML based printouts. At that point, I’ll need some help - I’ve never really attempted to product PDF reports, so I’m not sure what’ll be needed.
CAVEAT NOTICE: I am new to OpenEMR development. I have not (yet) made a git account, etc. I plan on doing that soon, and attempting to incorporate my code into that so I can submit it for testing and such. Any help/suggestions/etc would be greatly appreciated.
There are things like the “clone” process that I have not yet even thought about taking into consideration. I figured that I’d cross that bridge once I had the printed reports done. But this is where y’all come into play - because you’ll know of the other things that I’ll have to take into consideration, and can give me the guidance I might need to do this right.
Thanks muchly,
Lee Crites
lee@tbfed.com