diff --git a/.nojekyll b/.nojekyll
new file mode 100644
index 00000000000..e69de29bb2d
diff --git a/404.md b/404.md
new file mode 100644
index 00000000000..a8a831d4fa7
--- /dev/null
+++ b/404.md
@@ -0,0 +1,8 @@
+—
+layout: default
+title: “404: Page not found”
+permalink: 404.html
+—
+
+# 404: Page not found
+Sorry, we’ve misplaced that URL or it’s pointing to something that doesn’t exist. [Head back home]({{ site.url }}) to try finding it again.
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 00000000000..8f0fef94665
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,12 @@
+# https://github.com/envygeeks/jekyll-docker did not work
+FROM ruby:3
+RUN gem install bundler
+COPY Gemfile .
+COPY Gemfile.lock .
+RUN bundle install
+WORKDIR /usr/src/app
+COPY . .
+
+EXPOSE 4000
+ENTRYPOINT ["bundle","exec","jekyll"]
+CMD ["serve","--incremental"]
diff --git a/LICENSE.md b/LICENSE.md
new file mode 100644
index 00000000000..1c061d37bc5
--- /dev/null
+++ b/LICENSE.md
@@ -0,0 +1,9 @@
+Copyright (c) 2013 Mark Otto.
+Copyright (c) 2019 Konrad Höffner
+Copyright (c) 2021 Michelle Bindel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/README.md b/README.md
new file mode 100644
index 00000000000..e0f370f7143
--- /dev/null
+++ b/README.md
@@ -0,0 +1,151 @@
+
+
+# SNIK Website
+
+[](https://github.com/snikproject/snik.eu/actions/workflows/deploy.yml)
+[](LICENSE)
+
+Live on and .
+This is the website for SNIK, the Semantic Network of Information Management in Hospitals.
+It is a copy of the [HITO website](https://github.com/hitontology/hitontology.eu), which is a fork of the [Hyde layout](https://github.com/poole/hyde), which itself is based on Jekyll, a static site generator.
+
+## Setup
+
+1. Install Ruby
+2. Install Bundler
+3. Use Bundler to install the dependencies
+
+### Example for Arch Linux
+
+ $ sudo pacman -S ruby
+
+Add the following to your environment configuration file, such as `.profile` or `.zshrc` and reload (`source ~/.zshrc`) it:
+
+ export GEM_HOME="$(ruby -e 'puts Gem.user_dir')"
+ export PATH="$PATH:$GEM_HOME/bin"
+
+Use bundler with the provided Gemfile:
+
+ $ gem install bundler
+ $ bundle install
+
+### Example for MacOS (with Homebrew)
+
+Install Ruby:
+
+ $ brew install ruby
+
+Add the brew ruby path to your shell configuration.
+If you're using Zsh, add the following lines to `~/.zshrc`
+
+ export GEM_HOME="$(ruby -e 'puts Gem.user_dir')"
+ export PATH="$PATH:$GEM_HOME/bin"
+
+Install bundler and the gems:
+
+ $ gem install --user-install bundler
+ $ bundle install
+
+## Preview
+Switch to the `master` branch and run `bundle exec jekyll serve --incremental`.
+Check if everything looks normal.
+
+## Build
+The GitHub workflow in `.github/workflows/deploy.yml` automatically builds the master branch and deploys it on the static branch.
+To build locally, run `bundle exec jekyll build (--incremental)`,
+This will put the static HTML content into the `_site` folder.
+
+## Deploy
+We serve the content of the static branch at the official SNIK website .
+The static branch is also automatically served using GitHub pages at .
+
+## Using Docker
+If you cannot or do not want to install Ruby and the gems on your system, or there is some problem with Ruby, you can also use the Dockerfile, which should work everywhere.
+Use the following commands or execute the associated script.
+
+| goal | command | script |
+|--------------|---------------------------------------------------------------------------|----------------------------|
+| build image | docker build -t snik.eu . | scripts/docker-build |
+| preview page | docker run --rm --network="host" snik.eu | scripts/docker-run-preview |
+| build page | docker run --rm -it --volume="$PWD:/usr/src/app" -it snik.eu build | scripts/docker-run-build |
+
+## Troubleshooting
+
+### Ruby cannot find the native extensions
+
+#### Exemplary error message
+
+ bundler: failed to load command: jekyll (/home/konrad/.local/share/gem/ruby/3.0.0/bin/jekyll)
+ /home/konrad/.local/share/gem/ruby/3.0.0/gems/ffi-1.15.1/lib/ffi.rb:5:in `require': libffi.so.7: cannot open shared object file: No such file or directory - /home/konrad/.local/share/gem/ruby/3.0.0/extensions/x86_64-linux/3.0.0/ffi-1.15.1/ffi_c.so (LoadError)
+
+This can happen if you already built the native extensions (e.g. via `bundle install`) with an older version of Ruby and then upgrade Ruby.
+Even `bundle install` will not rebuild the native extensions in that case if they are already present.
+To fix this, run `bundle pristine`.
+It is also possible that you installed some dependencies using `gem install` system- or user-wide, which bundler will not overwrite by default.
+In this case, even `bundle pristine` may not be enough.
+In our experience, this can be fixed by deinstalling Ruby, deleting all leftover gem directories and reinstalling Ruby afterwards.
+
+### Preview URL not working in MacOS using Docker
+
+Docker may run in it's own virtual machine under MacOS and not thus not forward `--network="host"` to the network of the machine itself.
+While the default way of port mapping in Docker using the `-p 4000:4000` gets forwarded to the local host under MacOS, this does not work with the underlying Jekyll server of this website.
+Thus, there may not be a way to preview the docker build using `jekyll serve` on MacOS.
+However you can still build it using Docker and use a local webserver to preview the _site folder.
+
+## Explanation for non-developer Windows users
+The SNIK website does not have a WYSIWYG editor like WordPress or Drupal, because it was originally maintained by the SNIK developers, for whom this way had many advantages, such as speed, simplicity, flexibility, stability, versioning and more.
+For example, even if the server crashes and all data and backups are lost, the newest state of the website or any earlier version can be instantly restored.
+This website is not designed to be changed by non-technical users, but if you want to make a small change after the end of the project and the developers are not reachable but you work with Windows and don't have technical knowledge and can't install the development tools (Git and either Ruby or Docker), you can follow this guide.
+
+This is the Git repository where the source code for the SNIK website is hosted.
+The website is not just static HTML, which you can put on an HTML webserver directly, but instead it is written in [Markdown](https://www.markdownguide.org/), an easy to read text format that is transformed into HTML.
+Like a compiler, which transforms source code into an executable, Jekyll transforms Markdown into HTML that can be served by a webserver.
+Jekyll also uses templates and layouts so you get a page with a sidebar, styling and so on.
+
+### Online Editing---Directly on Master
+If you want to change content in a page on the website and your GitHub account has the required rights, you can log in to GitHub and edit the content using the pen symbol ("Edit this file") in one of the files, for example [index.md](https://github.com/snikproject/snik.eu/blob/master/index.md) for the home page.
+GitHub will give you a basic idea of how it will turn out in the "Preview" tab next to "Edit file", however it will not include any of the styling of Jekyll, so the layout will be broken and there is no sidebar but you can at least see the text.
+Then you can commit the changes to the master branch.
+This violates our normal procedure because you should always make sure that the master branch is in a functioning state, which you can't preview, but if you don't have any other option and you only make small textual changes it is relatively low risk.
+There are automatic actions in place that will now build the website and deploy it on the ["static" branch](https://github.com/snikproject/snik.eu/tree/static) as HTML.
+When the [actions are successfully finished (green checkmark)](https://github.com/snikproject/snik.eu/actions), the page is automatically published on GitHub pages at , where you can check if everything is working as expected.
+Then someone with access to the "datrav" server can do a `git pull` on `/var/www/snikproject/`.
+It is also possible to circumvent the server entirely and [point the domain `snik.eu` to GitHub pages](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site), however then you can't check between build and deploy.
+
+### Online Editing---Pull request
+If you don't have edit rights, you can instead choose to create a pull request.
+This is also good if you want to edit multiple files, such as an image and it's refering text, because then those with write access can perform a squash merge to combine your changes into a single commit.
+
+Delete and add images in the `public` folder as needed, change content in the appropriate `.md` files.
+
+1. Perform the first change on the website and create a pull request in a new branch with a note to not merge it yet.
+2. Perform the other changes on the website on the same branch.
+3. Use a "Squash Merge" to combine all commits into one into the master branch and delete the temporary branch.
+4. Wait until the [build and deploy actions](https://github.com/snikproject/snik.eu/actions) are finished, then check if everything is correct.
+5. Update the repository on the server.
+
+### GitHub Desktop
+You can also use the [GitHub Desktop client on Windows](https://desktop.github.com/).
+After checking out this repository, choose "Use for my own purposes" because we want to modify snik.eu as a fork of Jekyll and not Jekyll itself.
+Modify the files using your normal tools like a file explorer and text editor and then commit the changes to the master branch.
+
+### Preview on Windows
+There may be a more elegant way to accomplish this, if you know one, please create a pull request or an issue.
+Needs the Windows package manager `winget` on your system.
+
+ winget install RubyInstallerTeam.RubyWithDevKit
+
+Open a terminal as administrator
+
+ ridk install
+
+Start `gem`, it will tell you a path for your gemfiles.
+Open a new terminal so that the `gem` command is available.
+Add that path your PATH environment variable but replace the slashes '/' with backslashes '\'.
+
+Open a new terminal in your project directory, e.g. using GitHub Desktop.
+
+ gem install --user-install bundler
+ bundle install
+
+Then you should be able to run `bundle exec jekyll serve --incremental`, which shows a link like that you can enter in the browser to preview the page.
diff --git a/abschlussarbeiten/index.html b/abschlussarbeiten/index.html
new file mode 100644
index 00000000000..ea6c22d4708
--- /dev/null
+++ b/abschlussarbeiten/index.html
@@ -0,0 +1,219 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Abschlussarbeiten · SNIK
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Systemanalyse und -bewertung von Informationsmanagement-Informationssystemen (IMIS)
+Masterarbeit
+Bearbeitet von: Manuel Jung
+Betreut von: Christian Kücherer
+Postanschrift:
+Prof. Dr. Alfred Winter
+Universität Leipzig
+Institut für Medizinische Informatik, Statistik und Epidemiologie
+Härtelstraße 16-18
+04107 Leipzig
+
These pages are being maintained by the research group Management of Information Systems in the Healthcare (MIG) of the Institute for Medical Informatics, Statistics and Epidemiology (IMISE) of the University of Leipzig.
+
+
Institut für Medizinische Informatik, Statistik und Epidemiologie
+Universität Leipzig
+Härtelstraße 16-18
+04107 LEIPZIG
+GERMANY
+
+
The University of Leipzig is a public body. It is legally represented by the acting chancellor. Further information, especially concerning supervisory authority, can be found in the imprint of the University of Leipzig.
+
+
Disclaimer
+
+
Every effort is taken to ensure that the information contained on this website is accurate at the time of creation and/or modification of the website. We cannot, however, guarantee that the contents provided will always be current, accurate or complete. The use of contents from this website is at your own risk. We reserve the right to remove, vary or amend any of the content which appears on the website at any time and without prior notice. Contributions identified by name reflect the opinions of the authors and not necessarily the opinion of MIG. The mere use of the website does not create any contractual relationship between the user and MIG. Further, we do not in any way guarantee that the website will be available, uninterrupted or error free.
+
+
According to §§8 to 10 of the TMG (German Tele-Media Act), we are not obligated to monitor third-party information provided or stored on our website. However, we shall promptly remove any content upon becoming aware that it violates the law. Our liability in such an instance shall commence at the time we become aware of the respective violation. External Links
+
+
This website provides links to other websites (“external links”), which are subject to the liability of the respective owners/providers. At the time these websites were linked to ours, we found NO GROUNDS WHATSOEVER of any likely violation. Likewise, we have no control over the current and future design and over the content of the pages linked with this website. The inclusion of external links should not be taken as an endorsement by MIG of the opinions expressed or services provided at those sites. Without concrete evidence of legal violations a permanent control of the external links is not reasonable. Should any violations become known, such external links will be deleted immediately. Copyrights
+
+
The information published on this site (including, but not limited to, texts and graphics) is subject to the copyright laws of Germany. Any use not permitted by German copyright requires the prior written consent of MIG or the respective rights owners. This applies especially to duplication, adaptation, translation, storage, processing and reproduction of contents in databases or other electronic media and systems. Contents and rights of third parties are marked as such. The unauthorized reproduction or distribution of contents or entire sites is not allowed and liable to prosecution. Only the production of copies and downloads for personal, private and non-commercial use is allowed.
+
+
The presentation of this website in external frames is not allowed without the prior permission in writing of MIG. Privacy and Data Protection
+
+
Please be aware that there are inherent security risks in transmitting data over the Internet (e.g. communication by e-mail) since it is impossible to protect completely against unauthorized access by third parties.
+
+
Using the contact details of the imprint for commercial purposes is expressly not allowed, unless we have given our written consent or there is already a business relationship. MIG and all persons named on this website hereby object to any commercial use and disclosure of their data.
+
+
Jurisdiction
+
+
These terms and conditions will be governed by the laws of the Federal Republic of Germany.
Ziel des DFG-geförderten Projektes ist ein semantisches Netz des integrierten Informationsmanagements im Krankenhaus (SNIK), welches Begriffe des Informationsmanagements und deren Beziehungen untereinander beschreibt.
+Auf Basis des SNIK entsteht das Werkzeug „CIO-Navigator“ (CION) und ein Blended-Learning-Modul für die Ausbildung in der Medizinischen Informatik.
+
+
Projektlaufzeit: 2014–2017
+
+
Projektförderkennzeichen: 1605/7-1 und 1387/8-1
+
+
Eine Auswahl unserer Visualisierungen, Schnittstellen und Werkzeuge:
A collection of links to our internal workspaces and applications
+
By clicking on any of the links below, which are only meant to be used internally be the SNIK team, you consent to potential cookies and usage of external services, some of which may reside outside of the EU.
Informationssystem und Informationsmanagement im Krankenhaus
+
+
Fortschritte in der Informationstechnologie (IT) schaffen neue Möglichkeiten für höhere Qualität und Effizienz in Gesundheitsversorgung und medizinischer Forschung und Lehre.
+Dies gilt für alle Krankenhäuser, aber besonders für Krankenhäuser in der Universitätsmedizin, wo Patientenversorgung, Forschung und Lehre in besonderer Weise integriert werden müssen.
+Weil Möglichkeiten und Chancen der IT bekannt sind, besteht sowohl bei den Nutzern von IT als auch beim Krankenhausmanagement sehr häufig große Unzufriedenheit über die als schleppend und unzureichend angesehene Einführung der Technologien.
+Ein Krankenhaus muss daher nicht nur in sein Informationssystem (IS), d.h. in sein Gesamtsystem aller Anwendungssysteme und physischer Datenverarbeitungssysteme, investieren.
+Vielmehr bedarf es des systematischen Managements, wobei einerseits die Komplexität des IS als auch seines Managements von den Nutzern abgeschirmt werden muss und andererseits durch geeignete Informationen Vertrauen in das IS und in sein Management erworben werden sollte.
+Das Management von IS wird als Informationsmanagement (IM) bezeichnet.
+Die Aufgaben des IM sind nicht mehr vorrangig darauf ausgerichtet, ein Rechenzentrum operativ zu betreiben, sondern das Krankenhauspersonal bei der Behandlung von Patienten und bei Sekundärprozessen, wie z. B. Ressourcenverwaltung und Personalmanagement, effizient zu unterstützen.
+Deshalb arbeitet das IM nicht nur mit Informationen zu Anwendungssystemen und Hardware, sondern es muss ebenso die Ziele des Krankenhauses und den Ablauf der Krankenhausprozesse, die zu diesen Zielen beitragen, im Blickfeld haben.
+Das IM im Krankenhaus umfasst also viele unterschiedliche Aufgaben, die wechselseitig durch Informationsaustausch miteinander vernetzt sein müssen.
+In der Lehre zum Informationsmanagement in Krankenhäusern besteht die Herausforderung, diese unterschiedlichen Aufgaben und dafür benötigte Informationen systematisch und in ihrem Gesamtzusammenhang zu vermitteln.
+
+
Bedarf an Informationen über das Informationssystem und das Informationsmanagement im Krankenhaus
+
+
Die einfache Bereitstellung einzelner Kostenkennzahlen reicht nicht aus, die Informationsbedürfnisse des Chief Information Officers (CIO) und der Krankenhausleitung zu befriedigen.
+Vielmehr benötigen sie ein tieferes Verständnis dafür, wie das IS zum Erreichen der strategischen Unternehmensziele eingesetzt werden kann.
+Daher sind CIO und Krankenhausleitung auf vernetzte Informationen über das Projektgeschehen im taktischen IM, den Betrieb des IS im operativen IM sowie die langfristige Weiterentwicklung im strategischen IM angewiesen.
+Die Informationen über das IM müssen wiederum mit Informationen über das IS und den von ihm unterstützten Geschäftsprozessen und mit der Unternehmensstrategie vernetzt sein.
+Sowohl CIO als auch Krankenhausleitung benötigen Unterstützung bei der Navigation durch diese vernetzten Informationen.
+Dafür sind möglichst formale Modelle des vernetzten IM notwendig.
+
+
Ansätze für das vernetzte Informationsmanagement
+
+
Grundsätzlich unterscheidet man im Informationsmanagement drei Ansätze mit entsprechend unterschiedlichen Schwerpunkten [1]:
+
+
+
Problemorientierte Ansätze legen den Fokus auf das strategische IM und das Strategic Alignment.
+
Aufgabenorientierte Ansätze sammeln die vielfältigen Aufgaben des Managements vom Projektmanagement über das operative Management bis zur Strategieformulierung und bemühen sich um einen systematischen Zusammenhang.
+
Prozessorientierte Ansätze detaillieren die Aufgaben des IM.
+
+
+
In der Summe der Ansätze werden also die relevanten Aspekte des IM angesprochen und je nach Ansatz auch Verknüpfungen zwischen Aufgaben des IM verbal erläutert.
+Ist in Veröffentlichungen zu den Ansätzen von Modellen des IM die Rede, dienen solche Modelle allerdings eher einer groben Strukturierung des Ansatzes.
+Sie beschreiben Konzepte des IM und ihre Beziehungen untereinander weder semiformal noch formal.
+Dies wäre aber die Voraussetzung für die Implementierung eines softwarebasierten Werkzeugs des vernetzten Informationsmanagements, das alle für die Entscheidungen von CIOs erforderlichen Informationen integriert.
+In der Lehre erleichtert eine zumindest semiformale Beschreibung die Vermittlung und systematische Einordnung von Begriffen und unterschiedlichen Ansätzen des Informationsmanagements.
+
+
Werkzeuge des vernetzten Informationsmanagements
+
+
Am Markt werden vielfältige generische Werkzeuge angeboten, die dem CIO und der Krankenhausleitung helfen könnten, die verschiedenen Informationen innerhalb des IM zu überblicken und zur Planung, Steuerung und Überwachung zu verwenden.
+Hierbei sind insbesondere Dashboards und Werkzeuge zur Modellierung von IS-Architekturen zu nennen.
+
+
Den auf dem Markt befindlichen Dashboards und Modellierungswerkzeugen liegen allerdings unterschiedliche Terminologien zugrunde.
+Außerdem stellen sie unterschiedliche Aspekte des IS und IM in den Vordergrund, welche miteinander vernetzt werden müssen.
+Es herrscht ein Mangel an Integration der für Entscheidungen von CIOs erforderlichen Informationen durch die gängigen Werkzeuge [2].
+
+
Semantische Netze und Ontologien zur Formalisierung des vernetzten Informationsmanagements
+
+
Das semantische Netz ist eine Technik, welche Informationen als Verknüpfungen zwischen Objekten darstellt.
+Je nach Grad der Formalisierung kann auch von einem Modell gesprochen werden [3].
+Wenn ein solches Modell einen hohen Komplexitäts- und Formalisierungsgrad hat und den Regeln der Prädikatenlogik folgt, kann man auch von einer Ontologie sprechen.
+Eine Ontologie ist die „explizite Spezifikation einer Konzeptualisierung“ [4].
+Sie wird in der Informatik genutzt, um Wissen über eine Domäne zu strukturieren, es vollständig abzubilden und schließlich in Softwareanwendungen zu repräsentieren und den Austausch von Daten inkl. ihrer Semantik zwischen Softwareanwendungen zu ermöglichen.
+Soll eine Domäne wie das vernetzte IM als Ontologie modelliert werden, wird eine Top-Level-Ontologie benötigt, die domänenunabhängige Konzepte zur Beschreibung von Wissen vorgibt.
+Die Formalisierung als Ontologie ist insbesondere nötig, wenn eine Werkzeugunterstützung für die Vernetzung zwischen Ansätzen des IM entwickelt werden soll.
+
+
Semantische Netze können Ontologien gegenüber von Vorteil sein, wenn das Domänenwissen nicht nur für Computer interpretierbar, sonder auch für menschliche Nutzer verständlich sein soll.
+Daher sind semantische Netze für die Darstellung des vernetzten IM im Krankenhaus gerade in der Lehre besonders geeignet.
+
+
Eigene Vorarbeiten
+
Projektbezogene Publikationen
+
+
Winter AF, Ammenwerth E, Bott OJ, Brigl B, Buchauer A, Gräber S, et al (2003).
+Strategic Information Management Plans: The Basis for systematic Information Management in Hospitals.
+Yearbook of Medical Informatics.
+Stuttgart: Schattauer; 2003. p. 431-41.
+
+
Müller U, Winter A (2006).
+A monitoring infrastructure for supporting strategic information management in hospitals based on key performance indicators.
+In: Hasmann A, Haux R, van der Lei J, De Clercq E, Roger-France F, editors.
+Ubiquity: Technologies for Better Health in Aging Societies (European Notes in Medical Informatics Vol II No2); 2006. p. 328–32.
+
+
Jahn F, Winter A (2011).
+A KPI Framework for Process-based Benchmarking of Hospital Information Systems.
+Stud Health Technol Inform. 2011;169:542-6.
+
+
Mueller U, Issler L, Funkat G, Winter A (2009).
+An Interactive Strategic Information Management Plan to Integrate Strategic and Tactical Information Management in Hospitals.
+IEEE Proceedings of the ICSE 2009 Workshop Software Engineering in Health Care; 2009. p. 12-9.
+
+
Winter A, Brigl B, Funkat G, Häber A, Heller O, Wendt T (2007).
+3LGM²-Modeling to Support Management of Health Information Systems.
+International Journal of Medical Informatics. 2007;76(2-3):145-50.
+
+
Paech B, Kohler K (2003).
+Task-driven Requirements in object-oriented Development.
+In: Leite J, Doorn J, editors.
+Perspectives on Requirements Engineering: Kluwer Academic Publishers; 2003.
+
+
Herrmann A, Paech B (2008).
+MOQARE: Misuse-oriented Quality Requirements Engineering.
+Requirements Engineering Journal. 2008;13(1):73-86.
+
+
Zorn-Pauli G, Paech B, Beck T, Karey H, Ruhe G (2013).
+Analyzing an Industrial Strategic Release Planning Process – A Case Study at Roche Diagnostics.
+Int Conf REFSQ, LNCS 7830: Springer; 2013. p. 269-84.
+
+
Glesner S, Jähnichen S, Paech B, Rumpe B, Wetter T, Winter A (2008).
+Manifest: Strategische Bedeutung des Software Engineering für die Medizin.
+Informatik Forschung und Entwicklung. 2008;22(3):127-35.
+
+
Forschungsbedarf
+
+
Es existieren keine Ontologie und kein semantisches Netz des vernetzten IM im Krankenhaus.
+Ein semantisches Netz des vernetzten IM im Krankenhaus würde Folgendes ermöglichen:
+
+
+
Die komplexen Zusammenhänge der verschiedenen Ansätze und Aspekte des IM könnten in der Lehre besser vermittelt werden.
+
Die verschiedenen Ansätze des IM könnten in der Forschung systematischer weiterentwickelt, branchenspezifisch angepasst und besser integriert werden.
+
Werkzeuge für das IM könnten zielgerichteter entwickelt und besser integriert werden.
+
CIO und Krankenhausleitung könnten besser kommunizieren, da sie mit denselben Werkzeugen auf dieselben Informationen zugreifen könnten.
+
+
+
Literaturverzeichnis
+
+
+
Krcmar H. Informationsmanagement. 4 ed. Berlin: Springer; 2005.
+
Riempp G, Gieffers-Ankel S. Application portfolio management: a decision-oriented view of enterprise architecture. Information Systems and E-Business Management. 2007;5(4):359-78.
Gruber TR. Toward Principles for the Design of Ontologies Used for Knowledge Sharing. International Journal Human-Computer Studies. 1995;43(5-6):907-28.
+
+
+
+
+
+
+
+
diff --git a/public/A Task-oriented Requirements Engineering Method for Personal Decision Support Systems.pdf b/public/A Task-oriented Requirements Engineering Method for Personal Decision Support Systems.pdf
new file mode 100644
index 00000000000..70a7459d243
Binary files /dev/null and b/public/A Task-oriented Requirements Engineering Method for Personal Decision Support Systems.pdf differ
diff --git a/public/An Approach to Support Collaborative Ontology Construction.pdf b/public/An Approach to Support Collaborative Ontology Construction.pdf
new file mode 100644
index 00000000000..390e9a7cfb4
Binary files /dev/null and b/public/An Approach to Support Collaborative Ontology Construction.pdf differ
diff --git a/public/An Ontology-Based Scenario for Teaching the Management of Health Information Systems.pdf b/public/An Ontology-Based Scenario for Teaching the Management of Health Information Systems.pdf
new file mode 100644
index 00000000000..7e49d21640b
Binary files /dev/null and b/public/An Ontology-Based Scenario for Teaching the Management of Health Information Systems.pdf differ
diff --git a/public/CIONo-Screenshot.png b/public/CIONo-Screenshot.png
new file mode 100644
index 00000000000..62c44c4c431
Binary files /dev/null and b/public/CIONo-Screenshot.png differ
diff --git a/public/Charakteristika von IT-Abteilungen in Krankenhaeusern in Deutschland.pdf b/public/Charakteristika von IT-Abteilungen in Krankenhaeusern in Deutschland.pdf
new file mode 100644
index 00000000000..e4b3cbc8bc0
Binary files /dev/null and b/public/Charakteristika von IT-Abteilungen in Krankenhaeusern in Deutschland.pdf differ
diff --git a/public/DsTORE.png b/public/DsTORE.png
new file mode 100644
index 00000000000..1244b844baf
Binary files /dev/null and b/public/DsTORE.png differ
diff --git a/public/Ein semantisches Netz des Informationsmanagements im Krankenhaus.pdf b/public/Ein semantisches Netz des Informationsmanagements im Krankenhaus.pdf
new file mode 100644
index 00000000000..90637590442
Binary files /dev/null and b/public/Ein semantisches Netz des Informationsmanagements im Krankenhaus.pdf differ
diff --git a/public/Eine Ontologie fuer die Unterstuetzung der Lehre und des Informationsmanagements im Gesundheitswesen.pdf b/public/Eine Ontologie fuer die Unterstuetzung der Lehre und des Informationsmanagements im Gesundheitswesen.pdf
new file mode 100644
index 00000000000..8911604ad97
Binary files /dev/null and b/public/Eine Ontologie fuer die Unterstuetzung der Lehre und des Informationsmanagements im Gesundheitswesen.pdf differ
diff --git a/public/Entwicklung und Einsatz einer Domaenenontologie des Informationsmanagements im Krankenhaus.pdf b/public/Entwicklung und Einsatz einer Domaenenontologie des Informationsmanagements im Krankenhaus.pdf
new file mode 100644
index 00000000000..5eded097c6a
Binary files /dev/null and b/public/Entwicklung und Einsatz einer Domaenenontologie des Informationsmanagements im Krankenhaus.pdf differ
diff --git a/public/Faulhaber_Ausarbeitung74103.pdf b/public/Faulhaber_Ausarbeitung74103.pdf
new file mode 100644
index 00000000000..eff68d3b803
Binary files /dev/null and b/public/Faulhaber_Ausarbeitung74103.pdf differ
diff --git a/public/Graph.png b/public/Graph.png
new file mode 100644
index 00000000000..3243b645378
Binary files /dev/null and b/public/Graph.png differ
diff --git a/public/LodView.png b/public/LodView.png
new file mode 100644
index 00000000000..7cf481872d2
Binary files /dev/null and b/public/LodView.png differ
diff --git a/public/Open and Linkable Knowledge About Management of Health Information Systems.pdf b/public/Open and Linkable Knowledge About Management of Health Information Systems.pdf
new file mode 100644
index 00000000000..5550884957b
Binary files /dev/null and b/public/Open and Linkable Knowledge About Management of Health Information Systems.pdf differ
diff --git a/public/SNIK_Metamodell_V10.svg b/public/SNIK_Metamodell_V10.svg
new file mode 100644
index 00000000000..82a3f240d99
--- /dev/null
+++ b/public/SNIK_Metamodell_V10.svg
@@ -0,0 +1,305 @@
+
diff --git a/public/System Analysis of Information Management.pdf b/public/System Analysis of Information Management.pdf
new file mode 100644
index 00000000000..9db4996bc5f
Binary files /dev/null and b/public/System Analysis of Information Management.pdf differ
diff --git a/public/Technical Environment for Developing the SNIK Ontology of Information Management in Hospitals.pdf b/public/Technical Environment for Developing the SNIK Ontology of Information Management in Hospitals.pdf
new file mode 100644
index 00000000000..b08ea05c7d4
Binary files /dev/null and b/public/Technical Environment for Developing the SNIK Ontology of Information Management in Hospitals.pdf differ
diff --git a/public/The SNIK Graph Visualization of a Medical Informatics Ontology.pdf b/public/The SNIK Graph Visualization of a Medical Informatics Ontology.pdf
new file mode 100644
index 00000000000..4b15fa9ded3
Binary files /dev/null and b/public/The SNIK Graph Visualization of a Medical Informatics Ontology.pdf differ
diff --git a/public/The Status Quo of Information Management in Hospitals.pdf b/public/The Status Quo of Information Management in Hospitals.pdf
new file mode 100644
index 00000000000..203131bc527
Binary files /dev/null and b/public/The Status Quo of Information Management in Hospitals.pdf differ
diff --git a/public/Ueberblick.png b/public/Ueberblick.png
new file mode 100644
index 00000000000..d610be4189b
Binary files /dev/null and b/public/Ueberblick.png differ
diff --git a/public/Use of Domain Ontologies to Improve Requirements Quality.pdf b/public/Use of Domain Ontologies to Improve Requirements Quality.pdf
new file mode 100644
index 00000000000..a7f5814b867
Binary files /dev/null and b/public/Use of Domain Ontologies to Improve Requirements Quality.pdf differ
diff --git a/public/Visualization of Large Ontologies in University Education from a Tool Point of View.pdf b/public/Visualization of Large Ontologies in University Education from a Tool Point of View.pdf
new file mode 100644
index 00000000000..648ecf92c3a
Binary files /dev/null and b/public/Visualization of Large Ontologies in University Education from a Tool Point of View.pdf differ
diff --git a/public/Zwischen Schattendasein Governance und Entrepreneurship.pdf b/public/Zwischen Schattendasein Governance und Entrepreneurship.pdf
new file mode 100644
index 00000000000..1bebeb2f3ff
Binary files /dev/null and b/public/Zwischen Schattendasein Governance und Entrepreneurship.pdf differ
diff --git a/public/bachelor-ar.pdf b/public/bachelor-ar.pdf
new file mode 100644
index 00000000000..07fe1a300a2
Binary files /dev/null and b/public/bachelor-ar.pdf differ
diff --git a/public/bachelor-bt.pdf b/public/bachelor-bt.pdf
new file mode 100644
index 00000000000..2b685b70f51
Binary files /dev/null and b/public/bachelor-bt.pdf differ
diff --git a/public/bachelor-tp.pdf b/public/bachelor-tp.pdf
new file mode 100644
index 00000000000..82ad0ee75d3
Binary files /dev/null and b/public/bachelor-tp.pdf differ
diff --git a/public/bell-hrb.pdf b/public/bell-hrb.pdf
new file mode 100644
index 00000000000..af86ca52edd
Binary files /dev/null and b/public/bell-hrb.pdf differ
diff --git a/public/bell-mw.pdf b/public/bell-mw.pdf
new file mode 100644
index 00000000000..335da16a302
Binary files /dev/null and b/public/bell-mw.pdf differ
diff --git a/public/browse.png b/public/browse.png
new file mode 100644
index 00000000000..69e91b6ac15
Binary files /dev/null and b/public/browse.png differ
diff --git a/public/catalogue.jpg b/public/catalogue.jpg
new file mode 100644
index 00000000000..65f05c0c73f
Binary files /dev/null and b/public/catalogue.jpg differ
diff --git a/public/css/collapse.css b/public/css/collapse.css
new file mode 100644
index 00000000000..c31209aa004
--- /dev/null
+++ b/public/css/collapse.css
@@ -0,0 +1,72 @@
+.wrap-collapsible {
+ margin-bottom: 1.2rem;
+}
+
+input[type='checkbox'] {
+ display: none;
+}
+
+.lbl-toggle {
+ display: block;
+
+ font-weight: bold;
+ font-family: monospace;
+ font-size: 1.2rem;
+ text-transform: uppercase;
+ text-align: center;
+
+ padding: 1rem;
+
+ color: #ffffff;
+ background: #ac4142;
+
+ cursor: pointer;
+
+ border-radius: 7px;
+ transition: all 0.25s ease-out;
+}
+
+.lbl-toggle:hover {
+ color: #ffffff;
+}
+
+.lbl-toggle::before {
+ content: ' ';
+ display: inline-block;
+
+ border-top: 5px solid transparent;
+ border-bottom: 5px solid transparent;
+ border-left: 5px solid currentColor;
+ vertical-align: middle;
+ margin-right: .7rem;
+ transform: translateY(-2px);
+
+ transition: transform .2s ease-out;
+}
+
+.toggle:checked + .lbl-toggle::before {
+ transform: rotate(90deg) translateX(-3px);
+}
+
+.collapsible-content {
+ max-height: 0px;
+ overflow: hidden;
+ transition: max-height .25s ease-in-out;
+}
+
+.toggle:checked + .lbl-toggle + .collapsible-content {
+ max-height: 100vh;
+}
+
+.toggle:checked + .lbl-toggle {
+ border-bottom-right-radius: 0;
+ border-bottom-left-radius: 0;
+}
+
+.collapsible-content .content-inner {
+ background: rgba(250, 224, 66, .2);
+ border-bottom: 1px solid rgba(250, 224, 66, .45);
+ border-bottom-left-radius: 7px;
+ border-bottom-right-radius: 7px;
+ padding: .5rem 1rem;
+}
diff --git a/public/css/custom.css b/public/css/custom.css
new file mode 100644
index 00000000000..0fb22083917
--- /dev/null
+++ b/public/css/custom.css
@@ -0,0 +1,37 @@
+.teamGrid > img {
+ height:4.5em;
+ height:5em;
+ justify-self: center;
+ alignment="center";
+}
+
+.teamGrid {
+ display:grid;
+ align-items:center;
+ grid-template-columns: 20em 20em;
+ grid-gap:1em;
+}
+
+.flex-item {
+ width: 15rem;
+ height: 15rem;
+ background-color: rgba(255, 255, 255, 0.8);
+ border: 1px solid rgba(255, 255, 255, 0.8);
+ padding: 10px;
+ font-size: 30px;
+ text-align: center;
+}
+
+.flex-item img {
+ display:inline;
+ max-width:100%;
+ max-height:80%;
+ margin:auto;
+}
+
+.flexy {
+ display: flex;
+ flex-wrap: wrap;
+ align-items: center;
+ justify-content: center;
+}
diff --git a/public/css/hyde.css b/public/css/hyde.css
new file mode 100644
index 00000000000..91567bde8e7
--- /dev/null
+++ b/public/css/hyde.css
@@ -0,0 +1,250 @@
+/*
+ * __ __
+ * /\ \ /\ \
+ * \ \ \___ __ __ \_\ \ __
+ * \ \ _ `\/\ \/\ \ /'_` \ /'__`\
+ * \ \ \ \ \ \ \_\ \/\ \_\ \/\ __/
+ * \ \_\ \_\/`____ \ \___,_\ \____\
+ * \/_/\/_/`/___/> \/__,_ /\/____/
+ * /\___/
+ * \/__/
+ *
+ * Designed, built, and released under MIT license by @mdo. Learn more at
+ * https://github.com/poole/hyde.
+ */
+
+
+/*
+ * Contents
+ *
+ * Global resets
+ * Sidebar
+ * Container
+ * Reverse layout
+ * Themes
+ */
+
+
+/*
+ * Global resets
+ *
+ * Update the foundational and global aspects of the page.
+ */
+
+html {
+ font-family: "PT Sans", Helvetica, Arial, sans-serif;
+}
+@media (min-width: 48em) {
+ html {
+ font-size: 16px;
+ }
+}
+@media (min-width: 58em) {
+ html {
+ font-size: 20px;
+ }
+}
+
+
+/*
+ * Sidebar
+ *
+ * Flexible banner for housing site name, intro, and "footer" content. Starts
+ * out above content in mobile and later moves to the side with wider viewports.
+ */
+
+.sidebar {
+ text-align: center;
+ padding: 2rem 1rem;
+ color: rgba(255,255,255,.5);
+ background-color: #202020;
+}
+@media (min-width: 48em) {
+ .sidebar {
+ position: fixed;
+ top: 0;
+ left: 0;
+ bottom: 0;
+ width: 18rem;
+ text-align: left;
+ }
+}
+
+/* Sidebar links */
+.sidebar a {
+ color: #fff;
+}
+
+/* About section */
+.sidebar-about h1 {
+ color: #fff;
+ margin-top: 0;
+ font-family: "Abril Fatface", serif;
+ font-size: 3.25rem;
+}
+
+/* Sidebar nav */
+.sidebar-nav {
+ margin-bottom: 1rem;
+}
+.sidebar-nav-item {
+ display: block;
+ line-height: 1.75;
+}
+a.sidebar-nav-item:hover,
+a.sidebar-nav-item:focus {
+ text-decoration: underline;
+}
+.sidebar-nav-item.active {
+ font-weight: bold;
+}
+
+/* Sticky sidebar
+ *
+ * Add the `sidebar-sticky` class to the sidebar's container to affix it the
+ * contents to the bottom of the sidebar in tablets and up.
+ */
+
+@media (min-width: 48em) {
+ .sidebar-sticky {
+ position: absolute;
+ right: 1rem;
+ bottom: 1rem;
+ left: 1rem;
+ }
+}
+
+
+/* Container
+ *
+ * Align the contents of the site above the proper threshold with some margin-fu
+ * with a 25%-wide `.sidebar`.
+ */
+
+.content {
+ padding-top: 4rem;
+ padding-bottom: 4rem;
+}
+
+@media (min-width: 48em) {
+ .content {
+ max-width: 63rem;
+ margin-left: 20rem;
+ margin-right: 2rem;
+ }
+}
+
+@media (min-width: 64em) {
+ .content {
+ margin-left: 22rem;
+ margin-right: 4rem;
+ }
+}
+
+
+/*
+ * Reverse layout
+ *
+ * Flip the orientation of the page by placing the `.sidebar` on the right.
+ */
+
+@media (min-width: 48em) {
+ .layout-reverse .sidebar {
+ left: auto;
+ right: 0;
+ }
+ .layout-reverse .content {
+ margin-left: 2rem;
+ margin-right: 20rem;
+ }
+}
+
+@media (min-width: 64em) {
+ .layout-reverse .content {
+ margin-left: 4rem;
+ margin-right: 22rem;
+ }
+}
+
+
+
+/*
+ * Themes
+ *
+ * As of v1.1, Hyde includes optional themes to color the sidebar and links
+ * within blog posts. To use, add the class of your choosing to the `body`.
+ */
+
+/* Base16 (http://chriskempson.github.io/base16/#default) */
+
+/* Red */
+.theme-base-08 .sidebar {
+ background-color: #ac4142;
+}
+.theme-base-08 .content a,
+.theme-base-08 .related-posts li a:hover {
+ color: #ac4142;
+}
+
+/* Orange */
+.theme-base-09 .sidebar {
+ background-color: #d28445;
+}
+.theme-base-09 .content a,
+.theme-base-09 .related-posts li a:hover {
+ color: #d28445;
+}
+
+/* Yellow */
+.theme-base-0a .sidebar {
+ background-color: #f4bf75;
+}
+.theme-base-0a .content a,
+.theme-base-0a .related-posts li a:hover {
+ color: #f4bf75;
+}
+
+/* Green */
+.theme-base-0b .sidebar {
+ background-color: #90a959;
+}
+.theme-base-0b .content a,
+.theme-base-0b .related-posts li a:hover {
+ color: #90a959;
+}
+
+/* Cyan */
+.theme-base-0c .sidebar {
+ background-color: #75b5aa;
+}
+.theme-base-0c .content a,
+.theme-base-0c .related-posts li a:hover {
+ color: #75b5aa;
+}
+
+/* Blue */
+.theme-base-0d .sidebar {
+ background-color: #6a9fb5;
+}
+.theme-base-0d .content a,
+.theme-base-0d .related-posts li a:hover {
+ color: #6a9fb5;
+}
+
+/* Magenta */
+.theme-base-0e .sidebar {
+ background-color: #aa759f;
+}
+.theme-base-0e .content a,
+.theme-base-0e .related-posts li a:hover {
+ color: #aa759f;
+}
+
+/* Brown */
+.theme-base-0f .sidebar {
+ background-color: #8f5536;
+}
+.theme-base-0f .content a,
+.theme-base-0f .related-posts li a:hover {
+ color: #8f5536;
+}
diff --git a/public/css/poole.css b/public/css/poole.css
new file mode 100644
index 00000000000..38e1bdf3451
--- /dev/null
+++ b/public/css/poole.css
@@ -0,0 +1,430 @@
+/*
+ * ___
+ * /\_ \
+ * _____ ___ ___\//\ \ __
+ * /\ '__`\ / __`\ / __`\\ \ \ /'__`\
+ * \ \ \_\ \/\ \_\ \/\ \_\ \\_\ \_/\ __/
+ * \ \ ,__/\ \____/\ \____//\____\ \____\
+ * \ \ \/ \/___/ \/___/ \/____/\/____/
+ * \ \_\
+ * \/_/
+ *
+ * Designed, built, and released under MIT license by @mdo. Learn more at
+ * https://github.com/poole/poole.
+ */
+
+
+/*
+ * Contents
+ *
+ * Body resets
+ * Custom type
+ * Messages
+ * Container
+ * Masthead
+ * Posts and pages
+ * Pagination
+ * Reverse layout
+ * Themes
+ */
+
+
+/*
+ * Body resets
+ *
+ * Update the foundational and global aspects of the page.
+ */
+
+* {
+ -webkit-box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ box-sizing: border-box;
+}
+
+html,
+body {
+ margin: 0;
+ padding: 0;
+}
+
+html {
+ font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
+ font-size: 16px;
+ line-height: 1.5;
+}
+@media (min-width: 38em) {
+ html {
+ font-size: 20px;
+ }
+}
+
+body {
+ color: #515151;
+ background-color: #fff;
+ -webkit-text-size-adjust: 100%;
+ -ms-text-size-adjust: 100%;
+}
+
+/* No `:visited` state is required by default (browsers will use `a`) */
+a {
+ color: #268bd2;
+ text-decoration: none;
+}
+a strong {
+ color: inherit;
+}
+/* `:focus` is linked to `:hover` for basic accessibility */
+a:hover,
+a:focus {
+ text-decoration: underline;
+}
+
+/* Headings */
+h1, h2, h3, h4, h5, h6 {
+ margin-bottom: .5rem;
+ font-weight: bold;
+ line-height: 1.25;
+ color: #313131;
+ text-rendering: optimizeLegibility;
+}
+h1 {
+ font-size: 2rem;
+}
+h2 {
+ margin-top: 1rem;
+ font-size: 1.5rem;
+}
+h3 {
+ margin-top: 1.5rem;
+ font-size: 1.25rem;
+}
+h4, h5, h6 {
+ margin-top: 1rem;
+ font-size: 1rem;
+}
+
+/* Body text */
+p {
+ margin-top: 0;
+ margin-bottom: 1rem;
+}
+
+strong {
+ color: #303030;
+}
+
+
+/* Lists */
+ul, ol, dl {
+ margin-top: 0;
+ margin-bottom: 1rem;
+}
+
+dt {
+ font-weight: bold;
+}
+dd {
+ margin-bottom: .5rem;
+}
+
+/* Misc */
+hr {
+ position: relative;
+ margin: 1.5rem 0;
+ border: 0;
+ border-top: 1px solid #eee;
+ border-bottom: 1px solid #fff;
+}
+
+abbr {
+ font-size: 85%;
+ font-weight: bold;
+ color: #555;
+ text-transform: uppercase;
+}
+abbr[title] {
+ cursor: help;
+ border-bottom: 1px dotted #e5e5e5;
+}
+
+/* Code */
+code,
+pre {
+ font-family: Menlo, Monaco, "Courier New", monospace;
+}
+code {
+ padding: .25em .5em;
+ font-size: 85%;
+ color: #bf616a;
+ background-color: #f9f9f9;
+ border-radius: 3px;
+}
+pre {
+ display: block;
+ margin-top: 0;
+ margin-bottom: 1rem;
+ padding: 1rem;
+ font-size: .8rem;
+ line-height: 1.4;
+ white-space: pre;
+ white-space: pre-wrap;
+ word-break: break-all;
+ word-wrap: break-word;
+ background-color: #f9f9f9;
+}
+pre code {
+ padding: 0;
+ font-size: 100%;
+ color: inherit;
+ background-color: transparent;
+}
+
+/* Pygments via Jekyll */
+.highlight {
+ margin-bottom: 1rem;
+ border-radius: 4px;
+}
+.highlight pre {
+ margin-bottom: 0;
+}
+
+/* Gist via GitHub Pages */
+.gist .gist-file {
+ font-family: Menlo, Monaco, "Courier New", monospace !important;
+}
+.gist .markdown-body {
+ padding: 15px;
+}
+.gist pre {
+ padding: 0;
+ background-color: transparent;
+}
+.gist .gist-file .gist-data {
+ font-size: .8rem !important;
+ line-height: 1.4;
+}
+.gist code {
+ padding: 0;
+ color: inherit;
+ background-color: transparent;
+ border-radius: 0;
+}
+
+/* Quotes */
+blockquote {
+ padding: .5rem 1rem;
+ margin: .8rem 0;
+ color: #7a7a7a;
+ border-left: .25rem solid #e5e5e5;
+}
+blockquote p:last-child {
+ margin-bottom: 0;
+}
+@media (min-width: 30em) {
+ blockquote {
+ padding-right: 5rem;
+ padding-left: 1.25rem;
+ }
+}
+
+img {
+ display: block;
+ max-width: 100%;
+ margin: 0 0 0;
+ border-radius: 0px;
+}
+
+/* Tables */
+table {
+ margin-bottom: 1rem;
+ width: 100%;
+ border: 1px solid #e5e5e5;
+ border-collapse: collapse;
+}
+td,
+th {
+ padding: .25rem .5rem;
+ border: 1px solid #e5e5e5;
+}
+tbody tr:nth-child(odd) td,
+tbody tr:nth-child(odd) th {
+ background-color: #f9f9f9;
+}
+
+
+/*
+ * Custom type
+ *
+ * Extend paragraphs with `.lead` for larger introductory text.
+ */
+
+.lead {
+ font-size: 1.25rem;
+ font-weight: 300;
+}
+
+
+/*
+ * Messages
+ *
+ * Show alert messages to users. You may add it to single elements like a `
`,
+ * or to a parent if there are multiple elements to show.
+ */
+
+.message {
+ margin-bottom: 1rem;
+ padding: 1rem;
+ color: #717171;
+ background-color: #f9f9f9;
+}
+
+
+/*
+ * Container
+ *
+ * Center the page content.
+ */
+
+.container {
+ max-width: 38rem;
+ padding-left: 1rem;
+ padding-right: 1rem;
+ margin-left: auto;
+ margin-right: auto;
+}
+
+
+/*
+ * Masthead
+ *
+ * Super small header above the content for site name and short description.
+ */
+
+.masthead {
+ padding-top: 1rem;
+ padding-bottom: 1rem;
+ margin-bottom: 3rem;
+}
+.masthead-title {
+ margin-top: 0;
+ margin-bottom: 0;
+ color: #505050;
+}
+.masthead-title a {
+ color: #505050;
+}
+.masthead-title small {
+ font-size: 75%;
+ font-weight: 400;
+ color: #c0c0c0;
+ letter-spacing: 0;
+}
+
+
+/*
+ * Posts and pages
+ *
+ * Each post is wrapped in `.post` and is used on default and post layouts. Each
+ * page is wrapped in `.page` and is only used on the page layout.
+ */
+
+.page,
+.post {
+ margin-bottom: 4em;
+}
+
+/* Blog post or page title */
+.page-title,
+.post-title,
+.post-title a {
+ color: #303030;
+}
+.page-title,
+.post-title {
+ margin-top: 0;
+}
+
+/* Meta data line below post title */
+.post-date {
+ display: block;
+ margin-top: -.5rem;
+ margin-bottom: 1rem;
+ color: #9a9a9a;
+}
+
+/* Related posts */
+.related {
+ padding-top: 2rem;
+ padding-bottom: 2rem;
+ border-top: 1px solid #eee;
+}
+.related-posts {
+ padding-left: 0;
+ list-style: none;
+}
+.related-posts h3 {
+ margin-top: 0;
+}
+.related-posts li small {
+ font-size: 75%;
+ color: #999;
+}
+.related-posts li a:hover {
+ color: #268bd2;
+ text-decoration: none;
+}
+.related-posts li a:hover small {
+ color: inherit;
+}
+
+
+/*
+ * Pagination
+ *
+ * Super lightweight (HTML-wise) blog pagination. `span`s are provide for when
+ * there are no more previous or next posts to show.
+ */
+
+.pagination {
+ overflow: hidden; /* clearfix */
+ margin-left: -1rem;
+ margin-right: -1rem;
+ font-family: "PT Sans", Helvetica, Arial, sans-serif;
+ color: #ccc;
+ text-align: center;
+}
+
+/* Pagination items can be `span`s or `a`s */
+.pagination-item {
+ display: block;
+ padding: 1rem;
+ border: 1px solid #eee;
+}
+.pagination-item:first-child {
+ margin-bottom: -1px;
+}
+
+/* Only provide a hover state for linked pagination items */
+a.pagination-item:hover {
+ background-color: #f5f5f5;
+}
+
+@media (min-width: 30em) {
+ .pagination {
+ margin: 3rem 0;
+ }
+ .pagination-item {
+ float: left;
+ width: 50%;
+ }
+ .pagination-item:first-child {
+ margin-bottom: 0;
+ border-top-left-radius: 4px;
+ border-bottom-left-radius: 4px;
+ }
+ .pagination-item:last-child {
+ margin-left: -1px;
+ border-top-right-radius: 4px;
+ border-bottom-right-radius: 4px;
+ }
+}
diff --git a/public/css/syntax.css b/public/css/syntax.css
new file mode 100644
index 00000000000..15ad797710b
--- /dev/null
+++ b/public/css/syntax.css
@@ -0,0 +1,65 @@
+.highlight .hll { background-color: #ffc; }
+.highlight .c { color: #999; } /* Comment */
+.highlight .err { color: #a00; background-color: #faa } /* Error */
+.highlight .k { color: #069; } /* Keyword */
+.highlight .o { color: #555 } /* Operator */
+.highlight .cm { color: #09f; font-style: italic } /* Comment.Multiline */
+.highlight .cp { color: #099 } /* Comment.Preproc */
+.highlight .c1 { color: #999; } /* Comment.Single */
+.highlight .cs { color: #999; } /* Comment.Special */
+.highlight .gd { background-color: #fcc; border: 1px solid #c00 } /* Generic.Deleted */
+.highlight .ge { font-style: italic } /* Generic.Emph */
+.highlight .gr { color: #f00 } /* Generic.Error */
+.highlight .gh { color: #030; } /* Generic.Heading */
+.highlight .gi { background-color: #cfc; border: 1px solid #0c0 } /* Generic.Inserted */
+.highlight .go { color: #aaa } /* Generic.Output */
+.highlight .gp { color: #009; } /* Generic.Prompt */
+.highlight .gs { } /* Generic.Strong */
+.highlight .gu { color: #030; } /* Generic.Subheading */
+.highlight .gt { color: #9c6 } /* Generic.Traceback */
+.highlight .kc { color: #069; } /* Keyword.Constant */
+.highlight .kd { color: #069; } /* Keyword.Declaration */
+.highlight .kn { color: #069; } /* Keyword.Namespace */
+.highlight .kp { color: #069 } /* Keyword.Pseudo */
+.highlight .kr { color: #069; } /* Keyword.Reserved */
+.highlight .kt { color: #078; } /* Keyword.Type */
+.highlight .m { color: #f60 } /* Literal.Number */
+.highlight .s { color: #d44950 } /* Literal.String */
+.highlight .na { color: #4f9fcf } /* Name.Attribute */
+.highlight .nb { color: #366 } /* Name.Builtin */
+.highlight .nc { color: #0a8; } /* Name.Class */
+.highlight .no { color: #360 } /* Name.Constant */
+.highlight .nd { color: #99f } /* Name.Decorator */
+.highlight .ni { color: #999; } /* Name.Entity */
+.highlight .ne { color: #c00; } /* Name.Exception */
+.highlight .nf { color: #c0f } /* Name.Function */
+.highlight .nl { color: #99f } /* Name.Label */
+.highlight .nn { color: #0cf; } /* Name.Namespace */
+.highlight .nt { color: #2f6f9f; } /* Name.Tag */
+.highlight .nv { color: #033 } /* Name.Variable */
+.highlight .ow { color: #000; } /* Operator.Word */
+.highlight .w { color: #bbb } /* Text.Whitespace */
+.highlight .mf { color: #f60 } /* Literal.Number.Float */
+.highlight .mh { color: #f60 } /* Literal.Number.Hex */
+.highlight .mi { color: #f60 } /* Literal.Number.Integer */
+.highlight .mo { color: #f60 } /* Literal.Number.Oct */
+.highlight .sb { color: #c30 } /* Literal.String.Backtick */
+.highlight .sc { color: #c30 } /* Literal.String.Char */
+.highlight .sd { color: #c30; font-style: italic } /* Literal.String.Doc */
+.highlight .s2 { color: #c30 } /* Literal.String.Double */
+.highlight .se { color: #c30; } /* Literal.String.Escape */
+.highlight .sh { color: #c30 } /* Literal.String.Heredoc */
+.highlight .si { color: #a00 } /* Literal.String.Interpol */
+.highlight .sx { color: #c30 } /* Literal.String.Other */
+.highlight .sr { color: #3aa } /* Literal.String.Regex */
+.highlight .s1 { color: #c30 } /* Literal.String.Single */
+.highlight .ss { color: #fc3 } /* Literal.String.Symbol */
+.highlight .bp { color: #366 } /* Name.Builtin.Pseudo */
+.highlight .vc { color: #033 } /* Name.Variable.Class */
+.highlight .vg { color: #033 } /* Name.Variable.Global */
+.highlight .vi { color: #033 } /* Name.Variable.Instance */
+.highlight .il { color: #f60 } /* Literal.Number.Integer.Long */
+
+.css .o,
+.css .o + .nt,
+.css .nt + .nt { color: #999; }
diff --git a/public/download.png b/public/download.png
new file mode 100644
index 00000000000..1f0a9e36b1c
Binary files /dev/null and b/public/download.png differ
diff --git a/public/ghalandari.jpg b/public/ghalandari.jpg
new file mode 100644
index 00000000000..4083f15de95
Binary files /dev/null and b/public/ghalandari.jpg differ
diff --git a/public/imise-logo.svg b/public/imise-logo.svg
new file mode 100644
index 00000000000..e4ae00c9945
--- /dev/null
+++ b/public/imise-logo.svg
@@ -0,0 +1,74 @@
+
+
\ No newline at end of file
diff --git a/public/jahn.jpg b/public/jahn.jpg
new file mode 100644
index 00000000000..25ed3842bed
Binary files /dev/null and b/public/jahn.jpg differ
diff --git a/public/logo-snik-alpha.png b/public/logo-snik-alpha.png
new file mode 100644
index 00000000000..9e5b259e005
Binary files /dev/null and b/public/logo-snik-alpha.png differ
diff --git a/public/master-az.pdf b/public/master-az.pdf
new file mode 100644
index 00000000000..026860829d4
Binary files /dev/null and b/public/master-az.pdf differ
diff --git a/public/master-tb.pdf b/public/master-tb.pdf
new file mode 100644
index 00000000000..8df8ccd3100
Binary files /dev/null and b/public/master-tb.pdf differ
diff --git a/public/poster/snik-complete-graph-poster-400.png b/public/poster/snik-complete-graph-poster-400.png
new file mode 100644
index 00000000000..165b7b06795
Binary files /dev/null and b/public/poster/snik-complete-graph-poster-400.png differ
diff --git a/public/poster/snik-complete-graph-poster.pdf b/public/poster/snik-complete-graph-poster.pdf
new file mode 100644
index 00000000000..b7731a7f93b
Binary files /dev/null and b/public/poster/snik-complete-graph-poster.pdf differ
diff --git a/public/poster/snik-complete-graph-poster.svg b/public/poster/snik-complete-graph-poster.svg
new file mode 100644
index 00000000000..9f51098050f
--- /dev/null
+++ b/public/poster/snik-complete-graph-poster.svg
@@ -0,0 +1,2 @@
+
+
diff --git a/public/poster/snik-graph-poster-medinfo2019-400.png b/public/poster/snik-graph-poster-medinfo2019-400.png
new file mode 100644
index 00000000000..5015cdd2d85
Binary files /dev/null and b/public/poster/snik-graph-poster-medinfo2019-400.png differ
diff --git a/public/poster/snik-graph-poster-medinfo2019.pdf b/public/poster/snik-graph-poster-medinfo2019.pdf
new file mode 100644
index 00000000000..b1e7a5435bb
Binary files /dev/null and b/public/poster/snik-graph-poster-medinfo2019.pdf differ
diff --git a/public/poster/snik-poster-medinfo2019-400.jpg b/public/poster/snik-poster-medinfo2019-400.jpg
new file mode 100644
index 00000000000..b969c5abfc1
Binary files /dev/null and b/public/poster/snik-poster-medinfo2019-400.jpg differ
diff --git a/public/poster/snik-poster-medinfo2019.pdf b/public/poster/snik-poster-medinfo2019.pdf
new file mode 100644
index 00000000000..a454f64dad7
Binary files /dev/null and b/public/poster/snik-poster-medinfo2019.pdf differ
diff --git a/public/poster/snik-poster-medinfo2019.svg b/public/poster/snik-poster-medinfo2019.svg
new file mode 100644
index 00000000000..5bb2596abf7
--- /dev/null
+++ b/public/poster/snik-poster-medinfo2019.svg
@@ -0,0 +1,7662 @@
+
+
diff --git a/public/pwl_bereichsbudget.png b/public/pwl_bereichsbudget.png
new file mode 100644
index 00000000000..1fca72bc205
Binary files /dev/null and b/public/pwl_bereichsbudget.png differ
diff --git a/public/search.jpg b/public/search.jpg
new file mode 100644
index 00000000000..3b8fbeb4869
Binary files /dev/null and b/public/search.jpg differ
diff --git a/public/snik-quiz-mie2022.pdf b/public/snik-quiz-mie2022.pdf
new file mode 100644
index 00000000000..6f4a4d0582e
Binary files /dev/null and b/public/snik-quiz-mie2022.pdf differ
diff --git a/public/snik.bib b/public/snik.bib
new file mode 100644
index 00000000000..4c5e01a45ac
--- /dev/null
+++ b/public/snik.bib
@@ -0,0 +1,293 @@
+% Bibliography of the SNIK project
+% See https://www.snik.eu
+
+@book{bb,
+ title={Health Information Systems: {A}rchitectures and Strategies},
+ author={Winter, Alfred and Haux, Reinhold and Ammenwerth, Elske and Brigel, Birgit and Hellrung, Nils and Jahn, Franziska},
+ isbn={9781849964418},
+ lccn={2010933608},
+ series={Health Informatics},
+ url={https://books.google.de/books?id=RzvmrgwCWncC},
+ year={2011},
+ publisher={Springer London}
+}
+
+@book{bb2,
+ title={Health Information Systems: Technological and Management Perspectives},
+ author={Winter, Alfred and Ammenwerth, Elske and Haux, Reinhold and Marschollek, Michael and Steiner, Bianca and Jahn, Franziska},
+ year={2023},
+ doi={10.1007/978-3-031-12310-8},
+ publisher={Springer Cham}
+}
+
+@book{ob,
+ author={Ammenwerth, Elske and Haux, Reinhold and Knaup-Gregori, Petra and Winter, Alfred},
+ title={{IT}-{P}rojektmanagement im {G}esundheitswesen},
+ edition={2},
+ publisher={Schattauer},
+ address={Stuttgart, Germany},
+ year={2014},
+ isbn={9783794530717}
+}
+
+@article{domaene,
+ title={Entwicklung und {E}insatz einer {D}om{\"a}nenontologie des {I}nformationsmanagements im {K}rankenhaus},
+ author={Schaaf, Michael and Jahn, Franziska and Tahar, Kais and Kucherer, Christian and Winter, Alfred and Paech, Barbara},
+ journal={Informatik 2015},
+ editor={Douglas W. Cunningham and Petra Hofstedt and Klaus Meer and Ingo Schmitt},
+ series={Lecture Notes in Informatics},
+ volume={246},
+ year={2015},
+ publisher={Gesellschaft f{\"u}r Informatik eV}
+}
+
+@book{he,
+ title={Informationsmanagement: Grundlagen, Aufgaben, Methoden},
+ author={Heinrich, Lutz J and Riedl, Ren{\'e} and Stelzer, Dirk},
+ year={2014},
+ publisher={De Gruyter}
+}
+
+@article{ciosurvey,
+ title={The status quo of information management in hospitals-results of an online survey},
+ author={K{\"u}cherer, Christian and Liebe, Jan David and Schaaf, Michael and Thye, Johannes and Paech, Barbara and Winter, Alfred and Jahn, Franziska},
+ journal={Informatik 2016},
+ series={Lecture Notes in Informatics},
+ year={2016},
+ publisher={Gesellschaft f{\"u}r Informatik eV}
+}
+
+@inproceedings{domainontologies,
+ title={Use of Domain Ontologies to Improve Requirements Quality},
+ author={K{\"u}cherer, Christian},
+ booktitle={Joint Proceedings of REFSQ-2017 Workshops, Doctoral Symposium, Research Method Track, and Poster Track co-located with the 23rd International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2017)},
+ volume={1796},
+ year={2017}
+}
+
+@Article{sniktec,
+ Author="H{\"o}ffner, Konrad and Jahn, Franziska and K{\"u}cherer, Christian and Paech, Barbara and Schneider, Birgit and Sch{\"o}bel, Martin and St{\"a}ubert, Sebastian and Winter, Alfred",
+ Title="{{T}echnical {E}nvironment for {D}eveloping the {S}{N}{I}{K} {O}ntology of {I}nformation {M}anagement in {H}ospitals}",
+ Journal="Studies in Health Technology and Informatics",
+ Year="2017",
+ Volume="243",
+ Pages="122--126"
+}
+
+@inproceedings{semantischesnetz,
+ title={Ein {S}emantisches {N}etz des {I}nformationsmanagements im {K}rankenhaus},
+ author = {Jahn, Franziska and Schaaf, Michael and Paech, Barbara and Winter, Alfred},
+ booktitle = {Informatik 2014},
+ series={Lecture Notes in Informatics},
+ year = {2014},
+ editor = {Pl{\"o}dereder, E. and Grunske, L. and Schneider, E. and Ull, D.} ,
+ pages = {1491-1498},
+ publisher = {Gesellschaft für Informatik e.V.},
+ address = {Bonn}
+}
+
+@Article{approachtosupport,
+ title={An Approach to Support Collaborative Ontology Construction},
+ author={Tahar, Kais and Schaaf, Michael and Jahn, Franziska and K{\"u}cherer, Christian and Paech, Barbara and Herre, Heinrich and Winter, Alfred},
+ journal={Studies in health technology and informatics},
+ volume={228},
+ pages={369--373},
+ year={2016}
+}
+
+@inproceedings{visualizationoflargeontologies,
+ title={Visualization of Large Ontologies in University Education from a Tool Point of View},
+ volume = {228},
+ journal = {Studies in health technology and informatics},
+ doi = {10.3233/978-1-61499-678-1-349},
+ author={Schaaf, Michael and Jahn, Franziska and Tahar, Kais and K{\"u}cherer, Christian and Winter, Alfred and Paech, Barbara},
+ booktitle={MIE},
+ pages={349--353},
+ year={2016}
+}
+
+@inproceedings{taskoriented,
+ title={A Task-oriented Requirements Engineering Method for Personal Decision Support Systems---{A} Case Study},
+ author={K{\"u}cherer, Christian and Paech, Barbara},
+ booktitle={Proceedings of the 19th International Conference on Enterprise Information Systems --- Volume 2: ICEIS},
+ doi = {10.5220/000-6-32530-099-0-110},
+ publisher={SciTePress},
+ organization={INSTICC},
+ isbn={978-989-758-248-6},
+ pages={99--110},
+ volume={2},
+ year={2017}
+}
+
+@inproceedings{schattenseiten,
+ title={Zwischen {S}chattendasein, Governance und Entrepreneurship -- {E}ine empirische {B}estandsaufnahme zum {P}rofessionalisierungsgrad des {IT}-{M}anagements in deutschen {K}rankenh{\"a}usern},
+ author={Liebe, Jan-David and Thomas, Oliver and Jahn, Franziska and K{\"u}cherer, Christian and Esdar, Moritz and Wei{\ss}, Jan-Patrick and H{\"u}sers, Jens and H{\"u}bner, Ursula},
+ booktitle = {Towards Thought Leadership in Digital Transformation: 13. Internationale Tagung Wirtschaftsinformatik, {WI} 2017, St.Gallen, Switzerland},
+ year={2017},
+ editor={Leimeister, Jan Marco and Brenner, Walter},
+ organization={Institut für Wirtschaftsinformatik}
+}
+
+@inproceedings{ontologybased,
+ title={An Ontology-Based Scenario for Teaching the Management of Health Information Systems},
+ author={Jahn, Franziska and Schaaf, Michael and Kahmann, Christian and Tahar, Kais and K{\"u}cherer, Christian and Paech, Barbara and Winter, Alfred},
+ journal={Studies in health technology and informatics},
+ volume={228},
+ pages={359--363},
+ year={2016}
+}
+
+@article{systemanalysis,
+ title={System analysis of information management},
+ author={Kucherer, Christian and Jung, Manuel and Jahn, Franziska and Schaaf, Michael and Tahar, Kais and Paech, Barbara and Winter, Alfred},
+ journal={Informatik 2015},
+ editor={Douglas W. Cunningham and Petra Hofstedt and Klaus Meer and Ingo Schmitt},
+ volume={246},
+ year={2015},
+ series={Lecture Notes in Informatics},
+ publisher={Gesellschaft f{\"u}r Informatik eV}
+}
+
+@phdthesis{toreonto,
+ title={Domain-specific Adaptation of Requirements Engineering Methods},
+ author={K{\"u}cherer, Christian},
+ year={2018}
+}
+
+@article{snikgraph,
+ title = {{SNIK} {G}raph---{V}isualizing Knowledge about Management of Hospital Information Systems},
+ author = {Konrad Höffner and Thomas Pause and Franziska Jahn and Hannes Brunsch and Anna Brakemeier and Alfred Winter},
+ doi = {10.21105/jose.00180},
+ url = {https://doi.org/10.21105/jose.00180},
+ year = {2024},
+ publisher = {The Open Journal},
+ volume = {7},
+ number = {77},
+ pages = {180},
+ journal = {Journal of Open Source Education}
+}
+
+@article{snikgraphposter,
+ title={The {SNIK} {G}raph: {V}isualization of a Medical Informatics Ontology},
+ author={Franziska Jahn and Konrad H{\"o}ffner and Birgit Schneider and Anna L{\"o}rke and Thomas Pause and Elske Ammenwerth and Alfred Winter},
+ journal={MEDINFO 2019: Health and Wellbeing e-Networks for All},
+ series={Studies in Health Technology and Informatics},
+ volume={264},
+ editor={Lucila Ohno-Machado and Brigitte S{\'{e}}roussi},
+ doi={10.3233/SHTI190724},
+ pages={1941--1942},
+ year={2019},
+ publisher={IOS Press}
+}
+
+@article{snikposter,
+ title={Open and Linkable Knowledge About Management of Health Information Systems},
+ author={H{\"o}ffner, Konrad and Jahn, Franziska and L{\"o}rke, Anna and Pause, Thomas and Schneider, Birgit and Ammenwerth, Elske and Winter, Alfred},
+ journal={MEDINFO 2019: Health and Wellbeing e-Networks for All},
+ series={Studies in Health Technology and Informatics},
+ volume={264},
+ editor={Lucila Ohno-Machado and Brigitte S{\'{e}}roussi},
+ doi={10.3233/SHTI190593},
+ pages={1678--1679},
+ year={2019},
+ publisher={IOS Press}
+}
+
+@techreport{characteristika,
+ author= "Franziska Jahn and Christian Kücherer and Jan-David Liebe and Barbara Paech and Alfred Winter",
+ title={{C}harakteristika von {IT}-{A}bteilungen in {K}rankenh{\"a}usern in {D}eutschland. {R}eport zur {U}mfrage unter {IT}-{L}eitern in {K}rankenhäusern ({F}ebruar-{A}pril 2016)},
+ year= "2019"
+}
+
+@article{snikquiz,
+ title={{SNIK Quiz}: {A} Multiple Choice Game About Information Management in Hospitals},
+ author={H{\"o}ffner, Konrad and Roszeitis, Arne and W{\"a}chtler, Max Niclas and Jahn, Franziska and Winter, Alfred},
+ journal={Studies in Health Technology and Informatics},
+ volume={294},
+ pages={790--795},
+ year={2022}
+}
+
+@mastersthesis{arneba,
+ title={Automatische {G}enerierung komplexer {F}ragen zum Informationsmanagement auf der Basis der {SNIK}-Ontologie},
+ author={Arne Roszeitis},
+ type={Bachelor's Thesis},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/bachelor-ar.pdf},
+ year={2022}
+}
+
+@mastersthesis{hannesbell,
+ title={{Q}uestion {A}nswering auf {SNIK}},
+ author={Hannes Raphael Brunsch},
+ type={Besondere {L}ernleistung},
+ school={Wilhelm-Ostwald-Schule},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/bell-hrb.pdf},
+ year={2022}
+}
+
+@mastersthesis{maxbell,
+ title={Automatische {E}rstellung von {Q}uizfragen aus einer {O}ntologie von {K}rankenhausinformationssystemen},
+ author={Max Niclas Wächtler},
+ type={Besondere {L}ernleistung},
+ school={Wilhelm-Ostwald-Schule},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/bell-mnw.pdf},
+ year={2022}
+}
+
+@mastersthesis{thomasba,
+ title={{O}rganisation von {T}eilgraphen semantischer {N}etze zur ontologiegestützten {W}issensvermittlung},
+ author={Thomas Pause},
+ type={Bachelor's Thesis},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/bachelor-tp.pdf},
+ year={2020}
+}
+
+@mastersthesis{benjaminma,
+ title={{I}ntegration von {ITIL}-{B}egriffen in die {SNIK}-{O}ntologie},
+ author={Benjamin R{\"o}sch},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ year={2018}
+}
+
+@mastersthesis{anatolima,
+ title={{O}ntologie-basierte {N}avigation für {CION}},
+ author={Anatoli Zeiser},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/master-az.pdf},
+ year={2016}
+}
+
+@mastersthesis{timma,
+ title={Architekturkonzept für {SNIK}-{CIO}-{N}avigator},
+ author={Tim Bittersohl},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/master-tb.pdf},
+ year={2016}
+}
+
+@mastersthesis{benediktba,
+ title={Einsatz einer {O}ntologie als {D}atenmodell zur {D}atenaggregation},
+ author={Benedikt Tr{\"o}ster},
+ type={Bachelor's Thesis},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ url={https://www.snik.eu/public/bachelor-bt.pdf},
+ year={2016}
+}
+
+@mastersthesis{manuelma,
+ title={{S}ystemanalyse und -bewertung von {I}nformationsmanagement-{I}nformationssystemen ({IMIS})},
+ author={Manuel Jung},
+ school={Institute for Medical Informatics, Statistics {and} Epidemiology (IMISE)},
+ address={Leipzig, Germany},
+ year={2015}
+}
diff --git a/public/snik.pdf b/public/snik.pdf
new file mode 100644
index 00000000000..eba9dda992a
Binary files /dev/null and b/public/snik.pdf differ
diff --git a/public/snik.tex b/public/snik.tex
new file mode 100644
index 00000000000..42662a567de
--- /dev/null
+++ b/public/snik.tex
@@ -0,0 +1,8 @@
+\documentclass{article}
+\begin{document}
+\title{Publications about SNIK}
+\maketitle
+\nocite{*}
+\bibliographystyle{plain}
+\bibliography{snik}
+\end{document}
diff --git a/public/snikBsp.png b/public/snikBsp.png
new file mode 100644
index 00000000000..76cc5db133c
Binary files /dev/null and b/public/snikBsp.png differ
diff --git a/public/sparql.png b/public/sparql.png
new file mode 100644
index 00000000000..f7b3a5a68c0
Binary files /dev/null and b/public/sparql.png differ
diff --git a/public/team.jpg b/public/team.jpg
new file mode 100644
index 00000000000..1ba2683368e
Binary files /dev/null and b/public/team.jpg differ
diff --git a/public/umfragereport.pdf b/public/umfragereport.pdf
new file mode 100644
index 00000000000..52085b8fd5b
Binary files /dev/null and b/public/umfragereport.pdf differ
diff --git a/public/umit-logo.svg b/public/umit-logo.svg
new file mode 100644
index 00000000000..016b3a18090
--- /dev/null
+++ b/public/umit-logo.svg
@@ -0,0 +1,27 @@
+
+
\ No newline at end of file
diff --git a/public/winter.jpg b/public/winter.jpg
new file mode 100644
index 00000000000..82808d254e0
Binary files /dev/null and b/public/winter.jpg differ
diff --git a/publications/index.html b/publications/index.html
new file mode 100644
index 00000000000..922138b2e87
--- /dev/null
+++ b/publications/index.html
@@ -0,0 +1,326 @@
+
+
+
+
Kücherer, C
+Use of Domain Ontologies to Improve Requirements Quality.
+23nd International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ’17), Doctoral Symposium, Essen (Germany), February 27 - March 2, 2017, CEUR Workshop Proceedings 1796, CEUR-WS.org 2017
Kücherer C, Jung M, Jahn F, Schaaf M, Tahar K, Paech B, Winter A.
+System Analysis of Information Management.
+In D. Cunningham, P. Hofstedt, K. Meer, & I. Schmitt (Eds.), GI-Jahrestagung 2015: 783-796.
+
+The SNIK Graph: Visualization of a Medical Informatics Ontology.
+Franziska Jahn, Konrad Höffner, Birgit Schneider, Anna Lörke, Thomas Pause, Elske Ammenwerth, Alfred Winter, Elske Ammenwerth.
+Medinfo 2019, Lyon.
+
+
+
+
+
+
+
+
+
+ @inproceedings{snikgraphposter,
+ author={Franziska Jahn and Konrad Höffner and Birgit Schneider and Anna Lörke and Thomas Pause and Elske Ammenwerth and Alfred Winter},
+ booktitle={MedInfo 2019, The 17th World Congress of Medical and Health Informatics, Lyon},
+ title={The {SNIK} {G}raph: {V}isualization of a Medical Informatics Ontology},
+ year={2019}
+ }
+
+
+Open and Linkable Knowledge about Management of Health Information Systems.
+Konrad Höffner, Franziska Jahn, Anna Lörke, Thomas Pause, Birgit Schneider, Elske Ammenwerth, Alfred Winter.
+MedInfo 2019, Lyon.
+
+
+
+
+
+
+
+
+
+ @inproceedings{snikposter,
+ title={Open and Linkable Knowledge About Management of Health Information Systems},
+ author={H{\"o}ffner, Konrad and Jahn, Franziska and L{\"o}rke, Anna and Pause, Thomas and Schneider, Birgit and Ammenwerth, Elske and Winter, Alfred},
+ booktitle={MedInfo 2019, The 17th World Congress of Medical and Health Informatics, Lyon},
+ year={2019}
+ }
+
+There are three immediate subclasses of meta:Top ("subtops"): Function, Role and Entity Type.
+
Problem
+As they are disjoint, any subclass of more than one of them would be empty, which we assume to be an error and thus show here.
+
Solution
+Automatically generate offending classes below and manually remove all but one of the subtop statements for each of them.
+
+
+
+
+
+
+
Inconsistent Subtop with Subclass
+
+
Situation
+In addition to direct subclass relations, we model the transitively implied subclass relation to a subtop using the meta:subtop relation.
+Other knowledge bases may handle this differently, for example DBpedia always explicitly defines all superclasses.
+
Problem
+If A is subclass of B and A and B have different disjoint superclasses C and D, this implies that A is empty, similar to the multiple subtops problem.
+
Solution
+Manually unify the subtops of the subclass-superclass pairs below.
+
+
+
+
+
+
+
subClassOf and component
+
+
Situation
+In addition to the subclass relation, we also have the similar but different component relations.
+
Problem
+If A is subclass of B and A is also a component of B (or vice versa in the other direction), this seems syntactically wrong.
+
Solution
+Manually decide for one of the relations. If a component relation is chosen and the supercount is only 1, a new superclass needs to be specified.
+
+
+
+
+
+
+
+
redundant superclass
+
+
Situation
+The subClassOf relation is transitive.
+
Problem
+If A is subClassOf B and B is subClassOf C then any explicit triple of A subClassOf C is redundant.
+
Solution
+Delete the explicit triple A subClassOf C.
+
+
+
+
+
+
+
SKOS Link to Different Subtop
+
+
Situation
+The different SNIK subontologies are linked mostly using skos:closeMatch, skos:narrowMatch and skos:broadMatch, which which imply owl:equivalentClass, rdfs:subClassOf and the inverse of rdfs:subClassOf.
+
Problem
+For the same reasons mentioned for multiple subtops and inconsistent subtop, we assume an error if the ends of a link have a different subtop.
+
Solution
+Remove all interlinks between classes with different subtops.
+
+
+
+
+
+
+
Subclass Cycles
+
+
Situation
+Classes are sets of individuals and can be subclasses (subsets) of other classes.
+
Problem
+Subclass cycles (A subclass of B ... subclass of A) collapse all members of the cycle to the same set, which is assumed to be unintentional.
+
Solution
+Find subclass cycles below and and manually remove at least one of them.
+Because of the limitiations of SPARQL 1.1 property paths, we cannot select the full cycle but only give all pairs of classes on a cycle.
+
+
+
+
+
+
+
Missing label
+
+
Situation
+All classes should have a label.
+
Problem
+Some classes don't have a specified label.
+
Solution
+Show classes with missing label and manually add labels.
+
+
+
+
+
+
+
Missing superclass
+
+
Situation
+For easier exploration, visualization and understanding, we want to group all our classes in a more or less balanced tree based on the subclass/superclass relation.
+
Problem
+Some classes don't have a specified superclass and thus are not connected to the rest of the hierarchy.
+
Solution
+Because nearly all have a subtop statement, we use this automatically to add a superclass statement to the graph http://www.snik.eu/ontology/virtual for classes that don't have one already.
+As this creates a very unbalanced tree, you can display those classes below and try to find a more specific superclass for them.
+
+
+
+
+
+
+
Undefined Objects
+
+
Situation
+If a concept is used as the object in some triple, then it should have its own attributes (occur as a subject).
+
Problem
+Sometimes concepts occur as only as an object but not as a subject.
+
Solution
+The responsible extractors for the respective subontologies need to add statements for the objects listed below.
+
+
+
+
+
+
+
Domain Violation
+
+
Situation
+Each SNIK property has a domain that defines allowed subjects.
+
Problem
+Some classes are used as a subject for a triple without being a direct or transitive subclass of the defined domain of the property.
+
Solution
+The offending triples should be removed or remodelled to conform to the domain.
+
+
+
+
+
+
+
Range Violation
+
+
Situation
+Each SNIK property has a range that defines allowed objects.
+
Problem
+Some classes are used as an object for a triple without being a direct or transitive subclass of the defined range of the property.
+
Solution
+The offending triples should be removed or remodelled to conform to the range.
+
+
+
+
+
+
+
Class URL Naming Convention Violations
+
+
Situation
+Class URLs should conform to UpperCamelCase.
+
Problem
+Naming conventions weren't clearly set from the beginning and some pecularities are not widely known, for example abbreviations such as IbmMachine, not IBMMachine.
+
Solution
+Manually correct offending class URLs.
+
+
+
+
+
+
+
Property URL Naming Convention Violations
+
+
Situation
+Property URLs should conform to lowerCamelCase.
+
Problem
+Naming conventions weren't clearly set from the beginning and some pecularities are not widely known, for example abbreviations such as updatesAtm, not updatesATM.
+
Solution
+Manually correct offending property URLs.
+
+
+
+
+
+
+
+
+
Missing Definition
+
+
Situation
+Every class should have a definition from the book.
+
Problem
+Some don't.
+
Solution
+Try to find a definition in the source.
+
+
+
+
+
+
+
Literals with Semicolons
+
+
Situation
+We use semicolons for multiple properties in our extraction tables to hold multiple values.
+
Problem
+Semicolons are rarely used in the textbooks, especially for short strings and outside of definitions.
+Thus they hint at semicolons being used at the wrong place or at errors in the conversion script.
+
Solution
+Generate all literals containing semicolons except those from definitions of more than 100 characters.
+
+
+
+
+
+
Classes with too many subclasses
+
+
Situation
+The subclass hierarchy should ideally be a more or less balanced tree.
+
Problem
+In practice, the hierarchy is too flat.
+
Solution
+List all classes with more than 20 subclasses.
+
+
+
+
+
+
+
+
+
+
+
No Restriction
+
+
Situation
+Classes are connected to other classes mostly by the subclass hierarchy and by restrictions.
+
Problem
+Some classes are isolated from all others, limiting their use and preventing them from being connected to the vizualization graph.
+
Solution
+List all classes that are not connected to other classes by restrictions.
+Because we already covered the hierarchy, we are not taking it into account here.
+Because there are over 1000 of those cases, we only list the first 100.
+They are not necessarily faulty but it may be worthy to investigate if they can be connected in some way.
+
+
+
+
+
+
+
Non-HTTP URI
+
+
Situation
+Our URIs begin with http://...
+
Problem
+Tools like the OntoWiki sometimes fail to expand a prefix and thus create URIs that have an incorrect prefix.
+
Solution
+List all triples with URIs that are neither HTTP URIs nor blanknodes.
+
+
+
+
+
+
+
+
OWL 2 DL: Undefined Properties
+
+
Situation
+Some URIs are used in the property position of a triple but are neither declared as owl:ObjectProperty, nor as owl:DataTypeProperty.
+
+List all URIs are used in the property position of a triple but are neither declared as owl:ObjectProperty, nor as owl:DataTypeProperty.
+Exclude those defined in vocabularies like RDF, RDFS, OWL and so on.
+
+
+
+
+
+
+
OWL 2 DL: Multiply Defined Properties
+
+
Situation
+Some URIs may be defined as more than one of owl:ObjectProperty, owl:DatatypeProperty and owl:AnnotationProperty.
+
+Abbildung 1: Übersicht über die erzielten Projektergebnisse
+
+
Das SNIK Metamodell
+
+
Die Strukturierung und Abbildung von Wissens in einer Ontologie, setzt ein Metamodell voraus, welches domänenunabhängige Konzepte zur Beschreibung von Wissen vorgibt.
+Im ersten Schritt wurde ein Metamodell (Abbildung 2) entwickelt , auf dessen Grundlage Wissen aus Literatur zum Informationsmanagement im Krankenhaus, strukturiert extrahiert werden kann.
+
+
+Abbildung 2: Das SNIK-Metamodell
+
+
Die Visualisierung der Ontologie
+
+
Die SNIK Ontologie beinhaltet (Stand 2024-06-06) 6354 Klassen, 336 Relationen und 43521 Tripel.
+Aktuelle und nach Subontologien aufgeschlüsselte Zahlen finden Sie im Dashboard.
+Die ursprüngliche Abbildung unserer Ontologie erfolgte mittels eines Spreadsheet im CSV-Format.
+Insbesondere im Bereich der Lehre benötigen Studenten ein tiefes Verständnis der Struktur und des Inhalts der Ontologie.
+Dies erscheint in Bezug auf kleine Ontologien einfach, wird jedoch mit steigender Größe nahezu unmöglich.
+Zur effektiven Nutzung der entwickelten Ontologie, ist also eine geeignete Darstellungsform zwingend erforderlich.
+Die Forschung zur Visualisierung von Ontologien, resultierte in einer Liste existierender Werkzeuge.
+Unter Berücksichtigung von Kriterien wie Performance, Bedienbarkeit, Wartung, Funktionalität und Aktualität, wurden diese bewertet.
+Vielversprechende Werkzeuge sind Gephi, Tulip und Cytoscape.
+Aufgrund der Erweiterbarkeit durch Plugins und der Möglichkeit der webbasierten Enwicklung mittels einer JavaScript Bibliothek erfolgte die Visualisierung (Abbildung 3) der SNIK Ontologie mit Cytoscape.
+
+Visualisierung im Browser ansehen.
+
+Abbildung 3: Die Visualisierung der Ontologie
+
+
CIO Umfrage
+
+
Die CIO Umfrage hat zum Ziel die Situation der IT-LeiterInnen des Informationsmanagements im Krankenhaus näher zu beleuchten.
+Dazu wurden 1284 IT-Leiterinnen per E-Mail kontaktiert, von denen 164 die Fragebögen beantwortet haben wurde (Rücklaufquote 12,8 %).
+Neben den Charakteristika der Krankenhäusern, IT-Abteilungen und den IT-LeiterInnen, wurden die Kommunikation mit der Geschäftsführung, die Aufgaben des Informationsmanagements, und die Anwendungssysteme für Aufgaben des Informationsmanagement im Detail erfasst und ausgewertet.
+Siehe auch: The Status Quo of Information Management in Hospitals – Results of an Online Survey
+
+
Umfragereport
+
+
Im Umfragereport “Charakteristika von IT-Abteilungen in Krankenhäusern in Deutschland” wird der Status quo und der Stellenwert des Informationsmanagements in Krankenhäusern zum Umfragezeitpunkt im Jahr 2016 dargestellt.
+Es wurde unter anderem überprüft, inwieweit die in SNIK modellierten Aufgaben des strategischen, taktischen und operativen Informationsmanagements tatsächlich im Informationsmanagement von Krankenhäusern eine Rolle spielen.
+
+
Systemanalyse
+
+
Die Systemanalyse wurde mit dem Ziel die Ist-Situation des Informationsmanagements zweiter deutscher Krankenhäuser zu erfassen durchgeführt.
+Neben einer detaillierten Beschreibung der bestehenden Aufgaben der Informationsmanagement-Abteilung wurden die dabei verwendeten Informationsobjekte und Anwendungssysteme als 3LGM2 Modelle beschrieben.
+Die Systemanalyse zeigt große Unterschiede in der Ausprägung der IM-Aufgaben und eingesetzten Werkzeuge.
+Siehe auch: System Analysis of Information Management
+
+
DsTORE
+
+
Zur Spezifikation des persönlichen entscheidungsuntertützenden System CIO-Navigator wurde die Aufgabenorientierte Requirements Engineering Methode TORE erweitert.
+DsTORE kombiniert die Vorteile von TORE mit der Spezifikation von Entscheidungsaufgaben.
+Die Vorteile von TORE sind die Erfassung und damit einhergehend das Verständnis von NutzerInnen-Aufgaben, die Unterstützung von UI-Prototypen und die explizite Berücksichtigung der Anwendungsdomäne und NutzerInnen-Interaktionen.
+DsTORE (vgl. Abbildung 4) erweitert TORE um die Klassifikation von Aufgaben hinsichtlich deren Entscheidungscharakter, die Berücksichtigung von entscheidungsspezifischen Datenstrukturen, die Verknüpfung von Entscheidungen mit den notwendigen Daten, und die explizite Dokumentation unterschiedlicher Datenquellen, deren Ort und Format.
+
+Abbildung 4: Entscheidungspunkte von DsTORE für die Spezifikation entscheidungsunterstützender Systeme
+
+
TOREOnto
+
+
Die Qualität von Anforderungen kann mit Hilfe von Domänenwissen verbessert werden.
+Domänen-Ontologien enthalten solches Wissen in maschinenlesbarer Form.
+Auf Basis einer Literaturstudie wurden 9 verschiedene Nutzungsszenarien identifiziert, wie Ontologien im Requirements Engineering zur Verbesserung der Qualität von Anforderungen verwendet werden können.
+TOREOnto ermöglicht die Instanziierung der RE-Methode TORE unter der Anwendung der Nutzungsszenarien auf den verschiedenen Spezifikationsebenen und den darin befindlichen Entscheidungspunkten.
+
+
CIONx
+
+
Ist ein entscheidungsuntersützendes System, das IT-LeiterInnen beim Treffen von zuvor definierten Entscheidungen im Informationsmanagement unterstützt.
+Der CIO Navigator (CIONx), wie in Abbildung 5 dargestellt, integriert Daten aus unterschiedlichen Quellen, um den individuellen Informationsbedarf der IT-LeiterInnen für zuvor definierte Entscheidungen übersichtlich darstellt.
+Screenshot des implementierten Systemprototyp CIONx für die Entscheidungsaufgaben Multiprojektmanagement und Changemanagement
+
+Abbildung 5: Screenshot des implementierten Systemprototyp CIONx für die Entscheidungsaufgaben Multiprojektmanagement und Changemanagement
+
+
CIONo
+
+
Die SNIK Ontologie beschreibt für das Informationsmanagement wesentliche Rollen, Aufgaben und Informationsobjekte und deren Relationen zueinander.
+CIONo stellt eine Ontologie-basierte Navigation und Exploration durch das Informationsmanagement zur Verfügung und ist in Abbildung 6 dargestellt.
+Klassen und Relationen der Ontologien können mit Daten hinterlegt werden, wodurch Zusammenhänge deutlich gemacht werden können.
+Beispielsweise können so Frage beantwortet werden, wie „welche MitarbeiterIn arbeitet an welchem Projekt mit wodurch welches IT-Ziel erfüllt wird?“.
+Als Erweiterung können die Klassen der Ontologie mit realen Daten verknüpft werden und über Mechanismen des Ontologie-basierten Datenzugriff (ontology based data access, OBDA) verwendet werden.
+Screenshot des Ontologie-basierten CIO Navigators CIONo
+
+Abbildung 6: Screenshot des Ontologie-basierten CIO Navigators CIONo
Das Semantische Netz des Informationsmanagements im Krankenhaus (SNIK)
+
+
Ziel des Forschungsprojekts ist ein theoretisch und empirisch begründetes, sowie erprobtes Semantisches Netz des Informationsmanagements im Krankenhaus (SNIK), das die Konzepte des Informationsmanagements beschreibt und verbindet.
+
+
Das zu entwickelnde Semantische Netz soll auf den Methoden des Unified Medical Language System (UMLS) beruhen und zur weiteren Professionalisierung des Informationsmanagements (IM) im Krankenhaus beitragen.
+Es verknüpft Begriffe des strategischen, operativen und taktischen IM, der Beschreibung von Informationssystemen und der Unternehmensstrategie und ordnet Methoden zu.
+Auf Instanzebene nimmt es zudem eine empirisch begründete Auswahl und Priorisierung von Aufgaben des IM im Krankenhaus vor und stellt die Verbindung zu krankenhaustypischen Prozessen her.
+Durch die Vernetzung der Begriffe der Ansätze für das IM und aktueller Rahmenwerke für das IM (z. B. COBIT und ITIL) schafft SNIK die Grundlage für krankenhausspezifische Anpassungen dieser Ansätze und Rahmenwerke.
+
+
+Abbildung 1: Beispielhafter, denkbarer Ausschnitt aus SNIK
+
+
Die Abbildung 1 veranschaulicht beispielhaft einen denkbaren Ausschnitt aus dem geplanten SNIK.
+Die IM-Konzepte Anwendungssystem, Krankenhausziel , IT-Ziel, Mitarbeiter und Projekt sind darin durch Relationen verknüpft.
+Synonyme, Instanzen und explizite Verknüpfungen zu Ansätzen des IM sind jedoch nicht berücksichtigt.
+
+
SNIK soll in der Lehre und in der Praxis des Informationsmanagements im Krankenhaus erprobt werden.
+
+
SNIK in der Lehre
+
+
Auf der Basis von SNIK soll eine Unterrichtseinheit zum Informationsmanagement entwickelt, erprobt und ausgewertet werden.
+
+
Diese Unterrichtseinheit, basierend auf einem eLearning-Modul, soll in das vorhandene Curriculum der internationalen Frank-vanSwieten-Lectures (FvSL) integriert, in allen an den FvSL beteiligten Universitäten eingesetzt und durch Befragung der Dozenten ausgewertet werden.
+
+
SNIK in der Praxis des Informationsmanagements im Krankenhaus
+
Auf der Basis von SNIK soll prototypisch die Software CIO-Navigator (CION) realisiert und erprobt werden, die dem CIO und der Krankenhausleitung die Navigation durch das vernetzte Informationsmanagement ermöglicht.
+
+
Der Prototyp eines SNIK-basierten CIO-Navigators dient der Datenintegration der im IM und im Krankenhausmanagement genutzten Werkzeuge und soll die für das vernetzte IM notwendigen Informationen visualisieren.
+Der CIO-Navigator kann als Business-Analyse-Werkzeug aufgefasst werden.
+Für den CIO-Navigator soll zunächst ein Nutzungs- und Architekturkonzept entwickelt werden.
+Dabei ist insbesondere der Umgang mit Änderungen in den Daten der integrierten Werkzeuge eine Herausforderung.
+Die Tauglichkeit des CIO-Navigators und des Architekturkonzepts soll schließlich an zwei Krankenhäusern erprobt werden.
+
+# SNIK Website
+
+[](https://github.com/snikproject/snik.eu/actions/workflows/deploy.yml)
+[](LICENSE)
+
+Live on 
+
+
+ 
+ 
+
+
+
+Abbildung 1: Übersicht über die erzielten Projektergebnisse
+Abbildung 3: Die Visualisierung der Ontologie
+Abbildung 4: Entscheidungspunkte von DsTORE für die Spezifikation entscheidungsunterstützender Systeme
+Abbildung 5: Screenshot des implementierten Systemprototyp CIONx für die Entscheidungsaufgaben Multiprojektmanagement und Changemanagement
+Abbildung 6: Screenshot des Ontologie-basierten CIO Navigators CIONo
+Abbildung 1: Beispielhafter, denkbarer Ausschnitt aus SNIK