Compatibility
Supported hospital information systems
These are the HIS platforms we currently integrate with or have a defined integration path for. If your system is not listed, contact us — integration is typically a 2–4 week project.
Oracle Health (Cerner)
Gulf, Global
✓ Integration ready
REST API + HL7 FHIR R4. Patient lookup, bed/room data, and staff directory sync.
InterSystems TrakCare
UAE, Saudi Arabia, Middle East
✓ Integration ready
Web API. Room and patient context can be pushed to 1 CLICKAWAY on admission events.
iHIS / Meditour
UAE government hospitals
Roadmap Q3 2026
HL7 v2.x messaging over MLLP. Staff roster import available now via CSV.
Mediware / Quadramed
Saudi Arabia, GCC
On request
Contact us — we scope integration per hospital based on what API surface is exposed.
Epic
Global
✓ Integration ready
Epic FHIR R4 API. OAuth 2.0 authentication. Patient + room context on admission.
Custom / Other
Any
REST webhook
If your HIS can send a JSON POST to a URL, it can integrate with 1 CLICKAWAY. No special protocol required.
Standalone vs. Connected
What works without any HIS connection
No integration is required to go live. 1 CLICKAWAY operates entirely standalone. Doctors manually enter room and patient context when submitting a request. HIS integration is an enhancement — it pre-fills that data automatically.
- Full interpreter request workflow — standalone, Day 1
- Porter dispatch, ward nursing, pharmacy — all standalone
- Admin dashboard, reporting, and exports — all standalone
- Push notifications on locked phones — standalone
- NFC room tags (doctor taps sticker → request pre-filled) — standalone
Integration Methods
Two ways to connect
REST Webhook (Easiest)
Your HIS sends a JSON POST to a 1 CLICKAWAY endpoint when a patient is admitted, discharged, or moved. We use that event to pre-fill room and patient context for the next doctor request. No client-side changes needed.
Available now
HL7 FHIR R4 (Standard)
We query your FHIR server for Patient, Location, and Practitioner resources. Doctors see a patient search field in the app — type MRN or name, select, room is auto-filled. Requires FHIR R4 endpoint from your HIS vendor.
Enterprise plan
Data Flow
What data moves between systems
1 CLICKAWAY only reads context data from your HIS (room, patient name/MRN). It never writes back to the HIS unless you explicitly request a custom integration.
HIS (Cerner/
TrakCare)
TrakCare)
→
1 CLICKAWAY
API endpoint
API endpoint
→
Request
pre-filled
pre-filled
→
Doctor
confirms
confirms
→
Interpreter
dispatched
dispatched
Example: HIS sends admission event to 1 CLICKAWAY
// POST https://api.1clickway.com/v1/webhook/admission // Authorization: Bearer <api_key> { "event": "patient_admitted", "patient": { "mrn": "HP-204817", "name": "Ahmed Al Mansouri", "language": "Arabic" }, "location": { "ward": "Ward 4 ICU", "room": "Room 412", "bed": "A" }, "timestamp": "2026-06-04T09:15:00+04:00" }
1 CLICKAWAY returns
{
"status": "ok",
"context_id": "ctx_8f2a1b",
"expires_in": 3600,
"prefill_url": "https://1clickway.com/app.html?ctx=ctx_8f2a1b"
// Doctor opens this URL — request is pre-filled, no typing needed
}
For Hospital IT
What we need from your team
Integration is a 2-sprint project. Here is what we need from your IT department to scope and complete it:
- Name and version of your HIS (e.g. "Cerner Millennium 2021.1" or "TrakCare 2023")
- Whether your HIS exposes a FHIR R4 endpoint (ask your vendor)
- Whether your HIS can send outbound webhooks (POST to a URL on patient events)
- A sandbox or test environment for integration testing
- An IT contact for the 2-week integration sprint
No HIS yet? Many smaller private hospitals in the Gulf do not have a full HIS. 1 CLICKAWAY works completely standalone in those cases — no integration needed, ever. The manual entry workflow is fast enough for all operational purposes.