Check to ensure you haven’t changed your setting for themes in top right user name dropdown Settings.
That overrides main theme setting.
Hi @htuck , would love to contribute to the documentation. I am 70years old (honestly!) I have been in the IT industry since 1976 starting with IBM mainframe and assembler360. I am freelancer for many areas of IT practices. Currently, i the business solution consultant./architect for a medical insurance claim audit and processing company.
Still coding my age and enjoying it too. Conversant in JS, Vuejs, Quasar, PHP, Codeigniter, MySQL, Oracle, MSSQL etc. Did a lot in Espocrm open source software. We have a full blown CRM running many different functional areas. The latest being COVID-19 patient monitoring for corporate clients. Working on integrating Quasar into Codeigniter 4.
Love to do documentation of features with working examples and models if given all the supporting information. Especially on howtos. I notice there is a lot of work to be done OpenEMR wifi.
Yes, appreciate your pointers on documentation. I love to take a mess and turn it into a monument. That goes for corporate IT restructure, Business Process Engineering and IT Standards.
Hi @kmendis ,
Good to hear from you. Guess you are in the same boat as I am. Its ok. This comes with open source. Changing the theme will only change background and text color scheme while everything else will remain the same.
If you expecting to change the styles and look-n-feel then it looks like code changes. Unfortunately, there are no theme or template builders.
@sjpadgett , I think what Kumara means is that he expected the UI to change as well. The LibreHealth EHR were doing good as they provided a feature under admin to do that. Would love to see something like that in OpenEMR.
Hi @mdsupport ,
Thank you for utility. Will try it out. I create themes using Pinegrow. Great piece for just USD 9/month. Handles all icons, frameworks like materialize, Tailwind etc easily does BS4 and 5. Includes JS and CSS (great on this one). Tutorials and help are fantastic. Forum users, like OpenEMR and Espocrm, are quick to respond.
Hi @murugappan - good on us for sticking with it-- I’m 68 and have been playing with computers since the Timex- Sinclair 1000, and coding since Commodore 64. I was the oldest graduate in my BS CompSci - Health Informatics class in 2014 and even though my recent coding only extends to VBA, basic html and perl scripting, that gives me just enough background to have a slight clue on what goes on under the hood of OpenEMR’s php. I’m mostly retired and don’t want to put in the extra time in front of a computer to get good at it but it helps me get the logic of the process when I document a workflow.
Here are couple links to other forum posts re: OpenEMR documentation:
Would be happy to answer any questions I can help with; you might want to post them in the ‘V6 Docs Wish List’ thread to keep topics compartmentalized.
Best- Harley
Hi @htuck, actually i started off with Cobol (fantastic that it is still alive) in the banking sector. My early days there was no computer courses, we were trained by each computer company like IBM, NCR, Univac etc. I used “jumper” configure PIBs (plug-in boards). And yeah commodore 64, I used apple IIe clone with CPM card and assembler/basic codes. Hehehe… good old days, mate.
One question for you. I always itch to change and correct errors or outdates immediately as I see them. In Espocrm, we created a parallel wiki which contained documentation updates and howtos. Big question is, can i do that by creating a new section in OpenEMR forum and how do i do that?
I have lots of ideas for a good wiki for OpenEMR.
1 Like
Jerry, Thanks. yes this was the issue.
Hi Murugappan, Yes I am a bit younger than you are! 65 but still practicing and working as a physician in a university set-up and promoting the OpenEMR in Sri Lanka. We have kind of completely modified OpenEMR to suit the average 3-5 minute primary care consultation in our country.
The majority primary care consultations do not have any kind of medical records - paper or computer!
I started coding with Pascal, Visual Basic and bit of PHP/MySql nothing more. Completely out of touch with programming. Most of our programmers work for foreign companies and we cannot afford to pay such high rates…
However we have now converted the V5 of the modified OpenEMR to V6 and all modifications are working!!! this was done by the software people who worked on V 5.
So we are ready to promote V6 !
kmendis
1 Like
Hi @kmendis
We dont believe in the changing the code of the original developers. Instead we suggest and seek their the help to add the codes. Most of the time we create peripheral applications using Vuejs and PHP and reporting tools like Reportico to achieve the same. User are never really bothered on beauty of the UI. Their concern is more usability rather and good guides and training. In many cases, our mobile apps team compensate for the shortfalls.
In the old days, we used a fantastic software called CA Clipper and developed application which used sequential flow. Microsoft killed it. The doctors prefer these. They want the system to tell them what they need to do next and let them focus on their practice.
Oh yeah, VB and Pascal, great programming kits not to mention Fortran as well. Oh well, they are all disappeared after the appearance of Bill Gates. Hehehe…
I want to contribute to OpenEMR in rebuilding the documentation but appear not getting much help how i can change or add to the wiki. Sigh!
1 Like
hi @murugappan ,
If you want a wiki account (so can change/add to wiki)), just email me at brady.g.miller@gmail.com with what username you want on the wiki and then I’ll create an account for you (and email you the credentials).
I am interested in creating a parallel website with documentation and tutorials. My problem is that intermittently I am under the weather. However, I do use openemr and don’t plan to switch EHR moving forward. I will keep working on it.
Hi,
That is a good thing to do. While wiki’s are good but they all perform differently. Now i am struggling with how to use wikimedia. It may be simple but i am doing much and so many tools i am overwhelmed. If you need help late me know and what, will be glad to try.
hi, it’d be better if we worked on our wiki, imo
It would be better to use OpenEMR’s wiki but the existing contents are pretty messed-up (sorry, in place of better word), too many broken links and outdated documents. Many time my search did not generate good results. In many areas the contents are mixed with current release and previous releases. That, in my opinion, may not not be a good strategy. Really confusing and hard to related to the installed version.
I suggest we create a new wiki and port over current contents. This time by each release and clear sections.
I just don’t see why we need another wiki to better organize. Other things to consider is that additional resources will cost more for hosting and will have to be supported as well. The wiki was recently upgraded to run the latest mediawiki, the software that runs wikipedia, and was placed on a new droplet running ubuntu 20 so it’s in good position to last awhile.
1 Like
So walk through this experiment. How would you organize this new wiki, what documentation would you add, how would you lay out the sections? If you’ve developed a plan of attack for how you would organize the wiki (if you were to start from scratch) then the next stage is to build a migration strategy of migrating any content you find relevant to the new sections/layouts. All that would be work you would have to do anyways if you were to start ‘a new wiki’. That same effort could be applied to the existing wiki.
There is over a decade of information in the old wiki. Quite a bit is out of date, but there is also a lot that is not. It would be a very heavy lift to just get rid of it all. The other thing to consider is that there are still a number of users that are on OpenEMR 4.2 and OpenEMR 5 release that still need and use the old documentation.
I know I have the same tendency to just go into the OpenEMR codebase and start chucking stuff out, but that’s a good way to break things that shouldn’t be broken. Its the downside of working on any large enterprise/‘legacy’ project of how to make changes without breaking the system. Its doable, but it does take effort. Often monumental refactors just blow up as there’s not enough time and resources for people to get it done before life pulls people away. Small incremental changes such as taking one section or one area you need / want done is more doable and will result in actual progress. Others will start to build on your work if you lay a foundation that they can build on. I’ve seen that happen with what I did with the module work, I would argue the same could be done for documentation.
Hi @adunsulag,
Agreed. The main strategy is fine. But the approach needs more refinement and control. Give me until this weekend and i will produce a template for review.
I my opinion, i wouldnt want to fool around with the existing wiki. As you rightly said it a spaghetti. Trying to make sense from that may end up into a life long task (hehehe… i know I may be over reacting). Proposing a sort of compromising solution to what we intend and what @stephenwaite said earlier.
My proposal is this:
(1) We continue existing wiki
(2) We create another fresh wiki (still under openemr community)
(3) Create a “GuideBook” for each release (lets start with version 6) with the template (to be agreed)
(4) Then pull each item from existing wiki, review and if still applicable repost in Guidebook under appropriate sections. Also the post should contain description, howto with screenshots and examples (see example below). This may be a lot of work but with a group volunteers we can do it.
