Platform overview
How ECG:Connect works end-to-end
These docs use ECG:Connect as the worked example. BM:Connect (bedside monitors), RAD:Connect (imaging) and LAB:Connect (lab) are installed and operated the same way — same gateway core, same control plane.
Architecture overview
ECG:Connect — one of OFFIN's X:Connect device gateways — is a two-component system:
The gateway — a Docker container installed inside your hospital network. It watches a drop folder for ECG files, parses them, stores records locally in SQLite, serves a clinical dashboard on your LAN, and sends HL7 messages to your HMIS.
The X:Connect Control Panel (cloud) — a PHI-free control plane hosted by OFFIN Healthcare. It licenses and manages the fleet, distributes AI models, and handles billing. No patient data is stored in the cloud — HL7 and FHIR R4 are served on-premise by the gateway/hub.
Key design principles
Data flow
| Step | Where | What happens |
|---|---|---|
| 1 | ECG device | Exports XML, PDF, or DICOM to drop folder via FTP or network share |
| 2 | Gateway | File watcher detects file in < 2 seconds; parser processes it |
| 3 | Gateway | Patient matched by MRN; record stored in local SQLite DB |
| 4 | Gateway | Rule-based AI flags computed on the gateway at ingest |
| 5 | Gateway | HL7 ORU sent to HMIS (and forwarded to the VitaLink hub, if present) |
| 6 | Gateway | Record + viewer served from the gateway dashboard on your LAN |
| 7 | Control Panel | Licence checked, fleet telemetry + usage counters reported — no patient data leaves the hospital |
Supported devices
- GE MAC Series (XML, DICOM)
- Mindray BeneHeart (XML, PDF)
- Philips PageWriter (XML)
- CardioSoft / GE MUSE (XML)
- Any DICOM 12-Lead Waveform Storage compliant device
Plans
| Plan | Users | Retention | Price |
|---|---|---|---|
| Basic | 5 | 30 days | $500/month |
| Professional | 25 | 1 year | $1,500/month |
| Enterprise | Unlimited | 7 years | Custom |
| Multi-site | Unlimited | 3 years | $1,000/gateway |