Micro Frontends Architecture for OpenMRS

On Slack, hum: https://openmrs.slack.com/archives/CHP5QAE5R/p1563462071102800

Some updates:

  • The microfrontends squad is starting to work on real features and modules that are intended to be used by as many people and distributions as possible. Please reach out if you want to be involved in this. Upcoming features are 1) Landing page after login, 2) patient search, and 3) patient chart/dashboard.
2 Likes

MF SQUAD Meeting 15th August 2019 Agenda Items

  1. Demo of login MF application (https://openmrs-spa.org/openmrs/spa/login). If interested, please see code at https://github.com/openmrs/openmrs-esm-login)

  2. Discussion of Patient Search Design (https://www.figma.com/file/0bNhP3xm4tB7rMwpMZe51n/Search?node-id=0%3A1)

  3. Sprint Planning For Remaining Login Tickets and Patient Search Widget .

  4. Overview of style guide (please take a look as much has been added in past week: https://styleguide.openmrs.org). Code available at (https://github.com/openmrs/openmrs-esm-styleguide)

Squad meeting will take place on zoom https://om.rs/zoommicrofrontend

Thanks @fali for the reminder

Hey Everyone

I just wanted to highlight some of the developments from the MF squad:

  1. In addition to the slack channel that has been created ,A set of wiki pages (as a reminder) have been created for the project can be found here. All meeting minutes and recordings will be captured here as well as on talk.

The current working collaboration conventions are as follows:

  1. Process for Application development:

Initial tickets will be created to define what needs to be done. These can be modified as necessary.

After a PR is done, the creator of the PR will assign it to a squad member within 24 hours. The squad member will then have 1 week to provide feedback or approve the PR.

Dev Side project management will be monitored through the JIRA Board https://issues.openmrs.org/projects/MF/summary

Process for developing the design and approval to start coding:

  1. Trello will be used to monitor design activities , A backlog will be created with the trello. User stories collected in google doc (like appointment UI)

  2. Figma will be used for designing the user interfaces https://www.figma.com/file/0sfnmvaW8yTCHrpDLyzmRz/OpenMRS-Flow-Toolbox

  3. The design is shared on slack channel/ or talk for review and discussion. Once agreed that the design in suitable

  4. The ticket is then moved to JIRA for coding.

  5. User testing on Prototypes? Can be done during design feedback stage.

The Summary of Today’s Squad call :slight_smile:

1. Review designs and finalize on presentations for today.
2.  @joeldenning  , @aojwang , @bistenes to work on creating a  local dev frontend documentation for startup, packaging  into a WAR file
3. New additional Members from Ampath Donald, Jacinta and Enchil
  1. Sprint planning: Tickets will be created and assigned to team members. Aim to have Demo for Main Nav and Patient Search Members are encouraged to PR small amounts of code rather than large batches.

See blogpost from Greg on responsive breakpoints: https://docs.google.com/document/d/1nk1uWd5UxE1DB1SdeNG4HfChXuB9gqXUEvs7uCwiHQ8/edit#heading=h.rbs2o24gvylu

we are currently designing the patient search feature and your feedback is very much appreciated. @Gregory Schmidt is working on the designs in Figma. If you care interested, please send me or Greg a slack message and we will help to get you set up.

We will close this feedback period end of day Monday, Aug. 19th. We hope to have a prototype out by Thursday Aug. 22.

@jdick @gschmidt @fali @joeldenning Please include anything I may have left out.

And by the way, which license are we using for the various pieces of the micro frontends work? One of the products is using the MIT license: https://github.com/openmrs/openmrs-esm-styleguide/blob/master/LICENSE

Do we have a criteria for which license a particular repository is going to use?

Feel free to PR any MF repos to change them to use whichever license OpenMRS prefers.

Do you see any disadvantage of using the same license as the OpenMRS platform? https://github.com/openmrs/openmrs-core/blob/master/LICENSE

Nope, I just didn’t look it up before creating the repos.

Announcement for Today’s call

Dear All,

I wanted to provide an update on the MF Squad.

The squad currently consists of Joel Denning, Fatma Ali (AMPATH), Brandon Isthenes (PIH), Angshuman Sarkar (Bahmni), Antony Ojwang (Palladium/KenyaEMR) and Andrei Stanila (Mekom). Several members from AMPATH (Jacinta, Derrick Rono, Donald Kibet, Eugene Kandie) are also beginning to contribute toward this project.

To date, we have focused on the creation of a login page, patient search, styleguide and an api module to interact with the backend. You can view all repositories on github by searching for “esm” as all MF modules use the naming convention openmrs-esm-[moduleName].

You can view the styleguide here: https://styleguide.openmrs.org/?path=/story/openmrs-styleguide--links-and-buttons

You can view our jira board at: https://issues.openmrs.org/projects/MF/issues/MF-38?filter=allopenissues

The current sprint can be seen here: https://issues.openmrs.org/secure/RapidBoard.jspa?projectKey=MF&rapidView=221

The slack channel is called Microfrontends and all are welcome to join.

Lastly, @gschmidt has been leading design efforts. He is using Figma as the design tool of choice.

We are finishing up work on patient search and are actively starting the design process for Patient Chart. This is perhaps the central feature used by OpenMRS users. It is critical that we get input from as many implementers as possible to ensure we are meeting your needs. We would very much appreciate feedback on the initial layout that Greg has been working on. It can be seen here: https://www.figma.com/file/XcyrlmDjMn2rkehroDXSvE/Patient-File-general-layout?node-id=0%3A1.

The first feature we will likely build into the patient chart is a “Patient Summary”, this is a snapshot of key information which will initially be shown to the user. This is similar in essence to what the ref app shows when you click on patient via search.

I think it would be useful to schedule a design session (if available) on Monday, Sept 9 to allow for additional feedback.

We are excited to be moving this forward and hope to attract as many of you as possible to contribute to this project.

Thanks,

JJ

@joeldenning, @burke, @gschmidt, @angshuonline, @jennifer, @mikejg, @mksd, @fali, @bistenes, @aojwang, @andu033, @mogoodrich, @mseaton, @paul, @janflowers, @pmanko, @dkayiwa, @ssmusoke,

2 Likes

Dear All,

@bistenes, introduced a new RFC for consideration on configuration. This is a critical proposal. Please take time to review here https://github.com/openmrs/openmrs-rfc-frontend/pull/14.

Thanks.

@angshuonline, @burke, @mksd, @mogoodrich, @mseaton, @ssmusoke

I just created two new RFCs:

  1. Issue tracking and documentation
  2. Pull request contribution guidelines
1 Like

Due to recent changes in my health, I will be stepping away from OpenMRS. What this means is that I will no longer attend any calls, review code, or write code. The changes to my work life also include resigning from my position with Just Utah Coders, laying off several employees and interns, and removing myself from many other time commitments and endeavors outside of OpenMRS.

I told this to the MF squad and OpenMRS leadership shortly before the OpenMRS conference last week, but decided to go to the conference since my tickets were already booked. Now that the conference is over, I’ll be stepping away.

My plan is to take a few weeks off and then apply to tech companies for a job as a software developer in an individual contributor role. I will be okay, and I expect my health to improve over time.

I have appreciated the opportunities presented to me within OpenMRS and have enjoyed working with the microfrontends squad. I wish each of you the best of luck and hope that the initiatives we started together will succeed. I have confidence in Fatma, Brandon, and JJ to continue to push things forward without me.

3 Likes

@joeldenning Sorry Joel for your poor health ,it’s also too sad to hear you’re leaving while we are in the early stages of this work.I actualy didn’t notice you were sick. Hope you Get well soon by God’s providence.

It’s a sad moment to know that you’re also leaving us too soon. But thank you for the awesome contributions and value you have added to the community and to some of us personally.

God Bless you.

@joeldenning it’s sad to learn about your health. I pray for your quick recovery. It was really a pleasure to meet you in the conference. Wish you all the best for future endeavors.

Not sure how I missed this Joel. I am very sorry to hear about your health challenge. I hope you will feel comfortable reaching out to those of us in the health care community who might be of help as you work through this. We will miss you and wish you the best in your recovery!

@joeldenning am please sorry to hear about the changes in your health. It is good that you have taken a bold step to address it before it gets out of hand!

It was great to see you for the first time at the conference. Thanks for accepting to come and please come again.

There are so many places you could go, but decided to chose OpenMRS to be among those projects that were lucky to have you onboard. Thank you so much for the great leadership and mentorship that you have provided us. We have learnt a lot from you and will use it all to save even more lives.

We shall greatly miss you, but are hopeful that in your spare time, you will remember us as one of your side projects! :slightly_smiling_face:

@joeldenning ohh sorry about the health.we do pray you get well soon and it will be nice seing you here whenever you can.

So sorry to learn of this. I wish you a quick recovery and may the Lord restore you to perfect health. Thanks for selflessly contributing to OpenMRS and mentoring some of us, it may have been indirect but I learnt a lot from you. I wish you wellness.