run_id linking it to the other calls in the same abstraction run.
Field-by-field
header
header
The Header: the protocol version, a stable
event_id, the invocation
timestamp, system info, and a run_id that links this call to the other LLM calls in the same
SEP-1 abstraction run.model_instance
model_instance
The Model instance:
Llama-3.1-8B-Instruct, version 2024-07-18.user_identity
user_identity
The User identity. Here the caller is an automated process
(
process_id: 3023) — the abstraction pipeline, not a human.target_identity
target_identity
The Target identity: the patient, referenced by de-identified EHR
identifiers (
MRN, CSN).inputs
inputs
The Inputs: the full prompt, including the abstraction instructions and the
specific SEP-1 compliance question posed to the model.
internal_artifacts
internal_artifacts
The Internal artifacts: the model’s chain-of-thought and the
supporting
extracts it pulled from the note. Trace-level analysis of this field is what revealed
the model’s confusion between intra-hospital transfers and true discharges.outputs
outputs
The Output shown downstream: the answer
N to the discharge question.outcomes
outcomes
The Outcome: the resulting SEP-1 population category for this case.
user_feedback
user_feedback
The User feedback: the quality-and-patient-safety (QPS) analyst’s
adjudication — “Agree, case passes.”
This record uses the protocol’s conceptual field names. The API reference
defines the concrete event payloads a collector accepts (for example,
system_metadata,
caller_type/caller_id, and the typed artifact / output / outcome objects). The conceptual
model and the wire format describe the same nine fields.