Everything you need to know about eForms in OSCAR
click the button to browse the shared eForms database
(see disclaimer below)
E-forms are arguably the most enabling EMR feature for OSCAR users. In simple terms eForms is a module for "plug-ins" in OSCAR to allow users to upload their own bits of code (HTML) to their OSCAR system.
The initial intention was to provide doctors with an elegant do-it-yourself electronic solution to manage the never-ending avalanche of new paper forms coming at them for all directions. Doctors actually spend a large part of their work hours filling in paper forms, such as lab or x-ray requisition forms, referral forms for services for their patients and bureaucratic forms, ranging from special authority coverage forms to handicapped parking permits. E-forms then are the electronic answer to this problem, as they are stored electronically right in the OSCAR server, can be optionally loaded into patient charts and auto-populate with the patient's demographic and some clinical information, from the OSCAR database. Once completed and finalized E-forms can be printed or even electronically faxed (on systems set up for this), and saved on the patient's chart as a record. They can be re-printed again in future if desired.
In the most basic form an eForm is a simple scanned image of a paper form in the background, with electronic HTML form elements superimposed on top of this, that allow the user to import text from the OSCAR database or type their own.
- Click here to learn how to download eForms from this site and plug them into your system. You can also download a PDF tutorial here.
- To access the database of user contributed eForms available for download from this site click here.
- Another very easy way to load new user contributed eForms into your OSCAR system is via the eForm emporium. As of OSCAR v9.12 or newer, you can easily access this by simply clicking the "download eForm" tab in your "manage eForms" window. Keep in mind however that eForms shared via the eForm emporium are, just like the ones posted on this site, contributed by users, provided "as is" (not vetted by OCUS or by the OSCAR developers), and many of them are province or location specific. The UI of the eForm emporium is still in the early stages of development, so it is still just a simple list of available eForms, not sorted by category or form type. If you want to search it, try CTRL+F in your browser.
OSCAR users can easily learn to create basic eForms themselves.
- For some basic instructions on how to use Shelter Lee's amazing eForm generator for OSCAR click here. There is a YouTube clip on using it here. More advanced eForming instructions are here.
- For a more comprehensive tutorial on manual eForm creation (without the eForm generator) click here.
- To manually download Shelter Lee's powerful eForm Generator to use from the desktop outside OSCAR click here. (for older versions of OSCAR - the newer versions come with the eForm generator pre-installed)
- For a comprehensive list of all the available eForm database tags (the bits of code that tell your eForm to fetch specific bits of data from your OSCAR EMR system and plug it into the form) click here.
- For more eForm building resources click here.
- eForms under development and not yet production ready can be found here.
One of the great things about being part of the open source OSCAR community is the ability to share the work you have done, so that others can benefit from this too. It is very rewarding to see your innovations make a difference for others. For this reason there are a number of our members who build a lot of great eForms and share them on this site. At OCUS we would like to encourage our members to embed a statement of authorship and a copy of the disclaimer posted at the bottom of this page into the head of their form (in the markup, as text commented out) when they share it back to the community. We would also recommend that the more complex clinical eForms be protected with a suitable Creative Commons share-alike free software license embedded.
If you have an eForm you would like to share back to the community, please post it to the "advanced user" OSCAR email discussion list for review (you can subscribe here), or send us an email at OscarCanadaUserSociety@gmail.com.
If you come across problems with an eForm you downloaded from this site, please submit a brief bug report, containing a description of your problem along with the URL where you found the form on this site, to the "advanced user" email OSCAR discussion list (you can subscribe here). The "advanced user" discussion list was set up specifically to aid in eForm development and troubleshooting, so as not to overwhelm the regular discussion list with technical eForm related mail traffic. Many of our enthusiastic eForm experts in the community hang out on this list and they are always keen to help debug a wayward eForm.
While eForms are incredibly powerful tools for OSCAR users, there recently has been some concern voiced by a variety of developers and OSCAR support providers about the potential for eForm malfunction and the attendant risks for medical-legal exposure related to such malfunction. Core OSCAR program developers have been concerned about the implications for provincial EMR validation testing and ISO certification. OSCAR support providers have voiced concerns about increases in support calls due to malfunctioning or poorly designed eForms. There have been some calls for central quality control and some kind of control to govern the scope of what OSCAR users may do with eForms.
At OCUS we understand these concerns, but disagree with them. Since we are physicians ourselves we understand that decision support is not decision management. We know that we are ultimately accountable for the the clinical decisions we make for our patients, no matter what happens in the EMR or in plug-in elements of the EMR. This is generally also the position taken by provincial physician colleges. We are still a long way away from seeing an EMR system that can take over patient care from the doctor.
On the other hand the ability to create bits of plug-in functionality ourselves as users, with our OSCAR system as the platform for this, is one of the truly enabling features of this EMR. User created and shared eForms are an example of how the four freedoms of open source software meet the world of electronic medical records in a real-world scenario; our core values in action. To hobble this ability would be to defeat the purpose of OSCAR.
With great power comes great responsibility. Physician OSCAR users understand that.
As is: eForms are shared "as-is" free of charge on a share-alike basis with absolutely no guarantee or warranty.
No Quality Control: We at OCUS do not vet any eForms and do not purport to apply any manner of quality control. We strongly encourage end-users to subject all the eForms loaded on their system to a thorough testing process and quality review themselves, before using them on real live patient charts.
Responsibility: The responsibility for the clinical and medical-legal consequences of any and all eForms, rest with the OSCAR end-users themselves. This applies to both eForms shared by others, and those created by users themselves.
- Attribution: eForms are shared freely among the user community, with attribution to the original author of the eForm.
- Free: eForms so shared may not be bought or sold.
- Provincial validation: eForms are optional and non-essential add-ons, separate from OSCAR, and each with their own license terms. eForms are not part of OSCARs core program functionality and code base. For this reason eForms are not subject to provincial validation testing and conformance criteria. eForms are also not subject to the ISO production process for OSCAR.
Text block version of DISCLAIMER (for pasting into eForm markup):
E-FORM DISCLAIMER: As is: eForms are shared as-is, free of charge on a share-alike basis with absolutely no guarantee or warranty. No Quality Control: The author does not vet any eForms and does not purport to apply any manner of quality control. Responsibility: The responsibility for the clinical and medical-legal consequences of any and all eForms, rest with the clinical OSCAR end-users themselves, not with the author of the eForm. This applies to both eForms shared by others, and those created by users themselves. Attribution: eForms are shared freely among the user community, with attribution to the original author of the eForm. Free: eForms so shared may not be sold or purchased. Provincial validation: eForms are optional and non-essential add-ons, separate from OSCAR, and with their own license terms. eForms are not part of the OSCAR core program functionality and code base. For this reason eForms are not subject to provincial validation testing and conformance criteria. eForms are also not subject to the ISO production process for OSCAR.