Frequently asked questions
What your committee will ask.
Plain answers to the questions every evaluation raises — deployment, data, safety, security, and cost.
Where does CareIT HMS run?
Each facility gets a dedicated instance with its own database — your patients never share tables with another institution. We host and manage it; self-managed deployment on your own infrastructure can be arranged from the same codebase.
Who owns our data?
You do. Your facility’s data lives in a database that is yours, reporting exports ship in the product, and if you ever leave, the database goes with you.
Can clinicians edit the record?
They can amend it — never silently edit it. Clinical data is append-only: an amendment supersedes the prior version and both stay readable, with authorship on each. That is what makes the record defensible.
What happens to a critical result at 2 a.m.?
The verifying clinician flags it (or an explicit rule does), everyone with authority to acknowledge is notified in-app, and an escalation deadline starts running. If nobody acknowledges in time, it escalates again. The patient portal never auto-releases a critical result.
How does billing stay honest?
Invoices are raised from charges captured at the point of care — never typed in at the desk. Discounts need an approver other than the requester, drafts owe nothing until finalized, cashier drawers reconcile cash only, and a charge can never ride on two claims.
Which modules do we get?
CareIT HMS has 29 modules across three tiers — outpatient core (patients, scheduling, EMR, orders, lab, billing), full hospital (inpatient, ED, pharmacy, radiology, claims, patient portal), and specialties (ICU, theatre, maternity, dental, and more). Module toggles double as licensing, so you enable what you license and add the rest later.
Is it secure enough for a hospital?
Two-factor authentication with TOTP and recovery codes, per-action permissions with audited break-glass, a hash-chained audit log that includes PHI reads, and encrypted identifiers with blind indexes. See the Security page for the complete picture.
Does it integrate with what we have?
The platform is API-first: 240+ documented endpoints under an OpenAPI 3 spec, covering everything the UI does. Accounting exports batch to your GL, radiology carries PACS study metadata, and the patient portal and mobile sync are API-ready today. Payer e-claims adapters are on the roadmap.
How much does it cost?
Four editions, priced by facility size — Outpatient Core at $249/month for clinics, Full Hospital at $749/month for admitting facilities up to about 150 beds, Enterprise from $1,999/month for multi-site networks, and Enterprise Plus from $5,000/month when you need high availability, disaster recovery, 24/7 support, and on-premises or hybrid deployment. Annual billing saves 15%. Each starts with a one-time implementation: a flat $3,500 for Outpatient Core, from $12,000 for hospitals, quoted above that — payable upfront or spread across 12 or 24 monthly installments, depending on the contract you sign. Quotes are shaped by beds, sites, staff accounts, the modules you enable, and your deployment model. You are never billed per patient. See the Pricing page for the full breakdown.
How fast can we go live?
Phased: outpatient core first, then wards and specialties as teams are trained. Discover, configure, enable, train, go live — the implementation section above is the actual process.
Something we didn’t cover? Ask us directly — we reply within one business day.
See your hospital running on one system.
A live walkthrough on the real product — registration to results to billing — mapped to how your facility actually works.