540Health
A Saudi Hospital Information System with native NPHIES insurance connectivity.
540Health is in active build. We'll show you what exists today and what is scheduled — no demo of software that isn't written yet.
- Platform
- ERPNext / Frappe v15 (extends Marley Health)
- Built for
- Hospitals · Clinics · Polyclinics
- Compliance
- NPHIES · ZATCA e-invoicing
What 540Health removes
Saudi providers need a hospital information system that speaks NPHIES from day one — not one that treats insurance as an afterthought bolted on with connectors. 540Health extends a proven HMS on Frappe with native NPHIES connectivity, without forking the core.
What it does
Core HMS & appointments
Patient records, scheduling and encounters as the operational backbone.
Specialty modules
Dental, ophthalmology and physiotherapy / rehabilitation, each modelled for its own workflow.
NPHIES-native revenue cycle
Eligibility, pre-authorization and claims through native NPHIES connectivity.
The depth, at a glance
6 modules — every one of them a first-class part of the same system, not an integration.
Written against the core — not copied from it.
Clinical, operational and financial data share one model, so a claim, an encounter and the ledger can never disagree.
540Health treats the ERP not as an external system to integrate with, but as its own runtime. It stores its data in the same model, posts to the same ledger, runs on the same workflow engine, obeys the same permissions and shows up in the same reports. On that foundation it adds what the platform lacks: the domain's objects, rules, language and screens.
Buyers are usually made to choose which gap to live with
Every business runs on a few hard things: a ledger that must balance, inventory that must be right, approvals that hold up to audit, and a permission model that keeps the wrong people out. Most of the market asks you to give up one side or the other.
Broad core, shallow domain
Very good at the universal hard things — a ledger that balances, approvals that survive an audit. Not good at the specific way your operation actually runs, and that last mile of domain fit is where the value is felt.
Deep domain, integration tax
Models the domain beautifully, then reaches back into the ERP through connectors that drift, duplicate data and quietly disagree. You pay a standing tax: engineering, reconciliation, latency, and doubt about which number is right.
Deep domain + native core
Uses the platform's data model, ledger, workflow and permissions as its foundation, and adds the domain depth on top. One system. Nothing to sync, because there is only one copy.
A custom point solution can do both, but only by re-implementing the accounting, workflow, security and reporting a mature platform already ships — most of the budget goes to rebuilding the floor before anyone reaches the product.
The clearest way to see the value is what disappears
Beside the platform
Two copies of the data · drift between syncs · reconciliation that never ends · every new feature re-plumbed back to the core · connectors that break whenever either side changes.
Integration is not a line item. It's a standing liability.
On the platform
One source of truth · nothing to reconcile · auditability that comes from the platform rather than a fragile mapping · saved engineering moved to the domain — the only place a product actually wins.
The product and the core cannot disagree, because they share the same records.
Five principles, and the path a deployment follows
The same rules apply to every product we ship — they are what keep an upgrade routine instead of a migration project.
- 1Build on the core, not beside it. The ERP platform is the runtime. If a capability exists in the core, we reach for it before building our own.
- 2Inherit, don't rebuild. Accounting, permissions, workflow, audit and reporting are solved. Every hour re-implementing them is an hour not spent on your domain.
- 3Speak the platform's data model. The domain is modelled in the core's own terms, so the product contributes to one ontology rather than a private schema — and is ready for agents.
- 4Design for composability. Each product is a clean building block that others can extend and combine.
- 5Ride the roadmap. Every platform upgrade, connector and ecosystem tool arrives at no extra cost.
How a 540Health deployment lands
- 1Discovery
- 2Feasibility & estimate
- 3Design
- 4Staged build on staging
- 5UAT
- 6Launch
- 7Support
We migrate through staging before production and script every schema change, so each stage has a tested path back.
The full thesis — the six advantages, the integration tax in detail and the five-level maturity model we build against — is set out on the ERP-based development page.
A hospital system that speaks NPHIES from day one.
540Health · HealthcareLicence and implementation are quoted per deployment — we estimate in ranges, not points, and every figure carries its assumptions, method and risks. Ask for a feasibility and you get a decision-ready go / no-go before anyone signs anything.
Also built on the same core
Hotel Pro
Front desk, housekeeping, rates, channels and finance — all connected on one platform and one ledger.
Learn more →Bussiness Center Management System
Run shopping malls end to end — property, leasing, billing, tenants and facilities.
Learn more →HSMS
A stud & stable suite — pedigree, breeding, veterinary, feed, training and sales.
Learn more →How we think about building this
Not ready to talk? These explain the method behind the product.
Why we build enterprise software on ERPNext instead of from scratch
The discipline that keeps vertical products fast to ship and safe to upgrade.
Read · 1 min →NPHIES, explained: what Saudi hospitals actually need from an HIS
A practical look at native insurance connectivity and revenue-cycle flow.
Read · 1 min →How an availability grid stops a hotel from overselling
Inside the concurrency-safe engine behind Hotel Pro.
Read · 1 min →Shape 540Health while it's being built.
Early customers set the priorities. Tell us how you operate and we'll show you where it lands on the plan.