ThematticStart a project

Software and apps for health care

Hospitals, clinics, diagnostic labs and health programmes need software that is quick for staff, simple for patients and careful with medical data. We implement and extend OpenMRS 3.x and Bahmni, the open-source medical record systems used by hospitals and health programmes around the world, and build the booking, patient portal, lab and billing tools around them. Registration, records, lab, pharmacy and billing then work as one system instead of five.

  • 01OpenMRS 3.x and Bahmni medical records
  • 02Online appointment booking
  • 03Patient portals
Clinic recordsPatientsVisitsLabBillingPatientsNewPatientDepartmentTokenStatusSita B.General OPD014With doctorHari P.Cardiology015Vitals takenMaya G.Pathology016Sample collectedKiran S.Orthopaedics017WaitingGita R.General OPD018Checked inSynced just now

What slows health care down, and how we fix it

  1. Problem

    Patient histories sit in paper files and registers that no other department can search or see

    What we buildOpenMRS 3.x and Bahmni medical records

    Electronic medical records set up for your OPD, wards and emergency: registration, visits, vitals, diagnoses, orders and clinical forms, on open-source platforms with no licence fees.

  2. Problem

    Patients queue at reception to book or change appointments

    What we buildOnline appointment booking

    Patients pick a doctor and an open slot online, reminders cut no-shows, and bookings arrive in the clinic queue.

  3. Problem

    Lab reports are printed and collected in person

    What we buildPatient portals

    Lab reports, prescriptions and bills available securely online, on the web or a phone.

  4. Problem

    Records, billing, lab and pharmacy run on separate systems that do not talk to each other

    What we buildConnected hospital system

    Registration, records, lab, radiology, pharmacy and billing linked in one flow, with Bahmni’s Odoo and OpenELIS modules or the tools you already use.

What we build for health care

01

OpenMRS 3.x and Bahmni medical records

Electronic medical records set up for your OPD, wards and emergency: registration, visits, vitals, diagnoses, orders and clinical forms, on open-source platforms with no licence fees.

Clinic recordsPatientsVisitsLabBillingPatientsNewPatientDepartmentTokenStatusSita B.General OPD014With doctorHari P.Cardiology015Vitals takenMaya G.Pathology016Sample collectedKiran S.Orthopaedics017WaitingGita R.General OPD018Checked inSynced just now
02

Online appointment booking

Patients pick a doctor and an open slot online, reminders cut no-shows, and bookings arrive in the clinic queue.

03

Patient portals

Lab reports, prescriptions and bills available securely online, on the web or a phone.

04

Connected hospital system

Registration, records, lab, radiology, pharmacy and billing linked in one flow, with Bahmni’s Odoo and OpenELIS modules or the tools you already use.

05

Telehealth tools

Video consultations and follow-ups for patients outside the valley.

06

Reports and dashboards

Daily OPD, admission, lab and revenue figures for management, with exports for programme and government reporting.

OpenMRS 3.x and Bahmni

OpenMRS is the open-source medical record platform used by hospitals and national health programmes across Africa, Asia and Latin America. Version 3.x brings a modern, modular interface on top of it, and Bahmni packages OpenMRS with lab, billing, pharmacy and radiology into a complete hospital system. We set up, adapt and support both.

New implementations

We map your departments and patient flow, configure OpenMRS 3.x or Bahmni to match, install it on a server or in the cloud, and train your staff to use it.

Custom modules and forms

Clinical forms, concept dictionaries, order sets and new 3.x frontend modules for the services your hospital offers.

Integrations

Lab machines, PACS for radiology, Odoo for billing and stock, SMS reminders, and data exchange with other systems through FHIR and REST APIs.

Upgrades and migration

Moving from OpenMRS 2.x, older Bahmni releases or paper and spreadsheet records to OpenMRS 3.x or current Bahmni, without losing patient history.

Reporting

Ward, OPD and programme reports, plus data exports in the formats your funders and health authorities ask for.

Hosting and support

Backups, security updates, monitoring and a team in Kathmandu to call when something needs fixing.

Hospital software that staff will use

Hospital management software ties together everything that happens to a patient: registration, the consultation, lab tests, medicines, admission, billing and follow-up. When each of those runs on paper or on a separate program, staff copy the same details again and again, and nobody sees the whole patient.

Themattic builds and implements hospital and clinic systems in Nepal around OpenMRS 3.x and Bahmni, two open-source platforms designed for health care. They have no licence fees, the data stays on servers you control, and they can be extended as your services change. Around them we build the enterprise tools and the parts patients see: booking, patient portals, SMS reminders and reports delivered online.

This page explains what a complete hospital information system covers, how it connects to labs, pharmacies and government reporting, how patient data is protected, and how to roll it out without disrupting care. Whether you run a private hospital, a polyclinic, a diagnostic lab or a health programme, it should help you scope the project before you talk to any vendor, including us.

Signs your hospital needs a new system

It is usually time to look at hospital software when:

  • Doctors cannot see a returning patient’s past visits, results or medicines without the paper file
  • Registration, OPD tickets and billing each ask the patient for the same details
  • Lab results are written or typed twice before they reach the doctor
  • Pharmacy stock and expiry dates are checked by hand, and shortages are found too late
  • Monthly HMIS and programme reports take staff days to compile from registers
  • Management cannot see daily OPD numbers, admissions or revenue without asking each department

What a connected hospital system gives you

The practical gains hospitals and clinics look for.

One record per patient

A unique patient ID links every visit, test, prescription and bill, so the history follows the patient across departments.

Shorter queues

Online booking, token numbers and quick re-registration move patients through reception faster.

Fewer transcription errors

Lab orders go to the lab electronically and results come back into the record, with no retyping.

Control of stock

Pharmacy and store stock, batches and expiry dates are tracked as medicines are dispensed.

Reports without registers

Daily, monthly and programme reports are built from data staff already enter during care.

No licence fees

OpenMRS and Bahmni are open source, so you pay for setup, hosting and support, not for each user.

Hospital management software, explained

What to know before you choose or build a system for your hospital, clinic or lab.

Key features of a hospital information system

A complete hospital information system, often called an HIS or HMIS, is a set of connected modules. You do not need all of them on day one, but you should know which ones you will add later, so the first phase does not block them. The core modules are:

  • Patient registration with a unique ID, details in English and Nepali, and photo or ID card capture
  • OPD and appointment management, with doctor schedules, tokens and queue screens
  • Electronic medical records (EMR): vitals, history, diagnoses, clinical notes, orders and discharge summaries
  • IPD and ward management: admission, bed allocation, transfers, nursing notes and discharge
  • Laboratory information system (LIS): sample collection, barcodes, result entry, validation and report printing
  • Radiology orders and reports, linked to images stored in a PACS
  • Pharmacy and store: dispensing against prescriptions, batches, expiry dates and reorder levels
  • Billing: cash, credit, insurance and package billing, deposits and refunds
  • Reports and dashboards for clinicians, departments and management

Why we build on OpenMRS 3.x and Bahmni

Most hospitals do not need a medical record system written from scratch. Patient records, clinical concepts, orders and encounters are well understood problems, and OpenMRS has been handling them in hospitals and health programmes for many years. Version 3.x adds a modern, modular interface that is quicker for clinicians and easier for us to extend with new screens.

Bahmni packages OpenMRS with a lab system (OpenELIS), Odoo for billing, pharmacy and stock, and radiology support, so a hospital gets a working whole rather than separate parts. We use OpenMRS 3.x on its own for clinics, programmes and facilities that already have billing, and Bahmni when a hospital wants records, lab, pharmacy and billing from one stack. Where neither suits a narrow need, such as a small diagnostic centre, a lighter custom system can be the better answer, and we will say so.

Integrations: lab machines, PACS, HMIS and DHIS2

A hospital system is only as useful as the data that reaches it. Many health facilities and programmes report monthly indicators into DHIS2-based systems. Where you need this, we map the data in your records to the required indicators, then export it in the format asked for or send it through the DHIS2 API, after checking the details with your reporting team.

Other integrations we commonly plan for include:

  • Lab analysers that send results straight to the lab system, where the analyser supports an interface
  • PACS and DICOM viewers, so radiology images open from the patient record
  • Odoo or your existing accounting software for billing, purchases and stock
  • Health insurance claim workflows, set up to match the schemes and formats your hospital works with
  • SMS and email for appointment reminders and report-ready alerts
  • FHIR and REST APIs for data exchange with other systems, apps and partners

Patient privacy and data security

Medical records are some of the most sensitive data any organisation holds. We design access around roles, so a receptionist, a lab technician, a nurse and a doctor each see only what their work needs, and views and changes to records are logged.

Data is encrypted in transit, backed up on a schedule you can check, and hosted on a server in your hospital, in a data centre in Nepal or in the cloud, depending on what your organisation requires. Patient portals show results only after a verified login. Retention, consent and audit settings are configured to your requirements and your legal advice, rather than assuming one rule fits every facility.

Rollout and training without disrupting care

A hospital cannot stop seeing patients while new software goes in. We phase the rollout so each step is small and can be checked before the next:

  1. Discovery: we walk the patient flow with each department and agree the scope in writing
  2. Configuration on a staging server, using your forms, services, prices and drug list
  3. Migration of patient lists and, where practical, past records from spreadsheets or an older system
  4. Training by department, with short guides in plain language
  5. A pilot in one area, such as OPD registration, before wider go-live
  6. Go-live support, then a review of what staff found hard in the first weeks

Build, buy or implement open source?

Commercial hospital software can be quick to start with and suits facilities whose processes match the product. The trade-offs are licence or subscription fees, limited room to change the system, and data held in a form that may be hard to take elsewhere.

A fully custom build gives total control, but it is slow and costly for something as broad as a medical record. Implementing OpenMRS 3.x or Bahmni sits between the two: a mature open-source core, with your own forms, reports and integrations on top, and code you own. For a single feature, such as online appointment booking or a patient app, a custom build connected to your existing system is often the simplest route.

Our health-care toolkit

Open platforms and standards that keep your data portable.

  • OpenMRS 3.x
  • Bahmni
  • OpenELIS
  • Odoo
  • HL7 FHIR
  • REST APIs
  • DHIS2 API
  • Open Concept Lab
  • PACS and DICOM
  • React
  • MySQL and PostgreSQL
  • Docker
  • AWS
  • SMS gateways

How much does hospital software cost?

Open-source platforms remove licence fees, but setup, configuration, training, hosting and support are real work. We give a fixed written quote after a discovery visit. The main factors are:

  • The number of departments and modules in the first phase
  • How many clinical forms, order sets and reports need to be configured
  • Integrations with lab analysers, PACS, accounting, insurance or DHIS2
  • Migration of existing patient records, and how clean that data is
  • Hosting on your own server, in a data centre in Nepal or in the cloud
  • The number of staff to train and the number of sites
  • The level of support and monitoring you need after go-live

Why choose Themattic for health care

A Kathmandu team that implements, extends and supports OpenMRS 3.x and Bahmni for hospitals, clinics and health programmes.

Health platforms we know

We work with OpenMRS 3.x and Bahmni, from clinical forms and frontend modules to integrations and upgrades.

Fixed quote and contract

Scope, phases and price agreed in writing before work starts.

You own the system

Code, configuration and data belong to your organisation, with no licence lock-in.

Shared progress

You test each phase on a staging server before it reaches reception or the wards.

Training around shifts

Each department is trained on the tasks it does, scheduled around patient care.

Support from Kathmandu

Backups, updates and fixes from a team in Baluwatar and Tripureshwor you can reach.

How the project runs

Every project follows the same route, so you always know where it stands and what comes next.

01

Discovery & strategy

We learn your business, goals, competitors and users, then agree the scope and plan in writing.

  1. 1

    Discovery & strategy

    We learn your business, goals, competitors and users, then agree the scope and plan in writing.

  2. 2

    UX & UI design

    User journeys and screens designed and reviewed with you before any code is written.

  3. 3

    Development

    Responsive, fast and secure builds, shared with you as they progress.

  4. 4

    Launch

    Testing, speed optimisation and analytics set up before the site or app goes live.

  5. 5

    Support & growth

    Ongoing support, maintenance, training and improvements as your business grows.

Excellent communication and seamless project delivery — highly recommended for any business looking to build a strong online presence.

Ramesh GCRamesh GCCEO, EcoTours Nepal

Questions about software for health care

Can’t find your answer here? Send us a message and we will reply.

Other industries

Build for health care with us

Share what you want to build. We reply with next steps and a time for a discovery call, then a written quote.

  1. 1
    We reply with next steps

    A short email from our team, usually with a few questions about goals and timing.

  2. 2
    Discovery call

    Thirty to sixty minutes on your business, users and what success looks like.

  3. 3
    Written proposal and quote

    Scope, timeline and a fixed price, before any work begins.

info@themattic.com

We use your details only to reply to this enquiry. See our privacy policy.