Final Project

About This Application

An ICD-11 to AIS mapping tool for injury coding and ISS calculation. This is the final project of Sajed Arabian.

What it does

This application helps clinicians and researchers map ICD-11 injury codes to AIS (Abbreviated Injury Scale) values and compute an ISS (Injury Severity Score). It supports both the official WHO coding workflow and a localized mapping workflow built for internal use and customization.

Two versions

Old Version

Modeled after the WHO ICD-11 Coding Tool. Searches the official ICD-11 API (Mortality and Morbidity Statistics) in real time, so results stay aligned with the WHO release.

New Version

Created when internet access was limited to the national network, so the app could work offline from the WHO API. It is more customized, with a richer local dataset of ICD–AIS mappings, and an admin panel for managing folders, codes, and descriptions.

Technologies

Laravel 12.20
PHP framework for routing, authentication, and database access.
Bootstrap 5.3
UI components and layout for the new version and admin pages.
jQuery 3.7.1
Search, AJAX loading, and interactive lists in both versions.
WHO ICD-11 API v2
Official source for ICD-11 entity search and details in the old version (release 2025-01).
Maatwebsite Excel 3.1
Import of ICD–AIS mapping data from spreadsheet files.
SQLite
Persistent storage for localized mappings and application data.
Git 2.47
Version control for tracking changes, collaboration, and project history.
PHP 8.2
Runtime language used by Laravel on the server.

Security

Admin features are protected by Laravel authentication, so only signed-in users can manage mappings. Forms use CSRF protection, and credentials for the WHO API are kept in server-side environment variables rather than the client. The new version can also run fully on a local or national network without depending on external services, which reduces exposure when internet access is restricted.

Scalability

Built on Laravel and a standard database stack, the application can scale both vertically (stronger servers, more CPU and memory) and horizontally (multiple app instances behind a load balancer, shared cache and database). With proper infrastructure—caching, queues, and database replication—it is designed to support growth toward millions of users.

Future capacity

The project is structured to grow beyond a coding demo. Possible next steps include:

  • Expanding and refining the local ICD–AIS dataset for more injury types
  • Role-based access for hospitals, researchers, and administrators
  • Export of selected codes and ISS results to Excel or clinical reports
  • Multi-language support and further localization of titles and descriptions
  • Integration with hospital information systems (HIS) or trauma registries
  • Offline packages and scheduled sync when external APIs become available again