Product shape
Vitalswise has a patient-facing mobile app and a separate clinician dashboard. Readings are kept in the Vitalswise Ovok project and can be read by compatible Ovok applications using that project.
| Surface | Purpose | Current capabilities |
|---|---|---|
| Patient app | Record and review personal health readings. | Today, Journal, Devices, Sharing, and You screens; manual entry, device pairing, phone-health imports, ECG and urine records. |
| Clinician dashboard | Review records available to the practitioner. | Care overview, patient search and invitations, observation history, Signals, clinic membership, and support. |
| Ovok platform | Provide the shared SDK and health-data services. | FHIR-backed records, identity and project access, device/data-sync SDK functionality, and app interoperability. |
Measurements
Values can be entered manually, received from a supported Bluetooth device, or imported from a connected phone-health platform where that platform supplies the type.
| Reading | Capture and display |
|---|---|
| Blood pressure | Systolic and diastolic values, with pulse when supplied; components remain linked to the main reading. |
| Heart rate | Manual or monitor readings; activity-tracker samples are summarized hourly in the diary. |
| Blood glucose | Manual entry, supported glucose meters, Apple Health, or Health Connect. |
| Weight | Manual entry, supported scales, Apple Health, or Health Connect. |
| Oxygen saturation | Manual entry, supported pulse oximeters, Apple Health, or Health Connect. |
| Temperature | Manual entry, supported thermometers, Apple Health, or Health Connect. |
| Respiratory rate | Manual entry and supported monitor readings. |
| Steps | Manual entry and phone-health imports; activity-tracker steps are kept as one finished daily total. |
| ECG | Stored recordings from supported ECG devices, shown as ECG strips without automated interpretation. |
| Urine test | Supported Contec BC401 strip results, displayed by analyte from the device reading. |
Connected devices
The mobile app uses the Ovok device catalog and supported-device decoding. It pairs known devices by model and also supports standard Bluetooth SIG profiles for compatible blood-pressure monitors, thermometers, scales, pulse oximeters, and heart-rate straps.
- Blood pressure: Viatom BP2, BP2A, BP2T, BP2W, BP3; Veroval; boso; visomat.
- Oximetry: OxySmart and Viatom oximeters, including O2Ring and Oxyfit.
- Glucose: TaiDoc TD4216, GlucoCheck Gold, and TeleBGM.
- Weight: Lescale F4.
- Temperature: AOJ-20A and cyclotest mySense basal thermometer.
- ECG: Veroval ECG, Viatom ER1/ER2/ER3 recorders, and Viatom Lepod/LepodPro.
- Urine analysis: Contec BC401.
- Activity: Veroval Activity tracker.
Pairing happens in the app. A nearby single device can be paired directly; if several are found, the user selects one. Device-reported make, model, measurement time, and supported memory-slot metadata are retained where available.
Apple Health & Health Connect
Imports are read-only. On first connection, the app imports up to 90 days of supported history and then checks for new records. Users control permissions in Apple Health or Health Connect and can change them later in those platform settings.
Imported types
Blood pressure, glucose, weight, oxygen saturation, temperature, and steps.
Heart-rate limit
Phone-health heart rate is skipped because the current daily-summary view does not present the frequent watch samples.
Background updates
Opt-in background delivery is subject to iOS, Android, battery, and permission settings; the operating system may delay work.
Data model & sync
Vitalswise records readings as FHIR Observation resources in the Ovok project. Blood-pressure components are linked to the main observation; the source, device, timestamp, units, and other supplied metadata are retained where available.
- Bluetooth measurements save while the app is open; optional background scanning can keep accepted monitors syncing when the phone permits it.
- Apple Health and Health Connect use the Ovok SDK sync flows. Background imports can run when the OS allows them and the relevant permissions are enabled.
- Uploads use a persistent queue with retries so temporary network failures do not require the user to re-enter a measurement.
- When enabled, local notifications may name measurement types that were saved or imported. They do not show the measured values. Vitalswise does not send remote push notifications.
- Activity-tracker heart-rate samples are grouped hourly; completed step totals are kept once per day. Unfinished current-day totals and minute-by-minute samples are not shown.
ECG & urine tests
ECG recordings
Vitalswise stores supported device recordings as FHIR observations with sampled data and displays them on ECG paper. Veroval recordings are 34 seconds at 128 Hz; Viatom stored recordings use 125 Hz and may be longer. Long recordings are stored in linked segments. The app displays the waveform and does not analyze or interpret it.
Urine strips
The Contec BC401 reads eleven strip pads. The app shows the SDK-decoded analytes and units for each strip, including negative results where provided by the device interpretation. This display is not a diagnosis.
Clinician workspace
The web dashboard at app.vitalswise.com provides a practitioner-scoped view of data available to the signed-in account.
- Care overview: patient and observation counts, latest observations, and recent Signals.
- Patients: search by name or identifier, view patient details, and invite a patient.
- Alerts: review Signals notifications and their reading details; acknowledge alerts when the account has permission.
- Clinic: eligible clinic members can review staff, invite practitioners, update roles, or remove memberships according to their role.
Dashboard readings come from Ovok FHIR Patient and Observation resources. Signals are read through Ovok’s Signals API; the dashboard presents the returned signal and status and does not create a diagnosis from a reading.
Built on Ovok, for interoperable health apps
The patient app uses Ovok’s React Native and core SDKs. Shared FHIR records make compatible readings available to other apps using the same Ovok project; app-specific screens and workflows remain with each application.