For Hospital at Home, virtual ward, and Spitex teams
Build care-at-home workflows on a shared FHIR foundation.
For providers extending care beyond the hospital and the digital-health teams supporting them—including Swiss Spitex organizations—Ovok provides backend, SDK, and supported-device infrastructure. Your team defines the service, patient experience, and clinical operations.
01
Care beyond the ward
Connect home measurements to the product your team operates.
Hospital at Home and virtual-ward services combine patient-reported information, supported measurements, and review by the provider's own care team.
Patient and practitioner records
Use FHIR R4 records as the data foundation for the patient, practitioner, and care-team workflows your application supports.
Measurements from home
Build around supported device models and documented SDK paths. Check the live catalogue for exact compatibility; live ingestion setup requires coordination with the Ovok team.
Check-ins and follow-up
Use documented questionnaire capabilities as building blocks for app-owned check-ins. Your organization decides staffing, review cadence, and response procedures.
02
A product workflow
Keep the data path explicit from home to care-team review.
- 01
Define the service workflow
Set the cohort, patient journey, staff roles, and intended use for your Hospital at Home, virtual-ward, or Spitex programme.
- 02
Collect supported inputs
Connect documented device workflows with the patient-entered information and questionnaires your application uses.
- 03
Store the product record
Use the FHIR backend for supported measurements and other records in the application's workflow.
- 04
Build review and response
Your application presents records and owns clinical interpretation, escalation, and follow-up. Optional Signals evaluation is configured per patient for eligible vital-sign readings.
03
Product boundary
Use infrastructure for the service your organization designs.
Ovok provides
- FHIR R4 backend and application SDKs
- Supported-device workflows and documented questionnaire capabilities
- Access Policies and optional patient-level Signals evaluation
Your organization defines
- Care pathway, staffing, operating hours, and patient eligibility
- Clinical thresholds, escalation, and response procedures
- The patient and practitioner experience and regulatory strategy
Ovok is infrastructure, not a managed virtual ward service or a finished hospital command centre. Signals is a separate component; its MDR Class IIa status does not apply to Ovok or to an application built on it.
04
Architecture and procurement
Review hosting and commercial terms against your requirements.
The published facts give provider and product teams a starting point for technical, privacy, and procurement review.
Hosting
The Ovok service is hosted in AWS Frankfurt. Assess this location against your organization's requirements.
Data-processing agreement
Every paid plan includes a DPA. Review the applicable plan and agreement for your use case.
Pricing and enterprise terms
Plans are priced per monitored patient. Enterprise teams can discuss custom contract and Signals terms with Actimi.
Evaluate the fit
Bring your care-at-home workflow to the review.
Start with the product documentation, then discuss your device, hosting, and commercial requirements with the Ovok team.
