Clear, careful and non-overclaiming.
Ambulant+ is designed to support privacy, security and clinical-governance workflows. Regulatory status depends on jurisdiction, device, module, intended use and formal approvals. Do not claim approval, certification or clearance unless verified by official documentation.
POPIA and GDPR-aligned privacy posture
Ambulant+ is designed to support privacy principles such as purpose limitation, data minimisation, appropriate access controls, user rights workflows and consent-aware sharing. Final compliance depends on your operating entity, policies, contracts and deployment configuration.
HIPAA-aware architecture
Ambulant+ can support healthcare privacy and security workflows relevant to HIPAA-style environments. HIPAA obligations depend on whether an entity is a covered entity or business associate and on the specific deployment and contractual context.
Medical-device regulatory caution
Device regulatory status depends on the specific device, manufacturer, country, intended use and applicable conformity pathway. Ambulant+ should not be described as SAHPRA-approved, FDA-cleared, CE-certified or TÜV-certified unless official documentation confirms that claim.
Clinical safety boundaries
Ambulant+ supports connected-care workflows but does not replace emergency care, in-person examination where clinically required, or professional clinical judgement.
Security governance
The platform is structured around protected workspaces, role-aware access, auditability, environment-specific configuration and responsible data handling.
Marketing claim control
Public materials should use careful language such as designed to support, aligned with, built for, and regulatory pathway pending unless approval, certification or clearance has been verified.
Route every user to the right Ambulant+ workspace.
Use the landing domain as the public front door. Patients, clinicians, clients, pharmacies, riders and programme teams can move into the correct secured app from here.