Capabilities and compatibility
Check the workflow, not just the app name.
Status reviewed 10 September 2026. Support depends on the application version, operating system, permissions and intended task.
Current evidence register
| Capability | Status | Scope and limitation |
|---|---|---|
| Hospital application stack | Prototype-tested | Bahmni, OpenMRS, OpenELIS and Orthanc; defined workflows only. Versions, test artefacts and deployment suitability must be confirmed. |
| Browser and web applications | In validation | Do not assume arbitrary websites or authenticated workflows are supported. |
| Files, PDFs and spreadsheets | In validation | Homepage document/workbook examples are illustrative, not proof of general support. |
| Email and productivity suites | Planned | No general production integration is represented here. |
| CRM and business platforms | Planned | Specific integrations require separate confirmation. |
| Citrix, VDI and legacy systems | Custom evaluation | Assess the exact application, access path and workflow. |
| SAP, Oracle and internal systems | Custom evaluation | Do not infer compatibility from a product category. |
| SDKs and Embedded | Private evaluation | No public self-serve package or stable API is published. |
This register preserves the currently documented evidence. A plan or architecture description does not expand the supported application set. Confirm your intended workflow before use.
Know what to verify.
Ask for the tested version, device requirements, a representative run, expected output and failure/recovery behaviour. The installed product should check device compatibility; this website does not perform that check.