Examples
Examples
Overview
Examples show concrete customer information, mappings, requests, responses, and evidence patterns for a FoxCommand integration.
They show how Customer Configuration, Business Semantics, Decision Mapping, runtime requests, runtime responses, validation, and workflow-specific material fit together. They are synthetic, not production data or runtime API definitions.
Start with the Prior Authorization workflow when you want the most complete first pattern. Then compare its prepared material with the runtime request and response examples before adapting templates or reference implementation code.
Workflow Examples
| Workflow | Best for |
|---|---|
| Prior Authorization | First guided integration pattern with Customer Configuration, Business Semantics, Decision Mapping, and runtime request/response examples. |
| Denial Resolution | Secondary healthcare pattern focused on review material and evidence retention. |
| Customer Support Escalation | Secondary non-healthcare pattern for mapping support escalation semantics. |
Runtime Examples
The runtime examples follow the evidence workflow:
runtime-requests/governed-execution.request.example.jsonruntime-responses/governed-execution.response.example.jsonruntime-requests/replay.request.example.jsonruntime-responses/replay.response.example.jsonruntime-requests/simulation.request.example.jsonruntime-responses/simulation.response.example.jsonruntime-requests/comparison.request.example.jsonruntime-responses/comparison.response.example.jsonruntime-requests/governance-rca.request.example.jsonruntime-responses/governance-rca.response.example.json
FoxCommand uses this sequence to move from initial evidence to replay, candidate evaluation, structured comparison, and bounded attribution.
Supporting Integration Material
business-semantics/captures your business terminology and decision meaning.decision-mapping/translates your business meaning into FoxCommand-compatible inputs.execution-contracts/shows returned evidence reference storage patterns.validation/shows readiness and validation output shapes.- Reference Implementations demonstrate request construction and evidence extraction.
- OpenAPI specification defines exact request and response contracts.
Examples are illustrative and synthetic. They are not production data, deployment instructions, runtime API definitions, or approval records.
First Integration Step
Start with the Prior Authorization Workflow Example. Use Templates when you already know your Customer Configuration and Decision Mapping, then use the Runtime API Reference to confirm exact request and response fields.
Updated 4 months ago