profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/mdsupport/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

mdsupport/openemr 2

Mirror of official OpenEMR Sourceforge repository

mdsupport/app-flutter-openemr 0

app-flutter-openemr

mdsupport/bootstrap 0

The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

mdsupport/google-apps-script-samples 0

Sample code for Google Apps Script, a cloud-based scripting service for Google Apps

mdsupport/hybridauth 0

Open source social sign on PHP Library. HybridAuth goal is to act as an abstract api between your application and various social apis and identities providers such as Facebook, Twitter and Google.

mdsupport/patternfly-bootstrap-treeview 0

Tree View for Twitter Bootstrap -

mdsupport/php-bootstrap-form 0

Continuation of php-form-builder-class (PFBC) development as a fork. Docs (http://smarttechdo.com/~avb/pfbc/)

mdsupport/qTip2 0

qTip2 - Pretty powerful tooltips

issue commentopenemr/openemr

ONC CQM Phase two

@sjpadgett Sounds like these would be mainly server processes (limited ui). If there is ancillary stuff that has some flexibility in delivery schedule we could pitch in as well. Just don't want to get in critical path for ONC train.

sjpadgett

comment created time in 20 hours

issue commentopenemr/openemr

Main tab bar is not mobile-friendly

@sunsetsystems Current approach has layout row as "inline form" layout. That is hard for the flex engine to handle with multiple rows. @tywrenn may have some ideas but you may want to switch vertical layout (field below label) otherwise the engine tries to keep label with the field but not always. And that becomes frustrating for the users.

Another consideration would be Bootstrap 5 implements floating labels, that eliminate chance of labels straying from the control.

sunsetsystems

comment created time in 6 days

issue commentopenemr/openemr

Main tab bar is not mobile-friendly

@sunsetsystems Just a simple feedback from past 5-6 years of support. Tab in jquery-ui world to Nav in bootstrap world is relatively easy migration if it is driven by database tables. In fact we even had some javascript reformatter that redid current screen layout. However that only addresses overall navigation. The content / forms that work well on desktop simply cannot be reformatted to work even a small tablet and definitely not on 6" phone screen. Our response to that problem was "App" feature added to login. That lets mobile users have all things they need for their role and suitable for their device form factor. As an example mobile user will never fully use an text area for data entry. But they can have 10s of checkboxes that builds a nice list in that text area. Our main problem with Layouts is standard library functions do not follow model and view principle. Hope as you work on LBFs you make it layered where data layer builds an field object that can be processed in very few common view routines. That will make future bootstrap 4 to bootstrap 5 or 6 migration trivial.

sunsetsystems

comment created time in 6 days

issue closedopenemr/openemr

Access the hidden layout export / backup feature

Few years ago I think @sunsetsystems had brought in feature to backup layouts and / or lists.

Current code has taken away entry for that feature although the code is there as seen if you POST form_export value to that script.

closed time in 15 days

mdsupport

issue commentopenemr/openemr

Access the hidden layout export / backup feature

My bad for not checking the globals! Thx @sjpadgett.

mdsupport

comment created time in 15 days

issue openedopenemr/openemr

Access the hidden layout export / backup feature

Few years ago I think @sunsetsystems had brought in feature to backup layouts and / or lists.

Current code has taken away entry for that feature although the code is there as seen if you POST form_export value to that script.

created time in 15 days

issue commentopenemr/openemr

ONC/MU3 eCQM Reporting

@sjpadgett eCQM is key element for primary care practices that sign up for CMS's Primary Care First payment model. Since the incentives are tied to these measurements, I hope all US primary care practices should be very interested. A few lines about how you envision this to work would be greatly appreciated.

sjpadgett

comment created time in 15 days

issue openedopenemr/openemr

Clinical Rule: Interval choices repeated on Add/Edit screen

Maybe the select build function needs 14th parameter to take care of this :)

image

created time in 16 days

delete branch mdsupport/openemr

delete branch : delete_userxxx

delete time in 17 days

issue closedopenemr/openemr

Eliminate all user* fields in new installations

Since the layouts have permitted addition (and problematically the deletion) of fields for a while, the user* fields are no longer useful. To make matters worse, they increase max size of the record computed by db engines without any apparent benefit and cause schema issues. These generic fields are purely bad practice to encourage and propagate in future installations.

Eliminating these from existing installations will be a challenge that should be left to respective admins. Did notice use by IPPF and @ophthal code. If project have to have these in current form, they should be included as sql patches for those specific modules but not for installations that are not IPPF or ophthalmologist specialty - guessing that would be 99%.

closed time in 17 days

mdsupport

issue commentopenemr/openemr

Eliminate all user* fields in new installations

For some reason project brought in eye forms as standard and not as addon with its own sql. That has meant portal and other modules have references to user* fields without any apparent business logic. No idea how @sjpadgett, @adunsulag will handle these fields in external interfaces.

Highly recommend to converting eye forms optional with a db install step and fixing the logic for portal mappings to account for these type of patient_data fields that are added in the field.

Closing the issue until that occurs as merely deleting user* fields for future/new installations will break a standard install.

mdsupport

comment created time in 17 days

create barnchmdsupport/openemr

branch : delete_userxxx

created branch time in 19 days

push eventmdsupport/openemr

Rod Roark

commit sha 7009c308b4050b8ab58b53f402f686a263d777f4

Fixed typo in CSV loader for translations.

view details

Brady Miller

commit sha fb52a8b69a798442cba843f3fe63939bd17d4283

incorporate swagger for api documentation and testing (#4605) Co-authored-by: Stephen Nielson <stephen@nielson.org>

view details

Brady Miller

commit sha 0434d4028422701c79ebb906ba2d68bcb571e7ca

devtools for swagger and api dev and testing (#4611)

view details

stephen waite

commit sha e71a3ff9a299a6a62230547562e837331acd37af

fixes for edihistory, remove jquery ui residuals, replace php each function removed in php8 (#4613) * fixes for edihistory, remove jquery ui residuals * replace deprecated each with foreach #2296

view details

push time in 19 days

PR opened openemr/openemr

Access to document creation error details

Get details about errors generated during new document creation. To maintain current behavior, use of additional parameter is necessary. Recommend updating current logic to display message(s) to user and then remove $incl_errors.

+19 -6

0 comment

1 changed file

pr created time in a month

push eventmdsupport/openemr

mdsupport

commit sha b92e9b2223c4ce1e40f2a7e07b63f60d423161cf

Access to document creation error details Get details about errors generated during new document creation. To maintain current behavior, use of additional parameter is necessary. Recommend updating current logic and remove $incl_errors.

view details

push time in a month

create barnchmdsupport/openemr

branch : doc_err

created branch time in a month

push eventmdsupport/openemr

stephen waite

commit sha dafeee7f0332ad087957b03c3ba0745680165a36

turn accept assign on by default (#4235)

view details

shubham17061999

commit sha c657914c1ee0d45c084c1c0650c24c2f0cdd15e3

Medicationfhir (#4234) * Corrections to MedicationRequest * Changes in FhirMedicationService and PrescriptionService * a * A * Few changes * Resolved Issues in Prescription Service * Changes made in Prescription Service * Small Change Co-authored-by: vishnu yarmaneni <3436873+vishnuyar@users.noreply.github.com>

view details

stephen waite

commit sha b931cfb583b650dafc94c5aa022a13dbde3fc2a2

fix sql query binds (#4238)

view details

Brady Miller

commit sha 6e6672ecf7e27ca3139ee6e307c80d31d5e2c80b

support patient binding in MedicationRequest (#4236)

view details

Brady Miller

commit sha 375b8c5fb33eb5d92114d45b863f25561daf5fb8

update insane dev environment (#4239)

view details

Jerry Padgett

commit sha 2c4a8c1cd0d2bd33fb72e1f4cae0925e611eac6a

database upgrade fix (#4237) * database upgrade fix - add $GLOBALS['ongoing_sql_upgrade'] = true; to status ajax * - fix text templating * - fix CAMOS events conflict with custom text templates - add ICD10 support - stop using body bubbling events for textarea/text templates. * - conflict

view details

stephen waite

commit sha be804ee8f66e53be0938d2b99f04daaa78fffccf

admininstration of codes search additions (#4240) * first add active to search * php8 fix plus style

view details

Sherwin Gaddis

commit sha e2cc157a60966b02c05ec90d21d9931e40096121

This suggested change puts the vitals display into a single column an… (#4174) * This suggested change puts the vitals display into a single column and splits the divs into two columns in the table to make reading the results faster. * Bump PR this may be my last chance to get this in. * Removing conflict * Removing blank space

view details

stephen waite

commit sha db479fc3a768552ff85fcc16e0605d7f06ecdc0c

quick follow up (#4243)

view details

Brady Miller

commit sha f2ebffae0c794f870d84d6961a1dbdafee3acb45

added Gujarati language

view details

Sherwin Gaddis

commit sha f8333e8576c79190aabc6e4438ffc87f98b2e4ae

These are some last minute changes that Weno wants after they have ex… (#4241) * These are some last minute changes that Weno wants after they have extensively tested the integration from the user stand point and meeting all of their requirements for day to day operations. This move the log sync to a background service. Moves the Prescription Log viewer to where a none admin can view it. Those are to two major changes requested for this PR. * Last minute global changes. * This is taken care of in the code and will be unique per clinic. This setting is not needed. Removed * made a couple of changes to the log to check a two day spanned of time for prescriptions that have been entered. * That was a goof of course that what reviews are there to catch.

view details

Brady Miller

commit sha ac477024b48a598e5d6fa46bc35d8eb65c36e401

adjustments to prior commit

view details

stephen waite

commit sha 169e1f6b7cfcb883b809ee4179ab4cd56e2ac105

add vscode to contributing guide (#4244)

view details

Brady Miller

commit sha 84cd98718396e3efc6aa171c972a8e675e221bcf

easy dev documentation updates (#4247)

view details

Brady Miller

commit sha d24c42b492063635cc4a9ed1cb540006b0c38b91

xdebug updates (#4248)

view details

Sherwin Gaddis

commit sha 10b040c0b46bb300ad25caebac39dc309635d097

Fixed function. (#4246) * Removed function. It was not needed. * This will serve better to alert the staff what information that is needed and is missing so they don't have to guess. Better user experience. * Correction to the corrections

view details

Brady Miller

commit sha 7d82bbaa7faf9dcbe5b37c194fa98f9d5093bee3

instructions to use different php versions in easy docker development environments (#4251)

view details

stephen waite

commit sha bc473e67b1a00962e67ff45dee90be0ba0c8c56b

add keyup to modifer entry in fee sheet, consolidate in common.js (#4250) * add keyup to modifer entry in fee sheet, consolidate in common.js * alphabetize setupheader

view details

Brady Miller

commit sha c24ae09c6876df222766a330578ed98950292d4e

xdebug docker development environment setting update (#4252)

view details

Brady Miller

commit sha b09371e0666f6d4c64a2a3151cbd9045a6270960

turn on rest_system_scopes_api in dev docker environments (#4253)

view details

push time in a month

issue commentopenemr/openemr

Eliminate all user* fields in new installations

On a related note, also suggest Eye Exam form should require normal optional form steps starting with DB install of the eye related tables. It should also include document categories that currently need to be deleted by most installations as not relevant.

mdsupport

comment created time in a month

issue openedopenemr/openemr

Eliminate all user* fields in new installations

Since the layouts have permitted addition (and problematically the deletion) of fields for a while, the user* fields are no longer useful. To make matters worse, they increase max size of the record computed by db engines without any apparent benefit and cause schema issues. These generic fields are purely bad practice to encourage and propagate in future installations.

Eliminating these from existing installations will be a challenge that should be left to respective admins. Did notice use by IPPF and @ophthal code. If project have to have these in current form, they should be included as sql patches for those specific modules but not for installations that are not IPPF or ophthalmologist specialty - guessing that would be 99%.

created time in a month

issue closedopenemr/openemr

solar theme menu

Still an issue

_Originally posted by @stephenwaite in https://github.com/openemr/openemr/issues/4163

closed time in a month

mdsupport

issue commentopenemr/openemr

solar theme menu

Sorry @sjpadgett. Ignoring theme related comments from users has become matter of habit over the years. Since themes don't add value to the operations, we have a small common css that supplements native bootstrap theme which gets included at end of the cascade. Anyone having problem with colors is free to use specialized facilities that do this well and then maintain the scss list.

mdsupport

comment created time in a month

issue commentopenemr/openemr

solar theme menus

Just saying the demo should be best foot forward.

stephenwaite

comment created time in a month

issue openedopenemr/openemr

solar theme menu

Still an issue

_Originally posted by @stephenwaite in https://github.com/openemr/openemr/issues/4163

created time in a month

issue commentopenemr/openemr

solar theme menus

If there is no solution for solar theme background color issue, we should at least not make it a default theme for demo. Here is picture - image

stephenwaite

comment created time in a month

issue closedopenemr/openemr

Use of sequences rather than autoincrement

.. it seems like it would be more robust to use a self incrementing id for most of the tables that use this rather than rely on the GenID function. Any folks know of the benefit of using this GenID mechanism over a simply id that counts for a table?

Originally posted by @bradymiller in https://github.com/openemr/openemr/issues/3788#issuecomment-669758698

Not sure if this strange legacy is noticed by anyone looking at database modernization. Databases are really good at keeping track of table row counters. Since encounters, documents and few other tables rely on this mechanism it creates random issues specially when transactions are not used.

Guess this should be part of #3273 as well.

closed time in a month

mdsupport

issue commentopenemr/openemr

Use of sequences rather than autoincrement

Possible fix to ORDataObject is :

  1. Replace the current SHOW COLUMNS by native ADODB calls that return field objects for mySQL databases.
  2. Where the sequences is called, check if any field (typically the primary key) is defined as autoincrement and skip call to get new sequence iff the field is empty. Guessing that the empty field should be dropped from list of columns as well in sql generation.
  3. Examine the value of ORDataObject vs several useful ADODB helper methods rather than keep increasing the cost of maintenance and future development.

ORDataObject is used for many tables from really old code. In addition most sensitive use of sequences is in encounter + forms creation which happens with abundance throughout the code. We have no desire or resources to take on this task. So going to close the issue.

@adunsulag, on a related note re. foreign keys - be aware of the enormity of fixing existing data during the upgrade. Also spotty use of gprelations approach which relies on developers to do the work of db-engine will become redundant - a welcome progress.

mdsupport

comment created time in a month

issue commentopenemr/openemr

List showing duplicates in the display of the list

Since only specific options are repeating it is probably related to SQL left joins being used for translation. Correct SQL will generate the list and then translate. Interesting that it took this long to be noticed. @juggernautsei is leaving no box untested!

juggernautsei

comment created time in a month

issue commentopenemr/openemr

Use of sequences rather than autoincrement

I just wanted to make future devs aware of these unexpected code variations since we assumed a library will implement add, change and delete methods. Combining "add+change" in single code is problematic behavior for such root class. I think ORDataObject comes through Smarty though it does not have any author block. So we find it easier to avoid its use for Add logic.

The reason I brought up this was that I am unsure how changing id to autoincrement will be handled by ORDataObject. It seemed like iterating through all columns using get/set methods for each field. So it could defeat/override the ddl change.

mdsupport

comment created time in 2 months

issue commentopenemr/openemr

Use of sequences rather than autoincrement

On a related note, the ORDataObject model uses REPLACE INTO taking away the option of hard error if two parallel processes got same ID because of lack of locks. So issue like #3788 is probably caused by a errant process that picked up existing ID while inserting a new document. Normally the INSERT error could have stopped the damage. But ORDataObject's persist removes all traces of old document while leaving the orphan physical file, the document category and pnote links untouched. Lot of finger pointing in the front office.

mdsupport

comment created time in 2 months

issue openedopenemr/openemr

Use of sequences rather than autoincrement

.. it seems like it would be more robust to use a self incrementing id for most of the tables that use this rather than rely on the GenID function. Any folks know of the benefit of using this GenID mechanism over a simply id that counts for a table?

Originally posted by @bradymiller in https://github.com/openemr/openemr/issues/3788#issuecomment-669758698

Not sure if this strange legacy is noticed by anyone looking at database modernization. Databases are really good at keeping track of table row counters.

created time in 2 months