Version updated for https://github.com/medvertical/records-fhir-validator to version validator-v0.4.4. This action is used across all versions by 0 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. Action Summary This GitHub Action is a TypeScript-based FHIR validator designed to automate validation of FHIR JSON resources in CI pipelines, GitHub Actions, or standalone Node.js environments. It supports multiple FHIR versions (R4, R4B, R5, R6) and provides features such as validating against StructureDefinitions, FHIRPath expressions, terminology bindings, references, slicing, extensions, Bundle rules, metadata, and custom rules without requiring a JVM or database. The action is available for both GitHub Actions pinning using floating tags and exact version pins, ensuring reproducibility and auditability.

Version updated for https://github.com/medvertical/records-fhir-validator to version validator-v0.4.2. This action is used across all versions by 0 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed npm tarball release for @records-fhir/validator@0.4.2. Synced from medvertical/records monorepo. Install npm install @records-fhir/validator@0.4.2 What’s new in 0.4.2 Patch release for validator architecture boundaries, evidence policy, and maintainability after the 0.4.1 evidence release. Added Added stable host and conformance package surfaces for embedding and evidence tooling, keeping repository consumers off deprecated implementation subpaths. Added dedupeIssuesWithTrace() so duplicate-suppression decisions expose the named policy rule that removed an issue. Added an explicit FHIR Schema runtime policy export that keeps the graph path evidence-only until Java/reference and dual-path gates justify promotion. Changed Hardened public-export and mirror-import architecture guards so new internal validator exports or repository imports fail fast. Split terminology remote CodeSystem budget handling out of the API client and kept the fail-open budget reason traceable. Split remote CodeSystem budget aggregation tests into focused coverage. Documentation Documented validator fallback, fail-open, fail-closed, legacy compatibility, and release-gate guardrails. Verification Verified with merged PR #252 CI, main CI, validator build, OSS boundary audit, OSS package smoke, architecture guards, focused Vitest suites, and npm publish dry-run. Matched npm tarballs @records-fhir/validator@0.4.2 — also tagged validator-v0.4.2 @records-fhir/validation-types@0.1.5 The matching GitHub Action release (if any) is published separately under tag v0.4.2 and is not auto-synced; this release covers the npm package only.

Version updated for https://github.com/medvertical/records-fhir-validator to version validator-v0.4.1. This action is used across all versions by 0 repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed npm tarball release for @records-fhir/validator@0.4.1. Synced from medvertical/records monorepo. Install npm install @records-fhir/validator@0.4.1 What’s new in 0.4.1 Patch release for the standalone validator evidence lanes and MII reference workflow. Released with @records-fhir/validation-types 0.1.5. Added Added validator claim summary generation for publishing the current HL7, MII reference, and FHIR Schema dual-path evidence in one machine-readable artifact. Added FHIR Schema dual-path action reporting so unconfirmed graph/reference buckets remain explicit follow-up work instead of hidden parity debt. Added package-backed terminology diagnostics and local terminology server helpers for deterministic MII/FHIR Schema quality lanes. Changed Hardened the MII reference triangulation workflow with reference-health probes, policy-rule extraction, skip taxonomy, and failed-profile prewarm details. Refreshed the public validator documentation around the 2026-07-01 evidence: 496/496 HL7 executable JSON comparisons, 231/231 measured MII reference parity, and 555-fixture FHIR Schema dual-path coverage. Tightened FHIR Schema graph slicing, reference-target extraction, and pattern diagnostics while keeping the graph path in parallel evidence mode. Fixed Fixed MII package relevance detection so package names containing substrings such as isik are not misclassified as Gematik ISiK packages. Fixed nested profile slice scoping and choice/FHIRPath edge cases uncovered by the MII and FHIR Schema dual-path lanes. Verification Verified with repository lint, stable tests, targeted validator Vitest suites, full affected conformance, MII reference gate, HL7 parity gate, and FHIR Schema dual-path report generation. Matched npm tarballs @records-fhir/validator@0.4.1 — also tagged validator-v0.4.1 @records-fhir/validation-types@0.1.5 The matching GitHub Action release (if any) is published separately under tag v0.4.1 and is not auto-synced; this release covers the npm package only.