LATEST

Care Connect — Operations

Care Connect is a 24/7 telecare alarm response service for elderly clients in Jersey, Channel Islands. Their existing system routed SOS alerts through a four-hop chain — pendant → SMS → relay → webhook with no monitoring at any stage. A device went offline undetected, leaving a client without emergency cover.

smartData built a purpose-built Operations Dashboard that connects EV12 pendants directly, surfaces SOS, device-offline, and low-battery alerts in real time, and embeds full client context address, medical conditions, emergency contacts on every alert.

The platform replaces Microsoft Power Apps as the client management tool, giving operations staff a single workspace for the entire monitoring workflow. Built on ASP.NET Core with Blazor, MQTT, and WebSocket infrastructure, the MVP delivers eleven functional modules across a 10-week timeline.

Features

  • Real-time Alert Dashboard: Live operations view with severity-coded SOS, offline, and low-battery alerts updating via WebSocket — no page reload required
  • Full Client Context on Alerts: Every alert surfaces the client's name, age, address, medical conditions, and emergency contacts in a single detail view
  • Device Fleet Monitoring: Fleet-wide visibility of battery %, connectivity %, last check-in, and firmware version per device with automated threshold alerts
  • EV12 Direct Integration: Vendor-agnostic adapter layer connects EV12 pendants via TCP/IP, eliminating the four-hop SMS relay and its silent failure points
  • Audit Trail & Workflow: Immutable log of every alert action, staff login, and device change with one-click status transitions from New → Acknowledged → Resolved

Technical Challenges

  • Challenge 1:EV12 device API documentation was incomplete at project start, risking integration delays in the critical path of the build.
  • Solution: Built a device simulator in Week 1 to allow parallel frontend and backend development; integration was slotted for Week 3 once vendor credentials were confirmed, keeping the overall timeline intact.
  • Challenge 2: Ensuring zero dropped SOS alerts under high device load — a safety-critical requirement where a missed event could result in a client not receiving emergency assistance.
  • Solution: Webhook receiver drops events to a Redis message queue and returns 200 OK instantly; the event processing engine consumes from the queue asynchronously, decoupling ingestion from processing and guaranteeing no event loss.
  • Challenge 3: Handling GDPR-compliant storage of sensitive client medical data including conditions, emergency contacts, and care notes in a healthcare context.
  • Solution: Embedded GDPR compliance requirements into the data model in Week 1 before schema finalisation; TLS 1.3 in transit and AES-256 at rest applied across all client data fields from the first migration.
  •  
Click to read more