Skip to content

Use R4-specific fhir-model artifact, drop direct fhir-path dep - #69

Draft
LZRS wants to merge 1 commit into
ohs-foundation:mainfrom
LZRS:use-r4-specific-fhir-artifacts
Draft

Use R4-specific fhir-model artifact, drop direct fhir-path dep#69
LZRS wants to merge 1 commit into
ohs-foundation:mainfrom
LZRS:use-r4-specific-fhir-artifacts

Conversation

@LZRS

@LZRS LZRS commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Depend on dev.ohs.fhir:fhir-model-r4 instead of the fhir-model umbrella, which also pulls in R4B and R5. All app models are dev.ohs.fhir.model.r4.*.

Remove the direct fhir-path dependency: no app code uses dev.ohs.fhir.fhirpath, and it still resolves transitively via fhir-engine and fhir-data-capture. It stays on the pre-split 1.0.0-beta03 because those two call FhirPathEngine.Companion.forR4(), which beta04+ moved out of the companion into a fhir-path-r4 extension.

Refresh the bundled-libraries table to match, and add the missing fhir-engine row.

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

  • All CI build checks pass e.g. Tests
  • Appropriate changes to documentation are included in the PR

Depend on dev.ohs.fhir:fhir-model-r4 instead of the fhir-model umbrella,
which also pulls in R4B and R5. All app models are dev.ohs.fhir.model.r4.*.

Remove the direct fhir-path dependency: no app code uses
dev.ohs.fhir.fhirpath, and it still resolves transitively via fhir-engine
and fhir-data-capture. It stays on the pre-split 1.0.0-beta03 because
those two call FhirPathEngine.Companion.forR4(), which beta04+ moved out
of the companion into a fhir-path-r4 extension.

Refresh the bundled-libraries table to match, and add the missing
fhir-engine row.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant