helios-sof 0.2.3

This crate provides a complete implementation of the SQL-on-FHIR specification for Rust, enabling the transformation of FHIR resources into tabular data using declarative ViewDefinitions. It supports all major FHIR versions (R4, R4B, R5, R6) through a version-agnostic abstraction layer.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

# SQL-on-FHIR conformance fixtures

The JSON files in `tests/` are the official SQL-on-FHIR declarative test
fixtures, kept here as a **verbatim** copy of upstream so they can run in CI.

Version 2.0.0 shipped this suite inside the published package. 3.0.0-ballot
does not: the specification moved to HL7 under CC0, while the reference
implementation and its test suite stayed with the FHIR Foundation under MIT,
and one package could not carry both licenses. The suite is now versioned with
the reference implementation, which is where the sync command below points.

- **Upstream source:** <https://github.com/FHIR/sql-on-fhir.js/tree/main/tests>
  (raw: `https://raw.githubusercontent.com/FHIR/sql-on-fhir.js/main/tests/<file>.json`)
- **Policy:** files are copied byte-for-byte. Do not hand-edit them — re-sync from
  upstream instead, so a plain `diff` against upstream stays meaningful.

To re-sync:

```sh
dir=crates/sof/tests/sql-on-fhir/tests
for f in "$dir"/*.json; do
  name=$(basename "$f")
  curl -fsS "https://raw.githubusercontent.com/FHIR/sql-on-fhir.js/main/tests/$name" -o "$f"
done
# Pick up any newly-added upstream files too (e.g. a future `fn_*.json`):
# list the upstream `tests/` directory and `curl` anything missing locally.
```

## Who runs these

- `crates/sof/tests/test_runner_integration.rs` — runs every fixture against the
  in-memory `run_view_definition` engine and asserts **all** pass.
- In-DB runners, each running every fixture against a real backend via the REST
  endpoint with a `PASS_FLOOR` ratchet (some fixtures exercise constructs a given
  in-DB compiler does not yet cover):
  - `crates/rest/tests/sof_conformance.rs` — SQLite (in-memory, no Docker; floor 132).
  - `crates/rest/tests/sof_conformance_postgres.rs` — PostgreSQL via testcontainers (floor 132).
  - `crates/rest/tests/sof_conformance_mongodb.rs` — MongoDB via testcontainers (floor 132).

  All three in-DB suites share the same floor (132) and the same 12 failing
  fixtures: nested/sibling `repeat` and `unionAll` nested inside another
  `select`, which no in-DB compiler covers yet.

## Notes

- `constant_types.json` omits the top-level `fhirVersion` field; the runners
  treat a missing `fhirVersion` as "applies to all versions".
- Row comparison is order-insensitive (matching the upstream compliance runner,
  which canonicalizes rows before comparing).

### `%rowIndex` support by backend

`%rowIndex` (the iteration-position environment variable) is implemented per
execution engine:

| Backend | Engine | `%rowIndex` |
|---------|--------|-------------|
| SQLite | in-DB SQL compiler | full (top-level, forEach/forEachOrNull, repeat) |
| PostgreSQL | in-DB SQL compiler | full (`WITH ORDINALITY` for forEach, pre-order `ord_path` in the repeat CTE) |
| S3 | in-process `helios-sof` engine | full (the engine's own `forEach`/`repeat` support) |
| MongoDB | in-DB aggregation | full (`$unwind … includeArrayIndex` for forEach; `$function` pre-order traversal for repeat) |
| Elasticsearch | — | no SOF runner; SOF is not served on ES |

Across all in-DB backends, 8 of the 9 `row_index.json` fixtures pass; the 9th
(`%rowIndex in unionAll inside forEach`) depends on the orthogonal, pre-existing
"unionAll nested inside another select" gap.