HIPAA and healthcare statement
Healthcare service scope, data-handling requirements, agreements and customer responsibilities.
Security, privacy & compliance
Understand the framework. Find the right agreement. Review the detail that matters to your organisation.
The document library
Start with the Privacy Policy for personal-data information, the Data Processing Agreement (DPA) for processing terms and the Terms of Service for platform use.
Start with the HIPAA statement and customer BAA. Your service schedules define the specific features, providers and responsibilities.
Healthcare service scope, data-handling requirements, agreements and customer responsibilities.
Our approach to access, infrastructure and data protection, with the current assurance status.
How personal data is collected and used, and how to contact us about privacy rights.
Our published GDPR processing terms. This document is not a HIPAA Business Associate Agreement.
The terms governing use of the Sysevo platform and services.
Information about cookies, analytics and consent choices on this website.
PDF copies identify their source and edition or capture date. Customer-specific signed agreements are exchanged directly.
For healthcare organisations
Healthcare engagements are defined by a service-specific scope, Business Associate Agreement and operating schedules. Review the statement and customer BAA template, then confirm the services, providers and safeguards required for your organisation.
Healthcare PHI processing requires written service approval and an executed Business Associate Agreement before it begins.
Scope, safeguards, AI and voice processing, providers, retention, individual rights, incidents and recovery.
Agreements & schedules
A Business Associate Agreement (BAA) sets the parties’ PHI-handling duties. Complete it together with the service schedules for the engagement, then obtain the required approvals and signatures.
Includes service, incident, rights-assistance and retention schedules.
Customer agreement template with permitted-use terms, safeguards, incident reporting, individual-rights assistance and signature fields. Complete the engagement schedules and obtain authorized signatures.
The engagement schedule identifies enabled features, permitted data, exact providers and models, processing locations, subprocessors and customer configuration duties.
The service schedule records retention by data class, secure return, destruction, backup expiry, legal holds and continuing protections.
Customer-specific agreements and confidential assurance records are exchanged through the agreed review process.
The review process
Connect the documents to the workflow your team will operate. Each step helps define what is included, who is responsible and what needs to be reviewed.
Identify contracting entities, HIPAA roles, workflows, data categories, locations, customer administrators and required integrations.
Review exact provider coverage, safeguards, access, retention, incident contacts, rights assistance and recovery responsibilities.
Complete the BAA and engagement schedules, resolve material requirements and obtain authorised signatures and service approval.
Use the agreed settings and channels, maintain access and operating records, and reassess material changes before extending PHI processing.
Beyond the public documents
Policies explain the framework. A security or procurement review also needs evidence relevant to the actual service, configuration and review date.
Include your legal entity and HIPAA role, intended workflows, data categories, integrations, location requirements and review contacts. Use business requirements only in an initial enquiry; request a secure route for confidential material.
A little more clarity
Understand which documents apply, how healthcare scope is approved and where to direct your request.
Use the Privacy Policy for website and personal-data information, the Terms for general service terms, the DPA for its stated processing obligations, and the healthcare statement and BAA template for a HIPAA engagement. The executed contract and completed schedules determine your specific scope.
The template provides the agreement structure. Authorised parties must complete the engagement details and schedules, execute the applicable BAA and obtain written service approval before PHI processing begins.
The approved schedule identifies included features, exact providers and models, integrations, regions and exclusions. New features, fallback routes and supplier changes require review before they receive PHI.
Contact the security team with your business requirements and intended workflow. Relevant service-specific material is exchanged through an agreed confidential process; customer agreements and internal security records are not public downloads.
Individuals should normally contact their healthcare organisation about access or amendments. Customers use the designated agreement contacts for rights assistance or incidents. Initial enquiries to security@sysevo.io should contain a safe reference and no patient records or credentials.
Public documents are versioned. Signed agreements and approved schedules determine the terms for an engagement; a new public document does not silently amend them.