01 · Context
The client runs a management information system for hospital finance teams. Source systems feed a data warehouse, with desktop MIS and BI tools on top.
The information already exists. The mobile project makes it accessible to hospital management away from the desktop, alongside a web version.
02 · Problem
Directors need to check results and trends without turning each question into a separate request to the finance team.
The app must also make the meaning of a figure clear: which period it covers, how current the source data is and whether the month is closed.
03 · Constraints
The existing BI engine reads the warehouse over SQL and does not provide an HTTP API.
Financial data needs controlled access even though the app does not handle patient records. Integration, authentication and security review have to fit the client’s environment.
Development uses synthetic data. Customer data does not enter the repository or public examples.
04 · Role
The existing system, warehouse and brand belong to the client.
The client builds the API and publishes the app. Tolaron builds the app against that interface.
05 · Solution
React Native and TypeScript share the core interface and logic. Reusable platform code is separated from the client-specific product.
A shared data contract. Schemas describe the data the API returns and give the app matching types. A common data-source interface separates the screens from the integration details.
Figures with context. The dashboard distinguishes source refresh time from response time and marks whether a reporting period is closed.
06 · Outcome
The development work connects warehouse data, financial calculations, the API contract and the app.
The work also identifies accounting cases that would otherwise distort a dashboard, including duplicate currency calculations, subtotals and unclosed periods. Integration and operating responsibilities remain part of the client agreement.