The ISiK module "Vital signs and body measurements" (Vitalzeichen und Körpermaße) provides FHIR resources as a specification, examples and an implementation guide. The FHIR resources can be used for structured, REST-based exchange of vital signs in hospital environments.
This is a Pullreuqest that requires an increase in the Version number. Therefore, multiple outside-github, related Task have to be performed and checked.
All jobs with an x in the boxes were performed to the best of knowledge.
Pre-Merge Activities
[x] This PR refers to a versioned Branch with a name and a version number in the form of N.n.n, e.g. "TC_3.2.1".
[x] This PR has a clean meaningful commit history. Minor commits or commits without description have been squashed, at the latest now.
[x] The ./github/workflows/main.yml refers to the correct Firely Terminal and SUSHI Version.
[x] By running the _ReleasePublish.py script, release version and date was updated accordingly. The script ran without errors.
[x] Eventually, increase the dependency of to newer Basis Modul (package and sushi-config)
[x] New Release Notes were created, alined to the commit history and cleaned. In Github, go to
[x] -> Releases then -> Draft a new release with the Modul Name and Version, then
[x] -> Target the main-Branch and ->enter a new Tag according to the Version, then click.
[x] Click -> Generate Release notes , ->Adjust them if necessary and -> Copy/Paste the Details in the RealeaseNotes.md of the very Branch you want to merge.
[x] Finally -> Save as Draft
Merge and Publishing
[x] With the updated Version, Dates, and Release Notes (as described above) with the last committ into the Branch you want to merge.
[x] In GitHub -> Actions the ->CI (FHIR Validation) workflow terminates successfully.
[x] Add the Approve / the PR gets positively reviewed by a colleague.
[x] Merge (without squash) the PR, delete the Branch.
Post-Merge Activities
[x] Go to the corresponding SIMPLIFIER Project and -> Github -> Reimport the project.
[x] Go to the corresponding SIMPLIFIER Project and -> Packages -> Expand the Dropdown for Create -> Create new package for the project.
[x] With the corresponding version number, and
[x] The Release notes (from above) and a compare-link to the previous Release.
[x] Unlist the old package by -> clicking on the old package, -> go to Administration and -> click on Unlist
[x] Publish the previously drafted Release, including version number, on GitHub.
[x] Provide / Archive the IG in the corresponding gh-pages branch of the GitHub project.
[x] Checkout the Branch (no need to merge it later).
[x] Export from Simplifier via -> Guides -> Expand the Modul ... -> Export
[x] Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version corresponding) new folder in the branch folder structure.
[x] Update the file index.html and check rendering
[x] commit the branch.
[ ] If ISiK Basismodul was updated all depending Modules should be updated with a renewed dependency to the incremented Basismodul version - possibly including and closing technical corrections
Version Upgrade Template
Version: 4.0.0
Date:
Description
This is a Pullreuqest that requires an increase in the Version number. Therefore, multiple outside-github, related Task have to be performed and checked.
All jobs with an
xin the boxes were performed to the best of knowledge.Pre-Merge Activities
Merge and Publishing
Post-Merge Activities
Finished