Align $sqlquery-run parameters with CQL $evaluate pattern

[niquola]

Summary

• BREAKING: Replace custom parameter (0..*) with {name, value} parts with a standard nested parameters: Parameters (0..1) resource
• Follows the CQL IG $evaluate operation pattern for passing arbitrary typed parameters to a library by name
• Updated all documentation examples to use the new calling convention

Motivation

The previous parameter input with custom part[name, value] reinvented what the FHIR Parameters resource already provides. The CQL $evaluate operation — the closest analogy (both execute a Library with user-supplied typed parameters) — uses parameters: Parameters (0..1). See CQL IG source and CQL community discussion.

Changes

• input/fsh/operations.fsh — replaced parameter[4] definition (19 lines of parts → 4 lines with type: Parameters)
• OperationDefinition-SQLQueryRun-intro.md — minor wording update
• OperationDefinition-SQLQueryRun-notes.md — rewrote all HTTP examples, added "Parameter Passing" section with CQL reference
• OpenSpec change artifacts in openspec/changes/align-sqlquery-run-with-cql/

Before / After

Before:

{ "name": "parameter", "part": [
  { "name": "name", "valueString": "patient_id" },
  { "name": "value", "valueString": "Patient/123" }
]}

After:

{ "name": "parameters", "resource": {
  "resourceType": "Parameters",
  "parameter": [
    { "name": "patient_id", "valueString": "Patient/123" },
    { "name": "from_date", "valueDate": "2024-01-01" }
  ]
}}

Test plan

• SUSHI compiles with 0 errors
• IG builds successfully, no new QA errors
• Review parameter table renders correctly on operation page

Closes #318
See also #320 (follow-up: GET parameter support)

🤖 Generated with Claude Code

[johngrimes]

This will need to be reconciled with #327 before merging.

[johngrimes]

I think this looks good, but we should merge #327 first, then merge master back into this branch.