I’m new to this whole Open Source Contribution thing and have a question about editing the OpenEMR wiki.
I’ve written documentation on the LBV forms which draws on what I learned in my technical writing classes; it has a TOC, sections with headings, numbered steps and screen shots, and it’s geared towards the technologically aware non-geek. I’d intended to put it on the LBV wiki page but I look at it and see it’s much more of a re- write than an edit. The field option explanations are retained in their entirety so a big chunk of the original material is still intact, but I don’t want to piss anybody off by just swooping in and making a massive change.
Despite the advisory of about merciless editing and the article being distributed at will, very little editing occurs and the greater the dissemination, the better.
Although most authors are very “grown up” about others editing their articles, it is best to avoid hurting the feelings of the authors. When in doubt, write a new article. That way you add to the collective wisdom and no feathers have been ruffled.
I see it listed under “FAQ”. It should also be listed in “Supplementary”, just under Pimm’s article, in the “User Manuals” section and in “Supplementary Topics” in the “Users Guide” section for versions 4.0 through 4.1.2 as well.
Very nice addition on LBVForms. Feel free to delete anything in my explanation WIKI-page on LBVF, that might create confusion or make a double for your nice explanation with the pictures.
Finaly Rod’s addition can have it attention, it should have had since it was implemented in OpenEMR!
Thanks both of you for your encouragement and good advice. Love this FOSS community!
I will get on linking the page to the other places fsgl recommended; will also fine tune the pic size and text formatting a little. Pieter, I don’t think anything needs to be deleted, since your article is where I got most all of my facts in the first place. As fsgl implied above about duplication of materials, the more different ways something is stated the more different people it is accessible to.
I hope to get another article posted before school starts in a month and I won’t have much free time at all. See you all around the forums!
when creating First group third field you insert a picture of the Group and only two fields, eighter move the picture upwards or replace it with a picture showing three fields.
Are you sure we should not delete the most part of my initial WIKI on LBVF’s it seems at some places a bit too much of repeat.
A picture shows much more than many words.
Tnx also for Re: Label/ Data Col values explanation.
(I changed “from” into “form”… once, nothing else to do! Great work, again)
I see the picture you mention. It ‘’‘was’’’ supposed to be in field #2; will move it up- thanks for catching that and also the typo.
As far as deleting most of your LBV page, I get what you’re saying but you seem to have a good grasp of the technical aspect of LBV forms. I gather from the forum posts that plenty of users out there would be able to use more advanced materials. Maybe you could replace some of your fundamentals with some deeper knowledge? I know I’d like to learn that stuff myself. Just a thought,
Can you be more specific? Except for an empty line, you are far ahead of my knowledge. I still work with trial and error.
But we might have to make some real life examples on why the LBVF’s are such a nice extra for OpenEMR. I am a general physician and all I use is in OpenEMR as is. But Specialist like Ophthalmology and Psychiatry migh want their own specialist forms. We could include them with the help of the Specialists and other Developers.
Hi Pimm, you must be a morning person. Here in the States, over the Labor Day weekend, all the young folks are “sleeping in” (still in bed because they don’t have to go to work).
The Layout Based Visit form can be “wilful”. It does not always behave the way we want. That is why trial and error is part of the tool box. Because of this fact and the needs of the specialties are so diverse, it is better to provide basic information and leave the rest to the users. With the new forum format, it is rare that user problems are not addressed in a timely fashion (if there are solutions).
For uniformity of the appearance of a listing of Wiki articles, the internal link is used. Just in case you are unaware of the location of the pipe symbol, it is on the same key as the back slash. I had a very difficult time finding it initially because it looks like an elongated colon symbol on my keyboard.
Jit Chawla did a nice video on the same topic here which you may consider incorporating. Pimm had suggested beefing up the Custom Button part of the video.
Thanks for the link to the video, it was helpful. Chawla did mention something in passing that I hadn’t come across elsewhere, and he didn’t expand upon. That was writing in the field description, “context=subjective”. Does that have any function besides set the text for the field’s tool tip?
As for the magnum opus, yes, there’s a lot of material there when details and screenshots are included. But I am trying to moderate my habitual verbosity.
The “Add Custom Button” function does get more mention in Part 3. Should be able to post it all tomorrow-ish, outside world permitting.
Somewhere in the discussion the Description was nominated for Tooltip. Knowing that, it worked as such for most of my fields.
Making the Title of a text-field empty, the Description becomes the Label.
On other occasion I got the impression Description worked more or less as a the translation for the Title.
Having made this remark I will investigate and see what is true and what is fiction for the Text Field Title and Description. If someone knows the correct answer please feel free to post it here.
contextName=Subjective Where do I find some more information on this option of Description field.
Why do you want to add a button like Space, Comma, Questionmark if these are readily available on the key board. And if my observation is correct, what could be a better usage for the buttons in NationNotes?
Hmm. I just now made an LBV leaving the label blank and when I went to save it got an error saying it can’t be blank. Also left the ID blank, same error. Left the description and the List blank (it’s a Textarea data type) and it accepted that without argument.
OpenEMR is full of surprises! First time use any kind of name or character in the Title field and Save. Next time after Save, you can make it empty and save again.
The only reference I’ve seen to making description be “context=subjective” is in Chawla’s video. And as far as pre- programming custom buttons with keyboard characters, all I can think is that some peoples’ thought processes are REALLY different than mine.
