Run a FHIR quality gate from any pipeline.
Start with local files and machine-readable output. Connect the same CLI to Records when you need runs, baselines, deltas, and evidence.
Available now · v0.1.1 · Apache-2.0
Smallest useful example
Turn a directory into a CI contract.
Run the same command locally and in CI. Machine-readable output and the process exit code let the pipeline own the gate.
Run a local gate
npx @records-fhir/cli validate-file ./fhir \ --engine \ --format junitExpected contract
What comes back
A deterministic exit status plus JUnit output that can be published by the existing test-reporting step in the pipeline.
| Runtime | Any Node.js-capable workstation or CI runner |
|---|---|
| Local mode | Files and directories; no account or Records instance required |
| Connected mode | Adds configured runs, accepted baselines, comparison and evidence through Records |
Built for one clear integration job
The surface stays small; Records carries the wider operational loop when you need it.
No-install local validation
Validate one file or a directory directly from npx.
CI-native contract
Use deterministic exit codes plus JSON or JUnit output in any Node.js pipeline.
Connected Records workflows
Point the CLI at Records for configured profile sets, runs, baselines, comparison, and export.
Scope
The boundary
Know what this surface owns before you put it into a workflow.
What remains outside this surface
Local mode validates the files you provide. It does not create Records run history, compare live environments, or produce governed evidence until connected to a Records instance.