Skip to main content
For operational telemetry, OpenTelemetry provides consistent schemas and collectors to transport and store event data across languages and platforms. A MedLog semantic convention can be defined as a custom OpenTelemetry registry using OpenTelemetry Weaver, reusing existing OpenTelemetry attributes where their semantics match and defining medlog.* attributes for concepts specific to medical AI.

​
Reusing Gen AI conventions

When logging generative AI models, existing OpenTelemetry Gen AI semantic conventions can be reused. Users and sessions can also be represented with existing User and Session semantic conventions such as user.id and user.name.

​
Emitting and collecting records

MedLog records can then be emitted as OpenTelemetry telemetry, and an OpenTelemetry Collector can receive, process, and export these records to observability platforms. This approach enables integration of MedLog with existing tracing, logging, and monitoring infrastructure.
Derived OpenTelemetry attributes do not replace the canonical MedLog payload. Populate trace and span identifiers only when genuine tracing context exists, and reuse an attribute only when its semantics actually match the MedLog field.