Skip to main content

Schemas & Outcomes

Schemas and outcomes are the shared language that lets OmegaX turn messy, private, real-world signals into comparable economic events.

They are how the protocol turns real-world activity, clinical inputs, and claims-relevant evidence into recognizable economic consequences without trying to publish raw data onchain.

What a schema does​

A schema defines the structure of a protocol-recognized event.

That can include:

  • event family
  • threshold or target definition
  • measurement window
  • evidence commitments
  • version or policy reference
  • interoperability or coding profile where needed

Public and private schema modes​

OmegaX should support both:

  • public schemas for reusable, ecosystem-readable event language
  • private schemas for sponsor-specific or regulated logic where the protocol still needs stable references

The rule is not that everything must be public in plain English.

The rule is that everything used for settlement must be stable enough to reference, version, and audit.

Versioning and comparability​

Versioning matters because health-plan logic changes over time.

OmegaX should be able to show:

  • which schema family a plan uses
  • which version was active when a right or claim was created
  • whether two plans are materially comparable
  • how reporting should treat different vintages

This is what lets health performance become comparable rather than bespoke.

How finality works​

  1. A plan references one or more outcome definitions.
  2. Event producers and oracles observe the relevant offchain facts.
  3. Oracles submit attestations under the plan's trust policy.
  4. The protocol determines whether the event is final under that policy.
  5. Settlement logic can then release rewards, claims, or other consequences.

Why the protocol does not store raw logic​

OmegaX should store:

  • schema references
  • commitments
  • hashes
  • version identifiers
  • rule linkage

OmegaX should not store:

  • raw health streams
  • verbose intermediate reasoning
  • giant claims bundles
  • full external codebooks

Relationship to external standards​

External healthcare and claims standards still matter.

Examples include:

  • FHIR for interoperability and evidence exchange
  • CPT, HCPCS, ICD, LOINC, and related coding systems where claims require them

Those standards help structure inputs.

OmegaX schemas define the normalized event language that the protocol can actually settle.

Why this matters for markets​

Schemas and outcomes are not only an oracle concern.

They shape:

  • plan comparability
  • sponsor reporting
  • claim semantics
  • health alpha reporting
  • capital pricing over time
Download PDF