Legal
Terms of use
These terms govern the HospitalMgr website and, together with a signed quotation, proposal, or hospital contract, the HospitalMgr software. The signed hospital contract wins if it conflicts with this page. Privacy is described in the Privacy policy.
1. Who these terms bind
The operator is Digital Monster Uganda (“we”, “us”). “You” means the person browsing this site, the person requesting a demo, or the facility (hospital, clinic, pharmacy, dental practice, health centre, or government site) that buys or trials HospitalMgr, including its staff who log in.
If you click “Request a demo”, create a user, or use the software, you accept these terms. If you buy for a facility, you confirm you have authority to bind that facility.
2. The product
HospitalMgr is hospital, clinic, and pharmacy operations software: patients, appointments, prescriptions, laboratory, radiology, pharmacy, IPD, antenatal, dental, ambulance, insurance, finance, accounting, HR, reports, communication, configuration, backups, and optional AI settings. Modules are licensed as agreed. We may improve, add, or retire features with notice when a change is material.
HospitalMgr is not a substitute for a licensed clinician, pharmacist, or accountant. Staff remain responsible for clinical judgement, dispensing, billing accuracy, and statutory reports.
3. Website and demos
This marketing site is informational. Prices, timelines, and module lists on it are invitations to talk, not a binding offer. A demo is a walkthrough. It does not create a licence until we accept an order and you pay (or a written trial letter says otherwise).
Demo requests should be truthful about facility type and what you need to see. We may refuse a demo that looks like competitive scraping or abuse.
4. Accounts, hospitals, and access
- Each live facility is a tenant. Users, patients, stock, invoices, backups, and AI keys belong to that hospital record.
- The facility names an administrator. That person grants roles. We are not responsible if an administrator over-shares access.
- You must keep passwords secret, retire staff who leave, and tell us promptly if you suspect misuse.
- Login logs exist so the facility can see who signed in. Do not disable security you need for an audit.
5. Licence
While fees are paid and these terms (and the hospital contract) are in force, we grant the facility a non-exclusive, non-transferable right to use HospitalMgr for its own operations in the licensed sites and user counts. You do not buy the source code, trademarks, or documentation copyright unless a separate agreement says so.
You may not resell HospitalMgr, clone it, scrape it to build a competing HIS, reverse engineer it except where the law cannot be waived, or put another organisation’s patients into a tenant that is not theirs.
6. Your duties
- Use the software only for lawful healthcare, pharmacy, and administration.
- Enter accurate master data (users, items, payers). Garbage in remains garbage out.
- Obtain any patient or staff consents your law requires.
- Keep local copies of anything you must retain if the law says the facility, not the vendor, holds the record.
- Train staff; we train as scoped in the implementation, not every future hire forever unless support says so.
- Provide a named in-charge for go-live.
- Do not upload malware, attack the platform, or attempt to read another hospital’s tenant.
7. Fees, implementation, and support
Licence, implementation, training, devices, and support are priced in the quotation. Unless stated, fees are exclusive of taxes. Late payment may suspend access after notice. Suspension does not erase your duty to pay amounts already due.
Implementation follows the counters you actually run. We do not promise a 500-bed theatre suite on a 20-bed clinic order. Change requests after scope lock may be extra.
Support hours, channels, and severity targets live in the hospital contract. Emergency clinical care is never “wait for a ticket”; treat the patient, then record.
8. Connectivity, Windows, and mobile
HospitalMgr is used as a connected platform with a Windows client and mobile systems. Unreliable internet is normal in the markets we serve; even so, we do not warrant uninterrupted uptime. Plan paper fallback for the hour the fibre dies. Backups are the facility’s safety net; keep restore permissions with people who can be reached at 7 a.m.
9. Backups and AI
Hospital-scoped gzip backups and restore are part of the product design. You must still run backups on the agreed schedule and test that a restore is possible. We are not liable for data you never backed up, or for a restore the administrator refused to authorise.
AI settings are optional. API keys you save are encrypted. Output from a model can be wrong. Do not let a model prescribe, diagnose, or post accounts without a human. Token and provider costs are the facility’s unless the quotation says we include a pool.
10. Intellectual property
HospitalMgr, the logo, this website, and our documentation are owned by Digital Monster Uganda or its licensors. Facility data (patients, invoices, notes) remains the facility’s. We may use anonymised, aggregated operational statistics to improve the product, never to publish a named patient’s file.
11. Confidentiality
Each side will keep the other’s non-public information confidential: our pricing and code; your patient and commercial data. Exceptions: information already public, independently developed, or demanded by law (with notice where legal).
12. Warranties and disclaimer
We warrant that we will provide HospitalMgr with reasonable skill and care, consistent with a Kampala software house shipping operational systems. Except as the hospital contract states in writing, the software is otherwise provided as available. We do not warrant that it will catch every clinical error, every expired batch, or every insurance rejection.
13. Liability
We are not liable for indirect loss, lost profit, lost stock, failed claims, or clinical outcomes. Our total liability arising from the website or the software in any twelve months is capped at the fees you paid us for HospitalMgr in that period, except where Uganda law forbids a cap (for example proven fraud or death caused by our negligence, if a court so finds).
Nothing in these terms limits liability that cannot be limited by law.
14. Indemnity
The facility will defend and pay claims that arise from its clinical decisions, unlawful processing of patient data, staff misuse, or content it stores in HospitalMgr, except to the extent we caused the claim by breaking these terms.
15. Term and termination
Website terms last while you use the site. Software terms last for the licence period. Either side may terminate for a material breach that is not cured within 30 days of written notice, or immediately for unpaid fees after the notice in the contract.
On exit we will, as scoped, help export hospital-scoped data, then delete or disable the tenant. You must download what you need before the exit window closes.
16. Governing law
These terms are governed by the laws of Uganda. Courts of Uganda have exclusive jurisdiction, unless the hospital contract names arbitration in Kampala.
17. Changes
We may update this page. The date at the top is the current version. For a paying facility, material changes take effect on renewal or 30 days after we notify the account contact, whichever the contract allows.
18. Contact
Digital Monster Uganda · HospitalMgr
Email: hello@digitalmonster.ug
Request a demo or send a legal notice via the contact page