ELC / ACTIVE / PRIVATE

Feed your agents
care events—not
documents.

Encounter Lifecycle resolves UB-04 and EOB/Remit evidence into a source-grounded account of what happened, who was involved, where and when care occurred, and how it was billed and adjudicated.

Run a synthetic call Request access

Synthetic contract call

Call the contract.

This browser demonstration validates a request and returns a deterministic synthetic care event. It does not invoke the private production binding.

Use the supplied fictional identifiers only. Do not enter protected health information or real case data.

Request

binding / box-salesforce

Response

ready

{
  "status": "ready",
  "message": "Run the synthetic contract to resolve the fixture."
}

ELC / any/encounter.lifecycle@1Encounter Lifecycle

One documented event.
Many agent views.

Patient, provider, payer, and workflow agents can consume the same contracted event through the context they need. Additional clinical, coverage, cost, quality, rate, or policy evidence must be joined before making conclusions those documents cannot support.

Current binding

any/encounter.lifecycle@1

active / private

Invoke: encounter.lifecycle.resolve
Request: case_id + box_folder_id
Evidence: UB-04 + EOB/Remit
Returns: Care event + economics + evidence
Binding: Box → ANY → Salesforce

The request schema is binding-specific. The generalized care-event response shown here is representative and not yet a normative family schema.

Representative family response

JSON

{
  "contract": "any/encounter.lifecycle@1",
  "operation": "encounter.lifecycle.resolve",
  "request_id": "…",
  "status": "resolved | partial | unresolved | failed",
  "observed_at": "…",
  "result": {
    "care_event": {
      "period": { "start": "…", "end": "…" },
      "place": { "facility_ref": "…" },
      "participants": [ "…" ],
      "clinical_context": { "diagnoses": [ "…" ] },
      "services": [ "…" ]
    },
    "economics": {
      "charged": "…", "allowed": "…",
      "paid": "…", "patient_responsibility": "…"
    }
  },
  "evidence": [ "…" ],
  "provenance": [ "…" ],
  "issues": [ "…" ]
}

Representative family shape. Inspect the registry for artifact maturity.

Current production binding

Invoke once. Resolve once.
Consume by contract.

The calling system does not orchestrate document parsing, source reconciliation, or destination mapping.

01 / invokeConsuming system
case_id + box_folder_id
POST
02 / evidenceBox
UB-04 claim form
EOB/Remit advice
READ
03 / returnCare event
Context + economics
Evidence + issues
CONTRACT
04 / bindSalesforce
Claim model
NSA IDR workflow
APPLY

Contract reuse

Same event.
Different context.

patient.agent

Explain the event

What happened, when and where it occurred, who was involved, and what was charged, paid, or assigned.

provider.agent

Reconcile economics

Compare documented services with adjudication and payment, then join cost or outcome evidence when available.

payer.agent

Inspect adjudication

Trace what was billed, allowed, denied, paid, and attributed before applying coverage or policy context.

workflow.agent

Advance the work

Use the same versioned event in IDR, appeals, reconciliation, audit, explanation, and downstream operations.

// truth boundary Encounter Lifecycle reports what UB-04 and EOB/Remit evidence documents. It does not by itself establish clinical outcome, provider cost or profit, payer value, medical necessity, coverage, or payment correctness.

Operating behavior

Unknown is not false.
Unresolved is not failed.

resolved

The requested scope is supported by available evidence.

partial

A result exists, with explicit unknowns, conflicts, or incomplete evidence.

unresolved

A valid domain outcome: identity or evidence could not support a result.

failed

Validation, authorization, or technical execution failed. Infer no domain conclusion.

These are forward-looking generalized semantics. They do not claim the current customer binding already emits this exact status vocabulary.