Skip to content
Fossible HIS · ERPNext / Frappe Healthcare · Agent-ready

One platform from ward to wallet — open-source CareOps on Frappe

Fossible HIS is a production-grade Hospital Information System on Frappe and ERPNext — EHR, LIS, RIS, pharmacy, billing, insurance, inventory, HR, and accounting on one database and one API. Self-host anywhere with zero per-user fees. Every doctype exposes REST, workflows run in Python, and Hydra MCP gives AI agents a typed, permissioned tool surface from day one.

Fossible HISPMSPractice MgmtLabModuleERPFull-stackDigitalHealthLowCodeEnterpriseReady

Platform proof points

Open-source CareOps,
built for real hospitals

GPL-3.0Fully open sourceFHIR R4HL7 compliant$0Per-user licensing
10K+Orgs on FrappeRESTEvery doctypeHydra MCPAgent-ready

The problem

Healthcare IT is expensive,
fragmented, and unsustainable

Most hospitals run five to eight disconnected systems. Fossible HIS replaces that sprawl with one integrated CareOps and ERP platform on Frappe.

Fragmented vendor stack

EMR, billing, inventory, HR, and lab each on separate systems — middleware, training, and license fees multiply.

Clinical vs financial silos

Encounters do not trigger billing, inventory, or GL automatically — reporting means manual reconciliation.

Vendor lock-in

Proprietary code, cloud-only hosting, and per-seat pricing that scales faster than your patient volume.

One platform, one truth

Fossible HIS unifies CareOps and ERP on Frappe/ERPNext — one database, one API, self-hosted, agent-ready via Hydra MCP.

Platform

Full-spectrum coverage across
clinical, operations, and business

Four operational domains in one Frappe stack — production-ready modules, deeply integrated, customizable through low-code.

Clinical workflows

FHIR-compliant patient management, encounters, vitals, procedures, medications, nursing tasks, and inpatient ADT — multi-specialty ready.

encountersvitalsipdicd-10

Lab, radiology & pharmacy

Full LIS with LOINC, RIS with DICOM, integrated pharmacy with inventory and interaction checks.

lisrisdicompharmacy

Business operations & ERP

Accounting, RCM, procurement, multi-warehouse inventory, HR and payroll — natively wired through ERPNext.

billingrcminventoryhrms

Platform & digital health

Low-code doctypes, portals, workflow designer, RBAC, audit trails, SSO, and REST on every entity.

low-coderbacportalswebhooks

Agent-ready

A real REST call. Today.

Every doctype is a versioned REST endpoint with filters, pagination, and field selection. Agents read and write through the same surface as your staff — RBAC and audit included.

# An agent fetching active patients
GET /api/resource/Patient
  ?filters=[["status","=","Active"]]
  &fields=["name","first_name","dob"]
  &limit_page_length=5

# → JSON response
{ "data": [{ "name": "PAT-0042", ... }] }
Modules

Hospital workflows end to end —
clinical, diagnostics, revenue, and ERP

From registration and ADT through lab, pharmacy, billing, and general ledger — one platform, one truth, no middleware tax.

Outpatient & inpatient care

Appointments, encounters, ADT, bed management, nursing checklists, and discharge — OPD and IPD on one chart.

opdipdadtbeds

Diagnostics & pharmacy

Lab orders, sample tracking, observations, radiology workflows, and medication requests tied to inventory.

lisrisloincrx

Billing, insurance & RCM

Invoicing, packages, payor contracts, eligibility, claims, and payments — clinical events drive revenue.

rcmclaimsinsurance

ERP backbone

GL, procurement, assets, HR, payroll, and multi-site company structure — no separate finance system.

erpnextglprocurement

Standards & compliance

FHIR R4, HL7, DICOM, LOINC, ICD-10, SNOMED-CT — plus HIPAA-ready patterns, ABDM, and NABH support.

fhirhl7abdmnabh

Customize without vendor tickets

Frappe low-code — new doctypes, reports, and workflows in days, not change-order quarters.

frappepythonworkflows

Comparison

Fossible HIS vs traditional HIMS

Most HIMS products stop at clinical workflows. Fossible HIS adds ERP, APIs, and open source — without extra vendors.

CapabilityTraditional HIMSFossible HIS + ERPNext
Clinical workflows (OPD, IPD)IncludedFHIR R4 compliant
Lab, radiology, pharmacyBasic modulesFull LIS, RIS, pharmacy
Accounting & GLSeparate systemMulti-currency GL built in
Billing & RCMBasic invoicingInsurance, claims, packages
Inventory & supply chainLimited or missingMulti-warehouse ERP
HR & payrollSeparate HRISFull HRMS on same stack
API accessLimited endpointsREST on every doctype
Source & licensingProprietary · per-seatGPL-3.0 · $0 seats

Ecosystem

Built on Frappe — trusted by
10,000+ organizations

You inherit a battle-tested open-source business platform, not a standalone app with a fragile plugin market.

10K+

Organizations

Run operations on Frappe/ERPNext worldwide.

50K+

Community

Forums, Frappeverse, and implementers.

300+

ERP modules

Extend beyond healthcare when you need to.

$0

Per-user fees

GPL-3.0 — full source, no seat tax.

140+

Countries

Multi-currency, language, and company.

Low-code

Frappe framework

Ship features in days, not months.

Compliance & standards

Healthcare standards,
not bolted on

FHIR R4InteroperabilityHL7MessagingDICOMImagingLOINCLab codingICD-10Diagnosis
SNOMED-CTClinical termsHIPAAUS privacy readyABDMIndia digital healthNABHAccreditation

Agent-ready

The next trillion users won't click.
They'll call.

REST on every doctype, Python workflows, and Hydra MCP — CareOps and ERP that AI agents can use on day one.

Auto REST on every doctype

Patient, Appointment, Lab Order, Inventory Item — CRUD via REST out of the box. No separate API layer to build or version.

Python execution environment

Server scripts, hooks, and background workers — agents trigger workflows with RBAC, audit trails, and rollback.

Hydra MCP

Typed MCP tools for any LLM client — read and act on live Fossible HIS through the same permissions as staff.

Policy-checked by default

Every agent action flows through validation, roles, and audit logging — no separate agent backdoor.

Built for

Multi-site enterprises that need
operational control

Multi-site hospital groups

Central admin, unified financials, shared formularies, and per-site access — one installation, many branches.

Diagnostic lab chains

High-volume LIS, LOINC coding, device integration, reagent inventory, and cross-location analytics.

Specialty & multi-specialty clinics

Per-specialty encounter templates, procedure sets, and billing rules on one consistent UX.

Greenfield health-tech ventures

Clinical plus operational backbone on day one — customize on Frappe low-code instead of rebuilding ERP.

Go deeper

Fossible HIS in the full stack

  • Need CareOps plus a FHIR CDR?

    Composable stack — Fossible HIS for operations, Medplum for clinical interoperability, and AI services when you need both planes.

    Health Central
  • Implementation, hosting, and sprints

    Espresso Cloud CI/CD, Fossible Sprints dev pods, and healthcare IT services to take Fossible HIS from pilot to production.

    Healthcare IT

FAQ

Frequently asked questions

What is Fossible HIS?

Fossible HIS is an open-source Hospital Information Management System built on Frappe/ERPNext. It unifies EHR, practice management, LIS, RIS, billing, inventory, HR, and pharmacy on a single platform with a single database, a single API, and zero per-user licensing fees.

Is Fossible HIS built on ERPNext and Frappe?

Yes. Fossible HIS is built natively on the Frappe Framework and ERPNext. It extends ERPNext Healthcare into a full Hospital Information Management System — so you get ERPNext's accounting, inventory, HR, and procurement alongside clinical EHR, LIS, RIS, pharmacy, and insurance on one Frappe/ERPNext stack, with every doctype exposed over REST.

Can I use Fossible HIS as an ERPNext Healthcare or Frappe Healthcare solution?

Yes. Fossible HIS is a production-grade ERPNext Healthcare / Frappe Health solution. If you are evaluating ERPNext for hospitals or building a Frappe healthcare app, Fossible HIS adds the clinical workflows, compliance (FHIR R4, HL7, ABDM, NABH), and multi-site operations that the base ERPNext Healthcare module does not — while staying fully open source under GPL-3.0.

Is Fossible HIS open source?

Yes. Fossible HIS is fully open source under the GPL-3.0 license. You get full source code access, can self-host anywhere, and there are no per-user licensing fees. The code is available on GitHub.

What healthcare standards does Fossible HIS support?

Fossible HIS supports FHIR R4, HL7, DICOM, LOINC, ICD-10, and SNOMED-CT. It is HIPAA-compliant ready and supports ABDM and NABH compliance requirements.

Who is Fossible HIS built for?

Fossible HIS is built for multi-site hospital groups, diagnostic lab chains, specialty clinics, health-tech startups, and government health programs that need an open-source, standards-compliant, self-hostable healthcare platform.

Is Fossible HIS AI-agent-ready?

Yes. Fossible HIS is agent-ready out of the box. Every doctype auto-exposes a REST endpoint, every workflow is scriptable in Python, and Hydra MCP gives any LLM client a typed MCP interface. AI agents can read and act on patient operations, clinical orders, billing, inventory, and ERP transactions — flowing through the same RBAC, workflows, and audit trail as human users.

What is Hydra MCP?

Hydra MCP is the agent surface for the operational stack. It exposes every Frappe doctype, workflow, and report in Fossible HIS as a structured, permissioned, auditable tool surface for AI agents. Agents operate through the same access controls and audit trail as human users — there is no separate agent backdoor.

How do AI agents interact with Fossible HIS?

AI agents interact with Fossible HIS through Hydra MCP — a Model Context Protocol server that exposes the entire CareOps and ERP layer as structured, permissioned tools. Agents can perform patient registration, clinical orders, billing and RCM, inventory management, workflow execution, and reporting. Every agent action flows through the same validation, permissions, and audit logging as a human action.

Ready to put agents to work on your hospital operations?

See Fossible HIS with your use cases — including Hydra MCP across every module. We'll walk through the platform, multi-site needs, and an implementation plan.