Custom integrations
Work Rhazes builds into your deployment for systems and processes the standard product does not already cover.
Updated
What this covers
Some things an organisation needs are specific to that organisation. A local system with its own API, a document format that has to match an existing template exactly, a data flow into a warehouse, a pathway that spans systems Rhazes has never met.
Custom integration is the route for those. Because your deployment is your own, work built for you can go into it without waiting on anyone else's roadmap.
Try the product first
Genuinely. A large proportion of what gets raised as a custom requirement turns out to be something Rhazes already does under a different name.
Before commissioning anything, check whether these cover it:
- Workflows, which automate multi-step clinical work, run on a schedule and chain together. They are the most under-estimated part of the product. See What a Rhazes workflow is.
- Templates and fillable PDF forms, which reproduce a document your organisation has already agreed. See Templates.
- Spaces, which put your own guidelines and policies behind every answer. See What a Rhazes space is.
- EHR integration, which covers any system on SMART on FHIR. See EHR integration with Rhazes.
If one of those does it, you get it now rather than after a build.
How an engagement works
Custom work is scoped with us rather than configured by you. In outline:
- Tell us the problem, not the solution. What the clinician is doing today, how long it takes and where it goes wrong. The best integrations come out of that conversation looking different from what was first asked for.
- We work out what is already possible, and what genuinely needs building.
- Scope, timeline and cost, agreed before anything starts.
- Build, then pilot with a small group before it goes near a whole department.
What we will tell you honestly
If something is a bad idea, or if the effort is out of proportion to what it saves, we would rather say so than build it. That includes cases where the honest answer is that a person should stay in the loop and the automation should stop short.
Getting started
Email support@rhazes.ai with what you are trying to achieve, which systems are involved, and who at your organisation would need to approve it.