DEV3 Technologies home

DEV3 Hearthdoc – Family Doctor Practice Management SaaS with Online Booking (built on the ClinicPro engine)

A cosy family-doctor practice system in cream paper and forest green: pencilled front-door website, folder-tab admin, a card-file drawer of patients and a fridge-door portal, with a native iPhone app. Built on the DEV3 ClinicPro engine: the same features, a different design.
by DEV3 TechnologiesVerified Author(0) 0 sales 1 viewsUpdated 12 Nov 2026

Launch Offer: up to 50% off

This item is 50% off: $24.50 instead of $49

Ends in
--
Days
--
Hrs
--
Min
--
Sec

Hearthdoc is a family general practice management suite that you host yourself, built by DEV3 Technologies on Next.js 15 (App Router and Server Actions) and MongoDB, with a native iPhone app. Built on the DEV3 ClinicPro engine: the same features, a different design. Hearthdoc is for the surgery where the receptionist knows Gran by name: cream paper with a faint grain, forest green headings, brick-red stamps and a front door drawn in pencil.

One installation serves many practices. Each practice has its own team, branding, display currency and language, a patient portal, a self check-in kiosk and a waiting-room display.

What it looks like

  • Front-door website. The home page opens on a pencilled house with a lit window and the practice hours pinned to its frame, then an Every-age section of arched cards (baby jabs to repeat prescriptions), a one-page day book room by room, price-led service cards and polaroid doctor portraits held with tape. Every page is editable from the admin.
  • Desk sign-in. Staff and patients sign in on a paper form lying on a wooden desk, with the front door drawn above it and a sticky note of house rules beside it. The wording is editable per language.
  • Folder-tab admin. A left sidebar whose section headers are folder tabs, a dashboard that starts with the waiting room and today's list, and settings in leaf-style tabs.
  • Card-file drawer of patients. The patients list, billing and every other list are a single stack of index cards: a hand-cut tab with the card number, the name on a red margin rule, facts on dotted leaders, the status stamped at the edge and actions underneath.
  • Family-folder patient record. The record opens as a stacked manila folder: a pencilled name header with facts on dotted lines, then staggered tabs for Visits, Medicines, Family details, Tests, Bills and Notes.
  • Fridge-door portal. The next visit on a taped appointment card, the balance as a little receipt, the medicine count on a shelf label and recent results held by magnets. Appointments are tear-off calendar leaves.
  • Hand-drawn icon set. Thirty-odd 1.5px line icons that draw themselves in on load (and stand still for reduced motion).
  • Four languages and dark mode. English, Arabic, Hebrew and Spanish with right-to-left layouts, plus a dark forest theme with checked contrast.

Demo content

Three fictional practices: Underhill (Porto, EUR), Larkmere (Abu Dhabi, AED, Arabic) and Eastlow (Portland, USD). The demo patients are whole families: only eight surnames (Penhallow, Treharne, MacAllister, Fitzmaurice, Pryce, Cullen, Ferrier, Llewellyn), so a grandmother, her daughter and a toddler can share one. First names match the sex shown, children carry a parent as emergency contact, and the memos read like a surgery noticeboard: the Thursday baby-jab clinic, 48-hour repeat prescriptions, Friday home visits.

Under the hood

Records, lab orders, consumable stock with expiry alerts, split payments and instalments in your currency, reminders, a self check-in kiosk and a waiting-room display, all shared with every ClinicPro design.

The iPhone app

The zip contains iOS-App/, the SwiftUI source with the Hearthdoc theme: forest and brick, Bricolage Grotesque and Source Sans 3, a roof-and-door mark and three app icons. Visitors browse the practice, patients book and read results, staff run the day. It was built and checked in the iOS Simulator only; it is source you build yourself.

Publishing the iOS app

You need a Mac with Xcode and XcodeGen, an Apple Developer account of your own and your own server URL. Edit Config.xcconfig (name, bundle id, team id, URL scheme, domain, server URLs), run scripts/make-icons.sh if you change the brand colours, run xcodegen generate, then archive in Xcode and upload through App Store Connect. Review and approval are Apple's decision; nothing in the package promises a listing. Push notifications stay off until you set the Apple push key on the server.

What you should know before buying

  • Same engine as the original ClinicPro. Features, database schema and APIs are identical across the design family. Choose Hearthdoc for its look and its family-practice sample content, not for different functionality.
  • Demo diagnoses and prescriptions are generic. They come from the shared engine; only people, practices and memos are Hearthdoc's own.
  • The portal shows one patient's own record. The fridge-door home is a layout for that patient; it does not group several family members under one login.
  • Email, card payments and file uploads need your own providers (SMTP, Stripe and an image host). Without them the app runs and logs outgoing mail.
  • Needs Node.js 20.9 or newer and MongoDB 5 or newer (a replica set is recommended; a hosted cluster works).

Included

Source code, a web installer that can load demo practices, the iOS app source, a buyer guide, a Docker setup, cron configuration and six months of support.

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Hearthdoc passed before release.

A family practice platform with a hand-drawn, cosy website and a folder-tab management console, built on the DEV3 ClinicPro engine.

The problem it solves

Family doctors are valued for being personal, yet practice software feels like a spreadsheet. The goal was a homely public site and a friendly admin without changing a line of the proven booking, records and billing logic underneath.

Architecture and approach

Hearthdoc is a design pack on the pinned ClinicPro engine. It brings its own tokens, a cream, forest and brick palette with checked contrast, code-drawn pencil art, a hand-drawn icon set, folder-tab navigation and index-card lists, while a build guard keeps every backend file identical to the engine.

Quality gates and results

  • Backend identical to the engine, verified by the guard on every build
  • Contrast checked for every text, link and button colour pair, light and dark
  • Install wizard driven end to end from the zip with Hearthdoc branding
  • Demo patients are whole families drawn from eight Welsh, Scots, Irish and Cornish surnames, so grandparents, parents and children share them (28% children with a parent as emergency contact, 48% parents, 24% grandparents); memos are written in a family doctor's voice

Tech stack

Area Technologies
Frontend Next.js 15, React 19, Tailwind CSS 4
Backend Server Actions, Mongoose 9, next-auth 5

Inside the build

The front door: a hand-drawn surgery with its opening hours pinned to the frame. The front door — a hand-drawn surgery with its opening hours pinned to the frame.

Every age at one door: arched cards from the baby's jabs to Gran's repeat prescription. Every age at one door — arched cards from the baby's jabs to Gran's repeat prescription.

Guides & articles

Practical guides and engineering write-ups for DEV3 Hearthdoc.

Designing a cosy family doctor platform: paper, forest green and a hand-drawn front door

Last updated
Designing a cosy family doctor platform: paper, forest green and a hand-drawn front door: DEV3 Hearthdoc

Choosing family general practice software is easy to demo and harder to live with. Here are 6 things to check before you pick a self-hosted system, with DEV3 Hearthdoc as the worked example. Hearthdoc is built on the DEV3 ClinicPro engine: the same features, a different design.

Video tour of Hearthdoc: the website, the dashboard and billing

The Hearthdoc home page

1. How does a family practice get a personal, homely feel?

Hearthdoc leans on paper: a cream background with a faint grain, notebook rules on cards, polaroid doctor portraits with a strip of tape and a pencilled house scene on the home page. The strokes are drawn in code, so they follow the clinic colour and the dark theme.

How does a family practice get a personal, homely feel?

2. What does the team see all day?

A classic sidebar whose groups are folder tabs, a dashboard that starts with the waiting room and today's list, and lists that read as index cards with a status stamp.

What does the team see all day?

3. How should a patient record feel?

Like the paper one: a manila folder with a pencilled name, then staggered tabs for visits, medicines, family details and notes. Underneath it is the same data as every other design.

How should a patient record feel?

4. How are services and prices shown?

As index cards with a ruled picture tile and a dotted leader line to the starting price, so a family can scan what a visit costs at a glance.

How are services and prices shown?

5. Who are the doctors?

Polaroid-style cards with a hand-drawn portrait, role and a line about how each person works.

Who are the doctors?

6. What do patients open at home?

A fridge door: the next visit on a taped card, the bill as a little receipt and recent results under magnets.

What do patients open at home?

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Questions about this product (0)

Answers from the DEV3 team and the community.

Ask a question

No questions yet.

Wondering about setup, licensing or customisation? Ask, and the DEV3 team will help.

More from this author

View all

Related in Enterprise SaaS Starters

View all