Initial commit

.devcontainer/Dockerfile

@@ -0,0 +1,55 @@
+FROM mcr.microsoft.com/devcontainers/base:alpine-3.18
+
+# Setzen der Umgebungsvariablen
+ENV FIRELY_TERMINAL_VERSION=3.1.0
+ENV JAVA_VALIDATOR_VERSION=6.0.11
+ENV SUSHI_VERSION=3.5.0
+
+# Installieren der notwendige Tools
+# Add Microsoft's .NET SDK repository and install .NET SDK
+RUN wget https://dot.net/v1/dotnet-install.sh \
+ && chmod +x dotnet-install.sh \
+ && ./dotnet-install.sh --channel 6.0 --install-dir /usr/share/dotnet \
+ && ln -s /usr/share/dotnet/dotnet /usr/local/bin \
+ && rm dotnet-install.sh
+
+# Install ICU libraries
+RUN apk add --no-cache icu-libs
+
+# Install Node.js and npm
+RUN apk add --no-cache nodejs npm
+
+# Install Java (OpenJDK)
+RUN apk add --no-cache openjdk11
+
+# Install Firely Terminal as vscode user
+# Switch to the vscode user
+USER vscode
+
+# Install Firely Terminal
+RUN dotnet tool install --global Firely.Terminal --version $FIRELY_TERMINAL_VERSION
+
+# Add .NET tools to PATH for vscode user
+ENV PATH="/home/vscode/.dotnet/tools:${PATH}"
+
+# Switch back to root user to perform remaining installations
+USER root
+
+RUN npm install -g fsh-sushi@$SUSHI_VERSION
+
+# Installieren der zusätzliche Abhängigkeiten
+RUN apk update && apk add --no-cache jq findutils curl ca-certificates
+
+# Setup for FHIR Validator
+RUN mkdir -p /home/vscode/.fhir/validators/
+RUN wget -q https://github.com/hapifhir/org.hl7.fhir.core/releases/download/$JAVA_VALIDATOR_VERSION/validator_cli.jar -O /home/vscode/.fhir/validators/validator_cli.jar
+
+RUN mkdir -p /home/vscode/.fhir/settings/
+COPY codfsh-config.yaml /home/vscode/.fhir/settings/codfsh-config.yaml
+
+# Setzen des Arbeitsverzeichnis
+WORKDIR /workspace
+
+COPY . /workspace
+
+CMD [ "/bin/bash" ]

.devcontainer/codfsh-config.yaml

@@ -0,0 +1,9 @@
+sushi:
+ min_version: "3.5.0"
+hapi:
+ min_version: "3.0.0"
+ parameters: 
+ jurisdiction: DE
+ locale: de-DE
+ tx: "n/a"
+ debug: true

.devcontainer/devcontainer.json

@@ -0,0 +1,38 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/alpine
+{
+ "name": "FHIR Development Container",
+ // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+ "build": {
+ "dockerfile": "Dockerfile"
+ },
+ "customizations": {
+ "vscode": {
+ "extensions": [
+ "gematikde.codfsh",
+ "MITRE-Health.vscode-language-fsh",
+ "ms-azuretools.vscode-docker",
+ "edenlabio.fhir-profiler-tool"
+ ],
+ "settings": {
+ "codfsh.HapiValidator.Executable": "/home/vscode/.fhir/validators/validator_cli.jar",
+ "codfsh.HapiValidator.Settings.SettingsFile": "/home/vscode/.fhir/settings/codfsh-config.yaml"
+ }
+ }
+ },
+ "mounts": [
+ "source=${localEnv:HOME}${localEnv:USERPROFILE}/.fhir/packages,target=/home/vscode/.fhir/packages,type=bind"
+ ]
+
+ // Features to add to the dev container. More info: https://containers.dev/features.
+ // "features": {},
+
+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
+ // "forwardPorts": [],
+
+ // Use 'postCreateCommand' to run commands after the container is created.
+ // "postCreateCommand": "uname -a",
+
+ // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+ // "remoteUser": "root"
+}

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,50 @@
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Calls for violence, vilification and advertising
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at OSPO@gematik.de. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -0,0 +1,76 @@
+name: "🐛 Bug Report"
+description: Create a new ticket for a bug.
+title: "🐛 [BUG] - <title>"
+labels: [
+ "bug",
+ "invalid"
+]
+body:
+ - type: textarea
+ id: description
+ attributes:
+ label: "Description"
+ description: Please enter an explicit description of the issue.
+ placeholder: |
+ Short and explicit description of the incident...
+ If you are able to specify, please also select the appropriate label:
+ - Bug, if something is technically not working, e.g. not compiling.
+ - Invalid, if something is technically working but does not seem to yield to correct outcome, e.g. 1+1 is 3.
+ validations:
+ required: true
+ - type: input
+ id: reprod-url
+ attributes:
+ label: "Reproduction URL"
+ description: Please enter the corresponding Simplifier URL (or other, e.g. GitHub) to provide a source for reproduction of the issue.
+ placeholder: ex. https://simplifier.net/REPO-NAME/RESOURCE-NAME
+ validations:
+ required: true
+ - type: input
+ id: version
+ attributes:
+ label: "Version or Branch"
+ description: If this bug occures only in a specific version or development branch, please tell us here.
+ placeholder: ex. Only occurs with ISiK 2.0.4.
+ validations:
+ required: false
+ - type: textarea
+ id: reprod
+ attributes:
+ label: "Reproduction Steps"
+ description: Please enter a step by step description of the issue.
+ value: |
+
+ 1. At the interface '....'
+ 2. With Data '....'
+ 3. Execute Operation '....'
+ 4. See error
+ render: bash
+ validations:
+ required: true
+ - type: textarea
+ id: logs
+ attributes:
+ label: "Stack Trace and Logs"
+ description: Please copy and paste any relevant stack trace or log output. This will be automatically formatted into code.
+ render: bash
+ validations:
+ required: false 
+ - type: textarea
+ id: screenshot
+ attributes:
+ label: "Screenshots"
+ description: If applicable, add screenshots to help explain your problem.
+ value: |
+ ![DESCRIPTION](LINK.png)
+ render: bash
+ validations:
+ required: false
+ - type: textarea
+ id: environment
+ attributes:
+ label: "Software and Environment"
+ description: Please describe the used software and your environment further.
+ placeholder: ex. I Use dotnet sdk 4.x and Firely Terminal to manage fhir packages
+ validations:
+ required: false

.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml

@@ -0,0 +1,72 @@
+name: "💡 Feature Request"
+description: Create a new ticket for a new feature request
+title: "💡 [REQUEST] - <title>"
+labels: [
+ "question",
+ "enhancement"
+]
+body:
+ - type: input
+ id: target_date
+ attributes:
+ label: "Target Date"
+ description: When would you need this feature to be available?
+ placeholder: "MM YYYY"
+ validations:
+ required: false
+ - type: input
+ id: implementation_pr
+ attributes:
+ label: "Implementation PR"
+ description: In case you already developed the feature yourself, please tell us the corresponding PR. Also, maybe you have seen this feature somewhere else?
+ placeholder: "Your Pull Request ID or link to a similar PR."
+ validations:
+ required: false
+ - type: textarea
+ id: reference_issues
+ attributes:
+ label: "Reference Issues"
+ description: Some common issues this feature would address.
+ placeholder: "Issues IDs and references"
+ validations:
+ required: false
+ - type: textarea
+ id: summary
+ attributes:
+ label: "Summary"
+ description: Please provide a brief explanation of the feature.
+ placeholder: |
+ Describe in a few lines your feature request ...
+ If you are able to specify, please also select the appropriate label:
+ - Question, if you would also be fine with more information, on how to address your request, e.g. with a workaround.
+ - Enhancement, if you are kinda sure your Request is an independent new addition, that could not be achieved otherwise.
+ validations:
+ required: true
+ - type: textarea
+ id: basic_example
+ attributes:
+ label: "Common Examples"
+ description: Indicate some basic examples of your feature or a common flow in which it would be used.
+ placeholder: |
+ In the use case of '...'
+ The necessary data will flow like '....'
+ Feature will be used '....'
+ With the result of '....'
+ validations:
+ required: true
+ - type: textarea
+ id: drawbacks
+ attributes:
+ label: "Drawbacks"
+ description: What are the drawbacks or mutual impacts of your feature request?
+ placeholder: Identify the drawbacks and mutual impacts with respect to other features.
+ validations:
+ required: true
+ - type: textarea
+ id: unadress_question
+ attributes:
+ label: "Unadressed questions"
+ description: What issues or questions still remain unadressed?
+ placeholder: Identify any unresolved issues or questions.
+ validations:
+ required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false