Home/ Docs/Platform overview

Platform overview

How ECG:Connect works end-to-end

3 min read

Architecture overview

ECG:Connect is a two-component system:

  1. 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.

  2. The cloud platform — a multi-tenant SaaS platform hosted by OFFIN Healthcare. It receives sync'd records, runs analytics and AI interpretation, manages billing and licenses, and provides FHIR R4 endpoints.

Key design principles

Offline-first. The gateway operates entirely on your hospital LAN with no internet required. Cloud sync is automatic when connectivity is available, and queues cleanly when it isn't.

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 HL7 ORU message sent to HMIS (if configured)
5 Gateway Record queued for cloud sync
6 Cloud Sync received, validated against license and plan limits
7 Cloud AI interpretation queued and processed
8 Gateway AI result returned on next sync poll

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