Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R4
Work Group:

FHIR Infrastructure
Related URL:
http://hl7.org/fhir
Related Artifact(s):

DomainResource
Related Page(s):

(NA)
Grouping:
- FHIR-Tools-IG
Resolution Description:

Hide

We will update the documentation to indicate that some legacy packages will use fhir-versions-list instead of fhirVersions. However, we won't fix what's there for the old packages as that would mean a breaking change for these old packages.

Show
We will update the documentation to indicate that some legacy packages will use fhir-versions-list instead of fhirVersions. However, we won't fix what's there for the old packages as that would mean a breaking change for these old packages.
Resolution Vote:
Eric Haas/John Moehrke: 6-0-0
Change Category:
Clarification
Change Impact:
Non-substantive
Applied for Version:

R5

(sorry, this is a tooling change request, but cannot find how to create one for tooling)

The core packages for R3 and R4 all contain a package.json file, which has a property "fhir-version-list". It seems this to me this is actually the `fhirVersions` property (as described in the FHIR NPM Package specification (https://confluence.hl7.org/display/FHIR/NPM+Package+Specification#NPMPackageSpecification-Packagemanifest).

In fact, other packages like "hl7.fhir.us.core" do use `fhirVersions`.

Why do these two properties differ? If they are not the same, I think we should document both.