Production Onboarding
Observability
Understand observability in the Mediloop Production Onboarding 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.
Overview
Observability 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.
Core 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.
Integration model
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.
Example
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/production-onboarding/observability -H "Authorization: Bearer $MEDILOOP_TOKEN" -H "X-Tenant-Id: $TENANT_ID"Security & governance
Apply least-privilege access, explicit tenant boundaries and auditable controls when using Observability. Sensitive healthcare data must only be processed for authorized purposes.
Validate authorization server-side, minimize sensitive data, use idempotency for writes where supported, and retain the request/event identifiers required for audit and troubleshooting.