Active Projects

From OpenEMR Project Wiki

Overview

This is a listing of currently important active projects. This is a place to see what's going on, and also a place to see where help is needed by other developers and testers. These are kind of ordered by how important they are to OpenEMR's future.

Wiki

We have just migrated the wiki to mediawiki. Below describes the active projects in this wiki migration that still need to be completed.

Sara created this that can be used right now:OSMS logoTINY.png --Tony - www.mi-squared.com 20:28, 1 December 2009 (UTC)

This now needs to be configured in the LocalSettings.php file (Link to instructions) (Jason B. needs to do this, since he's the gatekeeper to this file) --Bradymiller 08:09, 3 December 2009 (UTC)

License

Change to GPL. All the FDL stuff needs to be changed to GPL.

Backup

  1. Daily
  2. Ensure also backup the screenshots folder

Jeremy and Jason B. are working on this.

Internationalization

  1. Once we have a verified backup then install/configure the following extensions:
    • Polyglot
      • The Polyglot extension provides automatic redirects based on user language. This allows for multilingual content to be handled more easily on a single wiki. Polyglot also changes the interlanguage links in the sidebar to automatically show available localized versions of each page on the same wiki.
    • LanguageSelector extensions
      • The LanguageSelector extension provides detection of the interface language to use for anonymous visitors, and a menu for selecting the user language on each page, for logged in users as well as anonymous visitors. It also provides an additional tag, <languageselector>, for embedding the selector into wiki pages and system messages.
    • Multilang
      • Multilang is a multi language extension for MediaWiki using <multilang> tag for selective text display depending on user language settings. It is used specifically for templates only since the above extensions won't work on templates.
  2. Recruit translators

Jason B. and Brady are working on this.

Certification

A very large multi-developer project is currently underway to get CCHIT certifications and is described on the CCHIT Roadmap wiki page.

Internationalization

OpenEMR supports internationalization and multi-language clinics. Most of this are from recent modifications that got released in OpenEMR 3.1.0. Further information on the project can be found on the internationalization configuration and development wiki pages.

CAMOS module internationalization

The CAMOS module is a form that can be activated in OpenEMR. It does not yet support internationalization. Current plans are the following:

  1. Primary author of module to commit most updated CAMOS code
  2. Change the escape() function call to encodeURIComponent() in javascript ajax call (DONE 12/01/2009 -Brady)
  3. While here will convert all magic quotes checks to openemr/library/formdata.inc.php function
  4. Also translate button labels and messages

Here are the bug tracker link and the forum thread associated with this.

Brady is planning to complete this at some point

Date formatting

Still work to do in order to support date formats across multiple languages. Here's the forum thread discussing this.

Awaiting a Analyzer to figure out a good plan for this.

Translation database maintenance/improvement

We currently have a stable collaborative system in place to allow translation of any language. The translations are entered into a OpenEMR Translation Google Doc Spreadsheet. These instructions and scripts (README files describes the pipeline in detail) then allows conversions of the translation spreadsheet to mysql tables and allow detection and insertion of new english constants into the translation spreadsheet.

A new set of official translation tables are created approximately every 1-6 weeks depending on where we are in the release cycle.

Brady is maintaining this.

Calendar

Multi-facility bugs

Description of bugs:

  1. Things work great with one facility
  2. With two facility the bugs appear (different bugs happen with the $GLOBALS['restrictuserfacility'] turned off(default) and on)
  3. When $GLOBALS['restrict_use\r_facility'] is turned off get following behavior. In essence the calendar only shows what is set as 'default facility' in the users settings. If you choose the facility then that user won't be available. By choosing all facilities, it will actually show all appointments from all facilities, however the scrollbar display is confusing (shows the top item), and unable to schedule an appt at anything but in the scroll bar; this also screws up what you see when scrolling through new days.
  4. When $GLOBALS['restrict_use\r_facility'] is turned on, then only seems to work right if you place all facilities in the users settings 'Schedule facilities'. Then everything seems to work fine, but there is no option to view all facilities, which seems like should be an option. If you don' t place all facilities in the users 'schedule facilities', then you'll see other appointments at other disallowed facilties like they are on the selected on (not much of a bug since appointments shouldn' be scheduled on disallowed facilities anyways), however can only add to the allowed facility, which is good.

Seems like the bug(s) really stem from three mechanisms:

  1. When choose all facilities, don't then highlight the item below it; highlight them all and that have this supported when click other buttons (moving days or adding appt)
  2. With global restric_user_facility off (default) allow users to be scheduled at all facilities.
  3. With global restric_user_facility on give option to show all facilties in calendar.

Currently linked to this tracker item and this forum thread.

Awaiting a Developer to fix this bug.

Recurring appointment bugs

This problem() is discussed in this forum thread and this forum thread.

Awaiting a Tester to further document this bug behavior and make a bug report in tracker with this behavior.

General code base improvements

Clean up magic quotes, prevent sql-injection, and prepare for PHP6

Plan to pass all input data through functions in the openemr/library/formdata.inc.php file before inserting into mysql database. This is useful for following reasons:

  1. Will centralize input validation
  2. Will centralize sql-injection blocking
  3. Fix the escaping bugs(magic quotes) that are seen throughout OpenEMR when inputting the apostrophe character
  4. Will allow easy migration to php6 (since magic quotes will no longer exist in php6)
  5. Simplify support for other database software


12/01/2009: Committed a cleaner openemr/library/formdata.inc.php to CVS and will include in patch#5 for 3.1.0. Read file for details. --Bradymiller 00:05, 2 December 2009 (UTC)
12/05/2009: Committed an even cleaner openemr/library/formdata.inc.php to CVS and will include in patch#5 for 3.1.0. Read file for details. --Bradymiller 09:08, 5 December 2009 (UTC)


This project will be a lot of work and will involve modifications to a large amount of files. This process is currently happening slowly as we modify files(example here). However at some point this will likely become a primary multi-developer project as we get closer to the release of php6.

Currently linked to this tracker item and this forum thread.

Configuration

Migrate configuration settings into OpenEMR program

Currently, many of the configuration settings are found in the actual source files. It will be very advantageous to migrate all configurations settings from these files into OpenEMR's mysql database. This would markedly simplify use, customization, upgrading, and patching of OpenEMR.

A proposed plan is the following:

  1. auto-detection of the webroot and webserverroot directories (it seems all other php projects do this, so shouldn't be hard) in the interface/globals.php file, so it doesn't need to be hard-coded.
  2. Create an Administration->Confiugration module to allow editing of the below settings within OpenEMR
  3. Migration of all configuration setting from the following files to above Administration->Configuration Module (ie. mysql database) (then could simply make a database call when need the variable. For example the globals.php file would then simply be a huge sql query to collect the configuration settings):
    • interface/globals.php
    • includes/config.php
    • custom/clickoptions.txt (place into current admin->lists structure)
    • custom/code_types.inc.php
    • custom/statement.inc.php
    • library/lists.inc
    • library/classes/class.ezpdf.php
    • interface/billing/billing_process.php

Here is the related feature request tracker item.

Awaiting a Developer to take this project on.

User Interface Refactor

  1. Major clean up and refactor of the User Interface experience.
    • Full pass internal cleanup and implementation of more AJAX for modern look and feel
    • Patient centric: using demographics page as the launch pad for all patient focused information
    • Use of modal windows rather that separate browser windows for all popups
    • Model for plugin of customizations that does not require code changes *designed*
    • Reporting look and feel standardization - *Done*
    • API to support clean work flow management
    • etc ...

In Progress at MI-SQUARED

Summary goals on User Interface Refactor

Retrieved from "https://www.open-emr.org/wiki/index.php?title=Active_Projects&oldid=5262"