Security & Compliance · Elevate platform · Leyline configuration

The HIPAA-certified cloud is the foundation. The configuration is the posture.

Leyline stands up every customer on Intermedia's HIPAA-certified Elevate cloud — encrypted voice, audit-ready logs, BAA-ready by default. The certified platform is the foundation; the configuration Leyline runs on top — the role separation, the retention windows, the BAA execution, the named engineer — is the posture that turns the platform into a working HIPAA roll.

Talk to a Leyline engineer about HIPAA postureSee the healthcare overview
Underlying platform
HIPAA-certified Elevate
Encryption
TLS + SRTP · at rest
Audit posture
Per-event, exportable
BAA
Day one for healthcare
Three dimensions of the posture

Data handling, access controls, and audit logging — each one a per-customer configuration.

The HIPAA-certified baseline ships with the platform. Each pillar below is what Leyline configures on top — the controls your reviewer inspects, and the surface your BAA names.

01 — Data handling

Encrypted in transit and at rest, hosted on US-resident infrastructure.

Every voice, video, message, and clinical file runs through the same encrypted pipe. Signaling is TLS, media is SRTP, files are encrypted at rest in the Intermedia cloud — and the entire corpus sits on US-resident infrastructure that we never replicate out of.

  • Pillar
    Encrypted in transit.

    TLS for SIP signaling, SRTP for media streams. No unencrypted voice crosses the platform — the elevated and standard tiers both terminate TLS 1.2+ at the edge, with certificate validation on every connection.

  • Pillar
    Encrypted at rest.

    Voicemail, recording, secure file rooms, and conference recordings are stored encrypted at rest with tenant-scoped keys. A retained item never sits as plaintext alongside another tenant’s.

  • Pillar
    US-resident infrastructure.

    Intermedia’s HIPAA-certified data centers host patient calls, messages, and files. Nothing replicates outside the US, and there is no dormant copy in a non-US region we have to disclose.

  • Pillar
    Posture matches the BAA scope.

    What the BAA covers and what the platform encrypts are the same surface. A reviewer reading the agreement is reading against the actual cryptographic surface — there is no gap to reconcile later.

02 — Access controls & admin separation

Role-based permissions, named engineers, no shared admin logins.

Access to your tenant is segregated by role, scoped to least privilege, and every administrative change is logged with the engineer responsible for it. Leyline engineers only touch your tenant through named, audited sessions — never via a shared admin login.

  • Pillar
    Role-based access control.

    Your customer admin sets per-user roles in the console — receptionist, billing, branch manager, full admin. A role that does not need to provision handsets cannot provision handsets.

  • Pillar
    Customer admin vs. Leyline engineer.

    Customer admins manage users, greetings, and call flows; Leyline engineers operate under a separate, customer-visible administrative identity scoped to support tickets. The two never share credentials.

  • Pillar
    Least privilege, per ticket.

    A Leyline engineer accesses a tenant under a time-bounded scope opened by the ticketing system. The scope is the smallest the remediation needs, and the session is logged end-to-end.

  • Pillar
    Audit-ready admin change history.

    Every administrative change — role grant, number port, handset re-provision — carries an actor, a timestamp, and a before/after. The history is exportable and the export is the same one your reviewer reads.

03 — Audit logging

A per-event trail, configurable retention, export for your reviewer.

Every call, every message, every file access, every administrative change is logged at the event level — not as a flat summary. Retention is configurable per event class, and the export is the format your compliance reviewer already reads.

  • Pillar
    Per-event records.

    Call records, voicemails, messages, secure file drops, and admin changes each carry their own event type in the audit trail. Searching for “who touched patient file X on date Y” returns the exact row, not a summary.

  • Pillar
    Configurable retention.

    Retention windows are scoped per event class — call detail records on one timeline, message retention on another, file history on a third. The windows match the retention your compliance officer already has on file.

  • Pillar
    Export to your compliance officer.

    Exports are produced in the format your reviewer expects. A periodic retention-aware export or a one-off incident pull is the same workflow — a Leyline engineer hands it over, the reviewer reads it.

  • Pillar
    The trail faces the BAA.

    The audit surface is the surface the BAA names. If the agreement says “call detail records retained for N months”, the audit trail is the system that produces them — not a parallel store.

BAA availability

The Business Associate Agreement is configured at cutover — not a procurement artefact.

For US healthcare customers, the BAA sits at the centre of the cutover — same engineer, same session, same window as the number port. The page below sketches the high-level posture; the full healthcare-specific roll — specialties, migration walkthrough, and audit surface — lives on the dedicated healthcare overview.

See the HIPAA-specific healthcare overviewAsk for the BAA attestation
BAA availability
BAA available on day one for healthcare customers.

For healthcare customers, the Business Associate Agreement is config, not a procurement step. We sign it as part of the cutover, and the same engineer who ports your numbers is the one who walks your compliance officer through what the agreement now covers. If your compliance team needs the attestation docs upfront, we send them with the reply.

Same engineer who ports your numbers is the engineer who walks your compliance officer through what the agreement now covers.

What is what — and who does what

The platform sets the baseline. Leyline configures the rest.

A HIPAA-certified platform and a HIPAA posture are two different things. Below is the split — what the underlying Elevate cloud ships with on day one, and what Leyline configures on the customer side during cutover. This is the page the compliance officer reads; the rest of the compliance review works against it.

Elevate platform

What HIPAA-eligible means on the underlying platform.

The cryptographic and operational surface the agreement is signed against — encryption, audit surface, BAA-ready infrastructure — sits in the platform. We do not build it per customer; every Leyline tenant inherits the same HIPAA-eligible baseline.

  • TLS signaling · SRTP media · encrypted-at-rest storage
  • Audit-ready per-event logging across voice, video, chat, files
  • US-resident Intermedia data centers, no out-of-region replication
  • Business Associate Agreement ready, signed at cutover
Leyline configuration

What Leyline configures on the customer side, in-house.

Most HIPAA posture is configuration, not construction. The patient-call auditability, the admin-vs-engineer separation, the retention windows, the cutover walkthrough — all of that is set up per customer by the Leyline engineer who runs the site survey. It is the human layer that turns the certified platform into a working HIPAA posture.

  • Per-customer BAA execution and counter-signature
  • Role assignment: customer admins vs. Leyline engineer scope
  • Retention windows tuned per event class to your compliance officer
  • Named engineer on speed-dial — same one who staged the system

Most of the HIPAA posture your reviewer inspects is configuration, not construction — it lives in roles, retention windows, BAA execution, and the named engineer on speed-dial. A HIPAA-certified Cloud is the prerequisite; the named-engineer cutover is the delivery.

HIPAA-ready, configured in-house

Walk your compliance officer through the posture, on a real call.

Tell us how many users and what kind of records you handle. We'll come back inside a business day with a per-user quote, the BAA on the table, and the engineer who will run the cutover — not a sales rep routing the call to a queue.

Talk to a Leyline engineer about HIPAA postureSee the healthcare overview

Adam Mohr & Courtney Moses · Founders, Leyline