This is the documentation home for CloudHealthOffice. It is organized for a first-time engineer who needs to understand the platform, run it locally, inspect the architecture, and find an area to contribute.
| Need | Start with |
|---|---|
| Understand the project | Repository README |
| Run it locally | Quickstart |
| Understand services and data flow | Architecture |
| Learn payer-domain concepts | Healthcare domain |
| Reproduce benchmark evidence | Benchmarks |
| Deploy beyond local development | Deployment |
| Sell the first Layer 1 pilot | CMS-0057-F Accelerator offer and diligence binder |
| Position software + professional services | Product-led services ADR, services content plan, and the assistant plan |
| Run the cms-0057-f.com companion property | ADR 013 and the cross-site contract |
| Turn payer operations work into product | Payer operations productization backlog |
| Contribute | Developer guide and CONTRIBUTING.md |
- Architecture index
- System architecture
- Claim adjudication pipeline
- FHIR conformance
- FHIR endpoint projection
- Claim FHIR projection
- Shared message bus
- Declarative benefit model
- Accumulator service
- Temporal eligibility
- Observability
- Deployment guide
- Deployment gates
- Known deployment gaps
- Kubernetes infrastructure
- Health-check dependency matrix
- Monitoring and observability
- Domain index
- Claims
- Benefits
- Provider networks
- Pricing
- Authorizations
- Eligibility
- Members and employers
- Appeals
- Accumulators
The domain index is intentionally written for software engineers who are new to healthcare payer systems.
- CMS-0057-F readiness matrix
- CMS-0057-F compliance guide
- FHIR integration
- Patient Access API
- Prior Authorization API
- HIPAA compliance matrix
- Benchmark index
- Million Claim Challenge podcast series
- 100K local Kubernetes result
- 100K benchmark results
- Pended-claim validation
- Architecture decision index
- ADR directory
- Argo vs Airflow
- Kafka vs NATS
- pyx12 library
- Remove Logic Apps
- Kubernetes-first runtime
- Persistence boundaries
- Blazor/Razor portal
- FHIR R4 projections
- X12 remains first-class
- Event evidence before full event sourcing
- Separate rules, scoring, and claims
- Product-led professional services and labelled operating models
- cms-0057-f.com as a companion educational property
- Keep claims factual and dated when they rely on benchmark results.
- Label planned capabilities as planned.
- Do not include PHI, production credentials, real member data, or real claim data in docs or screenshots.
- Prefer Mermaid for diagrams that should render in GitHub.
- Add new major docs to this index.