Hamyar Paygah

Package

Poetry Development Release Stable Release

Quality Assurance

SonarQube Quality Gate SonarQube Reliability Rating SonarQube Maintainability Rating SonarQube Technical Debt SonarQube Bugs SonarQube Code Smells

Stats

Contributors Stars GitHub Issues GitHub Pull Requests SonarQube Lines of Code Repository Size

Tests

Nox CodSpeed pre-commit.ci status Coverage status OpenSSF Scorecard

Security

Analyzed with Synk SonarQube Security Rating SonarQube Vulnerabilities Open Source Security Foundation Best Practices Badge Open Source Security Foundation Baseline Badge

Linters

Ruff pre-commit MegaLinter status Checked with MyPy Linting with Pylint

Activity

GitHub commit activity

Documentation

Documentation Status

Overview

Hamyar Paygah is an application designed for Emergency Medical Services (EMS) overseers to gather and review information from EMS servers.

The system provides structured operational visibility into:

  • Mission lists

  • Individual mission details

  • Consumables and drugs used per patient

  • Regional-level usage statistics and equipment trends

The project is intended strictly for authorized internal EMS use.

Development Status

Alpha

This software is under active development.

Interfaces, behavior, and internal data handling may change without backward compatibility guarantees. Deployment should remain internal during this phase.

Core Capabilities

Current implemented features include:

  • Retrieval of mission lists from EMS servers

  • On-demand retrieval of individual mission details

  • Display of consumables and drugs used for each patient

  • Regional analysis of:

    • Number of patients

    • Equipment usage patterns

  • Local caching of retrieved mission data to reduce load on the primary server

No telemetry collection is implemented.

Architecture (High-Level)

Hamyar Paygah follows a structured desktop architecture:

  • Python 3.13 application core

  • Qt-based graphical user interface

  • Direct communication with EMS server endpoints

  • Local caching layer for mission data

  • Packaged as Windows executable via GitHub Actions workflows

The system operates without background services or external telemetry.

Data Handling & Storage

  • Mission data is cached locally to reduce repeated server load.

  • No telemetry or analytics data is transmitted externally.

  • The application does not intentionally log sensitive mission data.

  • Cached data exists solely to improve performance and reduce server strain.

Users are responsible for ensuring lawful and compliant data usage within their operational environment.

Authentication & Communication Model

  • The user must manually provide the EMS server address.

  • No username, password, or token authentication is required.

  • The EMS server does not provide encryption.

As a result, deployment is intended exclusively within trusted and controlled network environments.

Example Workflow

  1. Launch the application.

  2. Provide the EMS server address.

  3. Retrieve the mission list.

  4. Select an individual mission.

  5. Inspect patient details, drugs, and consumables used.

  6. Review regional equipment and patient statistics.

The interface is designed for operational clarity and structured oversight.

Installation

Prebuilt Windows executable files are published via:

GitHub Releases

Versioning follows Semantic Versioning.

Executables are automatically built using GitHub workflows. They are not digitally signed.

Roadmap

Planned areas of improvement:

  • Expanded data analytics capabilities

  • Performance optimizations

  • Stability hardening

  • Potential future support for macOS and Linux

Multi-platform support is not currently a priority.

Audience

This project is intended exclusively for:

  • Authorized Emergency Medical Services overseers

  • Internal operational or supervisory use within EMS organizations

It is not intended for public use, consumer use, or deployment in uncontrolled environments.

Lawful Use Only

This application is intended solely for lawful, authorized, and ethical use.

The developer explicitly does not authorize, support, or condone any use of this software for:

  • Unauthorized access to systems or data

  • Surveillance, profiling, or monitoring beyond legal authority

  • Collection, exposure, or misuse of personal or sensitive information

  • Any activity that violates privacy rights, organizational policy, or applicable local or international law

Any misuse, abuse, or unlawful deployment of this application is the sole responsibility of the user.

Security

Security vulnerabilities must not be reported through public issues.

Please refer to SECURITY.md for instructions on responsible vulnerability reporting.

Contributing

Contributions are subject to strict rules and discretionary acceptance.

Please read CONTRIBUTING.rst before submitting issues or pull requests. Participation is a privilege, not a right.

Code of Conduct

All project-related interactions are governed by the project’s CODE_OF_CONDUCT.rst.

License

This project is licensed under the MIT License.

See the LICENSE file for full license text and terms.