Skip to main content
MedLog can be implemented using existing open standards and tooling. The MedLog protocol defines what information should be recorded at each invocation of a medical AI model; existing frameworks provide complementary ways to represent, exchange, and analyze that information.

​
The layers

Provenance and lineage

W3C PROV provides a conceptual model for computational provenance, and OpenLineage supports lineage tracking across institutional workflows.

Health data elements

USCDI defines high-level health data classes and elements, and FHIR provides structured resource representations.

Telemetry standards

OpenTelemetry supports operational telemetry, with collectors that transport and store event data across languages and platforms.

EHR audit logs

Event-level logging already runs at scale in healthcare. EHR audit logs offer a decade of learnings for real-world MedLog deployment.
These interoperability layers enable scalable, vendor-agnostic deployments and lower the barrier to multi-institutional analyses.

​
Explore the mappings

Field mapping explorer

Select any of the nine MedLog fields to see related USCDI concepts and FHIR and OpenTelemetry representations, each linked to its documentation.
The mappings throughout this section are illustrative, not normative. They identify related concepts rather than exact equivalents, and they are conditional on matching semantics, available source information, and local capture policy. None of them replace the canonical MedLog payload.