The business mandate
The mandate.
Give disease managers a coordinated view of what happens between clinical visits, then connect that information to patient engagement and access to care. Monitoring needed to support a working intervention process rather than create another isolated data stream.
Executive priorities
- Improve visibility between visits. Home readings and self-reported symptoms supplied information to the health-plan disease management team.
- Connect signals to outreach. Alerts, visualization, IVR and live communication linked monitoring with care-manager engagement.
- Address practical access barriers. Transportation integration supported access to primary care as part of the coordination workflow.
From home signals to coordinated care. Home measurements and symptom reporting connect to a monitoring platform, professional review and practical support for the member.
The return signal represents member outreach and engagement.
Pilot objective: reduce 30-day readmissions and unnecessary emergency-department use. No quantified clinical or financial outcomes are reported. Disease managers retain responsibility for clinical interpretation, engagement and care coordination. The diagram represents the reported workflow, not a specific network topology.
Reported scale and delivery
What was delivered. At what scale.
The delivered pilot joined connected devices, symptom self-reporting, data visualization, chat and video, IVR outreach and transportation coordination. Reducing 30-day hospital readmissions and unnecessary emergency-department use were program objectives. No quantified clinical or financial outcome is reported for the pilot.
Reported project figures. Selected experience of the team behind AIGard.
From scope to operations
The capabilities that connected the service journey.
Bring home measurements into one workflow
Withings blood pressure cuffs and weight scales, Fitbit activity monitors and Accu-Chek glucometers contributed data to a central team of HMO-employed disease managers.
Surface changes for professional review
Monitoring included rapid weight changes, elevated blood pressure or glucose readings, and medication-adherence information. Disease managers reviewed these signals in clinical context; the platform is not presented as an autonomous diagnosis or treatment system.
Capture symptoms beyond connected devices
Interactive voice response supported symptom self-reporting and case-manager outreach, engaging members outside an app-only experience.
Connect monitoring and communication
Web and mobile interfaces supported longitudinal visualization and chat and video consultations, with Twilio communications and Mirth Connect for HL7 integration.
Close the access gap
An Uber integration supported transportation to primary care, connecting the digital workflow with a practical service.
Governance and control
Disease managers remained responsible for clinical interpretation, member engagement and care coordination. Monitoring, visualization and outreach supported this human-led workflow.
Technology and integration
The platforms behind delivery.
- Application language
- Java
- Web server and application runtime
- Eclipse Jetty
- Cloud and operating environment
- AWS, Ubuntu virtual machines
- Database
- MySQL
- Communications service
- Twilio
- Healthcare interoperability
- Mirth Connect, HL7 messaging
- Connected health devices
- Withings blood pressure cuffs and weight scales, Fitbit activity monitors, Accu-Chek glucometers
- Transportation integration
- Uber
- Other supplied platform components
- Citrix, Apache
The integration scope spans connected devices, healthcare messaging, patient communications and transportation. Technologies, equipment brands and companies are named to describe the work. They do not indicate endorsement or direct AIGard client relationships.
Relevance to enterprise leaders
Relevant to health plans and chronic-care programs seeking to connect monitoring with operational follow-through. The experience spans connected devices, healthcare messaging, member engagement and transportation coordination.
Discuss a remote monitoring and care-management pilot.
Schedule a Call →More team experience
Other platforms our team has built.
All Health
Conversational AI connected to diagnostic data and clinical care.
Read the case study
Applied AI in Healthcare
Diagnostic AI embedded in the clinician workflow.
Read the case study
Agentic Commerce for Distribution
Connecting enterprise data, product intelligence and commercial execution.
Read the case studyFAQ
Remote Disease Management: frequently asked questions
What was delivered in the Remote Disease Management project?
The team piloted a remote disease management platform for an undisclosed Optum HMO, connecting home-device readings, symptom reporting and disease-manager outreach. The program targeted members with CHF and COPD and related comorbidities, with reducing 30-day readmissions as its objective.
The delivered pilot joined connected devices, symptom self-reporting, data visualization, chat and video, IVR outreach and transportation coordination. Reducing 30-day hospital readmissions and unnecessary emergency-department use were program objectives. No quantified clinical or financial outcome is reported for the pilot.
What business problem did Remote Disease Management address?
The mandate was to give disease managers a coordinated view of what happens between clinical visits, then connect that information to patient engagement and access to care. Monitoring needed to support a working intervention process rather than create another isolated data stream.
What capabilities did the Remote Disease Management work include?
The work connected the following capabilities:
- Bring home measurements into one workflow. Withings blood pressure cuffs and weight scales, Fitbit activity monitors and Accu-Chek glucometers contributed data to a central team of HMO-employed disease managers.
- Surface changes for professional review. Monitoring included rapid weight changes, elevated blood pressure or glucose readings, and medication-adherence information. Disease managers reviewed these signals in clinical context; the platform is not presented as an autonomous diagnosis or treatment system.
- Capture symptoms beyond connected devices. Interactive voice response supported symptom self-reporting and case-manager outreach, engaging members outside an app-only experience.
- Connect monitoring and communication. Web and mobile interfaces supported longitudinal visualization and chat and video consultations, with Twilio communications and Mirth Connect for HL7 integration.
- Close the access gap. An Uber integration supported transportation to primary care, connecting the digital workflow with a practical service.
- Governance and control. Disease managers remained responsible for clinical interpretation, member engagement and care coordination. Monitoring, visualization and outreach supported this human-led workflow.
Which technologies were used in Remote Disease Management?
The reported technology and integration scope was:
- Application language: Java
- Web server and application runtime: Eclipse Jetty
- Cloud and operating environment: AWS, Ubuntu virtual machines
- Database: MySQL
- Communications service: Twilio
- Healthcare interoperability: Mirth Connect, HL7 messaging
- Connected health devices: Withings blood pressure cuffs and weight scales, Fitbit activity monitors, Accu-Chek glucometers
- Transportation integration: Uber
- Other supplied platform components: Citrix, Apache
The integration scope spans connected devices, healthcare messaging, patient communications and transportation.
Are the figures in the Remote Disease Management case study AIGard client results?
They are reported project figures and describe selected experience of the team behind AIGard.
The case study separates delivered scope and reported scale from measured outcomes. Technology and company references describe the work; they do not imply endorsement or a direct AIGard client relationship.
Which organizations is the Remote Disease Management experience relevant to?
Relevant to health plans and chronic-care programs seeking to connect monitoring with operational follow-through. The experience spans connected devices, healthcare messaging, member engagement and transportation coordination.
Can AIGard build something similar for us?
Yes. The same disciplines are available through staff augmentation, dedicated teams or software outsourcing.
Tell us what you are building, and on a 30-minute call we will recommend an engagement model, a team shape and first milestones.
How does AIGard protect our data and systems?
NDAs are signed before any access is given, and engineers work inside your environment under least-privilege access, with permissions limited to their responsibilities.
Access is reviewed as roles change and removed when work ends. Our practices align with ISO 27001, SOC 2, GDPR and HIPAA, with PII masking, encryption and audit logging built into data work. We review your access policies, data-handling needs and vendor requirements during scoping.
How quickly can AIGard engineers start?
Engineers typically start within two to four weeks of the scoping call. The exact date depends on the roles, seniority and number of people required.
We confirm a realistic start date in writing before you commit, and you meet the proposed engineers before work begins.