Skip to content

About

Offline compatibility evidence for HL7 FHIR R4 implementation-guide package releases

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

IG Release Check

CI

IG Release Check is an experimental local compatibility gate for released packages built for the HL7® FHIR® R4 standard, implemented in Python 3.12. The project has completed its Gate 0 technical evidence and a founder-operated real-package alpha against US Core 8.0.1 → 9.0.0.

Status: 0.1.0a0 is a public-development preview, not a validated public alpha. The strict policy is experimental, and community promotion remains gated on an independent FHIR practitioner run.

Start with COMPATIBILITY-CONTRACT.md. Reproduce the evidence with evidence/README.md.

The scoped Python architecture, promotion gates, and community-release sequence are in PROJECT-PLAN.md.

Run from source

Install uv, clone this repository, and run:

uv sync --locked --python 3.12
uv run --python 3.12 ig-release-check --version

Compare two local FHIR package archives or package directories:

uv run --python 3.12 ig-release-check compare baseline.tgz candidate.tgz \
  --policy strict --format markdown --output report.md

The comparison itself is offline. Exit 0 means no configured blocking finding, exit 1 means the policy deliberately blocked, and exit 2 means the tool could not produce a trustworthy verdict.

Evidence

Current evidence:

  • all 15 synthetic validator cases pass with freshly generated snapshots, network access disabled, and no terminology cache;
  • the direct canonical-surface set-difference proof passes;
  • the pinned US Core alpha produced 67 specific findings across 67 matched profiles and 3,265 snapshot elements; see real-alpha/README.md; and
  • the first Fable adversarial review was reconciled; the attempted closure pass exhausted its budget without returning a verdict, so no independent PASS is claimed. See evidence/fable-review.md.

No patient data, hosted service, or AI model is involved in runtime analysis. The current policy is experimental; exit 0 never means clinically compatible.

Contributing and security

FHIR package maintainers can help most by reviewing the taxonomy against real release pairs. Start with CONTRIBUTING.md, and report archive handling or unsafe-input issues through SECURITY.md. Never attach patient data or private package contents to a public issue.

License

Apache License 2.0. See LICENSE.

Some reproducible fixtures incorporate content generated from the CC0-licensed HL7 FHIR specification. See THIRD_PARTY_NOTICES.md.

HL7, FHIR, and the FHIR flame design are registered trademarks of Health Level Seven International. Their use does not constitute endorsement by HL7.

About

Offline compatibility evidence for HL7 FHIR R4 implementation-guide package releases

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages