DEV3 Wardkeep – Hospital Management System Laravel Script with Bed Board, IPD Billing and Flutter Patient App

Wardkeep is hospital management software for one hospital or a group of facilities, built inpatient-first. It follows a patient from admission to discharge: the bed, the nursing chart, medicines, theatre, lab, the running bill and the discharge summary. It is built by DEV3 Technologies on Laravel 12 and Filament 4, and it ships with seven staff areas, a patient web area, a public hospital page with outpatient booking, a REST API with webhooks, and a Flutter patient app with full source and a publishing guide.

What it does

• Admissions and beds. An admission wizard (record first, then consent with a drawn signature, bed and deposit), a live bed board with drag to admit or transfer, a tariff preview before a move, held and cleaning beds, isolation rules and a waiting list. Wristbands, sample labels and visitor passes print from the browser with Code 128 or QR codes.
• Nursing and medication chart. A patient chart with vitals in colour bands you set, intake and output, notes, orders, rounds and a medication grid where every dose is due, late, given, refused or missed. Controlled drugs need a second person with their own PIN, and every correction is a new row rather than an edit.
• Theatre, pharmacy and lab. A theatre calendar with a pre-op checklist and consumables, ward pharmacy indents issued by soonest expiry with returns, a controlled-drug register, and a lab worklist where a second person verifies before a result reaches the patient.
• Running IPD bill. Bed-days are posted on a schedule, charges are posted from services, pharmacy, lab and theatre, and every line shows the package, insurer and patient share side by side. Discounts above a limit need an approver PIN. Deposits, refunds, interim and final bills, and PDFs are included.
• Insurance records. Pre-authorisations and claims are records and documents your insurance desk prepares: draft, mark as sent by hand, record the insurer's answer, prepare a claim pack PDF and record settlement. Nothing is submitted to an insurer or a scheme from the software.
• Discharge. Planned discharge, a signed discharge summary with a PDF, and a recorded path for leaving against advice or a death, which pauses family access at once and lets the final bill follow.
• Reports. Occupancy, average stay, bed turnover, medication-round compliance, theatre use, revenue, receivables ageing and deposits held, with CSV export, plus a Ward Glance grid of every bed.
• Patient and family. A patient web area and the Flutter app show the stay card, the bill with a deposit top-up, verified results, the signed discharge summary, consents, medicines given and due, insurance status, clinic visits, visitor passes and a log of who opened the record. Family members are invited with limited scopes.

The Flutter patient app

One app for patients and invited family, with full source: stay card and timeline, running bill with a deposit top-up through a test card sheet, results with range bars, discharge summary and PDFs, a read-only medicine summary, insurance status, messages with the ward team, signing a requested consent with a drawn signature, clinic visits, visitor passes with a QR, a record access log, and people and access settings. It starts in demo mode with sample data and no server, and switches to your Wardkeep install with an address and a flag. The Documentation folder has a Publishing the apps guide for renaming it, setting your icons and backend, and releasing it under your own Apple and Google developer accounts, including notes for health apps.

What you should know before buying

• One hospital or one group. Several facilities under one organisation, not a multi-tenant service for many hospitals.
• Inpatient first. Outpatient is registration, appointments, a consultation note and a referral only. Lab and radiology are order and result entry; there is no analyser, PACS or DICOM link, and no HL7 or FHIR in this version.
• Records you prepare. Insurance pre-authorisations and claims are not sent electronically to insurers or schemes. There is no ICD or CPT content.
• Not a medical device. No clinical decision support, no dose checking and no early-warning score. It makes no compliance or certification claim, and you are responsible for health-data law where you operate.
• Simulated by default. Card payments, mail, SMS and push use working simulated drivers until you connect your own.
• You publish the app. Building, signing and store review are your step; health apps face stricter review. The app was checked in simulator and APK builds, automated tests and a run against a live backend, not on real devices.
• Use MySQL or MariaDB for a live site. One cron entry every minute is required.

Included

Source code of the Laravel app, the web installer, the Flutter patient app with a publishing guide, a buyer guide, demo data for a fictional hospital network (two facilities, 280 beds, 26 wards, six theatres, about 150 staff accounts, 18,000 patients and thousands of closed admissions with bills), and six months of support.