What problem does it solve? Working with FHIRPath in the Helios FHIR Server requires knowing the correct CLI flags, server endpoints, environment variables, and test locations, which are scattered across multiple crates and binaries. ## Core Features & Use Cases - CLI Expression Evaluation: Run FHIRPath expressions against JSON resources with context expressions, variables, stdin input, and FHIR version selection (R4, R4B, R5, R6). - HTTP Server: Start a fhirpath-lab-compatible evaluation server with version-specific endpoints, compression support, and configurable CORS, port, and body size limits. - Parser Debugging and Testing: Inspect parse debug trees and run official fhir-test-cases suites located under crates/fhirpath/tests/. - Use Case: A developer debugging why "Patient.name.given.first()" returns unexpected results can render the parse debug tree with fhirpath-cli, then test the expression against a sample Patient resource before touching server code. ## Quick Start Evaluate the FHIRPath expression "Patient.name.family" against my patient.json file using the fhirpath CLI and show me the result.