FEATURES / RAKT
Hospital software
features, explained.
See how RAKT handles patient records, billing, stock, reports, and integrations. Each feature page explains what the software does and what to check in a demonstration.
Explore the detailSHARED FOUNDATIONS
Records used
across departments.
Patient records
Find a patient’s visits, clinical notes, and investigation requests through the same patient record. Each consultation or admission has its own record, so staff can tell previous care from the current visit.
02 / SHARED CAPABILITYBilling & payments
See which consultation, investigation, medicine, or admission produced a charge. RAKT keeps invoices, individual charges, payments, and refunds in the same system.
03 / SHARED CAPABILITYInventory & stores
Record hospital items, quantities, receipts, issues, transfers, and expiry dates. Use the stock history to see where an item is held and why its quantity changed.
04 / SHARED CAPABILITYReports & analytics
Prepare department documents and review hospital activity. Explore the report examples, then check which records, dates, and statuses contribute to the totals your team uses.
05 / SHARED CAPABILITYAPIs & integrations
RAKT has API keys, app permissions, and webhooks for connecting other systems. Agree what information will be exchanged, who can access it, and how failures will be handled.
Follow a patient through the hospital
A returning patient may need an earlier report during a consultation. A ward transfer changes the admission record, and the cashier needs to know which services produced the bill. Staff in different departments need to find those records for the same patient.
RAKT combines department workflows with shared patient, visit, organisation, and financial records. Explore the capability pages below alongside the department demonstrations. The demonstrations use fictional data and explain a workflow; they are not a live hospital account.
Find the feature you want to review
The patient records page explains how a patient’s identity relates to their visits and admissions. Billing follows the relationship between an invoice, its line items, and payments. Inventory separates item definitions from quantities, movements, and expiry. Reporting distinguishes clinical documents from management information. Integrations sets out the questions to ask before connecting another system.
Each page includes practical review questions. Use them to turn a product demonstration into a working session with the people who will use the system. Bring examples of your existing forms, charges, and handoffs, with personal data removed.
Check the work in each department
Each department has different tasks to complete. Laboratory work includes specimen tracking, verification, signing, and release. Pharmacy dispensing depends on usable batch stock. Inpatient care needs beds, admissions, transfers, and discharge documents. A feature checklist is only complete when these distinctions have been tested.
Visit the seven department pages to try their separate examples. Then use the buying guide to record what was demonstrated, what needs configuration, and what still needs confirmation. Record which requirements are included, which need setup, and which remain unresolved.
COMMON QUESTIONS
Questions about this topic.
Does every feature work the same way in every department?
No. Patient and financial context can be shared while each department has its own workflow, permissions, and records.
Are the website examples a live product account?
No. They are interactive explanations using fictional data. Create an account or arrange a walkthrough to inspect the application itself.
PLAN A DEMONSTRATION
See how RAKT handles
your team’s work.
Use fictional examples or blank formats. Keep patient information out of an initial enquiry.