Architect Roles across OpenMRS

Part 4: Backend Architect

About the OpenMRS Backend:

The OpenMRS Platform is a modular, database-agnostic, Java-based application providing the key resources and services needed to support an extensible electronic medical record system. Many different organizations and countries have built solutions on top of this platform, making it very important to provide stability, reliability, security, and a clear upgrade path while working with a worldwide community of developers.

Role Overview:

  • Plan to modernize OpenMRS: Need more modern software stack, amidst reality that this needs to work in situations with not highly technical staff who will not understand more complex things.
  • Security: work with security experts on handling custom parts of our application with regard to Security - e.g. Authentication & Authorization is in the application. Consider security issues when reviewing PRs and committing code. Demonstrate security best practices for new code and when refactoring existing code.
  • Integration: Vision for how to integrate vast space in healthcare IT into the EMR - complex data exchange, that data will need to leave or make its way into the EMR. e.g. integrations (Radiology, Pharmacy, HR)
  • Dig through mountains of code and figure out areas of tech debt and legacy complexity

Skills Required:

  • Excellent communication skills
  • Deep understanding of Java and the standard Java Servlet stack
  • Strong familiarity with the Spring & Hibernate frameworks (beyond just Spring Boot)
  • Deep familiarity with REST and at least some experience working with FHIR (has gone beyond using APIs - understanding of REST framework & experience developing APIs)
  • Knowledge of the healthcare space and particularly the challenges facing EHRs.
2 Likes