I ceated a table of THO Value Sets and Code Systems to update my packages. Instead of having to update each version manually, it Would be nice to be able specify the version of THO on which to base the Code systems and Value Sets in the Manifest and have those versions populated the version field over-riding the package versions.
example THO tables I used for US Core to update the versions:
CodeSystem Version Comparison
Comparison of CodeSystem .version across hl7.terminology.r4 packages 5.2.0, 6.0.2, 6.5.0, and 7.2.0.
Sorted alphabetically by URL. A ✅ marks each cell where the version increased relative to the prior column (5.2.0 is the baseline).
Note: v2-0074, v2-0131, v2-0443, and v2-0493 carry a higher version number in 5.2.0 than in 6.0.2 (a THO renumbering), so no ✅ is shown at the 6.0.2 column for those rows.
I ceated a table of THO Value Sets and Code Systems to update my packages. Instead of having to update each version manually, it Would be nice to be able specify the version of THO on which to base the Code systems and Value Sets in the Manifest and have those versions populated the version field over-riding the package versions.
example THO tables I used for US Core to update the versions:
CodeSystem Version Comparison
Comparison of CodeSystem
.versionacrosshl7.terminology.r4packages 5.2.0, 6.0.2, 6.5.0, and 7.2.0.Sorted alphabetically by URL. A ✅ marks each cell where the version increased relative to the prior column (5.2.0 is the baseline).