404
Page not found
Looks like we've got some broken links.
404
Looks like we've got some broken links.
Feel free to contact us via E-Mail (dsf-gecko@hs-heilbronn.de) and we will take care of your request as soon as possible.
DSF's community is growing and we welcome anyone who would like to join! 🚀
You can get familiar with the DSF code on GitHub. Branching follows the git-flow model, for the latest development version see branch develop. Additionally, you can find more information here in the documentation.
You´re welcome to share your experience with the Community. If you have a bug to report or feature to request, that's what the GitHub issues are for.
Funded for further development of the Data Sharing Framework are:
The GECKO Institute is a research institution of Heilbronn University of Applied Sciences and conducts research and development at the interfaces between medicine, economics and computer science. The DSF is part of Prof. Fegeler's research area: Interoperability and Digital Processes in Medicine. Other areas of research include educational technologies, health economics, and consumer health informatics.
The Institute of Medical Informatics belongs to the University of Heidelberg. The scientific focus of the institute is on structured patient data, e.g.
The LIFE Institute of the University of Leipzig manages collaborative and follow-on projects in the fields of medicine, public health, medical informatics, and biobanking.
The DSF Community connects the DSF competencies of the entire Medical Informatics Initiative (MII) so that new use cases, in particular from Module 3 or the Network University Medicine (NUM), are better supported in creating the respective DSF plugins. In the context of Module 2b, the DSF Community contributes to the further development of the common digital infrastructure of the MII together with the FDPG+ and TRANSIT projects. BMBF
Heilbronn University (HHN) focuses on the connecting of DSF related topics and competencies in the MII with the community management. The quality assurance of new DSF plugins and further development of the application and core components aim at a scalable, stable and secure operation of the DSF (Funding code: 01ZZ2307A).
Heidelberg University is focusing on the further development of the DSF core components as well as the rollout of the DSF plugins, in particular also from the perspective of a data integration center in consultation with the FDGP+ and TRANSIT projects (Funding code: 01ZZ2307B).
The University of Leipzig will further develop and adapt the DSF plugin for the Research Data Portal for Health FDPG according to specifications resulting from the FDPG+ project and enable Data Integration Centers (DIC) to operate the FDPG plugin (Funding code: 01ZZ2307C).
HiGHmed aims to increase the efficiency of clinical research and improve patient care through new medical informatics solutions and cross-organizational data exchange. The concept will be developed on the basis of three defined prototypical use cases, which will ensure close integration with the requirements of patient care and medical research. The GECKO Institute of HHN will establish a trusted third party with pseudonymization service to implement the goals of HiGHmed and is involved in the technical development of the DSF together with the partners (Funding code: 01ZZ1802E). Heidelberg University is in particular involved in the technical development of the DSF (Funding code: 01ZZ1802A).
404 Not Found
\\n"}');export{m as comp,p as data}; diff --git a/assets/GMDS2022-dev.html-DIJQX8MW.js b/assets/GMDS2022-dev.html-DIJQX8MW.js new file mode 100644 index 000000000..c61f289ca --- /dev/null +++ b/assets/GMDS2022-dev.html-DIJQX8MW.js @@ -0,0 +1 @@ +import{_ as a}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as i,o as n,c as r,a as t,b as e,d as s,w as l}from"./app-9qxDwvDG.js";const c={},m=t("meta",{"http-equiv":"refresh",content:"0; URL=/oldstable/tutorial/"},null,-1);function d(h,u){const o=i("RouteLink");return n(),r("div",null,[t("p",null,[e("Redirect to "),s(o,{to:"/oldstable/tutorial/"},{default:l(()=>[e("this webpage")]),_:1}),e(".")]),m])}const f=a(c,[["render",d],["__file","GMDS2022-dev.html.vue"]]),b=JSON.parse('{"path":"/intro/tutorials/GMDS2022-dev.html","title":"GMDS2022 - Process Development","lang":"en-US","frontmatter":{"title":"GMDS2022 - Process Development","icon":"code"},"headers":[],"git":{"createdTime":1690461865000,"updatedTime":1699955216000,"contributors":[{"name":"Simon Mödinger","email":"smoeding@stud.hs-heilbronn.de","commits":1},{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":0.07,"words":20},"filePathRelative":"intro/tutorials/GMDS2022-dev.md","localizedDate":"July 27, 2023","excerpt":"Redirect to this webpage.
\\n\\n"}');export{f as comp,b as data}; diff --git a/assets/MIE2023.html-XbQcy1P_.js b/assets/MIE2023.html-XbQcy1P_.js new file mode 100644 index 000000000..194e8bfcc --- /dev/null +++ b/assets/MIE2023.html-XbQcy1P_.js @@ -0,0 +1 @@ +import{_ as r}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as s,o as n,c as o,a as e,b as t,d as i,e as l}from"./app-9qxDwvDG.js";const d="/photos/tutorials/dsf-architecture.svg",c={},h=e("h2",{id:"abstract",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#abstract"},[e("span",null,"Abstract")])],-1),u={href:"https://github.com/highmed/highmed-dsf",target:"_blank",rel:"noopener noreferrer"},p={href:"https://www.medizininformatik-initiative.de/en/start",target:"_blank",rel:"noopener noreferrer"},m=l('The use of real-world data collected by healthcare providers for bio-medical research requires the data to be available and accessible. This is especially important when considering the usage of data across organizations. Distributed processes such as feasibility studies, record linkage, and data sharing need to be established for effective consolidation and analysis.
While even multi-center retrospective studies using real-world data become commonplace, maintaining infrastructure components for every project conducted is not sustainable. To address this, the Data Sharing Framework (DSF) was developed as an open source, use case independent distributed business process engine to execute cross-organizational research and healthcare delivery processes.
The tutorial will cover the fundamental concepts of distributed processes and will provide an overview of the DSF's architecture and key standards such as HL7 FHIR and BPMN 2.0 that are used in the framework. The tutorial will present real-world examples to illustrate the DSFs capabilities and delve into specific issues the DSF addresses for the German Medical Informatics Initiative (MII).
Participants will have the opportunity to gain hands-on experience with the DSF by working with different processes in a lab setting. Technical aspects such as authentication and authorization, onboarding of new organizations and guidance on using the DSF for other use cases, such as specific research projects or new infrastructure developments, will be covered.
Finally, the tutorial will present lessons learned from the last years of using the DSF in test and production environments in multiple research consortia and will present ideas for future improvements based on feedback from end-users, process developers, project managers and administrative staff.
Decision makers and project members with data sharing ideas looking for an architecture, as well as medical informatics professionals and software developers tasked with building multi-centric data sharing applications, are the target audience for this tutorial.
You need a laptop with a web browser for the hands-on portion of the tutorial.
You will...
With this tutorial, participants will gain a detailed insight into the Data Sharing Framework (DSF) (https://github.com/highmed/highmed-dsf). The open source DSF enables users to execute biomedical research and healthcare delivery processes across organizations, and the tutorial will demonstrate this with examples from the German Medical Informatics Initiative (MII) (https://www.medizininformatik-initiative.de/en/start) funded by the Federal Ministry of Education and Research (BMBF). The tutorial will cover fundamental concepts of distributed processes, the DSFs architecture and key standards such as HL7 FHIR and BPMN 2.0. Participants will have the opportunity to gain hands-on experience with the DSF by working with different processes in a lab setting. Technical aspects such as authentication and authorization will be covered, as well as guidance on using the DSF for other use cases. This tutorial is designed for those involved in distributed research projects, including project members and software developers, as well as individuals interested in multi-organizational research projects.
"}');export{y as comp,k as data}; diff --git a/assets/SearchResult-CJORLP05.js b/assets/SearchResult-CJORLP05.js new file mode 100644 index 000000000..5e73b655f --- /dev/null +++ b/assets/SearchResult-CJORLP05.js @@ -0,0 +1 @@ +import{u as G,f as Z,g as ee,h as _,i as te,j as ae,t as ie,k as le,l as P,m as D,n as ne,p as N,q as a,s as re,R as O,v as oe,x as se,y as me,z as j,A as B,B as ve,C as ue,D as he,E as ce,O as de,F as pe,G as fe,P as ge,H as be,I as ye,J as L}from"./app-9qxDwvDG.js";const xe=["/","/about/","/hackathon/","/for-you/","/for-you/learn.html","/intro/","/intro/publications.html","/oldstable/","/oldstable/introduction.html","/security/","/sprechstunde/","/stable/dsf-for-dev.html","/stable/","/stable/process-plugins-advanced.html","/v1.0.0/dsf-for-dev.html","/v1.0.0/","/v1.0.0/process-plugins-advanced.html","/v1.1.0/dsf-for-dev.html","/v1.1.0/","/v1.1.0/process-plugins-advanced.html","/v1.2.0/dsf-for-dev.html","/v1.2.0/","/v1.2.0/process-plugins-advanced.html","/v1.3.0/dsf-for-dev.html","/v1.3.0/","/v1.3.0/process-plugins-advanced.html","/v1.3.1/dsf-for-dev.html","/v1.3.1/","/v1.3.1/process-plugins-advanced.html","/v1.3.2/dsf-for-dev.html","/v1.3.2/","/v1.3.2/process-plugins-advanced.html","/v1.4.0/dsf-for-dev.html","/v1.4.0/","/v1.4.0/process-plugins-advanced.html","/v1.5.0/dsf-for-dev.html","/v1.5.0/","/v1.5.0/process-plugins-advanced.html","/v1.5.1/dsf-for-dev.html","/v1.5.1/","/v1.5.1/process-plugins-advanced.html","/about/learnmore/","/about/learnmore/contact.html","/about/learnmore/partners.html","/about/learnmore/public.html","/about/learnmore/team.html","/intro/info/allowList.html","/intro/info/architecture.html","/intro/info/basics.html","/intro/info/introduction.html","/intro/info/networkSetup.html","/intro/info/process-plugins.html","/intro/info/security.html","/intro/tutorials/GMDS2022-dev.html","/intro/tutorials/MIE2023.html","/intro/tutorials/","/intro/tutorials/Talks.html","/intro/use-cases/","/intro/use-cases/feasibility.html","/intro/use-cases/num.html","/oldstable/build/","/oldstable/build/build.html","/oldstable/build/proxyTestTool.html","/oldstable/build/releaseANewVersion.html","/oldstable/code/","/oldstable/code/addingANewFhirR.html","/oldstable/code/addingANewMpiClient.html","/oldstable/code/addingANewOpenEhrClient.html","/oldstable/code/changingBpmnProcesses.html","/oldstable/code/code.html","/oldstable/code/eclipseContent.html","/oldstable/code/intelliJContent.html","/oldstable/code/libraries.html","/oldstable/code/usingTheGitHubMaven.html","/oldstable/generalinformation/","/oldstable/generalinformation/authentication.html","/oldstable/generalinformation/networkSetup.html","/oldstable/releases/","/oldstable/releases/configBpe.html","/oldstable/releases/configFhir.html","/oldstable/releases/configFhirReverseProxy.html","/oldstable/releases/highmedInstall.html","/oldstable/releases/num-codexInstall.html","/oldstable/releases/upgradeFrom7.html","/oldstable/releases/upgradeFrom8.html","/oldstable/releases/upgradeFrom90.html","/oldstable/releases/upgradeFrom91.html","/oldstable/releases/upgradeFrom92.html","/oldstable/tutorial/","/oldstable/tutorial/ex11-docker-composeyml.html","/oldstable/tutorial/exercise1-simpleProcess.html","/oldstable/tutorial/exercise11-processDebugging.html","/oldstable/tutorial/exercise2-inputParameters.html","/oldstable/tutorial/exercise3-messageEvents.html","/oldstable/tutorial/exercise4-exclusiveGateways.html","/oldstable/tutorial/exercise5-eventBasedGateways.html","/oldstable/tutorial/prerequisites.html","/stable/contribute/code.html","/stable/contribute/documentation.html","/stable/contribute/","/stable/develop/","/stable/develop/create.html","/stable/develop/upgrade-from-0.html","/stable/maintain/","/stable/maintain/allowList-mgm.html","/stable/maintain/install-plugins.html","/stable/maintain/install.html","/stable/maintain/upgrade-from-0.html","/stable/maintain/upgrade-from-1.html","/v1.0.0/develop/","/v1.0.0/develop/create.html","/v1.0.0/develop/upgrade-from-0.html","/v1.0.0/maintain/","/v1.0.0/maintain/allowList-mgm.html","/v1.0.0/maintain/install.html","/v1.0.0/maintain/upgrade-from-0.html","/v1.1.0/develop/","/v1.1.0/develop/create.html","/v1.1.0/develop/upgrade-from-0.html","/v1.1.0/maintain/","/v1.1.0/maintain/allowList-mgm.html","/v1.1.0/maintain/install.html","/v1.1.0/maintain/upgrade-from-0.html","/v1.1.0/maintain/upgrade-from-1.html","/v1.2.0/develop/","/v1.2.0/develop/create.html","/v1.2.0/develop/upgrade-from-0.html","/v1.2.0/maintain/","/v1.2.0/maintain/allowList-mgm.html","/v1.2.0/maintain/install.html","/v1.2.0/maintain/upgrade-from-0.html","/v1.2.0/maintain/upgrade-from-1.html","/v1.3.0/develop/","/v1.3.0/develop/create.html","/v1.3.0/develop/upgrade-from-0.html","/v1.3.0/maintain/","/v1.3.0/maintain/allowList-mgm.html","/v1.3.0/maintain/install-plugins.html","/v1.3.0/maintain/install.html","/v1.3.0/maintain/upgrade-from-0.html","/v1.3.0/maintain/upgrade-from-1.html","/v1.3.1/develop/","/v1.3.1/develop/create.html","/v1.3.1/develop/upgrade-from-0.html","/v1.3.1/maintain/","/v1.3.1/maintain/allowList-mgm.html","/v1.3.1/maintain/install-plugins.html","/v1.3.1/maintain/install.html","/v1.3.1/maintain/upgrade-from-0.html","/v1.3.1/maintain/upgrade-from-1.html","/v1.3.2/develop/","/v1.3.2/develop/create.html","/v1.3.2/develop/upgrade-from-0.html","/v1.3.2/maintain/","/v1.3.2/maintain/allowList-mgm.html","/v1.3.2/maintain/install-plugins.html","/v1.3.2/maintain/install.html","/v1.3.2/maintain/upgrade-from-0.html","/v1.3.2/maintain/upgrade-from-1.html","/v1.4.0/contribute/code.html","/v1.4.0/contribute/documentation.html","/v1.4.0/contribute/","/v1.4.0/develop/","/v1.4.0/develop/create.html","/v1.4.0/develop/upgrade-from-0.html","/v1.4.0/maintain/","/v1.4.0/maintain/allowList-mgm.html","/v1.4.0/maintain/install-plugins.html","/v1.4.0/maintain/install.html","/v1.4.0/maintain/upgrade-from-0.html","/v1.4.0/maintain/upgrade-from-1.html","/v1.5.0/contribute/code.html","/v1.5.0/contribute/documentation.html","/v1.5.0/contribute/","/v1.5.0/develop/","/v1.5.0/develop/create.html","/v1.5.0/develop/upgrade-from-0.html","/v1.5.0/maintain/","/v1.5.0/maintain/allowList-mgm.html","/v1.5.0/maintain/install-plugins.html","/v1.5.0/maintain/install.html","/v1.5.0/maintain/upgrade-from-0.html","/v1.5.0/maintain/upgrade-from-1.html","/v1.5.1/contribute/code.html","/v1.5.1/contribute/documentation.html","/v1.5.1/contribute/","/v1.5.1/develop/","/v1.5.1/develop/create.html","/v1.5.1/develop/upgrade-from-0.html","/v1.5.1/maintain/","/v1.5.1/maintain/allowList-mgm.html","/v1.5.1/maintain/install-plugins.html","/v1.5.1/maintain/install.html","/v1.5.1/maintain/upgrade-from-0.html","/v1.5.1/maintain/upgrade-from-1.html","/stable/maintain/bpe/","/stable/maintain/bpe/access-control.html","/stable/maintain/bpe/configuration.html","/stable/maintain/bpe/oidc.html","/stable/maintain/bpe-reverse-proxy/","/stable/maintain/bpe-reverse-proxy/configuration.html","/stable/maintain/fhir/","/stable/maintain/fhir/access-control.html","/stable/maintain/fhir/configuration.html","/stable/maintain/fhir/oidc.html","/stable/maintain/fhir-reverse-proxy/","/stable/maintain/fhir-reverse-proxy/configuration.html","/v1.0.0/maintain/configuration/","/v1.0.0/maintain/configuration/bpe.html","/v1.0.0/maintain/configuration/common.html","/v1.0.0/maintain/configuration/fhir.html","/v1.0.0/maintain/configuration/reverseproxy.html","/v1.1.0/maintain/bpe/","/v1.1.0/maintain/bpe/configuration.html","/v1.1.0/maintain/fhir/","/v1.1.0/maintain/fhir/access-control.html","/v1.1.0/maintain/fhir/configuration.html","/v1.1.0/maintain/fhir/oidc.html","/v1.1.0/maintain/fhir-reverse-proxy/","/v1.1.0/maintain/fhir-reverse-proxy/configuration.html","/v1.2.0/maintain/bpe/","/v1.2.0/maintain/bpe/configuration.html","/v1.2.0/maintain/fhir/","/v1.2.0/maintain/fhir/access-control.html","/v1.2.0/maintain/fhir/configuration.html","/v1.2.0/maintain/fhir/oidc.html","/v1.2.0/maintain/fhir-reverse-proxy/","/v1.2.0/maintain/fhir-reverse-proxy/configuration.html","/v1.3.0/maintain/bpe/","/v1.3.0/maintain/bpe/configuration.html","/v1.3.0/maintain/fhir/","/v1.3.0/maintain/fhir/access-control.html","/v1.3.0/maintain/fhir/configuration.html","/v1.3.0/maintain/fhir/oidc.html","/v1.3.0/maintain/fhir-reverse-proxy/","/v1.3.0/maintain/fhir-reverse-proxy/configuration.html","/v1.3.1/maintain/bpe/","/v1.3.1/maintain/bpe/configuration.html","/v1.3.1/maintain/fhir/","/v1.3.1/maintain/fhir/access-control.html","/v1.3.1/maintain/fhir/configuration.html","/v1.3.1/maintain/fhir/oidc.html","/v1.3.1/maintain/fhir-reverse-proxy/","/v1.3.1/maintain/fhir-reverse-proxy/configuration.html","/v1.3.2/maintain/bpe/","/v1.3.2/maintain/bpe/configuration.html","/v1.3.2/maintain/fhir/","/v1.3.2/maintain/fhir/access-control.html","/v1.3.2/maintain/fhir/configuration.html","/v1.3.2/maintain/fhir/oidc.html","/v1.3.2/maintain/fhir-reverse-proxy/","/v1.3.2/maintain/fhir-reverse-proxy/configuration.html","/v1.4.0/maintain/bpe/","/v1.4.0/maintain/bpe/configuration.html","/v1.4.0/maintain/fhir/","/v1.4.0/maintain/fhir/access-control.html","/v1.4.0/maintain/fhir/configuration.html","/v1.4.0/maintain/fhir/oidc.html","/v1.4.0/maintain/fhir-reverse-proxy/","/v1.4.0/maintain/fhir-reverse-proxy/configuration.html","/v1.5.0/maintain/bpe/","/v1.5.0/maintain/bpe/access-control.html","/v1.5.0/maintain/bpe/configuration.html","/v1.5.0/maintain/bpe/oidc.html","/v1.5.0/maintain/bpe-reverse-proxy/","/v1.5.0/maintain/bpe-reverse-proxy/configuration.html","/v1.5.0/maintain/fhir/","/v1.5.0/maintain/fhir/access-control.html","/v1.5.0/maintain/fhir/configuration.html","/v1.5.0/maintain/fhir/oidc.html","/v1.5.0/maintain/fhir-reverse-proxy/","/v1.5.0/maintain/fhir-reverse-proxy/configuration.html","/v1.5.1/maintain/bpe/","/v1.5.1/maintain/bpe/access-control.html","/v1.5.1/maintain/bpe/configuration.html","/v1.5.1/maintain/bpe/oidc.html","/v1.5.1/maintain/bpe-reverse-proxy/","/v1.5.1/maintain/bpe-reverse-proxy/configuration.html","/v1.5.1/maintain/fhir/","/v1.5.1/maintain/fhir/access-control.html","/v1.5.1/maintain/fhir/configuration.html","/v1.5.1/maintain/fhir/oidc.html","/v1.5.1/maintain/fhir-reverse-proxy/","/v1.5.1/maintain/fhir-reverse-proxy/configuration.html","/404.html","/intro/info/"],we="SEARCH_PRO_QUERY_HISTORY",d=G(we,[]),He=()=>{const{queryHistoryCount:i}=L,l=i>0;return{enabled:l,queryHistory:d,addQueryHistory:n=>{l&&(d.value.lengthRedirect to this webpage.
\\n\\n"}');export{b as comp,k as data}; diff --git a/assets/access-control.html-BTGCEF0M.js b/assets/access-control.html-BTGCEF0M.js new file mode 100644 index 000000000..ca0973ee4 --- /dev/null +++ b/assets/access-control.html-BTGCEF0M.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),p={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},h=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{w as comp,x as data}; diff --git a/assets/access-control.html-BdPtTQ83.js b/assets/access-control.html-BdPtTQ83.js new file mode 100644 index 000000000..7bf37c90d --- /dev/null +++ b/assets/access-control.html-BdPtTQ83.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),h={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},p=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-Bh4iDgaV.js b/assets/access-control.html-Bh4iDgaV.js new file mode 100644 index 000000000..753c05a91 --- /dev/null +++ b/assets/access-control.html-Bh4iDgaV.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),p={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},h=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{w as comp,x as data}; diff --git a/assets/access-control.html-BkP29Xsy.js b/assets/access-control.html-BkP29Xsy.js new file mode 100644 index 000000000..b65874136 --- /dev/null +++ b/assets/access-control.html-BkP29Xsy.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),p={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},h=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-Bx2B4nWC.js b/assets/access-control.html-Bx2B4nWC.js new file mode 100644 index 000000000..e328ae45f --- /dev/null +++ b/assets/access-control.html-Bx2B4nWC.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),p={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},h=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{w as comp,x as data}; diff --git a/assets/access-control.html-CfvLASIr.js b/assets/access-control.html-CfvLASIr.js new file mode 100644 index 000000000..86bd0637d --- /dev/null +++ b/assets/access-control.html-CfvLASIr.js @@ -0,0 +1,26 @@ +import{_ as i}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as t,o as r,c,a,b as e,d as o,e as n}from"./app-9qxDwvDG.js";const l={},d=n(`The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
Access to the user interface can be enabled for client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable access for a specific client-certificate:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - ADMIN
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the user interface. Allowed values are:
ADMIN.
The BPE server currently does not support any practionier-roles.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - ADMIN
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - ADMIN
+The third example allows administrator access and users e-mail addresses to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - email-admins:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - ADMIN
+The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
\\nOpenID Connect
\\nTo enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
\\nOpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-DdJwZdMu.js b/assets/access-control.html-DdJwZdMu.js new file mode 100644 index 000000000..2ac1262c1 --- /dev/null +++ b/assets/access-control.html-DdJwZdMu.js @@ -0,0 +1,26 @@ +import{_ as i}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as t,o as r,c,a,b as e,d as o,e as n}from"./app-9qxDwvDG.js";const l={},d=n(`The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
Access to the user interface can be enabled for client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable access for a specific client-certificate:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - ADMIN
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the user interface. Allowed values are:
ADMIN.
The BPE server currently does not support any practionier-roles.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - ADMIN
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - ADMIN
+The third example allows administrator access and users e-mail addresses to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - email-admins:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - ADMIN
+The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
\\nOpenID Connect
\\nTo enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
\\nOpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-DtDewR4o.js b/assets/access-control.html-DtDewR4o.js new file mode 100644 index 000000000..e2fccc837 --- /dev/null +++ b/assets/access-control.html-DtDewR4o.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),h={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},p=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-ZcE2aRxa.js b/assets/access-control.html-ZcE2aRxa.js new file mode 100644 index 000000000..eb60cbbd5 --- /dev/null +++ b/assets/access-control.html-ZcE2aRxa.js @@ -0,0 +1,46 @@ +import{_ as t}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o,c,a,b as e,d as s,e as i}from"./app-9qxDwvDG.js";const l={},d=a("h2",{id:"overview",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#overview"},[a("span",null,"Overview")])],-1),p={href:"http://hl7.org/fhir/R4/http.html",target:"_blank",rel:"noopener noreferrer"},h=a("a",{href:"configuration#dev-dsf-fhir-server-organization-thumbprint"},"DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT",-1),u=i(`OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF FHIR server OpenID Connect configuration page.
Access to the API and user interface can be enabled for additional client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable read access for a specific client-certificate:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The list of user roles above contains a single entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_FHIR_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
To types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the REST API and user interface. Allowed values are:
CREATE, READ, UPDATE, DELETE, SEARCH, HISTORY, PERMANENT_DELETE and WEBSOCKET.
Process plugins can defined and use there own code-systems. However, the DSF specifies a standard set of practitioner roles within the CodeSystem http://dsf.dev/fhir/CodeSystem/practitioner-role:
UAC_USER, COS_USER, CRR_USER, DIC_USER, DMS_USER, DTS_USER, HRP_USER, TTP_USER, AMS_USER and DSF_ADMIN.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - CREATE
+ - READ
+ - UPDATE
+ - DELETE
+ - SEARCH
+ - HISTORY
+ practitioner-role:
+ - http://dsf.dev/fhir/CodeSystem/practitioner-role|DSF_ADMIN
+
+The third example allows read-only access. Two e-mail addresses are used to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_FHIR_SERVER_ROLECONFIG: |
+ - read-only:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - READ
+ - SEARCH
+ - HISTORY
+The DSF FHIR server implements a subset of the FHIR R4 REST API. When accessing the API with a web browser a limited graphical user interface is shown. Without any additional configuration the API and user interface is only accessible with the X.509 client certificate configured for the organization via the configuration parameter: DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT
"}');export{O as comp,x as data}; diff --git a/assets/access-control.html-kswS7Ezb.js b/assets/access-control.html-kswS7Ezb.js new file mode 100644 index 000000000..59a0bcbbf --- /dev/null +++ b/assets/access-control.html-kswS7Ezb.js @@ -0,0 +1,26 @@ +import{_ as i}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as t,o as r,c,a,b as e,d as o,e as n}from"./app-9qxDwvDG.js";const l={},d=n(`The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
OpenID Connect
To enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
Access to the user interface can be enabled for client certificates and local users authenticating via OAuth 2.0 OpenID Connect. Access can be configured for so called roles, with all roles specified using the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG. The value for this environment variable is specified as YAML using the block scalar |.
The listing below shows a minimal configuration to enable access for a specific client-certificate:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - example_read_only_role:
+ thumbprint: 00474993fa261b0225f93c5a66aa6fcc... [a-f0-9]{128}
+ dsf-role:
+ - ADMIN
+The list of user roles above contains a single rule-entry example_read_only_role, matching the user via a client certificate SHA-512 thumprint and assigning three DSF roles. Any string can be used as the name for the rule-enty.
Certificate Thumbprints
SHA-512 certificate thumbprints in HEX form [a-f0-9]{128} can be calculated using:
certtool --fingerprint --hash=sha512 --infile=certificate.pem
+Multiple user roles can be specified and all matching roles will be applied to an authenticated users. Use an empty string "" or a single block scalar | character as the value for the configuration parameter DEV_DSF_BPE_SERVER_ROLECONFIG if no roles should be configured.
To apply roles, users can be matched via the thumbprint, email, token-role or token-group properties. A single value or a list of values can be specified.
The property thumbprint can used to specify one or multiple SHA-512 certificate thumbprints. Roles from this rule are applied to the authenticating user if the certificate matches one of the specified thumbprints.
With the properties token-role and token-group role and group names can be specified to match against role and group claims within OAuth 2.0 access tokens.
Two types of roles can be applied to matched users.
DSF roles specified via the dsf-role property define general access to the user interface. Allowed values are:
ADMIN.
The BPE server currently does not support any practionier-roles.
The first example defines a group of DSF administrators. Two client certificates match against this role:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - certificate-admins:
+ thumbprint:
+ - afb68b1d9d47e691b8b3d50fd9848467cada8b1c76f5f4b45f00c9f8432d505361a3ee27805f4aa06799d9ac8dace94b3f1942fce44d84866961259b13be825d
+ - 2441bfddcad97eeb83c8c31fe181b90652787b8b59bf4e569219da7db4429e389479cb7c4a2f311e34217357d594ecad7d58ccfeef2a9e93c6fcf8d98897d88c
+ dsf-role:
+ - ADMIN
+The second example defines a group of DSF administrators by specifying an admin role that gets matched against OAuth 2.0 access tokens:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - token-role-admins:
+ token-role: admin
+ dsf-role:
+ - ADMIN
+The third example allows administrator access and users e-mail addresses to match this role. E-mail addresses from X.509 client certificates and OAuth 2.0 access tokens are matched:
DEV_DSF_BPE_SERVER_ROLECONFIG: |
+ - email-admins:
+ email:
+ - first.user@test.org
+ - second.user@test.org
+ dsf-role:
+ - ADMIN
+The DSF BPE server provides a user interface for administrators. Without any additional configuration the user interface is not accessible with the organizations X.509 client certificate or any other certificate or OpenID Connect authenticated user.
\\nOpenID Connect
\\nTo enable OpenID Connect authentication of local user, see the DSF BPE server OpenID Connect configuration page.
\\nThis wiki entry walks through the steps to add a new FHIR resource to the server
dsf-fhir-server > resources > db copy/past one file and change content to new resource (don't forget to allow permanent deletes like in db.questionnaires.changelog-0.6.0.xml)dsf-fhir-server > resources > db > db.changelog.xml include new generated db changelog file (are in alphabetic order)dsf-fhir-server > resources > db > trigger_functions copy/paste existing functions for insert/update triggers and change content to new resourcedsf-fhir-server > resources > db > db.read_access.changelog.xml include new generated functions for insert/update triggers (are in alphabetic order)dsf-fhir-rest-adapter > java copy/paste existing adapter for json/xml/html and change content to new resourcedsf-fhir-webservice-client > java > FhirWebserviceClientJersey.javaregister generated json/xml (not html) adapters according to existing registrations (are in alphabetic order)dsf-fhir-server > java > dao copy/paste dao interface and change content to new resourcedsf-fhir-server > java > search > parameters copy/paste a search parameter class based on type of the parameter (extends abstract search parameter type) and change content to new resource (existing search parameters can be found on the resources specification website)dsf-fhir-server > java > search > parameters > rev > include copy/paste rev include class and adapt content to resource to be rev includeddsf-fhir-server > java > search > parameters > user copy/paste a search user filter class and adapt content to new resourcedsf-fhir-server > java > dao > jdbc copy/paste dao jdbc class and adapt content (add search user filter and parameter)dsf-fhir-server > java > spring > config > DaoConfig.java register bean by adding a method according to existing resource bean methods (are in alphabetic order) and add it in the `daoProvider()´ methoddsf-fhir-server > java > spring > config > EventConfig.java add the new created bean from the DaoConfig to the MatcherFactory according to existing dao's (are in alphabetic order)dsf-fhir-server > java > dao > provider > DaoProvider.java add a method similar to the existing onedsf-fhir-server > java > dao > provider > DaoProviderImpl.java adapt the class according to the other resource and implement the method similar to the existing onedsf-fhir-rest-adapter > java > service > ReferenceExtractor.java add a method similar to the existing onesdsf-fhir-rest-adapter > java > service > ReferenceExtractorImpl.java implement the method similar to the existing onesdsf-fhir-server > java > authorization copy/paste class and change content to new resourcedsf-fhir-server > java > spring > config > AuthorizationConfig.java register bean by adding a method according to existing resource bean methods (are in alphabetic order) and add it in the authorizationRuleProvider() and the binaryAuthorizationRule() methoddsf-fhir-server > java > webservice > specification copy/paste interface and change content to new resourcedsf-fhir-server > java > webservice > impl copy/paste class and change content to new resourcedsf-fhir-server > java > webservice > jaxrs copy/paste class and change content to new resourcedsf-fhir-server > java > webservice > secure copy/paste class and change content to new resourcedsf-fhir-server > java > webservice > impl > ConformanceServiceImpl add new Resource to list and add Search Parameter created abovedsf-fhir-server > java > spring > config > WebserviceConfig.java register bean by adding a method according to existing resource bean methods (are in alphabetic order)dsf-fhir-server > test-java > dao copy/paste class and change tests to new resourcedsf-fhir-server > test-java > integration copy/paste class and change tests to new resource and above create search parametersThis wiki entry walks through the steps to add a new FHIR resource to the server
\\ndsf-fhir-server > resources > db copy/past one file and change content to new resource (don't forget to allow permanent deletes like in db.questionnaires.changelog-0.6.0.xml)dsf-fhir-server > resources > db > db.changelog.xml include new generated db changelog file (are in alphabetic order)dsf-fhir-server > resources > db > trigger_functions copy/paste existing functions for insert/update triggers and change content to new resourcedsf-fhir-server > resources > db > db.read_access.changelog.xml include new generated functions for insert/update triggers (are in alphabetic order)The Master Patient Index (MPI) client that will be used by the Business Process Engine (BPE) is determined by the property org.highmed.dsf.bpe.mpi.webservice.factory.class and loaded using a service loader, which searches for a class of type MasterPatientIndexClientFactory on startup of the BPE.
The openEHR client that will be used by the Business Process Engine (BPE) is determined by the property org.highmed.dsf.bpe.openehr.webservice.factory.class and loaded using a service loader, which searches for a class of type OpenEhrClientFactory on startup of the BPE.
To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the Gecko Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use your personal client certificate or the client certificate from your DSF BPE, which needs to be added to your webbrowser. For instructions on how to add a client certificate to your browser, please follow here.
Currently, the Allow List Management Tool is only for DSF TEST infrastructure. For production, please write us an E-Mail with your information.
When you have fulfilled all the prerequisites, you can start managing your Allow Lists on the DSF Allow List Management Tool.
At the beginning, a popup will appear where you have to select your certificate. Only then you will have access to the website.
Ideas for improvement?
Have you found an error or is something unclear to you? Then please feel free to contact us on the MII-Zulip Channel or write us at gth-gecko@hs-heilbronn.de. Thank you very much!
Caution
\\nThis is an outdated version of the Allow List Management documentation. Please use the current version, even if you use an outdated DSF version.
\\nYou can read all about the concept of Allow Lists here.
"}');export{T as comp,F as data}; diff --git a/assets/allowList-mgm.html-Bw_tyzsb.js b/assets/allowList-mgm.html-Bw_tyzsb.js new file mode 100644 index 000000000..e72ce1bd2 --- /dev/null +++ b/assets/allowList-mgm.html-Bw_tyzsb.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),m={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},f=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",m,[f,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const S=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),T=JSON.parse('{"path":"/stable/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1691410780000,"updatedTime":1692790324000,"contributors":[{"name":"Maximilian Kurscheidt","email":"maximilian.kurscheidt@hs-heilbronn.de","commits":3},{"name":"Simon Mödinger","email":"smoeding@stud.hs-heilbronn.de","commits":2},{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"stable/maintain/allowList-mgm.md","localizedDate":"August 7, 2023","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{S as comp,T as data}; diff --git a/assets/allowList-mgm.html-CnJ5tXqW.js b/assets/allowList-mgm.html-CnJ5tXqW.js new file mode 100644 index 000000000..46913bb62 --- /dev/null +++ b/assets/allowList-mgm.html-CnJ5tXqW.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),f={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},m=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",f,[m,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const T=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),S=JSON.parse('{"path":"/v1.5.1/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1713374283000,"updatedTime":1713374283000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"v1.5.1/maintain/allowList-mgm.md","localizedDate":"April 17, 2024","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,S as data}; diff --git a/assets/allowList-mgm.html-Da_KiY2h.js b/assets/allowList-mgm.html-Da_KiY2h.js new file mode 100644 index 000000000..aac0422c8 --- /dev/null +++ b/assets/allowList-mgm.html-Da_KiY2h.js @@ -0,0 +1 @@ +import{_ as s}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as o,o as l,c as h,a as e,b as t,d as i,w as c,e as a}from"./app-9qxDwvDG.js";const u={},d=e("div",{class:"hint-container caution"},[e("p",{class:"hint-container-title"},"Caution"),e("p",null,[t("This is an outdated version of the Allow List Management documentation. Please use "),e("a",{href:"/stable//maintain/allowList-mgm"},"the current version"),t(", even if you use an outdated DSF version.")])],-1),m=a('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the Gecko Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use your personal client certificate or the client certificate from your DSF BPE, which needs to be added to your webbrowser. For instructions on how to add a client certificate to your browser, please follow here.
Currently, the Allow List Management Tool is only for DSF TEST infrastructure. For production, please write us an E-Mail with your information.
When you have fulfilled all the prerequisites, you can start managing your Allow Lists on the DSF Allow List Management Tool.
At the beginning, a popup will appear where you have to select your certificate. Only then you will have access to the website.
Ideas for improvement?
Have you found an error or is something unclear to you? Then please feel free to contact us on the MII-Zulip Channel or write us at gth-gecko@hs-heilbronn.de. Thank you very much!
Caution
\\nThis is an outdated version of the Allow List Management documentation. Please use the current version, even if you use an outdated DSF version.
\\nYou can read all about the concept of Allow Lists here.
"}');export{A as comp,F as data}; diff --git a/assets/allowList-mgm.html-KVrCvdTe.js b/assets/allowList-mgm.html-KVrCvdTe.js new file mode 100644 index 000000000..3b815e0ac --- /dev/null +++ b/assets/allowList-mgm.html-KVrCvdTe.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),m={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},f=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",m,[f,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const T=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),S=JSON.parse('{"path":"/v1.3.1/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1698748420000,"updatedTime":1699815669000,"contributors":[{"name":"Hauke Hund","email":"hauke.hund@hs-heilbronn.de","commits":1},{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"v1.3.1/maintain/allowList-mgm.md","localizedDate":"October 31, 2023","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,S as data}; diff --git a/assets/allowList-mgm.html-Kk0AZ49f.js b/assets/allowList-mgm.html-Kk0AZ49f.js new file mode 100644 index 000000000..e0e42ad85 --- /dev/null +++ b/assets/allowList-mgm.html-Kk0AZ49f.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),m={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},f=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",m,[f,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const T=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),S=JSON.parse('{"path":"/v1.4.0/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1702917645000,"updatedTime":1702917645000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"v1.4.0/maintain/allowList-mgm.md","localizedDate":"December 18, 2023","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,S as data}; diff --git a/assets/allowList-mgm.html-YYmWsncl.js b/assets/allowList-mgm.html-YYmWsncl.js new file mode 100644 index 000000000..a51e0d260 --- /dev/null +++ b/assets/allowList-mgm.html-YYmWsncl.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),m={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},f=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",m,[f,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const T=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),S=JSON.parse('{"path":"/v1.3.2/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1701710218000,"updatedTime":1701710218000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"v1.3.2/maintain/allowList-mgm.md","localizedDate":"December 4, 2023","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,S as data}; diff --git a/assets/allowList-mgm.html-bI2ynTVf.js b/assets/allowList-mgm.html-bI2ynTVf.js new file mode 100644 index 000000000..c91eee827 --- /dev/null +++ b/assets/allowList-mgm.html-bI2ynTVf.js @@ -0,0 +1 @@ +import{_ as s}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as l,c as h,a as e,b as t,d as o,w as c,e as n}from"./app-9qxDwvDG.js";const u={},d=n('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the Gecko Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use your personal client certificate or the client certificate from your DSF BPE, which needs to be added to your webbrowser. For instructions on how to add a client certificate to your browser, please follow here.
When you have fulfilled all the prerequisites, you can start managing your Allow Lists respective Allow List Management Tool.
Click here to open the DSF Allow List Management Tool for the Test infrastructure.
Click here to open the DSF Allow List Management Tool for the Production infrastructure.
We use different colors for the DSF Allow List Management Tools in the Test (green) and Production (blue) infastructure.
At the beginning, a popup will appear where you have to select your certificate. Only then you will have access to the website.
Ideas for improvement?
Have you found an error or is something unclear to you? Then please feel free to contact us on the MII-Zulip Channel or write us at gth-gecko@hs-heilbronn.de. Thank you very much!
You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the Gecko Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,A as data}; diff --git a/assets/allowList-mgm.html-dtaS79L_.js b/assets/allowList-mgm.html-dtaS79L_.js new file mode 100644 index 000000000..837432f3f --- /dev/null +++ b/assets/allowList-mgm.html-dtaS79L_.js @@ -0,0 +1 @@ +import{_ as s}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as o,o as l,c as h,a as e,b as t,d as i,w as c,e as a}from"./app-9qxDwvDG.js";const u={},d=e("div",{class:"hint-container caution"},[e("p",{class:"hint-container-title"},"Caution"),e("p",null,[t("This is an outdated version of the Allow List Management documentation. Please use "),e("a",{href:"/stable//maintain/allowList-mgm"},"the current version"),t(", even if you use an outdated DSF version.")])],-1),m=a('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the Gecko Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use your personal client certificate or the client certificate from your DSF BPE, which needs to be added to your webbrowser. For instructions on how to add a client certificate to your browser, please follow here.
Currently, the Allow List Management Tool is only for DSF TEST infrastructure. For production, please write us an E-Mail with your information.
When you have fulfilled all the prerequisites, you can start managing your Allow Lists on the DSF Allow List Management Tool.
At the beginning, a popup will appear where you have to select your certificate. Only then you will have access to the website.
Ideas for improvement?
Have you found an error or is something unclear to you? Then please feel free to contact us on the MII-Zulip Channel or write us at gth-gecko@hs-heilbronn.de. Thank you very much!
Caution
\\nThis is an outdated version of the Allow List Management documentation. Please use the current version, even if you use an outdated DSF version.
\\nYou can read all about the concept of Allow Lists here.
"}');export{T as comp,F as data}; diff --git a/assets/allowList-mgm.html-o1nagjTk.js b/assets/allowList-mgm.html-o1nagjTk.js new file mode 100644 index 000000000..0f23ecf42 --- /dev/null +++ b/assets/allowList-mgm.html-o1nagjTk.js @@ -0,0 +1 @@ +import{_ as n}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as s,c as l,a as e,b as t,d as i,w as c,e as h}from"./app-9qxDwvDG.js";const u={},d=h('To simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
The DSF Allow List management tool uses client certificates for authentication. You can either use a personal client certificate or the client certificate from your DSF BPE, which needs to be added to your web-browsers certificate store.
my-hospital.dehttps://dsf.my-hospital.de/fhirWhen you have fulfilled all the prerequisites, you can start managing your Allow Lists via the environment specific Allow List Management Tool:
',7),f={href:"https://allowlist-test.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},m=e("strong",null,"Test",-1),p={href:"https://allowlist.gecko.hs-heilbronn.de",target:"_blank",rel:"noopener noreferrer"},w=e("strong",null,"Production",-1),g=e("p",null,[t("We use different highlight colors for the DSF Allow List Management Tool: Green for the "),e("strong",null,"Test"),t(" environment and blue for the "),e("strong",null,"Production"),t(" infrastructure. To access the site, you have to authenticate yourself with a client certificate. Your web-browser will show a dialog to choose a valid certificate.")],-1),b=e("div",{class:"hint-container tip"},[e("p",{class:"hint-container-title"},"Ideas for improvement?"),e("p",null,[t("Have you found an error or is something unclear to you? Then please feel free to contact us on the "),e("a",{href:"https://mii.zulipchat.com/#narrow/stream/392426-Data-Sharing-Framework-.28DSF.29"},"MII-Zulip Channel"),t(" or write us at "),e("a",{href:"mailto:dsf-gecko@hs-heilbronn.de"},"gth-gecko@hs-heilbronn.de"),t(". Thank you very much!")])],-1);function v(_,y){const a=r("RouteLink"),o=r("ExternalLinkIcon");return s(),l("div",null,[e("p",null,[t("You can read all about the concept of Allow Lists "),i(a,{to:"/intro/info/allowList.html"},{default:c(()=>[t("in our introduction")]),_:1}),t(".")]),d,e("ul",null,[e("li",null,[e("a",f,[m,t(" infrastructure"),i(o)])]),e("li",null,[e("a",p,[w,t(" infrastructure"),i(o)])])]),g,b])}const T=n(u,[["render",v],["__file","allowList-mgm.html.vue"]]),S=JSON.parse('{"path":"/v1.5.0/maintain/allowList-mgm.html","title":"Allow List Management","lang":"en-US","frontmatter":{"title":"Allow List Management","icon":"share"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"Prerequisites","slug":"prerequisites","link":"#prerequisites","children":[]},{"level":2,"title":"Start here","slug":"start-here","link":"#start-here","children":[]}],"git":{"createdTime":1708419681000,"updatedTime":1708419681000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.15,"words":345},"filePathRelative":"v1.5.0/maintain/allowList-mgm.md","localizedDate":"February 20, 2024","excerpt":"You can read all about the concept of Allow Lists in our introduction.
\\nTo simplify the DSF Allow List Management we have built a portal for administration. The portal is managed by the GECKO Institute at Heilbronn University. You as an DSF administrator can create or update your Allow List information. The information you provide on this portal will be transferred to us and will be used to built Allow List bundles that get distributed to the communication partners of the distributed processes.
"}');export{T as comp,S as data}; diff --git a/assets/allowList.html-DKwCm5QJ.js b/assets/allowList.html-DKwCm5QJ.js new file mode 100644 index 000000000..96eeeaeae --- /dev/null +++ b/assets/allowList.html-DKwCm5QJ.js @@ -0,0 +1 @@ +import{_ as o}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as i,o as n,c as s,a as e,d as l,w as r,b as a,e as c}from"./app-9qxDwvDG.js";const h="/photos/info/allowList/allowList-architecture.png",d={},m=c('The main objective is to allow only authorized organizations to do what "we" allow them to do (e.g. query data).
First, we need a list of organizations that we trust. Secondly, we need a way to ensure that the other party is a member of the parent organization. Thirdly, a list of actions we want to allow the organization to perform is needed. An organization can have different roles in different use cases.
The Allow List consists of Organization-, Endpoint- and OrganisationAffiliation- resources. With these resources the allow list defines communication partners and and parent organizations like research consortia and groups as well as the roles of each organization. Each DSF FHIR server stores their own allow list. To make sure that processes can be executed, parties must allow access via their allow list.
The main objective is to allow only authorized organizations to do what \\"we\\" allow them to do (e.g. query data).
\\nFirst, we need a list of organizations that we trust. Secondly, we need a way to ensure that the other party is a member of the parent organization. Thirdly, a list of actions we want to allow the organization to perform is needed. An organization can have different roles in different use cases.
The Data Sharing Framework implements a distributed business process engine based on the BPMN 2.0 and FHIR R4 standards. Every participating organisation (e.g. ORG. A) runs a FHIR endpoint accessible by other sites and a business process engine (BPE) in the local secured network. Once the DSF has been installed in an organisation, it can be used for multiple use cases.
The following architecture diagram also shows three organisations, each of which has installed the DSF. The FHIR endpoint (green) is located in a demilitarised zone (DMZ) and is accessible from outside for communication with other organisations. It can be compared to a mailbox. The Business Process Engine (BPE - blue) is located in the intranet of an organisation and is responsible for the execution of processes. The metaphor: control centre helps here.
As mentioned above, the externally accessible DSF FHIR server acts as a mailbox for communication. This means that an organisation creates a task resource in its DSF and drops the task resource (letters) into the mailbox of another organisation, requesting that something happen. Task resources have been explained in more detail in the section Basics and Standards.
It is important to understand that the DSF FHIR server is not used for persisting medical data.
The BPE located in the secure internal network executes the processes (BPMN/Java). The BPE is deployed in the internal network and has access to the local systems, such as the organisation's own FHIR server, on which medical data is stored. These FHIR servers are not to be confused with the DSF FHIR server, on which no medical data is persisted.
Different processes can be executed simultaneously. For this, only a new process plugin file has to be added and configured. More about this in the Process Plugins.
The deployment of the architecture is flexible. The organisations can be deployed as a star schema (left) or as a mesh schema (right). In the Star schema (left), all Data Integration Centres (DIC) are connected to a central node (CRR - Central Research Repository), which transfers the information to all nodes (DIC). For security reasons, a data transfer hub (DTH) is connected upstream, which provides additional security so that the medical data is never transferred together with the authenticating data.
In the mesh scheme (right), the nodes (DIC) are all directly connected to each other and the information is transferred from node to node. Here in the FDPG (Forschungsdatenportal - Research Data Portal), the data can then be accessed for research purposes. More about this here.
You can find more information about the network setup here
',19),g=[m];function f(b,y){return t(),i("div",null,g)}const F=e(u,[["render",f],["__file","architecture.html.vue"]]),_=JSON.parse('{"path":"/intro/info/architecture.html","title":"Architecture","lang":"en-US","frontmatter":{"title":"Architecture","icon":"structure"},"headers":[{"level":2,"title":"DSF FHIR Server 📫","slug":"dsf-fhir-server","link":"#dsf-fhir-server","children":[]},{"level":2,"title":"Business Process Engine (BPE)","slug":"business-process-engine-bpe","link":"#business-process-engine-bpe","children":[]},{"level":2,"title":"Flexible Deployment","slug":"flexible-deployment","link":"#flexible-deployment","children":[]},{"level":2,"title":"Network Setup & Additional Reverse Proxy in external DMZ","slug":"network-setup-additional-reverse-proxy-in-external-dmz","link":"#network-setup-additional-reverse-proxy-in-external-dmz","children":[]}],"git":{"createdTime":1690473388000,"updatedTime":1690822842000,"contributors":[{"name":"Simon Mödinger","email":"smoeding@stud.hs-heilbronn.de","commits":3}]},"readingTime":{"minutes":1.66,"words":498},"filePathRelative":"intro/info/architecture.md","localizedDate":"July 27, 2023","excerpt":"The Data Sharing Framework implements a distributed business process engine based on the BPMN 2.0 and FHIR R4 standards. Every participating organisation (e.g. ORG. A) runs a FHIR endpoint accessible by other sites and a business process engine (BPE) in the local secured network. Once the DSF has been installed in an organisation, it can be used for multiple use cases.
"}');export{F as comp,_ as data}; diff --git a/assets/authentication.html-B4CwiFHl.js b/assets/authentication.html-B4CwiFHl.js new file mode 100644 index 000000000..28b025222 --- /dev/null +++ b/assets/authentication.html-B4CwiFHl.js @@ -0,0 +1 @@ +import{_ as r}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as a,o as s,c as o,a as t,b as e,d as n,e as l}from"./app-9qxDwvDG.js";const c={},d={href:"https://www.pki.dfn.de/ueberblick-dfn-pki/",target:"_blank",rel:"noopener noreferrer"},h={href:"https://www.tmf-ev.de",target:"_blank",rel:"noopener noreferrer"},f={href:"https://doku.tid.dfn.de/de:dfnpki:start",target:"_blank",rel:"noopener noreferrer"},u={href:"https://www.pki.dfn.de/fileadmin/PKI/anleitungen/DFN-PKI-Zertifikatprofile_Global.pdf",target:"_blank",rel:"noopener noreferrer"},p=l('Authentication of organizations within the DSF is handled by the use of X.509 client and server certificates. Currently the certificate authorities run by DFN-PKI Global G2, D-Trust via TMF e.V. and GÉANT TCS via DFN are supported. All participating organizations are entered in a distributed and synchronized allow-list of valid organizations and certificates.
"}');export{_ as comp,F as data}; diff --git a/assets/basics.html-uTe6ng_s.js b/assets/basics.html-uTe6ng_s.js new file mode 100644 index 000000000..ba215458c --- /dev/null +++ b/assets/basics.html-uTe6ng_s.js @@ -0,0 +1 @@ +import{_ as i}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as o,o as r,c as d,a as e,b as t,d as a,e as s}from"./app-9qxDwvDG.js";const h="/photos/info/basics/interoperability.png",l="/photos/info/basics/bpmn1.png",c="/photos/info/basics/bpmn2.png",m={},p={href:"https://www.hl7.org/fhir/",target:"_blank",rel:"noopener noreferrer"},f={href:"https://www.bpmn.org/",target:"_blank",rel:"noopener noreferrer"},u=s('Interoperability is the ability of different systems to work together as seamlessly as possible. We can divide interoperability into four levels.
On the one hand we use FHIR because of the mentioned benefits. On the other hand FHIR fits great with BPMN and these two in combination are a great fit for what we do:
Execute distributed data sharing Processes.
We do not need all 150 FHIR resources. The following FHIR resources are the ones we need and have implemented: ActivityDefinition, Binary, Bundle, CodeSystem, DocumentReference, Endpoint, Group, Library, Measure, MeasureReport, NamingSystem, Organization, Questionnaire, QuestionnaireResponse, ResearchStudy, StructureDefinition, Subscription, Task and ValueSet.
Don't worry, it is not important to understand them all now. But to understand why we use FHIR and BPMN, it is important to look at the ActivityDefinition and TaskResources on the FHIR side and the Message Events on the BPMN side.
In the following picture you can see parts of BPMN. These Message Events enable the communication between different organizations. Every time there is a Message Event between two business processes, there is a corresponding TaskResource on the FHIR side. When one organization sends a message for example “do some work” to another organization or when we send a message to ourselves to start or continue a process, we do this by creating a FHIR TaskResource with the status “requested”. After that the Business Process Engine starts the work and the status switches to “in-progress” and if the work is done to “completed” or if there is a problem to “failed”.
The ActivityDefinition is needed to publish what can be done in an instance. That means the ActivityDefinition contains the process description with the authorisation who is allowed to send a message.
Here you can find some basic information about interoperability and the standards were using within the DSF before we go into details about the architecture. Here we only describe how the standards (FHIR and BPMN) are used within the DSF. If you want to gain a deeper knowledge of the standards, we recommend visiting these websites: HL7 FHIR and BPMN
"}');export{k as comp,B as data}; diff --git a/assets/bpe.html-B8bXr636.js b/assets/bpe.html-B8bXr636.js new file mode 100644 index 000000000..f81a82b52 --- /dev/null +++ b/assets/bpe.html-B8bXr636.js @@ -0,0 +1 @@ +import{_ as e}from"./plugin-vue_export-helper-DlAUqK2U.js";import{o as s,c as r,e as i}from"./app-9qxDwvDG.js";const t={},o=i('Please also check common parameters for additional configuration options.
truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_server_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhirhospital.com-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse-1 means infinite number of retries-15000processfoo.bar, test.com:8080http://proxy.foo:8080Please also check common parameters for additional configuration options.
\\ntruefalsePrerequisite: Java 11, Maven 3.6, Docker
mvn install
+Prerequisite: Java 11, Maven 3.6, PostgreSQL 11
`,5),u=r(`mvn install
+CREATE USER liquibase_user WITH LOGIN NOSUPERUSER INHERIT CREATEDB CREATEROLE NOREPLICATION
+PASSWORD 'fLp6ZSd5QrMAkGZMjxqXjmcWrTfa3Dn8fA57h92Y';
+CREATE DATABASE bpe OWNER liquibase_user;
+CREATE DATABASE fhir OWNER liquibase_user;
+mvn install
+docker-build.bat
+docker-build.sh
+dev:
+docker-compose up
+
+prod:
+docker-compose -f docker-compose.yml -f docker-compose.prod.yml up
+dev:
+docker-compose up
+
+prod:
+docker-compose -f docker-compose.yml -f docker-compose.prod.yml up
+docker network ls -q | xargs docker network rmdocker-compose down -v
+Each process contains an ExampleStarter which creates FHIR resources and sends them to a designated FHIR-Endpoint in order to start the corresponding process in the Manual Integration Test Setup. The same client certificate can be used as above: .../highmed-dsf/dsf-tools/dsf-tools-test-data-generator/cert/Webbrowser_Test_User/Webbrowser_Test_User_certificate.p12 (Password: password).
The following configuration is needed:
DSF_CLIENT_CERTIFICATE_PATH or args[0] has to be setDSF_CLIENT_CERTIFICATE_PASSWORD or args[1] has to be setPrerequisite: Java 11, Maven 3.6, Docker
\\nmvn install\\nPrerequisite: Java 11, Maven 3.6, PostgreSQL 11
"}');export{C as comp,R as data}; diff --git a/assets/changingBpmnProcesses.html-BqtqsNSb.js b/assets/changingBpmnProcesses.html-BqtqsNSb.js new file mode 100644 index 000000000..a449a9280 --- /dev/null +++ b/assets/changingBpmnProcesses.html-BqtqsNSb.js @@ -0,0 +1 @@ +import{_ as e}from"./plugin-vue_export-helper-DlAUqK2U.js";import{o as t,c as o,e as n}from"./app-9qxDwvDG.js";const s={},i=n("
DEPRECATED SINCE VERSION 0.4.0
A service task of a process integrated in the framework can be overwritten using the plugin interface. This means that entire processes do not have to be replaced when only individual steps need adaption. An example can be found in the module dsf-bpe > dsf-bpe-process-plugin-example > dsf-bpe-process-service-overwrite.
A plugin has as its only dependency the process module which contains the service task to be overwritten.
For a plugin replacing one service task, two new files must be generated:
doExecute(DelegateExecution execution).@Primary.\\n\\n\\n
DEPRECATED SINCE VERSION 0.4.0
A service task of a process integrated in the framework can be overwritten using the plugin interface. This means that entire processes do not have to be replaced when only individual steps need adaption. An example can be found in the module dsf-bpe > dsf-bpe-process-plugin-example > dsf-bpe-process-service-overwrite.
HiGHmed DSF code-style configurations for Eclipse and IntelliJ IDEA can be found here:
\\nPull Requests are only approved, if the code is formatted according to the code-style configurations above. To format the code with maven before pushing to GitHub, use mvn compile -Pformat-and-sort.
Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
Start now by visiting our contribution pages. Every line of code helps us build a stronger and more versatile DSF.
You can import our code style for your specific IDE:
',7),d={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/eclipse-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},u=e("code",null,"Java",-1),p=e("code",null,"Code style",-1),m=e("code",null,"Formatter",-1),g=e("code",null,"Import",-1),f={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/intellij-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},b=e("code",null,"Editor",-1),_=e("code",null,"Code style",-1),v=e("code",null,"Java",-1),w=e("code",null,"import scheme",-1),y=e("code",null,"IntelliJ",-1),k=e("p",null,[t("Pull requests will only be approved if the code is formatted according to the code style configurations above. To format the code with maven before pushing to GitHub, use "),e("code",null,"mvn compile -Pformat-and-sort"),t(".")],-1),x=e("h3",{id:"branching-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#branching-strategy"},[e("span",null,"Branching strategy")])],-1),S={href:"https://www.atlassian.com/de/git/tutorials/comparing-workflows/gitflow-workflow",target:"_blank",rel:"noopener noreferrer"},D=r('Notice that only the first two elements listed are actual branches. The other elements are containers to hold all branches belonging to that category.
The following ruleset is applied to name branches:
issue/<issue-number>_<issue-name>hotfix/<version>release/<version>This chapter lists all important requirements to get the project buildable and running properly.
This project uses Java JDK 17, so make sure you have it installed on your system.
We follow Martin Fowler's method for managing pull requests. This approach categorizes pull requests based on the level of trust and experience of the contributor, as well as the impact of the changes. Here's how we apply it:
Ship: For our most trusted contributors with a proven track record. These members can merge their pull requests without prior review, typically for minor or highly confident changes.
Show: This level is for trusted contributors who need some oversight, as well as for experienced developers who want to demonstrate how certain changes should be made in the future. They create pull requests and show their work to the team.
Ask: New or less experienced contributors, as well as those submitting more complex changes, fall into this category. They are required to ask for feedback and approval before their changes can be merged, ensuring thorough review and quality control.
This method helps us maintain a balance between code quality and efficient development, recognizing the varying levels of expertise among our contributors.
',4),V={href:"https://martinfowler.com/articles/ship-show-ask.html",target:"_blank",rel:"noopener noreferrer"},O=e("h2",{id:"data-security-in-dsf-development",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#data-security-in-dsf-development"},[e("span",null,"Data Security in DSF Development")])],-1),R=e("p",null,"The DSF (Data Sharing Framework) and its process plugins are frequently used to transmit sensitive personal data. To prevent the release of personal data during development, please adhere to the following guidelines:",-1),Y=e("ul",null,[e("li",null,[e("strong",null,"No development with real personal data:"),t(" Always use anonymized or synthetic data for development purposes.")]),e("li",null,[e("strong",null,"No personal data in repositories:"),t(" Ensure no personal data is present in local and remote repositories intended for publication, not even temporarily.")]),e("li",null,[e("strong",null,"Review all log files:"),t(" Before using log files in issues, examples, etc., thoroughly review them to ensure no personal and sensitive data is included.")])],-1);function A(H,L){const n=s("ExternalLinkIcon");return l(),a("div",null,[h,e("ul",null,[e("li",null,[e("a",d,[t("Eclipse"),o(n)]),t(". Open your preferences, click on "),u,t(", "),p,t(", "),m,t(", "),g,t(" and select the downloaded file.")]),e("li",null,[e("a",f,[t("IntelliJ"),o(n)]),t(". Open your settings, click on "),b,t(", "),_,t(", "),v,t(", the settings icon, "),w,t(", "),y,t(" and select the downloaded file.")])]),k,x,e("p",null,[e("a",S,[t("Git Flow"),o(n)]),t(" is used as this project's branching strategy. Therefore, you will find the following structure:")]),D,e("p",null,[e("a",F,[t("Docker"),o(n)]),t(" is used in this project to test database functionality and to run more complex test-setups.")]),q,e("p",null,[t("The project relies on "),e("a",T,[t("Maven"),o(n)]),t(" as its management tool."),j,C,t(" When building the project you might encounter the following error:"),B,J,t(),e("a",I,[t("GPG"),o(n)]),t(" is used to sign artifacts for public release. Since this does not concern contributors, you may skip this step in the maven build process with "),N,t(".")]),z,e("ol",null,[E,G,P,e("li",null,[t("If your changes are production-ready, create a "),e("a",W,[t("pull request"),o(n)]),t(".")])]),M,e("p",null,[t("For more information on Fowler's approach, visit "),e("a",V,[t("Martin Fowler's article on Pull Requests"),o(n)]),t(".")]),O,R,Y])}const Q=i(c,[["render",A],["__file","code.html.vue"]]),X=JSON.parse('{"path":"/v1.4.0/contribute/code.html","title":"Contribute code","lang":"en-US","frontmatter":{"title":"Contribute code","icon":"info"},"headers":[{"level":3,"title":"Benefits of Contributing:","slug":"benefits-of-contributing","link":"#benefits-of-contributing","children":[]},{"level":2,"title":"General","slug":"general","link":"#general","children":[{"level":3,"title":"Code style","slug":"code-style","link":"#code-style","children":[]},{"level":3,"title":"Branching strategy","slug":"branching-strategy","link":"#branching-strategy","children":[]}]},{"level":2,"title":"Setting up the project","slug":"setting-up-the-project","link":"#setting-up-the-project","children":[{"level":3,"title":"Java","slug":"java","link":"#java","children":[]},{"level":3,"title":"Docker","slug":"docker","link":"#docker","children":[]},{"level":3,"title":"Maven","slug":"maven","link":"#maven","children":[]}]},{"level":2,"title":"Workflow","slug":"workflow","link":"#workflow","children":[{"level":3,"title":"Pull request process","slug":"pull-request-process","link":"#pull-request-process","children":[]}]},{"level":2,"title":"Data Security in DSF Development","slug":"data-security-in-dsf-development","link":"#data-security-in-dsf-development","children":[]}],"git":{"createdTime":1706191215000,"updatedTime":1706191215000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":2.51,"words":754},"filePathRelative":"v1.4.0/contribute/code.md","localizedDate":"January 25, 2024","excerpt":"Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
\\nYour code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
Start now by visiting our contribution pages. Every line of code helps us build a stronger and more versatile DSF.
You can import our code style for your specific IDE:
',7),d={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/eclipse-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},u=e("code",null,"Java",-1),p=e("code",null,"Code style",-1),m=e("code",null,"Formatter",-1),g=e("code",null,"Import",-1),f={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/intellij-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},b=e("code",null,"Editor",-1),_=e("code",null,"Code style",-1),v=e("code",null,"Java",-1),w=e("code",null,"import scheme",-1),y=e("code",null,"IntelliJ",-1),k=e("p",null,[t("Pull requests will only be approved if the code is formatted according to the code style configurations above. To format the code with maven before pushing to GitHub, use "),e("code",null,"mvn compile -Pformat-and-sort"),t(".")],-1),x=e("h3",{id:"branching-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#branching-strategy"},[e("span",null,"Branching strategy")])],-1),S={href:"https://www.atlassian.com/de/git/tutorials/comparing-workflows/gitflow-workflow",target:"_blank",rel:"noopener noreferrer"},D=r('Notice that only the first two elements listed are actual branches. The other elements are containers to hold all branches belonging to that category.
The following ruleset is applied to name branches:
issue/<issue-number>_<issue-name>hotfix/<version>release/<version>This chapter lists all important requirements to get the project buildable and running properly.
This project uses Java JDK 17, so make sure you have it installed on your system.
We follow Martin Fowler's method for managing pull requests. This approach categorizes pull requests based on the level of trust and experience of the contributor, as well as the impact of the changes. Here's how we apply it:
Ship: For our most trusted contributors with a proven track record. These members can merge their pull requests without prior review, typically for minor or highly confident changes.
Show: This level is for trusted contributors who need some oversight, as well as for experienced developers who want to demonstrate how certain changes should be made in the future. They create pull requests and show their work to the team.
Ask: New or less experienced contributors, as well as those submitting more complex changes, fall into this category. They are required to ask for feedback and approval before their changes can be merged, ensuring thorough review and quality control.
This method helps us maintain a balance between code quality and efficient development, recognizing the varying levels of expertise among our contributors.
',4),V={href:"https://martinfowler.com/articles/ship-show-ask.html",target:"_blank",rel:"noopener noreferrer"},A=e("h2",{id:"data-security-in-dsf-development",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#data-security-in-dsf-development"},[e("span",null,"Data Security in DSF Development")])],-1),O=e("p",null,"The DSF (Data Sharing Framework) and its process plugins are frequently used to transmit sensitive personal data. To prevent the release of personal data during development, please adhere to the following guidelines:",-1),R=e("ul",null,[e("li",null,[e("strong",null,"No development with real personal data:"),t(" Always use anonymized or synthetic data for development purposes.")]),e("li",null,[e("strong",null,"No personal data in repositories:"),t(" Ensure no personal data is present in local and remote repositories intended for publication, not even temporarily.")]),e("li",null,[e("strong",null,"Review all log files:"),t(" Before using log files in issues, examples, etc., thoroughly review them to ensure no personal and sensitive data is included.")])],-1);function Y(H,L){const n=s("ExternalLinkIcon");return l(),a("div",null,[h,e("ul",null,[e("li",null,[e("a",d,[t("Eclipse"),o(n)]),t(". Open your preferences, click on "),u,t(", "),p,t(", "),m,t(", "),g,t(" and select the downloaded file.")]),e("li",null,[e("a",f,[t("IntelliJ"),o(n)]),t(". Open your settings, click on "),b,t(", "),_,t(", "),v,t(", the settings icon, "),w,t(", "),y,t(" and select the downloaded file.")])]),k,x,e("p",null,[e("a",S,[t("Git Flow"),o(n)]),t(" is used as this project's branching strategy. Therefore, you will find the following structure:")]),D,e("p",null,[e("a",F,[t("Docker"),o(n)]),t(" is used in this project to test database functionality and to run more complex test-setups.")]),q,e("p",null,[t("The project relies on "),e("a",T,[t("Maven"),o(n)]),t(" as its management tool."),j,C,t(" When building the project you might encounter the following error:"),B,I,t(),e("a",J,[t("GPG"),o(n)]),t(" is used to sign artifacts for public release. Since this does not concern contributors, you may skip this step in the maven build process with "),N,t(".")]),z,e("ol",null,[E,G,P,e("li",null,[t("If your changes are production-ready, create a "),e("a",W,[t("pull request"),o(n)]),t(".")])]),M,e("p",null,[t("For more information on Fowler's approach, visit "),e("a",V,[t("Martin Fowler's article on Pull Requests"),o(n)]),t(".")]),A,O,R])}const Q=i(c,[["render",Y],["__file","code.html.vue"]]),X=JSON.parse('{"path":"/v1.5.1/contribute/code.html","title":"Contribute code","lang":"en-US","frontmatter":{"title":"Contribute code","icon":"info"},"headers":[{"level":3,"title":"Benefits of Contributing:","slug":"benefits-of-contributing","link":"#benefits-of-contributing","children":[]},{"level":2,"title":"General","slug":"general","link":"#general","children":[{"level":3,"title":"Code style","slug":"code-style","link":"#code-style","children":[]},{"level":3,"title":"Branching strategy","slug":"branching-strategy","link":"#branching-strategy","children":[]}]},{"level":2,"title":"Setting up the project","slug":"setting-up-the-project","link":"#setting-up-the-project","children":[{"level":3,"title":"Java","slug":"java","link":"#java","children":[]},{"level":3,"title":"Docker","slug":"docker","link":"#docker","children":[]},{"level":3,"title":"Maven","slug":"maven","link":"#maven","children":[]}]},{"level":2,"title":"Workflow","slug":"workflow","link":"#workflow","children":[{"level":3,"title":"Pull request process","slug":"pull-request-process","link":"#pull-request-process","children":[]}]},{"level":2,"title":"Data Security in DSF Development","slug":"data-security-in-dsf-development","link":"#data-security-in-dsf-development","children":[]}],"git":{"createdTime":1713374283000,"updatedTime":1713374283000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":2.51,"words":754},"filePathRelative":"v1.5.1/contribute/code.md","localizedDate":"April 17, 2024","excerpt":"Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
\\nYour code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
Start now by visiting our contribution pages. Every line of code helps us build a stronger and more versatile DSF.
You can import our code style for your specific IDE:
',7),d={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/eclipse-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},u=e("code",null,"Java",-1),p=e("code",null,"Code style",-1),g=e("code",null,"Formatter",-1),m=e("code",null,"Import",-1),f={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/intellij-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},b=e("code",null,"Editor",-1),_=e("code",null,"Code style",-1),v=e("code",null,"Java",-1),y=e("code",null,"import scheme",-1),w=e("code",null,"IntelliJ",-1),k=e("p",null,[t("Pull requests will only be approved if the code is formatted according to the code style configurations above. To format the code with maven before pushing to GitHub, use "),e("code",null,"mvn compile -Pformat-and-sort"),t(".")],-1),x=e("h3",{id:"branching-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#branching-strategy"},[e("span",null,"Branching strategy")])],-1),S={href:"https://www.atlassian.com/de/git/tutorials/comparing-workflows/gitflow-workflow",target:"_blank",rel:"noopener noreferrer"},D=r('Notice that only the first two elements listed are actual branches. The other elements are containers to hold all branches belonging to that category.
The following ruleset is applied to name branches:
issue/<issue-number>_<issue-name>hotfix/<version>release/<version>This chapter lists all important requirements to get the project buildable and running properly.
This project uses Java JDK 17, so make sure you have it installed on your system.
We follow Martin Fowler's method for managing pull requests. This approach categorizes pull requests based on the level of trust and experience of the contributor, as well as the impact of the changes. Here's how we apply it:
Ship: For our most trusted contributors with a proven track record. These members can merge their pull requests without prior review, typically for minor or highly confident changes.
Show: This level is for trusted contributors who need some oversight, as well as for experienced developers who want to demonstrate how certain changes should be made in the future. They create pull requests and show their work to the team.
Ask: New or less experienced contributors, as well as those submitting more complex changes, fall into this category. They are required to ask for feedback and approval before their changes can be merged, ensuring thorough review and quality control.
This method helps us maintain a balance between code quality and efficient development, recognizing the varying levels of expertise among our contributors.
',4),V={href:"https://martinfowler.com/articles/ship-show-ask.html",target:"_blank",rel:"noopener noreferrer"},O=e("h2",{id:"data-security-in-dsf-development",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#data-security-in-dsf-development"},[e("span",null,"Data Security in DSF Development")])],-1),R=e("p",null,"The DSF (Data Sharing Framework) and its process plugins are frequently used to transmit sensitive personal data. To prevent the release of personal data during development, please adhere to the following guidelines:",-1),Y=e("ul",null,[e("li",null,[e("strong",null,"No development with real personal data:"),t(" Always use anonymized or synthetic data for development purposes.")]),e("li",null,[e("strong",null,"No personal data in repositories:"),t(" Ensure no personal data is present in local and remote repositories intended for publication, not even temporarily.")]),e("li",null,[e("strong",null,"Review all log files:"),t(" Before using log files in issues, examples, etc., thoroughly review them to ensure no personal and sensitive data is included.")])],-1);function A(H,L){const n=s("ExternalLinkIcon");return l(),a("div",null,[h,e("ul",null,[e("li",null,[e("a",d,[t("Eclipse"),o(n)]),t(". Open your preferences, click on "),u,t(", "),p,t(", "),g,t(", "),m,t(" and select the downloaded file.")]),e("li",null,[e("a",f,[t("IntelliJ"),o(n)]),t(". Open your settings, click on "),b,t(", "),_,t(", "),v,t(", the settings icon, "),y,t(", "),w,t(" and select the downloaded file.")])]),k,x,e("p",null,[e("a",S,[t("Git Flow"),o(n)]),t(" is used as this project's branching strategy. Therefore, you will find the following structure:")]),D,e("p",null,[e("a",F,[t("Docker"),o(n)]),t(" is used in this project to test database functionality and to run more complex test-setups.")]),q,e("p",null,[t("The project relies on "),e("a",T,[t("Maven"),o(n)]),t(" as its management tool."),j,C,t(" When building the project you might encounter the following error:"),B,I,t(),e("a",J,[t("GPG"),o(n)]),t(" is used to sign artifacts for public release. Since this does not concern contributors, you may skip this step in the maven build process with "),N,t(".")]),E,e("ol",null,[G,P,W,e("li",null,[t("If your changes are production-ready, create a "),e("a",z,[t("pull request"),o(n)]),t(".")])]),M,e("p",null,[t("For more information on Fowler's approach, visit "),e("a",V,[t("Martin Fowler's article on Pull Requests"),o(n)]),t(".")]),O,R,Y])}const Q=i(c,[["render",A],["__file","code.html.vue"]]),X=JSON.parse('{"path":"/stable/contribute/code.html","title":"Contribute code","lang":"en-US","frontmatter":{"title":"Contribute code","icon":"info"},"headers":[{"level":3,"title":"Benefits of Contributing:","slug":"benefits-of-contributing","link":"#benefits-of-contributing","children":[]},{"level":2,"title":"General","slug":"general","link":"#general","children":[{"level":3,"title":"Code style","slug":"code-style","link":"#code-style","children":[]},{"level":3,"title":"Branching strategy","slug":"branching-strategy","link":"#branching-strategy","children":[]}]},{"level":2,"title":"Setting up the project","slug":"setting-up-the-project","link":"#setting-up-the-project","children":[{"level":3,"title":"Java","slug":"java","link":"#java","children":[]},{"level":3,"title":"Docker","slug":"docker","link":"#docker","children":[]},{"level":3,"title":"Maven","slug":"maven","link":"#maven","children":[]}]},{"level":2,"title":"Workflow","slug":"workflow","link":"#workflow","children":[{"level":3,"title":"Pull request process","slug":"pull-request-process","link":"#pull-request-process","children":[]}]},{"level":2,"title":"Data Security in DSF Development","slug":"data-security-in-dsf-development","link":"#data-security-in-dsf-development","children":[]}],"git":{"createdTime":null,"updatedTime":null,"contributors":[]},"readingTime":{"minutes":2.51,"words":754},"filePathRelative":"stable/contribute/code.md","excerpt":"Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
\\nYour code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
Start now by visiting our contribution pages. Every line of code helps us build a stronger and more versatile DSF.
You can import our code style for your specific IDE:
',7),d={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/eclipse-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},u=e("code",null,"Java",-1),p=e("code",null,"Code style",-1),m=e("code",null,"Formatter",-1),g=e("code",null,"Import",-1),f={href:"https://github.com/datasharingframework/dsf/blob/main/src/main/resources/intellij-formatter-config.xml",target:"_blank",rel:"noopener noreferrer"},b=e("code",null,"Editor",-1),_=e("code",null,"Code style",-1),v=e("code",null,"Java",-1),w=e("code",null,"import scheme",-1),y=e("code",null,"IntelliJ",-1),k=e("p",null,[t("Pull requests will only be approved if the code is formatted according to the code style configurations above. To format the code with maven before pushing to GitHub, use "),e("code",null,"mvn compile -Pformat-and-sort"),t(".")],-1),x=e("h3",{id:"branching-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#branching-strategy"},[e("span",null,"Branching strategy")])],-1),S={href:"https://www.atlassian.com/de/git/tutorials/comparing-workflows/gitflow-workflow",target:"_blank",rel:"noopener noreferrer"},D=r('Notice that only the first two elements listed are actual branches. The other elements are containers to hold all branches belonging to that category.
The following ruleset is applied to name branches:
issue/<issue-number>_<issue-name>hotfix/<version>release/<version>This chapter lists all important requirements to get the project buildable and running properly.
This project uses Java JDK 17, so make sure you have it installed on your system.
We follow Martin Fowler's method for managing pull requests. This approach categorizes pull requests based on the level of trust and experience of the contributor, as well as the impact of the changes. Here's how we apply it:
Ship: For our most trusted contributors with a proven track record. These members can merge their pull requests without prior review, typically for minor or highly confident changes.
Show: This level is for trusted contributors who need some oversight, as well as for experienced developers who want to demonstrate how certain changes should be made in the future. They create pull requests and show their work to the team.
Ask: New or less experienced contributors, as well as those submitting more complex changes, fall into this category. They are required to ask for feedback and approval before their changes can be merged, ensuring thorough review and quality control.
This method helps us maintain a balance between code quality and efficient development, recognizing the varying levels of expertise among our contributors.
',4),V={href:"https://martinfowler.com/articles/ship-show-ask.html",target:"_blank",rel:"noopener noreferrer"},O=e("h2",{id:"data-security-in-dsf-development",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#data-security-in-dsf-development"},[e("span",null,"Data Security in DSF Development")])],-1),R=e("p",null,"The DSF (Data Sharing Framework) and its process plugins are frequently used to transmit sensitive personal data. To prevent the release of personal data during development, please adhere to the following guidelines:",-1),Y=e("ul",null,[e("li",null,[e("strong",null,"No development with real personal data:"),t(" Always use anonymized or synthetic data for development purposes.")]),e("li",null,[e("strong",null,"No personal data in repositories:"),t(" Ensure no personal data is present in local and remote repositories intended for publication, not even temporarily.")]),e("li",null,[e("strong",null,"Review all log files:"),t(" Before using log files in issues, examples, etc., thoroughly review them to ensure no personal and sensitive data is included.")])],-1);function A(H,L){const n=s("ExternalLinkIcon");return l(),a("div",null,[h,e("ul",null,[e("li",null,[e("a",d,[t("Eclipse"),o(n)]),t(". Open your preferences, click on "),u,t(", "),p,t(", "),m,t(", "),g,t(" and select the downloaded file.")]),e("li",null,[e("a",f,[t("IntelliJ"),o(n)]),t(". Open your settings, click on "),b,t(", "),_,t(", "),v,t(", the settings icon, "),w,t(", "),y,t(" and select the downloaded file.")])]),k,x,e("p",null,[e("a",S,[t("Git Flow"),o(n)]),t(" is used as this project's branching strategy. Therefore, you will find the following structure:")]),D,e("p",null,[e("a",F,[t("Docker"),o(n)]),t(" is used in this project to test database functionality and to run more complex test-setups.")]),q,e("p",null,[t("The project relies on "),e("a",T,[t("Maven"),o(n)]),t(" as its management tool."),j,C,t(" When building the project you might encounter the following error:"),B,I,t(),e("a",J,[t("GPG"),o(n)]),t(" is used to sign artifacts for public release. Since this does not concern contributors, you may skip this step in the maven build process with "),N,t(".")]),z,e("ol",null,[E,G,P,e("li",null,[t("If your changes are production-ready, create a "),e("a",W,[t("pull request"),o(n)]),t(".")])]),M,e("p",null,[t("For more information on Fowler's approach, visit "),e("a",V,[t("Martin Fowler's article on Pull Requests"),o(n)]),t(".")]),O,R,Y])}const Q=i(c,[["render",A],["__file","code.html.vue"]]),X=JSON.parse('{"path":"/v1.5.0/contribute/code.html","title":"Contribute code","lang":"en-US","frontmatter":{"title":"Contribute code","icon":"info"},"headers":[{"level":3,"title":"Benefits of Contributing:","slug":"benefits-of-contributing","link":"#benefits-of-contributing","children":[]},{"level":2,"title":"General","slug":"general","link":"#general","children":[{"level":3,"title":"Code style","slug":"code-style","link":"#code-style","children":[]},{"level":3,"title":"Branching strategy","slug":"branching-strategy","link":"#branching-strategy","children":[]}]},{"level":2,"title":"Setting up the project","slug":"setting-up-the-project","link":"#setting-up-the-project","children":[{"level":3,"title":"Java","slug":"java","link":"#java","children":[]},{"level":3,"title":"Docker","slug":"docker","link":"#docker","children":[]},{"level":3,"title":"Maven","slug":"maven","link":"#maven","children":[]}]},{"level":2,"title":"Workflow","slug":"workflow","link":"#workflow","children":[{"level":3,"title":"Pull request process","slug":"pull-request-process","link":"#pull-request-process","children":[]}]},{"level":2,"title":"Data Security in DSF Development","slug":"data-security-in-dsf-development","link":"#data-security-in-dsf-development","children":[]}],"git":{"createdTime":1708419681000,"updatedTime":1708419681000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":2.51,"words":754},"filePathRelative":"v1.5.0/contribute/code.md","localizedDate":"February 20, 2024","excerpt":"Your code can make a difference for the Data Sharing Framework (DSF). We invite all users to share their code, tests, scripts and improvement ideas. Contributions of any size enhance the DSF and support the data sharing framework community.
\\n0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.1100000.0.0.0127.0.0.1Please note: Additional parameters (not listed here) are used to configure process plugins.
org.highmed.consent.client.stub.ConsentClientStubFactory/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.passwordhttp://proxy.foo:8080200060000truefalsehttp://proxy.foo:8080http://proxy.foo:8080500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhirhospital.com-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalseorg.highmed.mpi.client.stub.MasterPatientIndexClientStubFactoryorg.highmed.openehr.client.stub.OpenEhrClientStubFactory-1 means infinite number of retries-15000processorg.highmed.pseudonymization.client.stub.PseudonymizationClientStubFactoryPlease note: Additional parameters (not listed here) are used to configure process plugins.
\\norg.highmed.consent.client.stub.ConsentClientStubFactoryPlease note: Additional parameters (not listed here) are used to define elements of the external FHIR bundle.
/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.passwordhttp://proxy.foo:8080200010000/run/secrets/app_client_trust_certificates.pemtruefalse/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.com20Please note: Additional parameters (not listed here) are used to define elements of the external FHIR bundle.
\\n/run/secrets/app_client_certificate.pemapp, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 secondsSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_usertrue.falsetrue.falsetrue.falsehttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1https://foo.bar/bpehttpsfalsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.10.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_server_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1foo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pemapp, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 secondsSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClient optional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./bpeSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./bpeSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1https://foo.bar/bpehttpsfalsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_usertrue.falsetrue.falsetrue.falsehttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_server_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhirhospital.com-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse-1 means infinite number of retries-15000processfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.30.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1foo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.10.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1foo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_server_trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20"" or a single block scalar | character if no roles should be configuredfalsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_server_trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pemapp, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_usertrue.falsetrue.falsetrue.falsehttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1foo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1https://foo.bar/bpehttpsfalsefalse for developmenttruedev, test and prod environments im configured; supported values: dev, test and prodfoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./bpeSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3app, 172.28.1.3443my-external.fqdn:44330 seconds30 seconds60 seconds60 seconds/ character at start, no / character at end, use '' (empty string) to configure root as context path./fhirSSLCACertificateFile/run/secrets/ssl_ca_certificate_file.pemAcceptable client certificate CA names send to the client, during TLS handshake, sets the apache httpd parameter SSLCADNRequestFile; if omitted all entries from SSL_CA_CERTIFICATE_FILE are used/run/secrets/ssl_ca_dn_request_file.pemSSLCertificateChainFile; can be omitted if either no chain is needed (aka self signed server certificate) or the file specified via SSL_CERTIFICATE_FILE contains the certificate chain/run/secrets/ssl_certificate_chain_file.pemSSLCertificateFile/run/secrets/ssl_certificate_file.pemSSLCertificateKeyFile/run/secrets/ssl_certificate_key_file.pemSSLVerifyClientoptional when using OIDC authenticationrequireapp, 172.28.1.3/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_client _trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.comcerttool --fingerprint --hash=sha512 --infile=client_certificate.pem20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000/run/secrets/app_client_certificate.pem0.0.0.0127.0.0.18080X-ClientCerttrue to enable OIDC authorization code flowfalsetrue to enable OIDC back-channel logouttrue (enabled), DEV_DSF_SERVER_AUTH_OIDC_CLIENT_ID and DEV_DSF_SERVER_AUTH_OIDC_BACK_CHANNEL_LOGOUT_PATH to be specifiedfalse/back-channel-logouttrue to enable OIDC bearer token authenticationfalse/run/secrets/oidc_provider_client_certificate.pem/run/secrets/oidc_provider_client_certificate_private_key.pem/run/secrets/oidc_provider_client_certificate_private_key.pem.password500030000/run/secrets/oidc_provider_trust_certificates.pemhttps://keycloak.test.com:8443/realms/example-realm-name/run/secrets/app_client_trust_certificates.pembpe docker image: /bpe, default in fhir docker image: /fhir127.0.0.110000truefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/bpecamunda_users/run/secrets/db_user_camunda.passwordcamunda_server_userbpe_users/run/secrets/db_user.passwordbpe_server_usertrue.falsetrue.falsetrue.falsetrue.false/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200060000truefalse500060000truefalse/run/secrets/app_client_trust_certificates.pem?criteria=QuestionnaireResponse%3Fstatus%3Dcompleted&status=active&type=websocket&payload=application/fhir%2Bjsonhttps://foo.bar/fhir-1 means infinite number of retries-15000?criteria=Task%3Fstatus%3Drequested&status=active&type=websocket&payload=application/fhir%2Bjson/run/secrets/smtp_server_client_certificate.pem/run/secrets/smtp_server_client_certificate_private_key.pem/run/secrets/smtp_server_client_certificate_private_key.pem.passwordsender@localhostsmtp.server.de4/opt/bpe/log/bpe.log4650reply.to@localhosttrue. Requires SMTP server to be configured.falsetrue. Requires SMTP server to be configured.false/run/secrets/smime_certificate.p12/run/secrets/smime_certificate.p12.passwordrecipient@localhostcc.recipient@localhost/run/secrets/smtp_server_trust_certificates.pemtruefalse41040dsfdev_updateAllowList|1.0, another_process|x.y-1 means infinite number of retries-15000processold_process|x.y<= 0 means number of cpu cores-1foo.bar, test.com:8080http://proxy.foo:80800.0.0.0127.0.0.1Feel free to contact us via E-Mail (dsf-gecko@hs-heilbronn.de) and we will take care of your request as soon as possible.
DSF's community is growing and we welcome anyone who would like to join! 🚀
Feel free to contact us via E-Mail (dsf-gecko@hs-heilbronn.de) and we will take care of your request as soon as possible.
"}');export{M as comp,I as data}; diff --git a/assets/create.html-BItTDjcM.js b/assets/create.html-BItTDjcM.js new file mode 100644 index 000000000..a9734cf44 --- /dev/null +++ b/assets/create.html-BItTDjcM.js @@ -0,0 +1 @@ +import{_ as i}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as a,o as s,c as p,a as t,b as e,d as o,w as l}from"./app-9qxDwvDG.js";const c={},h={class:"hint-container tip"},d=t("p",{class:"hint-container-title"},"Work in progress",-1),u={href:"https://github.com/datasharingframework/dsf-process-hello-world",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/datasharingframework/dsf-process-ping-pong",target:"_blank",rel:"noopener noreferrer"},m={href:"https://github.com/datasharingframework/dsf-process-allow-list",target:"_blank",rel:"noopener noreferrer"};function f(_,w){const n=a("RouteLink"),r=a("ExternalLinkIcon");return s(),p("div",null,[t("p",null,[e("Visit the "),o(n,{to:"/for-you/"},{default:l(()=>[e("how the DSF can help you")]),_:1}),e(" page to get started.")]),t("div",h,[d,t("p",null,[e("We are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the "),o(n,{to:"/oldstable/tutorial/"},{default:l(()=>[e("process plugin tutorial")]),_:1}),e(". Additionally, we recommend to take a look at the upgraded DSF processes here:")]),t("ul",null,[t("li",null,[e("The "),t("a",u,[e("hello world plugin"),o(r)])]),t("li",null,[e("The "),t("a",g,[e("ping pong plugin"),o(r)])]),t("li",null,[e("The "),t("a",m,[e("update allowlist plugin"),o(r)])])])])])}const v=i(c,[["render",f],["__file","create.html.vue"]]),y=JSON.parse('{"path":"/v1.5.0/develop/create.html","title":"Create a new process plugin","lang":"en-US","frontmatter":{"title":"Create a new process plugin","icon":"code"},"headers":[],"git":{"createdTime":1708419681000,"updatedTime":1708419681000,"contributors":[{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":0.34,"words":102},"filePathRelative":"v1.5.0/develop/create.md","localizedDate":"February 20, 2024","excerpt":"Visit the how the DSF can help you page to get started.
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nVisit the how the DSF can help you page to get started.
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nVisit the how the DSF can help you page to get started.
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nVisit the how the DSF can help you page to get started.
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nWork in progress
\\nWe are currently in the process of updating the written documentation on how to create a DSF process plugin. In the meantime we recommend to study the oldstable version of the process plugin tutorial. Additionally, we recommend to take a look at the upgraded DSF processes here:
\\nJoin us in enhancing our documentation!
\\nWe believe in the power of community collaboration to make our documentation clearer, more comprehensive, and more user-friendly. There are several ways you can contribute, and we welcome greatly your input!
\\nJoin us in enhancing our documentation!
\\nWe believe in the power of community collaboration to make our documentation clearer, more comprehensive, and more user-friendly. There are several ways you can contribute, and we welcome greatly your input!
\\nJoin us in enhancing our documentation!
\\nWe believe in the power of community collaboration to make our documentation clearer, more comprehensive, and more user-friendly. There are several ways you can contribute, and we welcome greatly your input!
\\nJoin us in enhancing our documentation!
\\nWe believe in the power of community collaboration to make our documentation clearer, more comprehensive, and more user-friendly. There are several ways you can contribute, and we welcome greatly your input!
\\n<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<profiles version="15">
+ <profile kind="CodeFormatterProfile" name="highmed_dsf" version="15">
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_ellipsis" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_allocation_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_at_in_annotation_type_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_for_statment" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.new_lines_at_block_boundaries" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_parameters" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.insert_new_line_for_parameter" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_package" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_method_invocation" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_enum_constant" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_after_imports" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_while" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.insert_new_line_before_root_tags" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_annotation_type_member_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_throws" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_switch_statement" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_javadoc_comments" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.indentation.size" value="4"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_postfix_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_enum_constant_declaration" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_increments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_arguments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_inits" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_for" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.align_with_spaces" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.disabling_tag" value="@formatter:off"/>
+ <setting id="org.eclipse.jdt.core.formatter.continuation_indentation" value="2"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_enum_constants" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_imports" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_after_package" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_binary_operator" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_local_declarations" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_if_while_statement" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_enum_constant" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_parameterized_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.indent_root_tags" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.wrap_before_or_operator_multicatch" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.enabling_tag" value="@formatter:on"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_closing_brace_in_block" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.count_line_length_from_starting_position" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_return" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_method_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_parameter" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_then_statement_on_same_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_field" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_explicitconstructorcall_arguments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_prefix_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_between_type_declarations" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_brace_in_array_initializer" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_for" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_catch" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_method" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_switch" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_parameterized_type_references" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_anonymous_type_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_parenthesized_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_annotation_declaration_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_enum_constant" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.never_indent_line_comments_on_first_column" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_and_in_type_parameter" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_inits" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_statements_compare_to_block" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_anonymous_type_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_question_in_wildcard" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_invocation_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_switch" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.align_tags_descriptions_grouped" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.line_length" value="120"/>
+ <setting id="org.eclipse.jdt.core.formatter.use_on_off_tags" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_method_body_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_brackets_in_array_allocation_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_loop_body_block_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_constant" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_invocation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_assignment_operator" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_type_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_for" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.preserve_white_space_between_code_and_line_comments" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_local_variable" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_method_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_enum_constant_declaration_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.align_variable_declarations_on_columns" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_invocation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_union_type_in_multicatch" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_colon_in_for" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_type_declaration_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.number_of_blank_lines_at_beginning_of_method_body" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_arguments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_else_statement_on_same_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_binary_expression" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_catch_clause" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_parameterized_type_reference" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_array_initializer" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_field_declarations" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_explicit_constructor_call" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_anonymous_type_declaration_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_annotation_declaration_header" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_superinterfaces" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_default" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_question_in_conditional" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_block" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_constructor_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_lambda_body" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.compact_else_if" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_catch" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_invocation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.put_empty_statement_on_new_line" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_parameters_in_constructor_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_type_parameters" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_invocation_arguments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_method_invocation" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_constructor_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_compact_loops" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_block_comment" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_before_catch_in_try_statement" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_try" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_simple_for_body_on_same_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_at_end_of_file_if_missing" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_javadoc_comment" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_array_initializer" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_binary_operator" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_unary_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_expressions_in_array_initializer" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.format_line_comment_starting_on_first_column" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.number_of_empty_lines_to_preserve" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_annotation" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_colon_in_case" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_ellipsis" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_try_resources" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_colon_in_assert" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_if" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_and_in_type_parameter" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_parenthesized_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_line_comments" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_colon_in_labeled_statement" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.align_type_members_on_columns" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_assignment" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_module_statements" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_type_header" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.align_tags_names_descriptions" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_enum_constant" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_type_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_if_then_body_block_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_first_class_body_declaration" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_conditional_expression" value="80"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_before_closing_brace_in_array_initializer" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.format_guardian_clause_on_one_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_if" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.align_assignment_statements_on_columns" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_type" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_block" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_enum_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_block_in_case" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_constructor_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_header" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_allocation_expression" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_invocation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_while" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_switch" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_method_declaration" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.join_wrapped_lines" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_constructor_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.wrap_before_conditional_operator" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_cases" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_allocation_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_synchronized" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.align_fields_grouping_blank_lines" value="2147483647"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.new_lines_at_javadoc_boundaries" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_annotation_type_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_for" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_resources_in_try" value="80"/>
+ <setting id="org.eclipse.jdt.core.formatter.use_tabs_only_for_leading_indentations" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_try_clause" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_selector_in_method_invocation" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.never_indent_block_comments_on_first_column" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_code_block_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_synchronized" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_throws" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.tabulation.size" value="4"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_allocation_expression" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_colon_in_conditional" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_source_code" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_array_initializer" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_try" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_try_resources" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_field" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.continuation_indentation_for_array_initializer" value="2"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_question_in_wildcard" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_method" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_superclass_in_type_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_enum_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_throw" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.wrap_before_assignment_operator" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_labeled_statement" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_switch" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_superinterfaces" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_parameters" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_type_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_brace_in_array_initializer" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_parenthesized_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_html" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation_type_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_parameters" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_method_delcaration" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_compact_if" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_lambda_body_block_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_empty_lines" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_type_arguments" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_parameterized_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_unary_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_enum_constant" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_annotation" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_declarations" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_empty_array_initializer_on_one_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_switch" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_before_else_in_if_statement" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_assignment_operator" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_constructor_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_new_chunk" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_label" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_declaration_header" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_allocation_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_constructor_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_conditional" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_parameterized_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_cast" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_assert" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_member_type" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_before_while_in_do_statement" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_parameterized_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_arguments_in_qualified_allocation_expression" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_after_opening_brace_in_array_initializer" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_breaks_compare_to_cases" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_if" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_semicolon" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_postfix_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_try" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_cast" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.format_block_comments" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_lambda_arrow" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_imple_if_on_one_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_parameters_in_method_declaration" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_brackets_in_array_type_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_for" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_throws" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_allocation_expression" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_statements_compare_to_body" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_multiple_fields" value="16"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_constant_arguments" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_simple_while_body_on_same_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_prefix_operator" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_array_initializer" value="end_of_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.wrap_before_binary_operator" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_method_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_parameters" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_catch" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_annotation" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_constant_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.parentheses_positions_in_lambda_declaration" value="common_lines"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_between_empty_braces_in_array_initializer" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_colon_in_case" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_local_declarations" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_simple_do_while_body_on_same_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_annotation_type_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_reference" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_enum_declaration_on_one_line" value="one_line_never"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.wrap_outer_expressions_when_nested" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_closing_paren_in_cast" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_enum_constant" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.brace_position_for_type_declaration" value="next_line"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_before_package" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_for" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_synchronized" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_increments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation_type_member_declaration" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.alignment_for_expressions_in_for_loop_header" value="0"/>
+ <setting id="org.eclipse.jdt.core.formatter.keep_simple_getter_setter_on_one_line" value="false"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_while" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_enum_constant" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_explicitconstructorcall_arguments" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_constant_header" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_lambda_arrow" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_constructor_declaration" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_throws" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.join_lines_in_comments" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_parameters" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_question_in_conditional" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.comment.indent_parameter_description" value="true"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_new_line_before_finally_in_try_statement" value="insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.tabulation.char" value="tab"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_field_declarations" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.blank_lines_between_import_groups" value="1"/>
+ <setting id="org.eclipse.jdt.core.formatter.lineSplit" value="120"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_annotation" value="do not insert"/>
+ <setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_switch" value="insert"/>
+ </profile>
+</profiles>
+<?xml version=\\"1.0\\" encoding=\\"UTF-8\\" standalone=\\"no\\"?>\\n<profiles version=\\"15\\">\\n <profile kind=\\"CodeFormatterProfile\\" name=\\"highmed_dsf\\" version=\\"15\\">\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_ellipsis\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_allocation_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_at_in_annotation_type_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_for_statment\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.new_lines_at_block_boundaries\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_parameters\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.insert_new_line_for_parameter\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_package\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_method_invocation\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_enum_constant\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_after_imports\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_while\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.insert_new_line_before_root_tags\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_annotation_type_member_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_throws\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_switch_statement\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_javadoc_comments\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indentation.size\\" value=\\"4\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_postfix_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_enum_constant_declaration\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_increments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_arguments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_inits\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_for\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.align_with_spaces\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.disabling_tag\\" value=\\"@formatter:off\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.continuation_indentation\\" value=\\"2\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_enum_constants\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_imports\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_after_package\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_binary_operator\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_local_declarations\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_if_while_statement\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_enum_constant\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_parameterized_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.indent_root_tags\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.wrap_before_or_operator_multicatch\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.enabling_tag\\" value=\\"@formatter:on\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_closing_brace_in_block\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.count_line_length_from_starting_position\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_return\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_method_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_parameter\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_then_statement_on_same_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_field\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_explicitconstructorcall_arguments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_prefix_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_between_type_declarations\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_brace_in_array_initializer\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_for\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_catch\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_method\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_switch\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_parameterized_type_references\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_anonymous_type_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_parenthesized_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_annotation_declaration_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_enum_constant\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.never_indent_line_comments_on_first_column\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_and_in_type_parameter\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_inits\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_statements_compare_to_block\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_anonymous_type_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_question_in_wildcard\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_invocation_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_switch\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.align_tags_descriptions_grouped\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.line_length\\" value=\\"120\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.use_on_off_tags\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_method_body_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_brackets_in_array_allocation_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_loop_body_block_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_constant\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_invocation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_assignment_operator\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_type_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_for\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.preserve_white_space_between_code_and_line_comments\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_local_variable\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_method_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_enum_constant_declaration_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.align_variable_declarations_on_columns\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_invocation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_union_type_in_multicatch\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_colon_in_for\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_type_declaration_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.number_of_blank_lines_at_beginning_of_method_body\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_arguments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_else_statement_on_same_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_binary_expression\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_catch_clause\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_parameterized_type_reference\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_array_initializer\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_field_declarations\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_explicit_constructor_call\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_anonymous_type_declaration_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_annotation_declaration_header\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_superinterfaces\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_default\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_question_in_conditional\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_block\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_constructor_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_lambda_body\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.compact_else_if\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_catch\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_invocation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.put_empty_statement_on_new_line\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_parameters_in_constructor_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_type_parameters\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_invocation_arguments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_method_invocation\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_constructor_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_compact_loops\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_block_comment\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_before_catch_in_try_statement\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_try\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_simple_for_body_on_same_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_at_end_of_file_if_missing\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_javadoc_comment\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_array_initializer\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_binary_operator\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_unary_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_expressions_in_array_initializer\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.format_line_comment_starting_on_first_column\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.number_of_empty_lines_to_preserve\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_annotation\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_colon_in_case\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_ellipsis\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_try_resources\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_colon_in_assert\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_if\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_and_in_type_parameter\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_parenthesized_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_line_comments\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_colon_in_labeled_statement\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.align_type_members_on_columns\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_assignment\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_module_statements\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_type_header\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.align_tags_names_descriptions\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_enum_constant\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_type_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_if_then_body_block_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_first_class_body_declaration\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_conditional_expression\\" value=\\"80\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_before_closing_brace_in_array_initializer\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.format_guardian_clause_on_one_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_if\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.align_assignment_statements_on_columns\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_type\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_block\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_enum_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_block_in_case\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_constructor_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_header\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_allocation_expression\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_invocation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_while\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_switch\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_method_declaration\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.join_wrapped_lines\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_constructor_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.wrap_before_conditional_operator\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_cases\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_allocation_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_synchronized\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.align_fields_grouping_blank_lines\\" value=\\"2147483647\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.new_lines_at_javadoc_boundaries\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_annotation_type_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_for\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_resources_in_try\\" value=\\"80\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.use_tabs_only_for_leading_indentations\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_try_clause\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_selector_in_method_invocation\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.never_indent_block_comments_on_first_column\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_code_block_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_synchronized\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_throws\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.tabulation.size\\" value=\\"4\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_allocation_expression\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_colon_in_conditional\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_source_code\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_array_initializer\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_try\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_try_resources\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_field\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.continuation_indentation_for_array_initializer\\" value=\\"2\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_question_in_wildcard\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_method\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_superclass_in_type_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_enum_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_throw\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.wrap_before_assignment_operator\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_labeled_statement\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_switch\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_superinterfaces\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_parameters\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_type_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_brace_in_array_initializer\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_parenthesized_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_html\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation_type_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_parameters\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_method_delcaration\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_compact_if\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_lambda_body_block_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_empty_lines\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_type_arguments\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_parameterized_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_unary_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_enum_constant\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_annotation\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_declarations\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_empty_array_initializer_on_one_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_switch\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_before_else_in_if_statement\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_assignment_operator\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_constructor_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_new_chunk\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_label\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_declaration_header\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_allocation_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_constructor_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_conditional\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_parameterized_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_cast\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_assert\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_member_type\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_before_while_in_do_statement\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_parameterized_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_arguments_in_qualified_allocation_expression\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_after_opening_brace_in_array_initializer\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_breaks_compare_to_cases\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_if\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_semicolon\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_postfix_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_try\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_cast\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.format_block_comments\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_lambda_arrow\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_imple_if_on_one_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_parameters_in_method_declaration\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_brackets_in_array_type_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_for\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_throws\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_allocation_expression\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_statements_compare_to_body\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_multiple_fields\\" value=\\"16\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_constant_arguments\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_simple_while_body_on_same_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_prefix_operator\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_array_initializer\\" value=\\"end_of_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.wrap_before_binary_operator\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_method_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_parameters\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_catch\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_comma_in_annotation\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_constant_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.parentheses_positions_in_lambda_declaration\\" value=\\"common_lines\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_between_empty_braces_in_array_initializer\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_colon_in_case\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_local_declarations\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_simple_do_while_body_on_same_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_annotation_type_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_reference\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_enum_declaration_on_one_line\\" value=\\"one_line_never\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.wrap_outer_expressions_when_nested\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_closing_paren_in_cast\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_enum_constant\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.brace_position_for_type_declaration\\" value=\\"next_line\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_before_package\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_for\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_synchronized\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_increments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation_type_member_declaration\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.alignment_for_expressions_in_for_loop_header\\" value=\\"0\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.keep_simple_getter_setter_on_one_line\\" value=\\"false\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_while\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_enum_constant\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_explicitconstructorcall_arguments\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_constant_header\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_lambda_arrow\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_constructor_declaration\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_throws\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.join_lines_in_comments\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_parameters\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_question_in_conditional\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.comment.indent_parameter_description\\" value=\\"true\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_new_line_before_finally_in_try_statement\\" value=\\"insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.tabulation.char\\" value=\\"tab\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_field_declarations\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.blank_lines_between_import_groups\\" value=\\"1\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.lineSplit\\" value=\\"120\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_annotation\\" value=\\"do not insert\\"/>\\n <setting id=\\"org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_switch\\" value=\\"insert\\"/>\\n </profile>\\n</profiles>\\nversion: '3.8'
+services:
+ proxy:
+ image: nginx:1.23
+ restart: "no"
+ ports:
+ - 127.0.0.1:443:443
+ secrets:
+ - proxy_certificate_and_int_cas.pem
+ - proxy_certificate_private_key.pem
+ - proxy_trusted_client_cas.pem
+ volumes:
+ - type: bind
+ source: ./proxy/conf.d
+ target: /etc/nginx/conf.d
+ read_only: true
+ - type: bind
+ source: ./proxy/nginx.conf
+ target: /etc/nginx/nginx.conf
+ read_only: true
+ networks:
+ dic-fhir-frontend:
+ ipv4_address: 172.20.0.66
+ hrp-fhir-frontend:
+ ipv4_address: 172.20.0.82
+ cos-fhir-frontend:
+ ipv4_address: 172.20.0.98
+ internet:
+ aliases:
+ - cos
+ - dic
+ - hrp
+ environment:
+ TZ: Europe/Berlin
+
+ db:
+ image: postgres:13
+ restart: "no"
+ healthcheck:
+ test: ["CMD-SHELL", "pg_isready -U liquibase_user -d postgres"]
+ interval: 10s
+ timeout: 5s
+ retries: 5
+ environment:
+ TZ: Europe/Berlin
+ POSTGRES_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ POSTGRES_USER: liquibase_user
+ POSTGRES_DB: postgres
+ networks:
+ - cos-fhir-backend
+ - dic-fhir-backend
+ - hrp-fhir-backend
+ - cos-bpe-backend
+ - dic-bpe-backend
+ - hrp-bpe-backend
+ secrets:
+ - db_liquibase.password
+ volumes:
+ - type: volume
+ source: db-data
+ target: /var/lib/postgresql/data
+ - type: bind
+ source: ./db/init-db.sh
+ target: /docker-entrypoint-initdb.d/init-db.sh
+ read_only: true
+
+ cos-fhir:
+ image: ghcr.io/highmed/fhir:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5002:5002
+ secrets:
+ - db_liquibase.password
+ - db_cos_fhir_user.password
+ - db_cos_fhir_user_permanent_delete.password
+ - app_client_trust_certificates.pem
+ - app_cos_client_certificate.pem
+ - app_cos_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./cos/fhir/conf/bundle.xml
+ target: /opt/fhir/conf/bundle.xml
+ - type: bind
+ source: ./cos/fhir/log
+ target: /opt/fhir/log
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5002
+ ORG_HIGHMED_DSF_FHIR_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PASSWORD_FILE: /run/secrets/db_cos_fhir_user.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_PASSWORD_FILE: /run/secrets/db_cos_fhir_user_permanent_delete.password
+ ORG_HIGHMED_DSF_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_cos_client_certificate.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_cos_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_FHIR_DB_URL: jdbc:postgresql://db/cos_fhir
+ ORG_HIGHMED_DSF_FHIR_DB_USER_GROUP: cos_fhir_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_USERNAME: cos_fhir_server_user
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_GROUP: cos_fhir_permanent_delete_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_USERNAME: cos_fhir_server_permanent_delete_user
+ ORG_HIGHMED_DSF_FHIR_SERVER_BASE_URL: https://cos/fhir
+ ORG_HIGHMED_DSF_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_COS
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS: ${COS_USER_THUMBPRINTS}
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS_PERMANENT_DELETE: ${COS_USER_THUMBPRINTS_PERMANENT_DELETE}
+ networks:
+ cos-fhir-frontend:
+ ipv4_address: 172.20.0.99
+ cos-fhir-backend:
+ internet:
+ depends_on:
+ - db
+ - proxy
+ cos-bpe:
+ image: ghcr.io/highmed/bpe:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5005:5005
+ secrets:
+ - db_liquibase.password
+ - db_cos_bpe_user.password
+ - db_cos_bpe_user_camunda.password
+ - app_client_trust_certificates.pem
+ - app_cos_client_certificate.pem
+ - app_cos_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./cos/bpe/plugin
+ target: /opt/bpe/plugin
+ read_only: true
+ - type: bind
+ source: ./cos/bpe/process
+ target: /opt/bpe/process
+ read_only: true
+ - type: bind
+ source: ./cos/bpe/log
+ target: /opt/bpe/log
+ - type: bind
+ source: ./cos/bpe/last_event
+ target: /opt/bpe/last_event
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005
+ ORG_HIGHMED_DSF_BPE_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_PASSWORD_FILE: /run/secrets/db_cos_bpe_user.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_PASSWORD_FILE: /run/secrets/db_cos_bpe_user_camunda.password
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_cos_client_certificate.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_cos_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_BPE_DB_URL: jdbc:postgresql://db/cos_bpe
+ ORG_HIGHMED_DSF_BPE_DB_USER_GROUP: cos_bpe_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_USERNAME: cos_bpe_server_user
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_GROUP: cos_camunda_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_USERNAME: cos_camunda_server_user
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_COS
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_BASE_URL: https://cos/fhir
+ networks:
+ cos-bpe-frontend:
+ cos-bpe-backend:
+ internet:
+ depends_on:
+ - db
+ - cos-fhir
+
+ dic-fhir:
+ image: ghcr.io/highmed/fhir:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5000:5000
+ secrets:
+ - db_liquibase.password
+ - db_dic_fhir_user.password
+ - db_dic_fhir_user_permanent_delete.password
+ - app_client_trust_certificates.pem
+ - app_dic_client_certificate.pem
+ - app_dic_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./dic/fhir/conf/bundle.xml
+ target: /opt/fhir/conf/bundle.xml
+ - type: bind
+ source: ./dic/fhir/log
+ target: /opt/fhir/log
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5000
+ ORG_HIGHMED_DSF_FHIR_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PASSWORD_FILE: /run/secrets/db_dic_fhir_user.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_PASSWORD_FILE: /run/secrets/db_dic_fhir_user_permanent_delete.password
+ ORG_HIGHMED_DSF_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_dic_client_certificate.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_dic_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_FHIR_DB_URL: jdbc:postgresql://db/dic_fhir
+ ORG_HIGHMED_DSF_FHIR_DB_USER_GROUP: dic_fhir_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_USERNAME: dic_fhir_server_user
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_GROUP: dic_fhir_permanent_delete_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_USERNAME: dic_fhir_server_permanent_delete_user
+ ORG_HIGHMED_DSF_FHIR_SERVER_BASE_URL: https://dic/fhir
+ ORG_HIGHMED_DSF_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_DIC
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS: ${DIC_USER_THUMBPRINTS}
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS_PERMANENT_DELETE: ${DIC_USER_THUMBPRINTS_PERMANENT_DELETE}
+ networks:
+ dic-fhir-frontend:
+ ipv4_address: 172.20.0.67
+ dic-fhir-backend:
+ internet:
+ depends_on:
+ - db
+ - proxy
+ dic-bpe:
+ image: ghcr.io/highmed/bpe:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5003:5003
+ secrets:
+ - db_liquibase.password
+ - db_dic_bpe_user.password
+ - db_dic_bpe_user_camunda.password
+ - app_client_trust_certificates.pem
+ - app_dic_client_certificate.pem
+ - app_dic_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./dic/bpe/plugin
+ target: /opt/bpe/plugin
+ read_only: true
+ - type: bind
+ source: ./dic/bpe/process
+ target: /opt/bpe/process
+ read_only: true
+ - type: bind
+ source: ./dic/bpe/log
+ target: /opt/bpe/log
+ - type: bind
+ source: ./dic/bpe/last_event
+ target: /opt/bpe/last_event
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5003
+ ORG_HIGHMED_DSF_BPE_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_PASSWORD_FILE: /run/secrets/db_dic_bpe_user.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_PASSWORD_FILE: /run/secrets/db_dic_bpe_user_camunda.password
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_dic_client_certificate.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_dic_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_BPE_DB_URL: jdbc:postgresql://db/dic_bpe
+ ORG_HIGHMED_DSF_BPE_DB_USER_GROUP: dic_bpe_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_USERNAME: dic_bpe_server_user
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_GROUP: dic_camunda_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_USERNAME: dic_camunda_server_user
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_DIC
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_BASE_URL: https://dic/fhir
+ networks:
+ dic-bpe-frontend:
+ dic-bpe-backend:
+ internet:
+ depends_on:
+ - db
+ - dic-fhir
+
+ hrp-fhir:
+ image: ghcr.io/highmed/fhir:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5001:5001
+ secrets:
+ - db_liquibase.password
+ - db_hrp_fhir_user.password
+ - db_hrp_fhir_user_permanent_delete.password
+ - app_client_trust_certificates.pem
+ - app_hrp_client_certificate.pem
+ - app_hrp_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./hrp/fhir/conf/bundle.xml
+ target: /opt/fhir/conf/bundle.xml
+ - type: bind
+ source: ./hrp/fhir/log
+ target: /opt/fhir/log
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5001
+ ORG_HIGHMED_DSF_FHIR_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PASSWORD_FILE: /run/secrets/db_hrp_fhir_user.password
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_PASSWORD_FILE: /run/secrets/db_hrp_fhir_user_permanent_delete.password
+ ORG_HIGHMED_DSF_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_hrp_client_certificate.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_hrp_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_FHIR_DB_URL: jdbc:postgresql://db/hrp_fhir
+ ORG_HIGHMED_DSF_FHIR_DB_USER_GROUP: hrp_fhir_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_USERNAME: hrp_fhir_server_user
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_GROUP: hrp_fhir_permanent_delete_users
+ ORG_HIGHMED_DSF_FHIR_DB_USER_PERMANENT_DELETE_USERNAME: hrp_fhir_server_permanent_delete_user
+ ORG_HIGHMED_DSF_FHIR_SERVER_BASE_URL: https://hrp/fhir
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS: ${HRP_USER_THUMBPRINTS}
+ ORG_HIGHMED_DSF_FHIR_SERVER_USER_THUMBPRINTS_PERMANENT_DELETE: ${HRP_USER_THUMBPRINTS_PERMANENT_DELETE}
+ ORG_HIGHMED_DSF_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_HRP
+ networks:
+ hrp-fhir-frontend:
+ ipv4_address: 172.20.0.83
+ hrp-fhir-backend:
+ internet:
+ depends_on:
+ - db
+ - proxy
+ hrp-bpe:
+ image: ghcr.io/highmed/bpe:0.7.0
+ restart: "no"
+ ports:
+ - 127.0.0.1:5004:5004
+ secrets:
+ - db_liquibase.password
+ - db_hrp_bpe_user.password
+ - db_hrp_bpe_user_camunda.password
+ - app_client_trust_certificates.pem
+ - app_hrp_client_certificate.pem
+ - app_hrp_client_certificate_private_key.pem
+ - app_client_certificate_private_key.pem.password
+ volumes:
+ - type: bind
+ source: ./hrp/bpe/plugin
+ target: /opt/bpe/plugin
+ read_only: true
+ - type: bind
+ source: ./hrp/bpe/process
+ target: /opt/bpe/process
+ read_only: true
+ - type: bind
+ source: ./hrp/bpe/log
+ target: /opt/bpe/log
+ - type: bind
+ source: ./hrp/bpe/last_event
+ target: /opt/bpe/last_event
+ environment:
+ TZ: Europe/Berlin
+ EXTRA_JVM_ARGS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5004
+ ORG_HIGHMED_DSF_BPE_DB_LIQUIBASE_PASSWORD_FILE: /run/secrets/db_liquibase.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_PASSWORD_FILE: /run/secrets/db_hrp_bpe_user.password
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_PASSWORD_FILE: /run/secrets/db_hrp_bpe_user_camunda.password
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_TRUST_CERTIFICATES: /run/secrets/app_client_trust_certificates.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE: /run/secrets/app_hrp_client_certificate.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY: /run/secrets/app_hrp_client_certificate_private_key.pem
+ ORG_HIGHMED_DSF_BPE_FHIR_CLIENT_CERTIFICATE_PRIVATE_KEY_PASSWORD_FILE: /run/secrets/app_client_certificate_private_key.pem.password
+ ORG_HIGHMED_DSF_BPE_DB_URL: jdbc:postgresql://db/hrp_bpe
+ ORG_HIGHMED_DSF_BPE_DB_USER_GROUP: hrp_bpe_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_USERNAME: hrp_bpe_server_user
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_GROUP: hrp_camunda_users
+ ORG_HIGHMED_DSF_BPE_DB_USER_CAMUNDA_USERNAME: hrp_camunda_server_user
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_ORGANIZATION_IDENTIFIER_VALUE: Test_HRP
+ ORG_HIGHMED_DSF_BPE_FHIR_SERVER_BASE_URL: https://hrp/fhir
+ networks:
+ hrp-bpe-frontend:
+ hrp-bpe-backend:
+ internet:
+ depends_on:
+ - db
+ - hrp-fhir
+
+secrets:
+ proxy_certificate_and_int_cas.pem:
+ file: ./secrets/proxy_certificate_and_int_cas.pem
+ proxy_certificate_private_key.pem:
+ file: ./secrets/proxy_certificate_private_key.pem
+ proxy_trusted_client_cas.pem:
+ file: ./secrets/proxy_trusted_client_cas.pem
+
+ db_liquibase.password:
+ file: ./secrets/db_liquibase.password
+
+ db_dic_fhir_user.password:
+ file: ./secrets/db_dic_fhir_user.password
+ db_dic_fhir_user_permanent_delete.password:
+ file: ./secrets/db_dic_fhir_user_permanent_delete.password
+ db_dic_bpe_user.password:
+ file: ./secrets/db_dic_bpe_user.password
+ db_dic_bpe_user_camunda.password:
+ file: ./secrets/db_dic_bpe_user_camunda.password
+
+ db_hrp_fhir_user.password:
+ file: ./secrets/db_hrp_fhir_user.password
+ db_hrp_fhir_user_permanent_delete.password:
+ file: ./secrets/db_hrp_fhir_user_permanent_delete.password
+ db_hrp_bpe_user.password:
+ file: ./secrets/db_hrp_bpe_user.password
+ db_hrp_bpe_user_camunda.password:
+ file: ./secrets/db_hrp_bpe_user_camunda.password
+
+ db_cos_fhir_user.password:
+ file: ./secrets/db_cos_fhir_user.password
+ db_cos_fhir_user_permanent_delete.password:
+ file: ./secrets/db_cos_fhir_user_permanent_delete.password
+ db_cos_bpe_user.password:
+ file: ./secrets/db_cos_bpe_user.password
+ db_cos_bpe_user_camunda.password:
+ file: ./secrets/db_cos_bpe_user_camunda.password
+
+ app_client_trust_certificates.pem:
+ file: ./secrets/app_client_trust_certificates.pem
+ app_client_certificate_private_key.pem.password:
+ file: ./secrets/app_client_certificate_private_key.pem.password
+
+ app_dic_client_certificate.pem:
+ file: ./secrets/app_dic_client_certificate.pem
+ app_dic_client_certificate_private_key.pem:
+ file: ./secrets/app_dic_client_certificate_private_key.pem
+
+ app_hrp_client_certificate.pem:
+ file: ./secrets/app_hrp_client_certificate.pem
+ app_hrp_client_certificate_private_key.pem:
+ file: ./secrets/app_hrp_client_certificate_private_key.pem
+
+ app_cos_client_certificate.pem:
+ file: ./secrets/app_cos_client_certificate.pem
+ app_cos_client_certificate_private_key.pem:
+ file: ./secrets/app_cos_client_certificate_private_key.pem
+
+networks:
+ internet:
+ dic-fhir-frontend:
+ driver: bridge
+ ipam:
+ driver: default
+ config:
+ - subnet: 172.20.0.64/28
+ dic-fhir-backend:
+ dic-bpe-frontend:
+ dic-bpe-backend:
+ hrp-fhir-frontend:
+ driver: bridge
+ ipam:
+ driver: default
+ config:
+ - subnet: 172.20.0.80/28
+ hrp-fhir-backend:
+ hrp-bpe-frontend:
+ hrp-bpe-backend:
+ cos-fhir-frontend:
+ driver: bridge
+ ipam:
+ driver: default
+ config:
+ - subnet: 172.20.0.96/28
+ cos-fhir-backend:
+ cos-bpe-frontend:
+ cos-bpe-backend:
+
+
+volumes:
+ db-data:
+ name: dsf-process-tutorial-db
+Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{m as comp,E as data}; diff --git a/assets/exercise1-simpleProcess.html-0shAeJAE.js b/assets/exercise1-simpleProcess.html-0shAeJAE.js new file mode 100644 index 000000000..edbbdc1a5 --- /dev/null +++ b/assets/exercise1-simpleProcess.html-0shAeJAE.js @@ -0,0 +1,4 @@ +import{_ as c}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as n,o as l,c as d,a as t,d as s,w as a,b as e,e as i}from"./app-9qxDwvDG.js";const h={},u=i('The first exercise focuses on setting up the testing environment used in this tutorial and shows how to implement and execute a simple BPMN process.
With this exercise we will take a look at the general setup of the tutorial code base, modify a service class and execute the service within a simple demo process.
The tutorial project consists of three parts: A test-data-generator project used to generate X.509 certificates and FHIR resources during the maven build of the project. The certificates and FHIR resources are needed to start DSF instances simulating installations at three different organizations used for this tutorial. The DSF instances are configured using a docker-compose.yml file in the test-setup folder. The docker-compose test setup uses a single PostgreSQL database server, a single nginx reverse proxy as well as three separate DSF FHIR server- and 3 separate DSF BPE server instances. The tutorial-process project contains all resource (FHIR resources, BPMN process models and Java code) for the actual DSF process plugin.
Java code for the tutorial-process project is located at src/main/java, FHIR resources and BPMN process models at src/main/resources as well as prepared JUnit tests to verify your solution at src/test/java.
HelloDic#doExecute method that logs the recipient organization identifier from the "leading" Task.HelloDic class as a singleton bean in the TutorialConfig class.hello-dic.bpmn process model.highmedorg_helloDic process to only allow local clients to instantiate the process via a helloDic message.Execute a maven build of the dsf-process-tutorial parent module via:
mvn clean install -Pexercise-1
+Verify that the build was successful and no test failures occurred.
To verify the highmedorg_helloDic process can be executed successfully, we need to deploy it into a DSF instance and execute the process. The maven install build is configured to create a process jar file with all necessary resources and to copy the jar to the appropriate locations of the docker test setup.
Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Caution: If you add the generated Root CA to your browsers certificate store as a trusted Root CA, make sure you are the only one with access to the private key at .../dsf-process-tutorial/test-data-generator/cert/ca/testca_private-key.pem.
Test_DIC organization in a second console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-bpe
+Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{ne as comp,ce as data}; diff --git a/assets/exercise11-processDebugging.html-Bmx7bmDp.js b/assets/exercise11-processDebugging.html-Bmx7bmDp.js new file mode 100644 index 000000000..654b2296c --- /dev/null +++ b/assets/exercise11-processDebugging.html-Bmx7bmDp.js @@ -0,0 +1,3 @@ +import{_ as a}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as l,o as c,c as n,a as t,d as s,w as o,b as e,e as d}from"./app-9qxDwvDG.js";const u="/photos/guideline/tutorial/eclipse.png",h="/photos/guideline/tutorial/intelliJ.png",m={},p=t("h2",{id:"exercise-1-1-process-debugging",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#exercise-1-1-process-debugging"},[t("span",null,"Exercise 1.1 - Process Debugging")])],-1),g=t("p",null,"This exercise looks at how to use the Java debugger of your IDE to remote debug the execution of a process plugin.",-1),x=t("h3",{id:"introduction",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#introduction"},[t("span",null,"Introduction")])],-1),b=t("hr",null,null,-1),_={href:"http://ghcr.io/highmed/fhir",target:"_blank",rel:"noopener noreferrer"},f={href:"http://ghcr.io/highmed/bpe",target:"_blank",rel:"noopener noreferrer"},E=t("code",null,"EXTRA_JVM_ARGS",-1),v=t("code",null,"EXTRA_JVM_ARGS",-1),k=d(`Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Test_DIC organization in second console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-bpe
+Eclipse:
IntelliJ:
Create a debug breakpoint in the first line of the HelloDic class doExecute method.
Start your previously defined remote Java debugger in your IDE.
Execute the TutorialExampleStarter class to start highmed_helloDic process.
User your IDE's debugger to step thru the code of the HelloDic class doExecute method.
Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{T as comp,J as data}; diff --git a/assets/exercise2-inputParameters.html-CG9H7Obf.js b/assets/exercise2-inputParameters.html-CG9H7Obf.js new file mode 100644 index 000000000..a4fb3dc61 --- /dev/null +++ b/assets/exercise2-inputParameters.html-CG9H7Obf.js @@ -0,0 +1,10 @@ +import{_ as l}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as i,o as c,c as d,a as t,d as s,w as n,b as e,e as r}from"./app-9qxDwvDG.js";const h={},u=t("h2",{id:"exercise-2-input-parameters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#exercise-2-input-parameters"},[t("span",null,"Exercise 2 - Input Parameters")])],-1),p=t("p",null,[e("In order to configure processes that are packaged as process plugins, we will take a look at two possibilities on how to pass parameters to a process. The goal of this exercise is to enhance the "),t("code",null,"highmedorg_helloDic"),e(" process by trying them both.")],-1),m=t("h3",{id:"introduction",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#introduction"},[t("span",null,"Introduction")])],-1),f=t("hr",null,null,-1),g=t("p",null,"DSF process plugins can be configured with input parameters using two different approaches:",-1),_=t("li",null,"Static configuration using environment variables during the deployment of a process plugin.",-1),b={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},v=t("h4",{id:"environment-variables",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#environment-variables"},[t("span",null,"Environment Variables")])],-1),k={href:"https://docs.spring.io/spring-framework/docs/current/reference/html/core.html#beans-value-annotations",target:"_blank",rel:"noopener noreferrer"},x=t("code",null,"TutorialConfig",-1),y=t("code",null,"${..}",-1),w=t("code",null,"${some.property:defaultValue}",-1),T=t("code",null,"some.property",-1),S=t("code",null,"SOME_PROPERTY",-1),D={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-tools/dsf-tools-documentation-generator/src/main/java/org/highmed/dsf/tools/generator/ProcessDocumentation.java",target:"_blank",rel:"noopener noreferrer"},E=t("code",null,"org.highmed.dsf.tools.generator",-1),P=t("code",null,"pom.xml",-1),R=t("code",null,"tutorial-process",-1),I={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-tools/dsf-tools-documentation-generator/src/main/java/org/highmed/dsf/tools/generator/DocumentationGenerator.java",target:"_blank",rel:"noopener noreferrer"},F={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-tools/dsf-tools-documentation-generator/src/main/java/org/highmed/dsf/tools/generator/ProcessDocumentation.java",target:"_blank",rel:"noopener noreferrer"},C=t("h4",{id:"task-input-parameters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#task-input-parameters"},[t("span",null,"Task Input Parameters")])],-1),V={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},B={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},q={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/StructureDefinition/highmed-task-base-0.5.0.xml",target:"_blank",rel:"noopener noreferrer"},H=t("ul",null,[t("li",null,[t("code",null,"message-name"),e(" (mandatory 1..1): the name of the BPMN message event, same as in the BPMN model")]),t("li",null,[t("code",null,"business-key"),e(" (optional 0..1): used to identify process instances")]),t("li",null,[t("code",null,"correlation-key"),e("(optional 0..1): used to identify multi-instance process instances used for messaging multiple targets")])],-1),A=t("p",null,"A later exercise will examine these input parameters and their meaning in more detail.",-1),M={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},z={href:"http://hl7.org/fhir/R4/codesystem.html",target:"_blank",rel:"noopener noreferrer"},N={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/CodeSystem/highmed-bpmn-message-0.5.0.xml",target:"_blank",rel:"noopener noreferrer"},j={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/ValueSet/highmed-bpmn-message-0.5.0.xml",target:"_blank",rel:"noopener noreferrer"},G={href:"https://github.com/highmed/highmed-dsf/blob/main/dsf-fhir/dsf-fhir-validation/src/main/resources/fhir/StructureDefinition/highmed-task-base-0.5.0.xml",target:"_blank",rel:"noopener noreferrer"},L={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},O=t("h4",{id:"version-and-release-date-placeholders",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#version-and-release-date-placeholders"},[t("span",null,"Version and Release-Date Placeholders")])],-1),U={href:"http://hl7.org/fhir/R4/codesystem.html",target:"_blank",rel:"noopener noreferrer"},W={href:"http://hl7.org/fhir/R4/structuredefinition.html",target:"_blank",rel:"noopener noreferrer"},$={href:"http://hl7.org/fhir/R4/valueset.html",target:"_blank",rel:"noopener noreferrer"},J=t("code",null,"#{version}",-1),Y=t("code",null,"#{date}",-1),K=t("code",null,"ProcessPluginDefinition#getVersion()",-1),Q=t("code",null,"ProcessPluginDefinition#getReleaseDate()",-1),X=t("br",null,null,-1),Z={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},ee={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},te=t("code",null,"Resource.meta.tag",-1),se=t("code",null,"read-access-tag",-1),ae=r(`<meta>
+ <tag>
+ <system value="http://highmed.org/fhir/CodeSystem/read-access-tag" />
+ <code value="ALL" />
+ </tag>
+</meta>
+TutorialConfig class specify the default value as false.HelloDic class, by modifying its constructor and using the new field of the TutorialConfig class.HelloDic class to decide whether the log message from exercise 1 should be printed.test-setup/docker-compose.yml by adding the new environment variable to the service dic-bpe and set the value to "true".Execute a maven build of the dsf-process-tutorial parent module via:
mvn clean install -Pexercise-2
+Verify that the build was successful and no test failures occurred.
To verify the highmedorg_helloDic process can be executed successfully, we need to deploy it into a DSF instance and execute the process. The maven install build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker test setup.
Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Verify the DSF FHIR server started successfully.
Test_DIC organization in second console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-bpe
+Verify the DSF BPE server started successfully and deployed the highmedorg_helloDic process.
`,14),Re={start:"3"},Ie=t("code",null,"highmedorg_helloDic",-1),Fe={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},Ce=t("code",null,"Test_DIC",-1),Ve=t("code",null,"main",-1),Be=t("code",null,"org.highmed.dsf.process.tutorial.TutorialExampleStarter",-1),qe={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},He=t("code",null,"highmedorg_helloDic",-1),Ae=r("Verify that the highmedorg_helloDic process was executed by the DSF BPE server. The BPE server should:
HelloDic implementation.Check that you can disable logging of you message by modifying the docker-compose.yml file and configuring your environment variable with the value "false" or removing the environment variable.
Note: Changes to environment variable require recreating the docker container.
Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{We as comp,$e as data}; diff --git a/assets/exercise3-messageEvents.html-D1vmc1mU.js b/assets/exercise3-messageEvents.html-D1vmc1mU.js new file mode 100644 index 000000000..f49366fcc --- /dev/null +++ b/assets/exercise3-messageEvents.html-D1vmc1mU.js @@ -0,0 +1,41 @@ +import{_ as l}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as c,c as p,a as t,d as n,w as o,b as e,e as i}from"./app-9qxDwvDG.js";const u="/photos/guideline/tutorial/ex3.png",h={},d=t("h2",{id:"exercise-3-message-events",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#exercise-3-message-events"},[t("span",null,"Exercise 3 - Message Events")])],-1),g=t("p",null,"Communication between organizations is modeled using message flow in BPMN processes. The third exercise shows how a process at one organization can trigger a process at another organization.",-1),f=t("code",null,"highmedorg_helloDic",-1),m=t("code",null,"highmedorg_helloCos",-1),_=t("code",null,"Test_DIC",-1),k=t("code",null,"Test_COS",-1),v={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},b=t("code",null,"Test_DIC",-1),x=t("code",null,"Test_COS",-1),D=t("h3",{id:"introduction",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#introduction"},[t("span",null,"Introduction")])],-1),S=t("hr",null,null,-1),y=t("h4",{id:"message-flow-and-fhir-task-resources",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#message-flow-and-fhir-task-resources"},[t("span",null,"Message Flow and FHIR Task resources")])],-1),z={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},w={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},E=t("p",null,'In order to exchange information between different processes, for example at two different organizations, BPMN message flow is used. Typically represented by a dashed line arrow between elements with black (send) and white (receive) envelop icons. The following BPMN collaboration diagram shows two processes. The process at "Organization 1" is sending a message to "Organization 2" which results in the instantiation and execution of new process instance at the second organization.',-1),T=t("figure",null,[t("img",{src:u,alt:"Message Flow",tabindex:"0",loading:"lazy"}),t("figcaption",null,"Message Flow")],-1),R={href:"http://hl7.org/fhir/R4/task.html",target:"_blank",rel:"noopener noreferrer"},I={href:"https://docs.camunda.org/manual/7.17/reference/bpmn20/events/message-events/#message-start-event",target:"_blank",rel:"noopener noreferrer"},F={href:"https://docs.camunda.org/manual/7.17/reference/bpmn20/events/message-events/#message-intermediate-catching-event",target:"_blank",rel:"noopener noreferrer"},q=t("em",null,"Business Key",-1),C=t("em",null,"Correlation Key",-1),A=i(`FHIR ActivityDefinition resources are used to announce what processes can be instantiated at a given DSF instance. They also control what kind of organization can request the instantiation or continuation of a process instance and what kind of organization is allowed to fulfill the request.
In order to link the FHIR and BPMN worlds the BPMN process definition key needs to be specified following the pattern ^[-a-zA-Z0-9]+_[-a-zA-Z0-9]+$ for example:
domainorg_processKey
+In addition the BPM process needs to specify a process version with the pattern ^\\d+.\\d+.\\d+$ for example:
1.0.0
+This results in a canonical URL used to identify the process, for example:
http://domain.org/bpe/Process/processKey/1.0.0
+The following example specifies that process execution can only be requested by a organization with a specific identifier and only allows execution of the process in the DSF instance of an organization with a specific identifier.
<extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization">
+ <extension url="message-name">
+ <valueString value="some-message-name" />
+ </extension>
+ <extension url="task-profile">
+ <valueCanonical value="http://foo.org/fhir/StructureDefinition/profile|#{version}" />
+ </extension>
+ <extension url="requester">
+ <valueCoding>
+ <extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization-organization">
+ <valueIdentifier>
+ <system value="http://highmed.org/sid/organization-identifier" />
+ <value value="identifier.remote.org" />
+ </valueIdentifier>
+ </extension>
+ <system value="http://highmed.org/fhir/CodeSystem/process-authorization" />
+ <code value="REMOTE_ORGANIZATION" />
+ </valueCoding>
+ </extension>
+ <extension url="recipient">
+ <valueCoding>
+ <extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization-organization">
+ <valueIdentifier>
+ <system value="http://highmed.org/sid/organization-identifier" />
+ <value value="identifier.local.org" />
+ </valueIdentifier>
+ </extension>
+ <system value="http://highmed.org/fhir/CodeSystem/process-authorization" />
+ <code value="LOCAL_ORGANIZATION" />
+ </valueCoding>
+ </extension>
+</extension>
+highmedorg_helloCos process and its resources to the TutorialProcessPluginDefinition class.HelloDic service class to set the target process variable for the Test_COS organization.HelloCosMessage class as a spring in the TutorialConfig class.Execute a maven build of the dsf-process-tutorial parent module via:
mvn clean install -Pexercise-3
+Verify that the build was successful and no test failures occurred.
To verify the highmedorg_helloDic and highmedorg_helloCos processes can be executed successfully, we need to deploy them into DSF instances and execute the highmedorg_helloDic process. The maven install build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker test setup.
Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Verify the DSF FHIR server started successfully.
Test_DIC organization in another console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-bpe
+Verify the DSF BPE server started successfully and deployed the highmedorg_helloDic process.
Test_COS organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-fhir
+Test_COS organization in another console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-bpe
+Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{Dt as comp,St as data}; diff --git a/assets/exercise4-exclusiveGateways.html-Cdj2WPAM.js b/assets/exercise4-exclusiveGateways.html-Cdj2WPAM.js new file mode 100644 index 000000000..17a59c4d1 --- /dev/null +++ b/assets/exercise4-exclusiveGateways.html-Cdj2WPAM.js @@ -0,0 +1,9 @@ +import{_ as l}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as n,o as c,c as d,a as t,d as s,w as o,b as e,e as r}from"./app-9qxDwvDG.js";const h={},u=r('Different execution paths in a process based on the state of process variables can be achieved using Exclusive Gateways. In Exercise 4 we will examine how this can be implemented by modifying the highmedorg_helloDic process.
Via the DelegateExecution execution parameter of the doExecute method of a class extending AbstractServiceDelegate, we can write and read process variables of the current process instance. The following code listing show how to write and read a boolean variable:
{
+ execution.setVariable("variable-name", Variables.booleanValue(false));
+ boolean variable = (boolean) execution.getVariable("variable-name");
+}
+HelloDic class, write an algorithm deciding based on the "leading" Task's input parameter tutorial-input, whether the highmedorg_helloCos process should be started.highmedorg_helloDic process model and two outgoing sequence flows - the first starting process highmedorg_helloDic, the second stopping process highmedorg_helloDic without starting process highmedorg_helloCos.Execute a maven build of the dsf-process-tutorial parent module via:
mvn clean install -Pexercise-4
+Verify that the build was successful and no test failures occurred.
To verify the highmedorg_helloDic and highmedorg_helloCos processes can be executed successfully, we need to deploy them into DSF instances and execute the highmedorg_helloDic process. The maven install build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker test setup.
Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Verify the DSF FHIR server started successfully.
Test_DIC organization in a second console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-fhir
+Verify the DSF FHIR server started successfully.
Test_COS organization in a fourth console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-bpe
+Verify the DSF BPE server started successfully and deployed the highmedorg_helloCos process.
Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{M as comp,A as data}; diff --git a/assets/exercise5-eventBasedGateways.html-DfF8YKrj.js b/assets/exercise5-eventBasedGateways.html-DfF8YKrj.js new file mode 100644 index 000000000..714880e4a --- /dev/null +++ b/assets/exercise5-eventBasedGateways.html-DfF8YKrj.js @@ -0,0 +1,56 @@ +import{_ as l}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r,o as c,c as p,a as t,d as n,w as o,b as e,e as i}from"./app-9qxDwvDG.js";const u="/photos/guideline/tutorial/ex5.png",h={},d=i('In the final exercise we will look at message flow between three organizations as well as how to continue a waiting process if no return message arrives. With this exercise we will add a third process and complete a message loop from Test_DIC to Test_COR to Test_HRP back to Test_DIC.
The following example specifies that process execution can only be requested by a organization with a specific identifier and only allows execution of the process in the DSF instance of an organization with a specific identifier.
<extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization">
+ <extension url="message-name">
+ <valueString value="some-message-name" />
+ </extension>
+ <extension url="task-profile">
+ <valueCanonical value="http://foo.org/fhir/StructureDefinition/profile|#{version}" />
+ </extension>
+ <extension url="requester">
+ <valueCoding>
+ <extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization-consortium-role">
+ <extension url="consortium">
+ <valueIdentifier>
+ <system value="http://highmed.org/sid/organization-identifier" />
+ <value value="identifier.consortium.org" />
+ </valueIdentifier>
+ </extension>
+ <extension url="role">
+ <valueCoding>
+ <system value="http://highmed.org/fhir/CodeSystem/organization-role" />
+ <code value="SOME_ROLE" />
+ </valueCoding>
+ </extension>
+ </extension>
+ <system value="http://highmed.org/fhir/CodeSystem/process-authorization" />
+ <code value="REMOTE_ROLE" />
+ </valueCoding>
+ </extension>
+ <extension url="recipient">
+ <valueCoding>
+ <extension url="http://highmed.org/fhir/StructureDefinition/extension-process-authorization-consortium-role">
+ <extension url="consortium">
+ <valueIdentifier>
+ <system value="http://highmed.org/sid/organization-identifier" />
+ <value value="identifier.consortium.org" />
+ </valueIdentifier>
+ </extension>
+ <extension url="role">
+ <valueCoding>
+ <system value="http://highmed.org/fhir/CodeSystem/organization-role" />
+ <code value="SOME_ROLE" />
+ </valueCoding>
+ </extension>
+ </extension>
+ <system value="http://highmed.org/fhir/CodeSystem/process-authorization" />
+ <code value="LOCAL_ROLE" />
+ </valueCoding>
+ </extension>
+</extension>
+hello-hrp.bpmn to the TutorialProcessPluginDefinition and configure the FHIR resources needed for the three processes.HelloCos, HelloHrpMessage , HelloHrp and GoodbyeDicMessage classes as spring beans.Execute a maven build of the dsf-process-tutorial parent module via:
mvn clean install -Pexercise-5
+Verify that the build was successful and no test failures occurred.
To verify the highmedorg_helloDic, highmedorg_helloCos and highmedorg_helloHrp processes can be executed successfully, we need to deploy them into DSF instances and execute the highmedorg_helloDic process. The maven install build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker test setup.
Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-fhir
+Verify the DSF FHIR server started successfully.
Test_DIC organization in a second console at location .../dsf-process-tutorial/test-setup:docker-compose up dic-bpe
+Verify the DSF BPE server started successfully and deployed the highmedorg_helloDic process.
Test_COS organization in a third console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-fhir
+Verify the DSF FHIR server started successfully.
Test_COS organization in a fourth console at location .../dsf-process-tutorial/test-setup:docker-compose up cos-bpe
+Verify the DSF BPE server started successfully and deployed the highmedorg_helloDic process.
Test_HRP organization in a fifth at location .../dsf-process-tutorial/test-setup:docker-compose up hrp-fhir
+Test_HRP organization in a sixth console at location .../dsf-process-tutorial/test-setup:docker-compose up hrp-bpe
+Based on the value of the Task.input parameter you send, the highmedorg_helloHrp process will either send a goodbyDic message to the Test_DIC organization or finish without sending a message.
To trigger the goodbyDic message, use send-response as the http://highmed.org/fhir/CodeSystem/tutorial#tutorial-input input parameter.
Verify that the highmedorg_helloDic process either finishes with the arrival of the goodbyDic message or after waiting for two minutes.
Prerequisites | Exercise 1 | Exercise 1.1 | Exercise 2 | Exercise 3 | Exercise 4 | Exercise 5
"}');export{St as comp,zt as data}; diff --git a/assets/feasibility.html-BlROhjZY.js b/assets/feasibility.html-BlROhjZY.js new file mode 100644 index 000000000..e8d9cae60 --- /dev/null +++ b/assets/feasibility.html-BlROhjZY.js @@ -0,0 +1 @@ +import{_ as a}from"./plugin-vue_export-helper-DlAUqK2U.js";import{r as s,o as n,c as o,a as e,b as i,d as r}from"./app-9qxDwvDG.js";const l={},c=e("h2",{id:"overview",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#overview"},[e("span",null,"Overview")])],-1),h={href:"https://www.forschen-fuer-gesundheit.de/menu_standorte.php",target:"_blank",rel:"noopener noreferrer"},d={href:"https://github.com/medizininformatik-initiative/feasibility-dsf-process/",target:"_blank",rel:"noopener noreferrer"},f={href:"https://www.forschen-fuer-gesundheit.de/",target:"_blank",rel:"noopener noreferrer"},m={href:"https://www.medizininformatik-initiative.de/sites/default/files/2023-05/20230509_TMF_Faltflyer_A4_digital.pdf",target:"_blank",rel:"noopener noreferrer"},u=e("h2",{id:"the-feasibility-process",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-feasibility-process"},[e("span",null,"The Feasibility Process")])],-1),p=e("p",null,"Medical routine data holds great promise for advancing research, yet its integration into a research context poses significant challenges. To address this, Medical Data Integration Centers have been established, by the medical informatics initiative to consolidate data from primary information systems into a central repository. However, relying on data from only one organization is rarely sufficient to answer complex research questions, so merging data across institutional boundaries is necessary.",-1),b={href:"https://github.com/medizininformatik-initiative/feasibility-dsf-process/",target:"_blank",rel:"noopener noreferrer"},y=e("h2",{id:"technical-information",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#technical-information"},[e("span",null,"Technical Information")])],-1),_={href:"https://github.com/medizininformatik-initiative/feasibility-deploy/wiki/DSF-Middleware-Setup",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/medizininformatik-initiative/feasibility-dsf-process/",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/medizininformatik-initiative/feasibility-deploy/tree/main/feasibility-triangle",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/medizininformatik-initiative/mii-dsf-processes/tree/main",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/medizininformatik-initiative/mii-dsf-processes/blob/main/mii-dsf-processes-docker-test-setup/README-Process-Projectathon-Data-Sharing.md",target:"_blank",rel:"noopener noreferrer"};function F(T,z){const t=s("ExternalLinkIcon");return n(),o("div",null,[c,e("p",null,[i("Funded by the German Federal Ministry of Research and Education, 25 "),e("a",h,[i("sites"),r(t)]),i(" have installed the DSF to execute the "),e("a",d,[i("Feasibility"),r(t)]),i(" process. To perform feasibility queries, a researcher can register and query data on the "),e("a",f,[i("FDPG (Forschungsdaten Portal für Gesundheit - Research Data Portal)"),r(t)]),i(" website. Basic data of hospitalizations of over 8 million patients with over 40 million diagnoses and much more such as laboratory values or drug prescriptions are available. After a successful query, the data is made available in standardized FHIR format. Further information can be found in the "),e("a",m,[i("flyer"),r(t)]),i(".")]),u,p,e("p",null,[i("To enable researchers to leverage this integrated data for specific research projects, there is a critical need for the ability to query cohort sizes across institutions. The "),e("a",b,[i("feasibility"),r(t)]),i(" process allows researchers to conduct automated and distributed feasibility queries, i.e., cohort size estimates. This process is executed according to the open standard BPMN 2.0, the underlying process data model is based on HL7 FHIR R4 resources.")]),y,e("ul",null,[e("li",null,[e("a",_,[i("DSF Middleware Setup"),r(t)]),i(": The DSF middleware connects your site to the central platform. This allows it to receive feasibility query requests as well as reporting back any results of these queries.")]),e("li",null,[e("a",g,[i("Feasibility Process"),r(t)]),i(": Core Feasibility Process")]),e("li",null,[e("a",v,[i("Feasibility Triangle"),r(t)]),i(": The Feasibility Triangle part of this repository provides a site (data integration center) with all the necessary components to set up in order to allow feasibility queries from the central feasibility portal.")]),e("li",null,[e("a",w,[i("Data Transfer"),r(t)])]),e("li",null,[e("a",k,[i("Data extraction after successful feasibility query"),r(t)])])])])}const q=a(l,[["render",F],["__file","feasibility.html.vue"]]),P=JSON.parse('{"path":"/intro/use-cases/feasibility.html","title":"Feasibility","lang":"en-US","frontmatter":{"title":"Feasibility","icon":"diagram"},"headers":[{"level":2,"title":"Overview","slug":"overview","link":"#overview","children":[]},{"level":2,"title":"The Feasibility Process","slug":"the-feasibility-process","link":"#the-feasibility-process","children":[]},{"level":2,"title":"Technical Information","slug":"technical-information","link":"#technical-information","children":[]}],"git":{"createdTime":1690473388000,"updatedTime":1698661553000,"contributors":[{"name":"Simon Mödinger","email":"smoeding@stud.hs-heilbronn.de","commits":3},{"name":"Simon Schweizer","email":"simon-tobias.schweizer@hs-heilbronn.de","commits":1}]},"readingTime":{"minutes":1.23,"words":370},"filePathRelative":"intro/use-cases/feasibility.md","localizedDate":"July 27, 2023","excerpt":"Funded by the German Federal Ministry of Research and Education, 25 sites have installed the DSF to execute the Feasibility process. To perform feasibility queries, a researcher can register and query data on the FDPG (Forschungsdaten Portal für Gesundheit - Research Data Portal) website. Basic data of hospitalizations of over 8 million patients with over 40 million diagnoses and much more such as laboratory values or drug prescriptions are available. After a successful query, the data is made available in standardized FHIR format. Further information can be found in the flyer.
"}');export{q as comp,P as data}; diff --git a/assets/fhir.html-B1Jq6wdi.js b/assets/fhir.html-B1Jq6wdi.js new file mode 100644 index 000000000..f6c6582b3 --- /dev/null +++ b/assets/fhir.html-B1Jq6wdi.js @@ -0,0 +1 @@ +import{_ as e}from"./plugin-vue_export-helper-DlAUqK2U.js";import{o as r,c as s,e as i}from"./app-9qxDwvDG.js";const t={},o=i('Please also check common parameters for additional configuration options.
/run/secrets/app_client_certificate.pem/run/secrets/app_client_certificate_private_key.pem/run/secrets/app_client_certificate_private_key.pem.password200010000/run/secrets/app_server_trust_certificates.pemtruefalsetruefalse2/run/secrets/db_liquibase.passwordliquibase_userjdbc:postgresql://db/fhirfhir_users/run/secrets/db_user.passwordfhir_permanent_delete_users/run/secrets/db_user_permanent_delete.passwordfhir_server_permanent_delete_userfhir_server_userhttps://foo.bar/fhirconf/bundle.xmlhospital.com20falsefalse for developmenttruefoo.bar, test.com:8080http://proxy.foo:8080Please also check common parameters for additional configuration options.
\\n/run/secrets/app_client_certificate.pem