Skip to main content

​
W3C PROV

MedLog implementations can use the W3C PROV conceptual model to distinguish data, activities, and responsible actors. A MedLog record and its fragments can be represented as prov:Entity instances; the model invocation itself as a prov:Activity; and the model and user as instances of prov:Agent or its subclasses, such as prov:SoftwareAgent, prov:Person, or prov:Organization. Relations connect an invocation to its inputs, outputs, and participating actors.

​
OpenLineage

OpenLineage can also be used to link AI interactions recorded in MedLog records to broader institutional computational workflows. For example, an inference pipeline can be represented as a job, with individual executions represented as runs and consumed or produced data represented as datasets. OpenLineage runId values can be referenced in the MedLog Header field, allowing inference events to be linked to upstream data processing steps and downstream computational outputs.
Linking a runId into the header is what makes an inference event traceable in both directions: back to the data preparation that produced its inputs, and forward to the analyses that consume its outputs.