Care platform

These namespaces serve care teams and administrators.

Residents, devices and notificationsCopy Anchor Link

ovok.slim covers care-home operations:

final residents = await ovok.slim.patients.list({'count': 25});
await for (final resident in residents.autoPaging()) {
  // each next page loads only when it is needed
}

final live = await ovok.slim.devices.live({'count': 50});
final alarms = await ovok.slim.notifications.alarms.list();

It also manages thresholds, trends, sleep, locations, zones, exports, change history, projects, policies, organizations, practitioners and users.

• devices.live, liveTelemetry and telemetry share one request when the same route and query are already in flight.
• Live count must be an integer from 1 to 100.
• Medical notification codes, when given, must hold 1–32 LOINC codes or PI.

SignalsCopy Anchor Link

ovok.signals.enable(patientId) turns Signals on for a patient. ovok.signals.undeliverable lists readings that did not reach Signals and repairs them.

Projects and peopleCopy Anchor Link

• ovok.projects: projects, members, settings and features.
• ovok.accounts, ovok.locales, ovok.localizations and ovok.email: accounts, languages, translations and email templates.
• ovok.invites: record-share, care, practitioner and patient invitations.
• ovok.sharing: patient-sharing invites, shares and settings.

CMSCopy Anchor Link

ovok.cms reads documents, legal pages, translations and release notes for the configured tenant without a signed-in session. ovok.content reads and edits CMS content.

final terms = await ovok.cms.legalPage('terms-and-conditions');