I found the problem, but I don't understand it. In the original I
referenced 2 measurements:
oscarDB=m$BMI#value
and
oscarDB=m$BMI#dateObserved
They were placed at the end of input lines immediately followed by an angle
bracket so:
oscarDB=m$BMI#value>
and
oscarDB=m$BMI#dateObserved>
I added a space and a slash and changed them to
oscarDB=m$BMI#value />
and
oscarDB=m$BMI#dateObserved />
and that seems to have worked - why?
JohnR.
On Wed, Apr 8, 2026 at 6:34 PM John Yap <joh...@gm...> wrote:
> I can attest to the fact the quote eFORM does save in WELL OscarPro
> version of Oscar. Interestingly, the previous version (2020 background) did
> not save. I have not had to use this eFORM before, so I only discovered
> this now.
>
> Luckily I now have a replacement, if needed.
>
> JohnY
>
> On Wed, Apr 8, 2026 at 6:13 PM John Yap <joh...@gm...> wrote:
>
>> The "bottombuttons" used in many of the OpenOSP eFORMS include these
>> lines:
>> <div class="DoNotPrint" id="BottomButtons" style="position:absolute;
>> left:30px; top:1100px; width:780px;">
>> <table>
>> <tr>
>> <td>
>> <input type="hidden" name="newForm" id="newForm" value="True" />
>> Subject: <input name="subject" size="40" type="text"> <br>
>> <input value="Submit" name="SubmitButton" id="SubmitButton" type="submit"
>> onclick="releaseDirtyFlag();setFlag();" />
>> <input value="Reset" name="ResetButton" id="ResetButton" type="reset" />
>> <input value="Print" name="PrintButton" id="PrintButton" type="button"
>> onclick="formPrint();" />
>> <input value="Print & Submit" name="PrintSubmitButton" id=
>> "PrintSubmitButton" type="button" onclick="formPrint();releaseDirtyFlag();
>> setFlag(); setTimeout('SubmitButton.click()',2000);">
>> </td>
>> </tr>
>> </table>
>> The setTimeout feature was needed to allow functions preceding this to be
>> completed, before the entire eFORM shut down prematurely. All of this was
>> done to save one click and allow for a Print & Submit button. Several years
>> ago, this issue came to a head as more complex functions required even
>> longer delay to allow for completing tasks before submit shutdown. It was a
>> bit of guesswork as to how much time was needed. I recall using up to 5000
>> ms for the longer eFORMS.
>>
>> Then some of us (me and others) concluded that we should go back to the
>> original separate submit and print buttons. So all of my eFORMS have this
>> format:
>> <table>
>> <tr>
>> <td style="background: #e5f2ff">
>> <input type="hidden" id="newForm" name="newForm" value="True" />
>> Subject: <input name="subject" id="subject" size="40" type="text" />
>> <input value="Reset" name="ResetButton" id="ResetButton" type="reset"
>> style="color: red" onclick="history.go(0);" />
>> <input value="Print" name="PrintButton" id="PrintButton" type="button"
>> style="color: green" onclick="printLetter();" />
>> <input value="Submit" name="SubmitButton" id="SubmitButton" type="submit"
>> onclick="submission();" />
>> </td>
>> </tr>
>> </table>
>>
>>
>>
>> Which requires additional scripts:
>>
>> /****************************
>> Print and submit/save functions
>> ****************************/
>> function printLetter() {
>> // Save reminder; allows for validity testing
>> document.getElementById("ResetButton").style.color = "black";
>> document.getElementById("SubmitButton").classList.toggle("attn");
>> document.getElementById("SubmitButton").style.border = "2px solid red";
>> // alert("eFORM has NOT been submitted. If needed, cancel print and
>> complete required fields. Ensure you click SUBMIT after print.");
>> window.print();
>> }
>>
>> function submission() {
>> // requires type="submit" in submit button input to allow for validity
>> testing
>> setFlag();
>> saveSig();
>> releaseDirtyFlag();
>> }
>>
>> And it is here where we take care of other business such as saving
>> signatures, noting first save vs subsequent save (setFlag), etc. I'm not a
>> big fan of the "alert" so I've commented it out. It saves me a click where
>> it doesn't affect the form submission.
>>
>> It also allows for the attention seeking submit button to remind one to
>> SAVE (submit) the eForm rather than force-closing it.
>>
>> I wonder if that is the issue with some versions of OPEN?
>>
>> JohnY
>>
>> On Wed, Apr 8, 2026 at 4:13 PM John Robertson <
>> joh...@gm...> wrote:
>>
>>> I am having trouble reconciling some eForm behaviour. The eform in
>>> question is found here:
>>>
>>>
>>> https://oscargalaxy.org/download/outpatient-fetal-monitoring-referral-fraser-health-july-2020/
>>>
>>> The problem is that clicking submit does not save the eForm on some
>>> installations of Open OPS OSCAR, while on other installations it does
>>>
>>> This form works as it is supposed to on my server. However, when I try
>>> to use it on a different server (still using the same settings on my
>>> laptop) it will not save to the patient's chart when I click save.
>>>
>>> Any thoughts?
>>>
>>> JohnR.
>>>
>>> --
>>> Therefore, since we are surrounded by such a great cloud of witnesses,
>>> let us throw off everything that hinders and the sin that so easily
>>> entangles, and let us run with perseverance the race marked out for us. Heb
>>> 12:1
>>> _______________________________________________
>>> OSCARmcmaster-advanced-users mailing list
>>> OSC...@li...
>>> https://lists.sourceforge.net/lists/listinfo/oscarmcmaster-advanced-users
>>>
>> _______________________________________________
> OSCARmcmaster-advanced-users mailing list
> OSC...@li...
> https://lists.sourceforge.net/lists/listinfo/oscarmcmaster-advanced-users
>
--
Therefore, since we are surrounded by such a great cloud of witnesses, let
us throw off everything that hinders and the sin that so easily entangles,
and let us run with perseverance the race marked out for us. Heb 12:1
|