I recently upgraded to version 5.0.1 (6) of OpenEMR. Since then When a doctor types SOAP notes and click the Save button, the following error message displays on the client side (browser):
“There was an OpenEMR SQL Escaping ERROR of the following string rosENTComment”
The is no error entry in the log files: apache2.log, syserror or mysql.log
This problem was not occurring with 5.0.0. The SOAP interface was customized many years (2013) ago but never experienced this issue until the latest version upgrade. The customized SOAP and EVAL interfaces have gone through many versions upgrades without any problem until now.
Any assistance will be greatly appreciated as the doctors cannot use the software. The only recourse is to downgrade to the previous version if this problem is unresolvable - but I want that to be the last option.
Below is the table structure of the customized soap table:
CREATE TABLE form_psych_soap
(
id
BIGINT(20) NOT NULL AUTO_INCREMENT,
date
DATETIME NULL DEFAULT NULL,
pid
BIGINT(20) NULL DEFAULT ‘0’,
user
VARCHAR(255) NULL DEFAULT NULL,
groupname
VARCHAR(255) NULL DEFAULT NULL,
authorized
TINYINT(4) NULL DEFAULT ‘0’,
activity
TINYINT(4) NULL DEFAULT ‘0’,
subjective
TEXT NULL,
objective
TEXT NULL,
Axis_I
TEXT NULL,
Axis_II
TEXT NULL,
Axis_III
TEXT NULL,
Axis_IV
TEXT NULL,
Axis_V
TEXT NULL,
plan
TEXT NULL,
Medications
TEXT NULL,
Return_Visit
DATETIME NULL DEFAULT NULL,
start_time
VARCHAR(5) NULL DEFAULT NULL,
end_time
VARCHAR(5) NULL DEFAULT NULL,
supervising
VARCHAR(255) NULL DEFAULT NULL,
supervisingSign
VARCHAR(255) NULL DEFAULT NULL,
attending
VARCHAR(255) NULL DEFAULT NULL,
attendingSign
VARCHAR(255) NULL DEFAULT NULL,
patientPresent
TINYINT(1) NULL DEFAULT ‘0’,
familyPresent
TINYINT(1) NULL DEFAULT ‘0’,
otherPresent
TINYINT(1) NULL DEFAULT ‘0’,
otherComment
VARCHAR(255) NULL DEFAULT NULL,
problem
TEXT NULL,
symptoms
TEXT NULL,
pastHistory
TEXT NULL,
rosCons
TINYINT(1) NULL DEFAULT ‘0’,
rosConsComment
VARCHAR(255) NULL DEFAULT NULL,
rosEyes
TINYINT(1) NULL DEFAULT ‘0’,
rosEyesComment
VARCHAR(255) NULL DEFAULT NULL,
rosENT
TINYINT(1) NULL DEFAULT ‘0’,
rosEntComment
VARCHAR(255) NULL DEFAULT NULL,
rosCardio
TINYINT(1) NULL DEFAULT ‘0’,
rosCardioComment
VARCHAR(255) NULL DEFAULT NULL,
rosResp
TINYINT(1) NULL DEFAULT ‘0’,
rosRespComment
VARCHAR(255) NULL DEFAULT NULL,
rosGast
TINYINT(1) NULL DEFAULT ‘0’,
rosGastComment
VARCHAR(255) NULL DEFAULT NULL,
rosGenit
TINYINT(1) NULL DEFAULT ‘0’,
rosGenitComment
VARCHAR(255) NULL DEFAULT NULL,
rosMusc
TINYINT(1) NULL DEFAULT ‘0’,
rosMuscComment
VARCHAR(255) NULL DEFAULT NULL,
rosInteg
TINYINT(1) NULL DEFAULT ‘0’,
rosIntegComment
VARCHAR(255) NULL DEFAULT NULL,
rosNeuro
TINYINT(1) NULL DEFAULT ‘0’,
rosNeuroComment
VARCHAR(255) NULL DEFAULT NULL,
rosEndo
TINYINT(1) NULL DEFAULT ‘0’,
rosEndoComment
VARCHAR(255) NULL DEFAULT NULL,
rosHemLym
TINYINT(1) NULL DEFAULT ‘0’,
rosHemLymComment
VARCHAR(255) NULL DEFAULT NULL,
rosAllerg
TINYINT(1) NULL DEFAULT ‘0’,
rosAllergComment
VARCHAR(255) NULL DEFAULT NULL,
medicalRecords
TEXT NULL,
pcProblem
TINYINT(1) NULL DEFAULT ‘0’,
pcStatus
TINYINT(1) NULL DEFAULT ‘0’,
pcStable
TINYINT(1) NULL DEFAULT ‘0’,
pcIMR
TINYINT(1) NULL DEFAULT ‘0’,
pcComplications
TINYINT(1) NULL DEFAULT ‘0’,
pcIMPC
TINYINT(1) NULL DEFAULT ‘0’,
pcNotes
TEXT NULL,
labs
TEXT NULL,
educationA
TINYINT(1) NULL DEFAULT ‘0’,
educationB
TINYINT(1) NULL DEFAULT ‘0’,
suicidality
TINYINT(4) NOT NULL DEFAULT ‘0’,
safetyPlanAction
TEXT NULL,
homicidality
TINYINT(4) NULL DEFAULT NULL,
homicidalitySafetyPlanAction
TEXT NULL,
PRIMARY KEY (id
)
)
COLLATE=‘utf8_general_ci’
ENGINE=InnoDB
AUTO_INCREMENT=156
;
Bisi