Know what the server does.
Then build on it.

Run Ilavrita, understand the architecture, and inspect the FHIR contract without guessing. Product documentation is synced from the repository so implementation truth stays close to the code.

Start with the limits, not the pitch.

Ilavrita remains a developer preview and is not ready for patient data. SMART App Launch STU2.2 now has a recorded Inferno functional pass, including OpenID Connect and fhirUser behavior; three TLS checks remain because the recorded run targeted plaintext local HTTP. External security review and broader profile conformance remain open gates.

Read the known limitations

Run Ilavrita locally

Build from source, start one node, and make your first request.

Understand the boundaries

See where FHIR behavior ends and storage begins.

Inspect the API

Read the HTTP contract and compare it with the live CapabilityStatement.

Build with us

Follow the development workflow, decisions, and contribution path.

Docs that move with the code.

30 pages imported from Ilavrita/Ilavrita, pinned to 9462213. Each page links back to its exact source revision.

These pages are generated from the Ilavrita repository. For runtime truth, use the CapabilityStatement from your running server together with Known limitations; the website should never promise behavior the build does not advertise.