PHPackages flowrise-hms/clinical - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. flowrise-hms/clinical ActiveLaravel-module[Utility & Helpers](/categories/utility) flowrise-hms/clinical ===================== Clinical module for patient encounters, service requests, tasks, vital signs, and clinical notes 00PHP Since Apr 29Pushed 2w agoCompare [ Source](https://github.com/Flowrise-HMS/Clinical)[ Packagist](https://packagist.org/packages/flowrise-hms/clinical)[ RSS](/packages/flowrise-hms-clinical/feed)WikiDiscussions main Synced 2w ago READMEChangelogDependenciesVersions (4)Used By (0) Clinical module =============== [](#clinical-module) **In one sentence:** The Clinical module is where **care happens on the record**—visits (**encounters**), **vital signs**, **clinical notes**, **orders** (**service requests** and their line items), **tasks** that staff fulfill, and **allergies**—so the hospital has a structured story of what was done for the patient and when. Why this module exists ---------------------- [](#why-this-module-exists) Registration (Patient) tells you **who** someone is. Clinical tells you **what happened to them medically**: they arrived for a visit, someone measured their blood pressure, a doctor wrote a note, a lab was ordered, a nurse completed a task. Without this layer, you only have demographics, not a **medical dossier** or a **timeline of care**. Where Clinical fits in FlowRise ------------------------------- [](#where-clinical-fits-in-flowrise) - **Depends on Core** (branches, locations, departments, users) and **Patient** (every clinical fact ties to a patient). - **Appointment** integrates with the same **clinical workspace** screens (for example, booking actions from patient-oriented pages). - **Diagnostics** listens for diagnostic `RequestItem` create/cancel events and creates or cancels `DiagnosticFulfillment` records. - **Pharmacy** attaches `dispenses` to medication-related `RequestItem` records. ``` flowchart LR Core[Core] Patient[Patient] Clinical[Clinical] Appointment[Appointment] Diagnostics[Diagnostics] Pharmacy[Pharmacy] Core --> Patient Core --> Clinical Patient --> Clinical Appointment -.->|workspace hooks| Clinical Clinical -->|RequestItem events| Diagnostics Clinical -->|medication RequestItems| Pharmacy ``` Loading What you can do with it (everyday language) ------------------------------------------- [](#what-you-can-do-with-it-everyday-language) - **Start and manage encounters** (outpatient, inpatient, emergency, virtual—whatever your configuration supports). - **Record vital signs** (blood pressure, pulse, temperature, and related measurements). - **Write clinical notes** tied to the patient’s care. - **Place service requests** (orders such as lab, imaging, or other services your catalog defines) and track **request items**. - **Track tasks** so departments know what must be done and whether it is done. - **Record allergies** where that workflow is enabled. - **Administer medications (MAR)** via the medication administration board, dose reminders, workspace actions, and patient relation manager. - Track **ADT location events** (admit/transfer/discharge bed moves) on encounters. - Use **workspace** pages (patient list, timeline, profile) to work in a patient-centric way rather than only from generic admin lists. For laboratory, radiology, and pathology fulfillment after an order is placed, see [Diagnostics Workflows](../../docs/user-guide/diagnostics.md). How it works (simple) --------------------- [](#how-it-works-simple) 1. A clinician or clerk opens a **patient** in the clinical area of the admin app. 2. They create or update an **encounter**, then add **vitals**, **notes**, or **orders** as the visit unfolds. 3. Business rules live in **service classes** under `app/Classes/Services/` (not only inside database models), so the same rules apply no matter which screen triggered the change. 4. Data is stored in clinical tables; other modules or reports read it through models and services—**not** by bypassing those layers. What is inside this folder (high level) --------------------------------------- [](#what-is-inside-this-folder-high-level) PathPurpose`app/Models/`Encounters, vitals, notes, service requests, request items, tasks, allergies, participants, etc.`app/Classes/Services/`Create, update, search, and filter operations—**primary business logic**.`app/Filament/`Plugin registration, workspace pages, widgets, and clinical UI clusters.`app/Schemas/`Shared form schema pieces where used.`app/Policies/`Who may view or edit sensitive clinical rows.`database/migrations/`Schema for clinical tables.Dependencies ------------ [](#dependencies) - **Core** and **Patient** (see `module.json`). Further reading --------------- [](#further-reading) - **Implementation plan:** [docs/implementation-plan.md](docs/implementation-plan.md) - **Staff-facing workflows:** [Clinical workflows](../../docs/user-guide/clinical-workflows.md) For developers -------------- [](#for-developers) - **Namespace:** `Modules\Clinical\...` - **Service provider:** `Modules\Clinical\Providers\ClinicalServiceProvider` (registers sub-providers and loads Filament views under the `clinical` view namespace). - **Patterns:** prefer `*Service` classes for writes; use Filament `Schema` / action patterns consistent with the rest of FlowRise (see implementation plan for naming). - **FHIR:** data shapes and names often follow **HL7 FHIR** ideas (for example, “Encounter”, “ServiceRequest”) to ease interoperability—you can ignore FHIR day-to-day unless you are building an export or API. ### Health Score 21 — LowBetter than 17% of packages Maintenance63 Regular maintenance activity Popularity0 Limited adoption so far Community6 Small or concentrated contributor base Maturity16 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/58814410?v=4)[Mushe Abdul-Hakim](/maintainers/musheabdulhakim)[@MusheAbdulHakim](https://github.com/MusheAbdulHakim) --- Top Contributors [![MusheAbdulHakim](https://avatars.githubusercontent.com/u/58814410?v=4)](https://github.com/MusheAbdulHakim "MusheAbdulHakim (75 commits)") ### Embed Badge ![Health badge](/badges/flowrise-hms-clinical/health.svg) ``` [![Health](https://phpackages.com/badges/flowrise-hms-clinical/health.svg)](https://phpackages.com/packages/flowrise-hms-clinical) ``` ### Alternatives [rupadana/filament-swiper The Most Modern Mobile Touch Slider on Filamentphp 3715.5k3](/packages/rupadana-filament-swiper) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)