Patient / Member
Explain the encounter.
Show the documented services, participants, dates, and amounts assigned to the patient.
ELC / Encounter Lifecycle
Feed your agents
care events—not documents.
One documented encounter. Shared meaning across agents and workflows—with the services, participants, time, economics, and evidence that make the record usable.
Call the contract / Synthetic example
Inspect the answer.
Follow the evidence.
Select a fact to see its source. Change the available evidence to explore a complete result, an unknown, or a conflict.
Synthetic illustration of the care-event vision. Fictional evidence, deterministic results, and browser-only interaction; no production service is invoked.
One documented event. Many agent views.
The context travels
with the work.
ELC is designed to give agents a shared account of an encounter that travels across organizations and workflows. Each agent brings its own question, supporting context, and authority.
Provider / Payer
Reconcile the record.
Compare what was billed with adjudication and payment. Join coverage, rates, or policy for further review.
Workflow
Carry the facts forward.
Use structured encounter context in IDR, appeals, reconciliation, and administrative explanation.
Inspectable by design
Read the artifacts.
Inspect the documented binding request and representative care-event response. The developer guide explains the artifacts, their maturity, and how to define a binding.
Implementation note
Where we are today.
The private Box-to-Salesforce binding extracts UB-04 and EOB/Remit evidence separately. The customer’s Salesforce workflow reconciles and reviews the results for NSA IDR work. The care-event response and explorer are representative design artifacts; no current binding serves that generalized response. A generalized family request is not yet published. Confirm deployment interfaces and compatibility terms for your environment.
Encounter evidence alone does not establish clinical outcome, provider cost or profit, payer value, medical necessity, coverage, or payment correctness. Further determinations require their own supporting evidence.
Your sources. Your workflow.
Let’s define your binding.
Start with the source evidence, destination model, and administrative decision you need to support.