Well for both ends, you need to choose a tool that is robust and sustainable, which can as well support generating test reports , i.e., can it generate results in some kind of standard format that can be easily used by other tooling to indicate how many tests passed or failed and which tests? (Most helpful would probably be something like the JUnit format). This will be of help to developers, organisation managers and as well give confidence to the users of your products.
Of recent were comparing different tools that would be suitable for Back-end testing which may be good for you to look at and follow the conversation on the talk post here to aid you choose desirably.
Cucumber-Selenium or Cucumber-Cypress would be a good deal for Front-end testing. They slightly differ in the language they use But both support Behavior Driven Development(BDD Framework) that has a workflow which entails writing feature files containing user stories written in a simple human readable language called Gherkin(which follow a very simple syntax of Given → When → Then) and these stories are wrapped in steps definition using either Cypress or Selenium.
The starting point would be selecting the tool, then set up a qaframework module for the organisation to have you get started with automated testing of your products. You may take a look at the POC for OpenMRS.
@valuoch would be glad hearing updates from you!