# Patches added to tracker

**URL:** <https://community.open-emr.org/t/patches-added-to-tracker/7573>\
**Category:** OpenEMR Development\
**Created:** [August 20, 2009, 5:26pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573 "2009-08-20T17:26:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 5:26pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/1 "2009-08-20T17:26:54Z")

</div>

**[ytiddo](https://sourceforge.net/u/ytiddo/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558):

I’m adding the following patches to the tracker for review.

001-interface\_main\_main\_screen.php-make\_default\_top\_pane\_selectable.patch

This patch adds the ability for a user to select what content shows by default in the top pane of openemr. the file to be displayed must be in the interface/main/ directory, and is configured by adding a line in interface/globals.php as follows:

$GLOBALS[‘default\_top\_pane’] = ‘finder/patient\_find.php’;

the default behavior when no configuration has been specified is to load the calendar, as normal.

002-interface\_main\_left\_nav.php-disable\_calendar.patch

this patch disables calendar related entries on the collapsable menu on the left hand side when calendars have been disabled in interface/globals.php, by adding the following line:

$GLOBALS[‘disable\_calendar’] = true;

by default, the calendar links are left alone.

003-interface\_main\_left\_nav.php-disable\_chart\_tracker\_immunizations\_and\_prescriptions.patch

this patch disables the chart tracker, prescriptions, and immunization related links in the left hand navigation menu when the following configuration options are added to interface/globals.php:

$GLOBALS[‘disable\_chart\_tracker’] = true;  
$GLOBALS[‘disable\_immunizations’] = true;  
$GLOBALS[‘disable\_prescriptions’] = true;

by default, the entries are displayed unless the previous lines have been added.

04-coding.php-disable\_prescriptions.patch

this patch disables prescriptions in the coding page, when the following  
line is added to interface/globals.php:

$GLOBALS[‘disable\_prescriptions’] = true;

by default, the prescription related entries are visible, unless the  
previous line has been added.

005-interface\_patient\_file\_summary\_demographics.php-disable\_calendar.patch

this patch disables links to the calendar in the demographics summary page, when the following line is added to interface/globals.php:

$GLOBALS[‘disable\_calendar’] = true;

without that line, links to the calendar in the demographics summary page show up as normal.

007-interface\_main\_finder\_patient\_find.php-create\_simple\_find\_form.patch

this patch adds a simple find form, that i use to replace the default calendar in the top pane. it requires only the configuration in the make\_default\_top\_pane\_selectable patch, and is based on an old version of the search function in the left\_nav.php, before tony added more features to it.

015-interface\_main\_left\_nav.php-disable\_calendar.patch

this is more code to disable the calendar related links in the left navigation bar when the following line is added to interface/globals.php:

$GLOBALS[‘disable\_calendar’] = true;

by default, the links are still visible.

020-interface\_patient\_file\_summary\_stats.php-disable\_prescriptions\_and\_immunizations.patch

this patch disables prescription and immunization links on the patient stats page, when the following configuration options are added to interface/globals.php:

$GLOBALS[‘disable\_immunizations’] = true;  
$GLOBALS[‘disable\_prescriptions’] = true;

without those lines, the links show up as normal.

I have more patches, but lets get started on this ‘new’(to me) integration procedure before diving into more controversial patches.

(for the record, in my first disable\_calendar patch, i remove ippf\_specific, and add disable\_calendar in its place. I have talked with someone from the IPPF, and they were fine with me doing this)

Flame On. 😃

Justin Doiel

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 6:01pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/2 "2009-08-20T18:01:57Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/643d):

hey,

For the future, I’d submit patches that are related, as one patch (for example, all disable calendar stuff in one patch then can also include the globals.php switch too)

This then makes it very easy for us to test it.

See this link on creating patch across multiple files:  
[http://stephenjungels.com/jungels.net/articles/diff-patch-ten-minutes.html](http://stephenjungels.com/jungels.net/articles/diff-patch-ten-minutes.html)

Since other users have asked to have the option of disabling these things, I am inclined to commit the patches to the development tip (after testing them, of course).

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 8:36pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/3 "2009-08-20T20:36:56Z")

</div>

**[jwallace00](https://sourceforge.net/u/jwallace00/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/9f86):

I just submitted patch ids 2841376 and 2841380.&nbsp; I submitted them before I saw the note, brady.&nbsp; These work together to satisfy the Confidentiality Notice portion for CCHIT Certification.&nbsp; I didn’t see a way to submit multiple attachments to the same patch.&nbsp; 2841376 is a diff patch file and will patch interface/login/login.php.&nbsp;&nbsp; 2841380 is a simple sql script to add entries to lang\_constants and lang\_descriptions (specifically for the US locale.)&nbsp;&nbsp;

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 9:12pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/4 "2009-08-20T21:12:25Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/a049):

Jeremy,  
For your patches, in future, create a new developer thread. Then easier to review, give input.

No need to mess with the translation tables; we have a script that picks up anything enclosed by xl() which we run intermittently to collect new constants. I would recommend just placing the entire english message (surrounded by xl() ) in interface/login/login.php . Then no need for the sql insert script.

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 10:58pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/5 "2009-08-20T22:58:40Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/cdb4):

Justin,

Committed following stuff to developer tip (also placed the globals in globals.php and set to false by default):  
002-interface\_main\_left\_nav.php-disable\_calendar.patch  
003-interface\_main\_left\_nav.php-disable\_chart\_tracker\_immunizations\_and\_prescriptions.patch  
005-interface\_patient\_file\_summary\_demographics.php-disable\_calendar.patch  
015-interface\_main\_left\_nav.php-disable\_calendar.patch  
020-interface\_patient\_file\_summary\_stats.php-disable\_prescriptions\_and\_immunizations.patch  
04-coding.php-disable\_prescriptions.patch

openemr/interface/main/left\_nav.php:  
line 792:  
!$GLOBALS[‘disable\_calendar’] && !$GLOBALS[‘ippf\_specific’]  
line 804:  
$GLOBALS[‘ippf\_specific’] && !$GLOBALS[‘disable\_calendar’]

openemr/interface/patient\_file/summary/stats.php  
!$GLOBALS[‘disable\_immunizations’] && !$GLOBALS[‘weight\_loss\_clinic’]

I made these changes to ensure weight\_clinic and ippf stuff kept same behavior.

Last two patches are next; since we can now disable the calendar, it makes sense that we should be able to set the default top window.

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 20, 2009, 11:37pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/6 "2009-08-20T23:37:37Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Thursday, August 20, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/3920):

Justin,

committed following patch to development tip:  
001-interface\_main\_main\_screen.php-make\_default\_top\_pane\_selectable.patch

and added following to globals.php in development tip:  
// Option to set the top default window. By default, it is set  
// to the calendar screen. The starting directory is  
// interface/main/ , hence:  
//&nbsp;&nbsp;&nbsp; The calendar screen is ‘main\_info.php’ .  
//&nbsp;&nbsp;&nbsp; The patient search/add screen is ‘…/new/new.php’ .  
$GLOBALS[‘default\_top\_pane’] = ‘main\_info.php’;

Didn’t see reason why to add the new search window. Why not just let users go to …/new/new.php instead, which also has a search mechanism (then no need to support a new search window)?

-brady

---

<div class="post-metadata">

**Author:** ![system](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/b/bb9e4e8ae2ea7faac2e952fd9e38a3ce03aac403.png) [@system](https://community.open-emr.org/u/system)\
**Post date:** [August 21, 2009, 3:57pm UTC](https://community.open-emr.org/t/patches-added-to-tracker/7573/7 "2009-08-21T15:57:25Z")

</div>

**[bradymiller](https://sourceforge.net/u/bradymiller/)** wrote on [Friday, August 21, 2009](https://sourceforge.net/p/openemr/discussion/202506/thread/e860a0e9/#3558/6189):

Justin and Jeremy,

Also forgot mention; thanks for giving the patches to the community. Keep them coming.

-brady
