PHP download

Download the PHP package flowrise-hms/patient without Composer

On this page you can find all versions of the php package flowrise-hms/patient. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download flowrise-hms/patient
More information about flowrise-hms/patient
Files in flowrise-hms/patient

Vendor flowrise-hms
Package patient
Short Description Patient management module for FlowRise HMS providing comprehensive patient registration, identification, demographics management, and emergency contact handling. Implements MRN auto-generation, UUID-based identifiers for interoperability, and PII encryption for data protection.
License MIT

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Informations about the package patient

Patient module

In one sentence: The Patient module is where the hospital creates and maintains who the patient is—legal name, demographics, contact details, official IDs (including MRN, Medical Record Number, and a global UUID), emergency contacts, and related records—so every other part of the system can point at one trusted person.

Why this module exists

Before anyone can document a visit, order a test, or schedule an appointment, the facility must answer: “Which human being is this?” That sounds obvious, but in real hospitals patients arrive with many IDs (national ID, insurance number, passport), may share similar names, and need privacy for phone and email. This module is the single place that registers the patient and keeps identifiers consistent.

Where Patient fits in FlowRise

Depends on Core for organization and branch context (where the patient is registered) and shared platform services.
Clinical, Appointment, Billing, and Insurance features all assume a Patient record exists when they record encounters, bookings, charges, or policies.

What you can do with it (everyday language)

Register a new patient with demographics and contact information.
Assign and manage identifiers (MRN, NHIS or other insurance numbers, national ID, passport, custom IDs).
Maintain emergency contacts (next of kin) for when the care team must reach someone quickly.
Search and open a patient dossier from reception or clinical workflows.
Protect sensitive fields (the system encrypts many personally identifiable fields at rest—think phone, email, and similar data).

Exact screens and click paths are described for staff in the User guide: Patient management.

How it works (simple)

Staff use the admin web app (Filament) to open the patient area.
They fill registration or edit forms; validation runs so duplicate or invalid IDs are caught early.
The module’s service layer applies business rules (for example, how an MRN is generated or validated) instead of scattering logic across random screens.
Data is saved to the patients and related tables; other modules only reference the patient by stable IDs.

What is inside this folder (high level)

Path	Purpose
`app/Models/`	`Patient`, identifiers, emergency contacts, schools, etc.
`app/Classes/Services/`	Registration, search, identifiers, schools—the place business rules live.
`app/Filament/`	Patient cluster, resources, forms, tables, and pages staff interact with.
`app/Policies/`	Fine-grained access (who may create or view a patient).
`app/Events/`, `app/Observers/`	Hooks when patients are created or updated (for integrations and side effects).
`database/migrations/`	Schema for patient-related tables.

Dependencies

Core (flowrise-hms/core in composer.json / module.json requires).

Rollout status for all modules: Module status.

For developers

Namespace: Modules\Patient\...
Service provider: Modules\Patient\Providers\PatientServiceProvider
Prefer services over ad hoc Model::create() in new code so rules stay consistent with existing patterns.
Tests: under tests/; run from repo root with paths pointing at Modules/Patient/tests as needed.

All versions of patient with dependencies

PHP Build Version

Package Version

Version v1.0.0 Release 15. Aug 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of patient from vendor flowrise-hms

Requires php Version ^8.4
flowrise-hms/core Version dev-main

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package flowrise-hms/patient contains the following files

Loading the files please wait ...