2019-11-20: Technical Action Committee Meeting

Dear community,

We have our next Technical Action Committee on Wednesday. I’d like us to answer two questions this week:

  • What are two areas that we want to focus on?
  • What about Sync 2.0, FHIR, and OCL for OpenMRS? (from the PCC + community)

Feel free to propose additional agenda items or questions!

When: Wednesday, 20 November at 7:30pm IST | 5pm Nairobi | 4pm Cape Town | 2pm UTC | 9am Boston | 6am Seattle

Anyone in the community is welcome to join the call! @burke @dkayiwa @ssmusoke @mogoodrich @angshuonline @ningosi @isears @k.joseph

To join the call by phone, dial +1-888-510-4073. To join the call using Audio, Chat, & Screen Sharing please use a compatible browser (Chrome, Firefox, Edge) and go to: http://www.uberconference.com/openmrs

Ack… unfortunately I will not be able to make the call this week.

I would like to suggest that we try to have a in-person meeting in Maputo, potentially longer than a single unconference session (could possible be handled by using two sessions…)

Take care, Mark

I am assuming we are not having the call today? Sorry, I was little late coming from another call.

Ah! And @dkayiwa and I were on for about 10 minutes before deciding to pick this up here on Talk. @mogoodrich, I agree that we need to set up some working sessions in Maputo. I’m working on our pre-meeting agenda this week - perhaps we can leverage some of that time in addition to the usual opportunities during the meeting itself.

I did some more work on the Technical Objectives yesterday. The first few seemed more like guiding principles or approaches that we want to take. Take a look and let me know what you think.

And then of the six focus areas, which two do you think we should focus on first? Keeping in mind that there is active work going on with the MF Squad, the FHIR Squad, as well as around OCL for OpenMRS and data migration.

  1. Improve configurability by end users
  2. Ease deployment and upgrade paths
  3. Increasing modularity and improving development experience
  4. Integration, interoperability and data sharing
  5. Making sure the platform is stable
  6. Improve metadata management

Looks good @jennifer… I just made some tweaks to the documentation… I think that the “metadata management” isn’t really it’s own bullet point, but rather something we can do that really can help with goals 1, 2 and 3… (and potentially 4 and 5 for that matter).

The work of the MF squad helps move forward at least goals 1 and 3… and assumedly the FHIR work helps with goal 4 (though I’m not as involved with that work).

It could make sense to pull together a “platform” squad?

Take care, Mark

1 Like