FirstCare is the authority on absence management and its financial impact. It's the UK's largest database on absence, covering 185,000 employees, and has records for more than 10.2 million absences.
FirstCare is a platform for reporting absences, processing them, making reports based on different criteria and also finding patterns in absences. The platform is used in large corporations to mitigate the financial impact of absences by assessing the patterns and finding a way to fix the problems before more people are affected.
The platform can be operated by many types of users, such as Absence Advisors, Nurse Advisors, Managers, Employees, etc. Based on type there’s different workflow and reporting available. For example, for Nurse Advisors there’s a call script which contains medical triage, by answering for which employees they can receive advice about what to do and some potential diagnoses.
The customer came to Devico with a request to develop a new version of the application instead of the old one which was developed more than 10 years ago. It was already in production, but we were required to make a new version from scratch. Our team was assigned to work on the front-end part of the platform and to interact with FirstCase developers on the back-end.
The API and front-end were developed in parallel. Therefore, at the first stages of development we were required to implement front-end parts before those parts were implemented on the back-end. In some situations, we had mocks for API, but for most of the parts at the first stages, we worked blind. The customer had tight delivery dates, so we were asked to propose the format of requests and responses that we would need for missing parts, so it will work without needing to be changed in the future. Our work with making positive-looking front-end was accurate to 70%, which is a good result when you are working blind based only on mockups, without real code.
Another challenge was related to forms which were generated automatically on UI based on received JSON Schemas from back-end; it was hard to apply design for a form, and make it responsive, when this form can be changed. The first attempts were to change schema on UI, to apply some styling to it, but we experienced a situation that developers on back-end didn’t knew that this form was already implemented, and sometimes changed it. Therefore, as a result, we started asking back-end developers to make some modifications in schemas so we will need to patch schemas on UI. Consequently, changes of forms were significantly smoothened, and it worked just as requested.
DCMS is a case management system for dentists and labs.
Memomeister helps you to organize document flow in your organization.