Project: Improvement of the setup for LibreHealth EHR


(mua laurent) #1

@tony , @pri2si17, @teryhill, @aethelwulffe Here ,the thread for discussions on my project: Improvement of the setup for LibreHealth EHR.

Rooms are open for all sorts of ideas

-Mentors @pri2si17 , @tony

(mua laurent) #2

Project Overview can be found here : Setup Improvement EHR

(Terry Hill) #3

Can you list the major points of your project here? It will be easier for us older folks to follow. :sunglasses:

(Michael Downey) #4

+1 to not using Google Docs.

@mua_rachmann if you want, you can make the top post in this topic a “wiki” post" (use the post options menu) so you can add all of your content from the google doc here.

(mua laurent) #5

@teryhill , @tony , @pri2si17, @aethelwulffe Here is the rundown of my project and the major points my project will address

In summary this is all about improving the setup for LibreHealth. This procedure will entail

  1. Creating and Designing a new UI for the setup procedure

  2. Offer a two way flow of the setup (using next and previous buttons).

  3. Correct versioning of the system until the extension for php 7.1 is totally merged (which is avoided for now) but i see this could be included.

  4. Upgrade server system’s dependencies if not optimal for the LibreHealth EHR environment.

  5. Initialization of important parameters such as email , clinic name , default theme , etc upon a successful install.

  6. A rapid walkdown tutorial on basic things the software does (in the form of images/sliders) of course there will be a skip button if the user wants to ignore this

This project is primarily aimed not only at producing an eye catching setup but at producing a setup environment that is optimal for LibreHealth EHR.

(Priyanshu Sinha) #6

@mua_rachmann I like the breakdown, but I would suggest one thing to you. IMO, you should first focus on functionality, regardless of UI (an okay UI will work in initial stages). Once you have rigorously tested your functionality, then work on UI. I think if we have a fully functional code, that can be adapted to UI later on.

Also I would like if you develop this as a standalone module. Opinion of @teryhill @aethelwulffe and @tony are much appreciated. :slight_smile:

(mua laurent) #7

Yeah! @pri2si17, the implementation will be done as a separate module found in the modules/setup dir as suggested by @aethelwulffe earlier.

(Tony McCormick) #8

@mua_rachmann - looks good to me. The core functions of the setup should have the ability to be run from an command line script. Then add UI. The current core is the Installer.class.php

There is an example in OpenEMR that might be useful to look at (not use, just get an idea or two)

(mua laurent) #9

@pri2si17, @tony, @teryhill the coding phase has begun and here is what i have started and plan to do.

  • Created a modules/setup directory (still doubting if i should put the installer class i am about to write here or leave it in the library folders)

  • I plan on creating a wizard class that will take care of the pages for the setup flow

  • Plan on using composer for dependency management.

Let me know your thoughts please

(Priyanshu Sinha) #10

@mua_rachmann some comments :

  1. Is your installer class is completely independent of rest of the code base? If yes, then move it from library directory, or else keep it there.

  2. I think composer is good to use for dependency management. I am in favor of using it. Let @tony @teryhill have their thoughts.

(mua laurent) #11

Yeah that’s the case it will be completely independent.

(Tony McCormick) #12

Composer is good with me, we need to make sure that how it’s used is well documented. We use it a lot (in my company) for customized versions of the EHR, where the “base” release is a dependency of the custom repo… etc.

(mua laurent) #13

Here is the link to my blog.You can read about my journey into gsoc2018 also

(mua laurent) #14

Implementation of my project proposal is ongoing and can be found here.

All ideas are welcomed. Lets make this a success :grinning: