Get More
Technical Information
Technical documentation and FAQs, with case studies and blog articles coming soon
Technical Documentation
Drive Product Datasheet
Complete product overview, specifications and supported device list (PDF).
New version coming soon
FHIR Integration Guide
Data mapping, API call examples and resource type reference.
Coming soon
API Documentation
Complete REST API reference with sample requests.
Coming soon
Frequently Asked Questions
Q: Does Drive need a separate server?
Yes. We recommend a central server to receive and store the data uploaded by Drive. See the Specifications section on the product page for requirements.
Q: Which medical devices are supported?
Currently Dräger, Hamilton, Maquet, GE, Philips, Mindray and other major brands, with more added continuously. If your device isn't listed, talk to us about a custom integration.
Q: Is data stored in the cloud?
Your choice. By default, data can be stored on the hospital's own servers, and cloud backup or a hybrid architecture can be configured on request.
Q: How is security handled?
Drive runs on an RTOS architecture, so it carries none of the vulnerability exposure of a general-purpose operating system. Data is uploaded to a server designated by the site (an in-hospital server by default), and transmission can run over a VPN or an encrypted network.
Q: How long does deployment take, and what does it involve?
It depends on scale, but a typical unit completes evaluation and deployment in 2 to 4 weeks. We support you through requirements analysis, device inventory, testing and staff training.