DEV3 Halewing – Doctor Appointment Marketplace Laravel Script with Video Consults and Flutter Patient and Doctor Apps

Halewing is a doctor appointment marketplace that you operate. Doctors and clinics apply and list themselves, you check their documents, patients search by condition, specialty or city, book a slot, pay and attend in clinic or on video, and you take a commission and pay doctors from their wallets. It is built by DEV3 Technologies on Laravel 12 and Filament 4, and it ships with an operator back office, a doctor workspace, a clinic panel, a public marketplace site, a patient area, and two Flutter apps (patient and doctor) with full source and a publishing guide.

What it does

• Public marketplace. Search that reads a plain phrase such as "skin rash Mapleford" and lands on a specialty and a city, filters for visit type, language, gender and fee, specialty and city pages, doctor profiles with qualifications, reviews and live slots, clinic pages with a drawn map, and a page that verifies a prescription code without showing the medicines.
• Booking. Slots come from each doctor's weekly hours, buffers and time off. A chosen slot is held for seven minutes while the patient pays, two people cannot take the same slot, family members and children can be booked as dependants, and cancelling shows the refund before the patient confirms. Patients can reschedule, review a completed visit and message the doctor.
• Video consults. The visit opens a Halewing consult page with a waiting room and an admit button for the doctor. The call itself runs on your own Jitsi server, with signed room tokens when you configure them. Halewing hosts and records no video.
• Doctor workspace. Today's visits, a consult workspace with a structured note, signing with an amendment trail, prescription PDFs with a verification code and the doctor's uploaded signature, consult types and weekly hours with a live preview of booked visits a change would clash with, time off, reviews with a reply, and earnings.
• Clinic panel. Clinic profile and locations, invite doctors, appointments without patient names, a weekly rota and earnings.
• Operator back office. A verification queue for doctor documents, doctors, clinics, specialties with keywords, appointments (metadata only), disputes and refunds, review moderation, commission rules per specialty and mode, weekly payout runs, strikes, a record access log, deletion requests, API keys, signed webhooks, video settings and a dashboard with a Care Map.
• Records you keep. Notes, prescription lines, allergies and visit reasons are stored encrypted, and every read of a record is written to an access log that the patient can see.

The Flutter apps

Two apps are included with full source: a patient app (search, doctor profile, book and pay, my visits, reschedule and cancel with a refund preview, join video in the browser, notes and prescription PDFs, reviews, messages, access log, family members) and a doctor app (today's queue, visit detail, start video as moderator, consult notes and signing, prescriptions, availability and time off, follow-ups, earnings and reviews). Both start in demo mode with sample data and no server, and switch to your Halewing install with an address and a flag. The Documentation folder has a Publishing the apps guide for renaming them, setting your icons and backend, and releasing them under your own Apple and Google developer accounts, including notes for health apps.

What you should know before buying

• A marketplace you operate. One operator, many doctors and clinics. It is not a multi-tenant SaaS.
• Verification is manual. Your team opens each document and approves it; there is no medical-council lookup.
• Simulated by default. Card payments, payouts, mail, SMS and push use working simulated drivers until you connect your own. You are the merchant of record.
• Video needs your own Jitsi server. meet.jit.si is for testing only, under its terms. There is no video SDK inside the apps: they open the consult page in the phone's browser.
• Records, not a medical product. Prescriptions are signed PDFs, not electronic prescriptions sent to a pharmacy. It gives no triage or diagnosis, makes no compliance or certification claim, and you are responsible for health-data law where you operate.
• You publish the apps. Building, signing and store review are your step; health apps face stricter review. Push needs your own Firebase or APNs setup.
• Known gaps. There is no QR image for reception check-in and clinic administrators have no check-in screen; the apps were tested with simulator and APK builds and a live-backend run, 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, both Flutter apps with a publishing guide, a buyer guide, demo data for a fictional care network (140 doctors, 18 clinics, thousands of patients and about 15,000 appointments), and six months of support.