Integrations
ACOS plays well with what you already have.
Replacing one system shouldn't mean replacing twenty.
Your hospital is a system of systems — lab analysers, accounting software, payment gateways, the messaging tool nurses already use. ACOS is built API-first and standards-based to fit alongside the tools you depend on, not demand that you rip them out.
Philosophy
API-first. Standards where they exist. Pragmatic where they don't.
Healthcare interoperability standards (HL7, FHIR, ICD-10, LOINC) cover most of what matters. We support them. For the things they don't cover — Ghana-specific NHIS portals, M-Pesa and MTN MoMo, your accountant's preferred export format — we build pragmatic adapters.
Categories
What ACOS connects with.
A non-exhaustive list of the systems we integrate with today, organised by what they do for your hospital.
Laboratory equipment
HL7 v2 · ASTM · LIS
ACOS receives results from lab analysers automatically: order goes out, sample is taken, instrument runs, result lands in the patient record and on the bill in minutes — not hours, not on a slip of paper that gets lost between departments.
Examples · Roche Cobas, Sysmex, Mindray, Beckman Coulter — and most analysers that speak the standards.
Imaging and PACS
DICOM · HL7
Radiology orders and reports flow through ACOS; images stay on your PACS but are linked from the patient record. Radiologists keep their viewer; clinicians get the report where they actually look.
Examples · GE Centricity, Carestream, generic DICOM modalities.
Payments
Native
Patients pay how they actually pay in Ghana — mobile money, card, or cash. Each transaction is reconciled against the bill automatically. No more matching M-Pesa receipts to encounter numbers by hand.
Examples · MTN Mobile Money, Vodafone Cash, Visa/Mastercard via local processors.
Accounting
CSV · API · Custom
Daily revenue, receivables, and expense entries can be exported in your accountant's preferred format — or pushed via API for facilities that want real-time book sync.
Examples · Tally, QuickBooks, Sage, Xero, Excel.
Pharmacy procurement
API · CSV
Stock receipts, drug catalogues, and price lists flow into ACOS so dispensing reflects what's actually on the shelf and what's actually billable.
Examples · Local pharmaceutical distributors, GHS NHIA medicines list, custom formularies.
Messaging and notifications
WhatsApp Business · SMS
Appointment reminders, prescription pickup notifications, and follow-up nudges go out by WhatsApp or SMS — the channels patients actually read in Ghana, not the inboxes they don't.
Examples · Twilio, Africa's Talking, WhatsApp Business API.
Insurance and claims
Custom per-payor
Claim forms generated from the encounter with the right diagnostic and procedure codes, ready for submission. Each insurer has a different submission portal; we adapt to yours.
Examples · Private insurers including Apex, Acacia, Glico Healthcare; NHIS where applicable.
Identity and SSO
OAuth 2.0 · OIDC · SAML
If your hospital uses Google Workspace or Microsoft 365, staff sign in to ACOS with the accounts they already have. No new password to forget.
Examples · Google Workspace, Microsoft 365, Okta, Auth0.
Don't see yours?
Custom integrations are real engineering. We scope and quote them.
If a system you depend on isn't on the list, we'll evaluate it during discovery. Some integrations are a day of work; some are a few weeks. We'll be honest about which yours is — and which path makes sense.
Standards-based
DaysIf the system speaks HL7, FHIR, DICOM, or another healthcare standard, integration is a configuration exercise. Usually included in the base implementation.
Custom adapter
1–3 weeksIf the system has an API or a clean export format but isn't standards-based, we build a thin adapter. Scoped during discovery, quoted before work starts.
Heavy lift
4+ weeksLegacy systems with no API and no export tooling are a real engineering project. We'll be upfront about cost and timeline — and whether it's worth doing at all.
One honest note
Sometimes the right integration is no integration. If your existing tool is doing one job poorly and ACOS already does it well, the simpler answer is to retire the tool — not to build a bridge that preserves a problem. We'll tell you when that's the case.
For technical buyers
A few specifics, for the IT lead reading this.
API
REST + GraphQL. Authenticated via OAuth 2.0 client credentials. Rate-limited per tenant. Sandbox environment available during integration.
Webhooks
Outbound webhooks on key events (encounter created, bill finalised, lab result available). Signed payloads, retry on failure, configurable per integration.
Data export
Full data export available on request — CSV, JSON, or SQL dump. Your data is yours. We don't lock it up.
Sandbox
A clean sandbox tenant for integration testing, populated with synthetic patient data. Promote tested integrations to production with one click.
The ask
Tell us what you already use. We'll map the rest.
During the discovery call, we go through your existing systems one by one and map a path: standards-based, custom adapter, or honest 'don't bother.'