What is OpenEMR?

What is the quickest way for me to evaluate OpenEMR?

What is FreeB?

What is SQL-Ledger?

What is GACL or php-GACL?

What is OpenEMR's default password?

Why can I not log into the demo?

Are other languages supported?

What are the correct PHP settings (can be found in the php.ini file) ?

Unknown column 'a.pc_aid' in 'on clause'

How do I delete a patient?

---

What is OpenEMR?

OpenEMR is Open Source electronic medical record and medical practice management software.

OpenEMR includes electronic health records, scheduling software, insurance billing, accounting, and fine-grained access controls.


What is the quickest way for me to evaluate OpenEMR?

There are several options:

We host an online demo here at: http://www.oemr.org/demo/openemr The user is "demo" and the password is "pass".

Several online demos are hosted at: http://www.bradymd.com/appliance/demos.html

We also have a configured Virtual Appliance. Further details can be found here: http://www.oemr.org/modules/wiwimod/index.php?page=OpenEmrVirtualMachineThree


What is FreeB?

FreeB is now obsolete. Previous to OpenEMR version 2.9.0, FreeB was a separate program that created insurance claims. However, in OpenEMR versions 2.9.0 and later the insurance billing engine is included in OpenEMR.


What is SQL-Ledger?

SQL-Ledger is now obsolete. Previous to version 3.0.0, SQL-Ledger was a separate accounting program to manage accounts receivable. However, in OpenEMR versions 3.0.0 and later the management of accounts receivables is included in OpenEMR.


What is GACL or php-GACL?

GACL or gacl is a short cut form for phpGACL. This is an acronym meaning Generic Access Control Lists. It allows fine grained control over OpenEMR. As an example, the physician can be permitted to view sensitive patient information, while the receptionist is unable to view this sensitive patient information.

Since OpenEMR version 3.0.0, access controls (php-GACL) is included in OpenEMR, thus requiring no separate installation or configuration. Administration of access controls is performed within OpenEMR in the admin->acl menu.

In OpenEMR versions 2.9.0 and earlier, php-GACL was actually installed separately.



What is OpenEMR's default password?

The default password is 'pass'

Why can I not log into the demo?

The OpenEMR demo site is set up for anonymous access. The username is "demo" and the password is "pass". The username and password used to access oemr.org will not work.

Are other languages supported?

Currently OpenEMR is being translated into several languages. If you have an interest in helping translate OpenEMR into your native language, please let us know. We will be glad to add your language to the list and help get you started on the translation.

Go here to get more details on which languages are supported and/or how to add language support: Language Translation


What are the correct PHP settings (can be found in the php.ini file) ?
We recommend the following PHP setting, which can be set in the php.ini file. If you do modify this file, remember to restart your web server (usually Apache) to apply the new settings.
short_open_tag = On
max_execution_time = 60
max_input_time = 90
memory_limit = 128M
display_errors = Off
log_errors = On
register_globals = Off
post_max_size = 30M
magic_quotes_gpc = On
file_uploads = On
upload_max_filesize = 30M
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT

Unknown column 'a.pc_aid' in 'on clause'

If I remember correctly this has to do with the calendar section and has to do with a quirk in one of the operating systems (most of the posts seem to involve using MySQL 5 on Windows usually XAMPP). The last post that seems to have fixed this was:

"Changing from "FROM $table AS a, $cattable AS b" to "FROM ($table a, $cattable b)" in the file pnuserapi.php did fix the issue. Thanks for the help. It is greatly appreciated. Keep up the good work!!!

We need to know your operating system, operating system version, OEMR version, PHP version, MySQL version.

I'm not sure but I think this may be from using MySQL 5 when OEMR version 2.8.1 (and earlier versions) still requires both MySQL 4+ and PHP 4+. Versions more recent than 2.8.1 can use PHP 5 but are still using MySQL 4+.

Again I quote from the prior conversations:

"This is a SQL 2003 compliance error with MsSQL 5.0 being more strict than 4. Simply change the query in \openemr\interface\main\calendar\ modules\PostCalendar\pnuserapi.php

to FROM $table AS a, $cattable AS b

to FROM ($table a, $cattable b)

this worked for me"

jkoch

A lot of the solutions involve simply reverting MySQL 5 to MySQL 4.

How do I delete a patient?

How do I delete a patient from the database.

My staff unintentionally added a patient to the database twice. To make matters worse they have some office visits on one chart number (pid) and some of the office visits on another chart number (pid).

For instance if one patient has two pids: 102 and 677

If you or one you trust with the possible deletion of your entire database want to delete a patient entry, in this case pid=677:

Administration ->

Database reporting ->

patient_data -> (this is the left frame)

SQL (tab on right panel)

I would recommend checking the EMR of patient pid that you want to delete. Generally, if there are two pids for one patient, some eager staff member has already entered data into both records and you should first merge the data into one record.

The most commonly affected tables are:

form_dictation

form_vitals

anything else that starts with form_....

history_data

lists

log

p_notes

Check for tables that you know that your practice uses a lot.

I do this by going into each table and executing the following SQL command:

UPDATE table_name SET pid='102' where pid='677';

repeat this for each table that has data then:

DELETE FROM patient_data WHERE pid=677;

Once you delete pid=677 any data that you may have forgotten will be orphaned in the database. This is not especially harmful but does slow down the database.

If another patient is later assigned pid=677, then any data belonging to pid=102 that was not changed in this way will show up spuriously on the pid=677. Remember: mucking with the database directly in this fashion is dangerous and may cause irreversible loss of data. In the wrong hands, the entire database can be deleted. It is far better to work with the staff not to make this type of error.