The OpenMRS 2019 Hackathon will take place over the course of 1 and a 1/2 days, commencing on 2^nd Dec 2019  and coming to a close on 3^rd Dec 2019 at 1:00 pm, to pave way to the official opening of the conference on the same day.

Participating teams will have time throughout the conference  to continue working on their solutions and present on their achievements to the community on Friday 6^th Dec 2019.

This is a technical space for software teams and architects to engage and get their “hands-in” or “on” OpenMRS and related projects. We are excited to provide a space for teams to connect and work on exciting and high priority tasks and challenges, as well as give the community an opportunity to propose low hanging fruit use cases for groups to work on. There is no better way to get working on OpenMRS than actively engaging in designing, developing, configuring, implementing and connecting to OpenMRS to grow existing skills, learn new skills, and build relationships with others in the community.

Slack Channel

Please join the OpenMRS #hackathon channel on Slack, which will be used for all hackathon-related discussions/chat during the course of the event.

Objectives

The attendees of the Hackathon are aiming to:

• Extend the core OpenMRS offering and the application of OpenMRS in the digital health space.
  
• Learn how to contribute to the OpenMRS community and codebase.
  
• Jointly work together to solve common challenges and priority use cases.
  
• Self-organise into learning sessions and create breakaway groups to discuss topics / show ideas

So what does this really mean/look like?

We are looking forward to the attendees (that is you, the participant) bringing their technical strengths to the table and bringing their challenges and use cases to engage with others in the field. These sessions are focused at providing the space for the architects, the analysts, the developers and the system integrators within the community to meet and discuss how to solve active problems and develop innovative solutions. We are expecting a combination of the following to emerge:

• Focused technical discussions around how best to engage with fundamental aspects and architecture of OpenMRS.
• Bringing your technical questions and projects/code to persons with expertise in these areas and engaging with them and others on how best to architect and develop solution(s).
• Resolving high priority issues and tackling new features on the OpenMRS roadmap.
• The role of OpenMRS in the HIE space, interfacing with other applications and services, and best practices regarding data standards, terminologies etc.
• Bring your development skills to the table and try to help others working on various challenges.

Current Challenges

Taking into account expertise and teams attending we are looking for groups and members to list out the current challenges that they are posing to the attendees. Please add your challenges/hacking ideas below.

TO NOTE: If you're proposing a topic because you're looking for help on an issue (as opposed to offering yourself up to work on the issue), please fill in the 'Support Needed'  column with the type of expertise or help you'd require.

High Priority OpenMRS Issues

In addition to the challenges raised above, there may smaller high priority issues raised by the community and/or from the core OpenMRS roadmap to be tackled at the Hackathon. These issues could be tackled by a specific working group or during dedicated time during the hackathon, or they may be broken out into broader topics/challenges and moved up into the Current Challenges section above, where appropriate.

Please add your issues to the table below along with a short description on why you consider this a high priority.

TO NOTE: If you're proposing an issue because you're looking for help on this (as opposed to offering yourself up to work on the issue), please fill in the 'Support Needed'  column with the type of expertise or help you'd require.