Android App for recording accident and illness information

We have a bespoke accident and reporting application which is Bootstrap 4, php, mysql based. There is currently a web app which enables us to record an accident (See attached). This webapplication also supports saving accidents to a temporary location when there is no internet and uploads on re-connection.

I would like to move this concept into an Android / iOS application where we can have the following

1) Welcome screen to the application, present notifications to the user and display a welcome message.
2) Form for adding an accident entry
The accident form should be able to

search for a person (student)
select a registration group, (dropdown list but Pre-populated from above search)
display dropdown lists for :-
accident location
type of injury, injury symptoms
how it happened
treatment given
followup steps

(Dropdown data list to display all pulled from db configuration table and cached for offline use)

When in an online situation this should be posted to a webservice which writes the data the accident log table (Certain information needs to be aes encrypted using a customers string).

When offline the person search should be a text box where a user can type in a name, they can then complete the rest of the drop downs from cached forms, the record should then be uploaded to an “offline” table where the organisation can map the person to a live record in the main portal dashboard.

3) Form for recording an illness entry
The illness form should be able to

search for a person (student)
select a registration group, (dropdown list but Pre-populated from above search)
Time illness reported
Illness category
display multi select dropdown lists for
illness type
Illness symptoms
Treatment Given
Next Steps
Follow-up Notes

(Dropdown data list to display all pulled from db configuration table and cached for offline use)

When in an online situation this should be posted to a webservice which writes the data the accident log table (Certain information needs to be aes encrypted using a customers string).

When offline the person search should be a text box where a user can type in a name, they can then complete the rest of the drop downs from cached forms, the record should then be uploaded to an “offline” table where the organisation can map the person to a live record in the main portal dashboard.

WEBSERVICES

There is no web services in place for the app to connect to, these will need to be considered.

There is source for the authentication model, this will enable username / password or URL string to authenticate and return the customers database server / connection strings / configuration keys

These should then be used by the webservice to ensure they are written to the correct customer data


** MORE INFORMATION **

The authentication model currently in place is one where the customer authenticates against the portal.

This then presents connection strings for their individual databases and encryption strings

Then any reads / saves are from their own DB on a private lan, the private lan can only be accessed via the front facing web servers.

The accèss is made available by the current authentication model, by private lan the database servers are not visible to the internet so any calls to access data / post data will need to be authenticated with the current model (or similar) and instructed from the web servers,

There is no web services in place to do this currently.