The field type for Billing Codes was improved so that the code descriptions are shown instead of their IDs.
A “Source” attribute may now be selected for each layout item in an encounter LBF. You can now reference a field from demographics (“Patient”) or history (“History”) or the New Encounter form (“VisForm”), or specify that the field is an attribute of the visit as a whole rather than just the form instance (“Visit”). Thus you can now have encounter forms that reference each other’s data.
Some cosmetic improvements of column widths in the layout editor.
3 new Edit Options were introduced for layout items.
0 = Make the field Read Only
A = For a Date field only, display the age in years corresponding to the date.
B = Like A, but showing in Gestational Age format (weeks and days).
Added a “P” edit option to make the field default to its previous value.
Added a “field skipping” feature, where you can enter the conditions referencing other fields for which the field in question will be hidden from the form. Click the “?” on the right side of the layout editor to access this area.
Seems good to have this in a Demo. For testing purposes and for making a WIKI page. Where should this be in the WIKI: make some changes in the LBV-Forms, inclusions etc, or in a separate page?
One thing I noted on testing when I place a DOB field in the LBF form. It shows up in the edit form and works, however the DOB entry does not show up on the report.php output (so not on encounter screen or the patient->report output).
I built another quick test form and once I press save, nothing saves but it updates in demographics. Check it out before it resets.The example form works though!
Overall nice job. But one big thing. How do we connect to medical issues? For instance I want to have a form with Medications. Filling the form would also change the patient summary. Is it possible to add a source for these?Problems,Allergies and Medications? Do these also have IDs?
Whoops, I forgot to port one of the commits. That would be the reason for the report.php omissions and the “nothing saves” issue. Will try to get to that and the review suggestions today.
Hi rod,
was testing your LBF improvement. its mindblowing and great contribution. Can you please explain me the “visit” source functionality? please tell in details a bit with one or two examples. will be very handy.
How can the LBF calculate Age? Is it possible? I have made a field called age and inserted the option A in the options field, but nothing happens. I know I am doing something wrong. Please help in it.
Thanks Arnab. “Visit” source is useful when you want multiple LBF encounter forms in the same visit with them sharing a common field. Most fields in encounter forms could be candidates for this, but ones that might have multiple instances per visit would not.
Thanks Rod, for the explanation. its a great contribution and definitely LBFs has expanded OPENEMR possibilities even further. What a work! Thanks a lot!
You can thank IPPF for their sponsorship of these features and for their understanding that sharing with the community is a win-win. Not everyone gets the value of that, and I generally won’t work with those who don’t.
Absolutely true Rod. A big thanks to IPPF for allowing this great piece of work to be shared with millions. Thats the true beauty of being open source.
I have tested it well…loved each and every feature of it. The conditionals added has been of great help.