Vital Sense
One platform for patient-reported readings and clinician oversight, built for patients of any age. Maternal hypertension is one application; Vital Sense is built to monitor older adults and others for conditions like hypertension and diabetes.
Remote monitoring that only worked for one condition, and one clinic’s trust.
Home-health providers and clinics manage patients across ages and conditions, not just one. A platform built narrowly around a single use case does not extend to the rest of a clinic’s caseload, and a platform that cannot prove data isolation does not earn the trust of a privacy officer.
- A monitoring pathway built for one condition (maternal hypertension) does not serve a clinic’s older-adult or diabetes patients without being rebuilt.
- Patient onboarding that ignores gender, age, pregnancy status, medical history, and medications cannot route each patient to the right monitoring pathway.
- Clinics need proof that one clinic’s data is never visible to another, not just a policy statement, especially when access is provisioned through the clinic’s own IT.
- Automated readings without a clinician gate risk guidance reaching a patient before a clinician has reviewed it.
From onboarding to clinician action.
How a patient of any age onboards, connects to a clinic, and how a reading becomes reviewed guidance.
Patient onboards
Signs in, completes a profile (age, pregnancy status, history, medications), and links to a clinic with an access code.
Shares a reading
Vital Sense checks and prioritizes the reading for the care team.
Clinician reviews
On the web dashboard, within the clinic’s isolated data.
Action back to patient
The clinician approves guidance before it reaches the patient.
Guidance to the patient goes out only after clinician review and approval. The profile, not a fixed script, routes each patient to the right pathway, from expectant mother to older adult.
Five workstreams, one monitoring loop.
Vital Sense has expanded from maternal hypertension monitoring into a platform built to monitor older adults and others for conditions like hypertension and diabetes, with clinic partnership, onboarding, and security built in from the start.
Patient onboarding
Sign-up, health profile, clinic connection, and guided setup, in four steps.
Patients sign up with email, or Google or Apple, confirm their email, and set consent. They complete a profile covering gender, age, pregnancy status, medical history, and current medications, then enter the access code their clinic provides to link accounts. Guided setup follows, and the patient begins sharing readings. Consent is captured at sign-up and remains the patient’s to review later.
Clinic partnership
A four-step path from partnership request to managed patients inside isolated data.
A clinic submits a partnership request from the sign-in page. The clinic’s IT then provisions clinician sign-in for approved staff. The clinic generates and manages the access codes that link patients to its account, and clinicians sign in to work inside their own isolated data. Each step keeps provisioning and access decisions with the clinic’s own IT, not with Vital Sense.
Onboarding profile and monitoring pathway
Gender, age, pregnancy status, history, and medications route each patient to the right pathway.
An onboarding profile tailors monitoring to each patient, from expectant mothers to older adults. Maternal hypertension is one application; the platform is built to monitor older adults and others too, for conditions like hypertension and diabetes. The same profile that a patient completes at sign-up is what determines which monitoring pathway they are routed into.
Clinician review loop
A reading is checked and prioritized, then reviewed and approved before it reaches the patient.
When a patient shares a reading, Vital Sense checks and prioritizes it for the care team. The clinician reviews it on the web dashboard, inside the clinic’s isolated data, and guidance reaches the patient only after the clinician approves it. The access code is what bridges the two accounts: a clinic issues it, the patient enters it at onboarding, and the accounts link inside the clinic’s isolated data.
Security and privacy
Clinic-level data isolation, role-based access, and an identity foundation for the privacy officer conversation.
Each clinic’s data is kept separate; one clinic never sees another’s, and a patient links to exactly one clinic. Clinician sign-in is provisioned through the clinic’s own IT, with role-based authorization deciding what each person can do. The platform is built on Microsoft Azure, with identity through Microsoft Entra.
One platform, any age, with the clinician still in the loop.
Vital Sense extends past its original maternal hypertension use case without giving up clinic-level isolation or clinician control over what reaches a patient.
The same onboarding profile that routes an expectant mother into maternal hypertension monitoring routes an older adult into hypertension or diabetes monitoring, without a separate build.
Clinic data isolation is enforced through access codes that tie a patient to exactly one clinic, not just described in policy.
No reading-derived guidance reaches a patient without a clinician reviewing and approving it first, keeping a human in control of clinical action.
Sign-in for clinicians is provisioned through the clinic’s own IT, so each clinic controls who on its own staff can access its own data.
Built to extend, not just to monitor one condition.
Any age, multiple conditions
An onboarding profile, not a rebuild, is what extends Vital Sense from maternal hypertension to older-adult hypertension and diabetes monitoring.
A security story for the privacy officer
Clinic-level data isolation and IT-provisioned clinician sign-in are structural, not policy language, addressing the question a privacy officer actually asks first.
The clinician stays in control
Guidance is checked and prioritized by the platform, but only reaches a patient after a clinician reviews and approves it, keeping clinical judgment with the clinician.