Mediloop

Teleconsultation

Overview

Understand overview in the Mediloop Teleconsultation platform and integrate it securely across tenant-aware healthcare workflows.

Tenant-aware by design

Requests are evaluated in the authenticated organization, tenant and membership context.

Secure & auditable

Least-privilege scopes, traceable events and explicit lifecycle rules are first-class concerns.

Built for integration

Predictable REST patterns, structured events and interoperable data models support production systems.

How it works

Overview is part of Mediloop's modular platform API. This page defines the resource or workflow boundary, expected authorization context and the integration behavior applications should rely on.

Key concepts

Use stable identifiers, explicit lifecycle states and scoped permissions. Keep identity, tenant membership and resource authorization separate so integrations remain predictable as organizations grow.

Architecture

Integrations authenticate first, select the permitted tenant context, then call the service with the minimum required scopes. Domain events can be consumed through Mediloop webhooks where supported.

01
Authenticate
02
Apply tenant context
03
Execute & audit

Common workflows

The example below illustrates the common request shape. Endpoint-specific schemas and production contracts should be validated against the API reference and the enabled capabilities for the tenant.

curl https://api.mediloop.com/v1/teleconsultation   -H "Authorization: Bearer $MEDILOOP_TOKEN"   -H "X-Tenant-Id: $TENANT_ID"

API quick start

Related capabilities connect this workflow to Identity & SSO, Organizations / Tenants, Users / Memberships / Roles, Permissions & Scopes, Webhooks and the relevant healthcare APIs.

Validate authorization server-side, minimize sensitive data, use idempotency for writes where supported, and retain the request/event identifiers required for audit and troubleshooting.

Next steps

Related capabilities connect this workflow to Identity & SSO, Organizations / Tenants, Users / Memberships / Roles, Permissions & Scopes, Webhooks and the relevant healthcare APIs.