TC 4.0.1

[f-peverali]

… FHIR Validation)

Version Upgrade Template

Version: 4.0.1

Date: 02.12.2024

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 x in the boxes were performed to the best of knowledge.

Pre-Merge Activities

• 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".
• The ./github/workflows/main.yml refers to the correct Firetly Terminal and SUSHI Version.
• By running the Release_Publish.py script, release version and date was updated accordingly. The script ran without errors.
• Eventually, increase the dependency of to newer Basis Modul (package and sushi-config)
• New Release Notes were created, aglined to the committ history and cleaned. In Github, go to
  • -> Releases then -> Draft a new release with the Modul Name and Version, then
  • -> Target the main-Branch and ->enter a new Tag according to the Version, then click.
  • 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.
  • Finally -> Save as Draft

Merge and Publishing

• With the updated Version, Dates, and Release Notes (as described above) with the last committ into the Branch you want to merge.
• In GitHub -> Actions the ->CI (FHIR Validation) workflow terminates successfully.
• Add the Approve / the PR gets posivitly reviewed by a collegue.
• Merge (without squash) the PR, delete the Branch.

Post-Merge Activities

• Go to the corresponding SIMPLIFIER Project and -> Github -> Reimport the project.
• Go to the corresponding SIMPLIFIER Project and -> Packages -> Expand the Dropdown for Create -> Create new package for the project.
  • With the corresponding version number, and
  • The Release notes (from above) and a compare-link to the previous Release.
  • Unlist the old package by -> clicking on the old package, -> go to Admininstration and -> click on Unlist
• Publish IG in Simplifier
  • Provide a version in the IG title --> (x.x.x)
  • Scope the IG to the published package
  • Set URL key to isik-[module-name]-version (version without dots)
  • Publish via Simplifier GUI (set to overwritable)
• Publish the previosuly drafteted Release, including version number, on GitHub.

Obsolet

• Provide / Archive the IG in the corresponding gh-pages branch of the GitHub project.
  • Checkout the Branch (no need to merge it later).
  • Export from Simplifier via -> Guides -> Expand the Modul ... -> Export
  • Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version coressponding) new folder in the branch folder structure.
  • committ the branch.

Finished

[f-peverali]

issue: hier ist ein veralteter Link.
question: @alexzautke auf was sollen wir hier am Besten verlinken - Stand Stufe 4? https://simplifier.net/guide/isik-connect-v4/ImplementationGuide-markdown-Conformance-ConformanceScopesKontexte?version=current

[f-peverali]

jo

[f-peverali]

question: @simoneOnFhir sollen wir die "USe Case Seite" Überarbeiten ? https://simplifier.net/guide/isik-dokumentenaustausch-401/Einfuehrung/UseCases/UseCases.page.md?version=current
... entsprechend der Basis https://simplifier.net/guide/isik-basis-401/Einfuehrung/UseCasesAnwendung?version=current ... ggf. streichen? Der eigentliche "Use Case" sit ja in der "Motivation erklärt mit " Voraussetzung dafür, ärztlichem und pflegerischem Personal relevante klinische Informationen an jedem Ort und zu jeder Zeit im benötigten Umfang zur Verfügung zu stellen." etc

-> kann raus

[f-peverali]

question: Ist der Satz noch zeitgemäß: "soll künftig jedoch auch Best Practice-Empfehlungen zur Einstellung von Dokumenten in die ePA eines Patienten" https://simplifier.net/guide/isik-dokumentenaustausch-401/Einfuehrung/Motivation.page.md?version=current