BfArM Terminologies - Versionsgeschichte

Billig am 28. Oktober 2025 um 21:30 Uhr

2025-10-28T21:30:00Z

Billig am 28. Oktober 2025 um 14:01 Uhr

2025-10-28T14:01:26Z

Billig am 24. September 2025 um 10:50 Uhr

2025-09-24T10:50:25Z

Billig am 24. September 2025 um 10:48 Uhr

2025-09-24T10:48:25Z

Billig am 24. September 2025 um 10:38 Uhr

2025-09-24T10:38:25Z

Billig am 22. September 2025 um 12:24 Uhr

2025-09-22T12:24:52Z

Billig am 22. September 2025 um 12:21 Uhr

2025-09-22T12:21:46Z

Billig am 22. September 2025 um 12:07 Uhr

2025-09-22T12:07:15Z

Billig am 22. September 2025 um 11:54 Uhr

2025-09-22T11:54:48Z

Billig am 22. September 2025 um 11:53 Uhr

2025-09-22T11:53:34Z

@@ Zeile 15: / Zeile 15: @@
 </pre>
 <h2 id="specification-file-sf">Specification File (<strong>SF</strong>)</h2>
-<syntaxhighlight lang="json">
+<syntaxhighlight lang="json" line>
+{
      "terminologyDesignator": "fhir-package",
@@ Zeile 60: / Zeile 60: @@
 </ul>
 <h3 id="example">Example</h3>
-<syntaxhighlight lang="json">
+<syntaxhighlight lang="json" line>
+{
      "terminologyDesignator": "fhir-package",

@@ Zeile 1: / Zeile 1: @@
 <p>BfArM (Bundesinstitut für Arzneimittel und Medizinprodukte) provides the standard terminologies for Germany. To load these standard terminologies the customer has to create a dedicated directory (called <strong>LD</strong> in the following) together with a specification json file (<strong>SF</strong>). In context of docker, kubernetes etc. a dedicated volume should be used.</p>
 <h2 id="packages">Packages</h2>
-<p>The packages downloaded from bfarm must be located in directory <strong>LD</strong><code>/packages</code>. The following structure is an example for two packages (ICDGM, OPS) with the specification file <code>fhir-pack-icd.jsonc</code> (<strong>SF</strong>).</p>
+<p>The packages downloaded from bfarm must be located in directory <strong>LD</strong><code>/packages</code> (e.g. <strong>LD</strong> = <code>bfarm</code>). The following structure is an example for two packages (ICDGM, OPS) with the specification file <code>fhir-pack-icd.jsonc</code> (<strong>SF</strong>).</p>
 <pre>
 bfarm
@@ Zeile 15: / Zeile 15: @@
 </pre>
 <h2 id="specification-file-sf">Specification File (<strong>SF</strong>)</h2>
-<pre>
+<syntaxhighlight lang="json">
+{
      "terminologyDesignator": "fhir-package",
      "canonicalUrlRegex": "<regex>", // optional
-     "canonicalPackageRegex": "<regex>", // optional
+     "packageRegex": "<regex>", // optional
      "loadGrouping": true // optional
+}
-</pre>
+</syntaxhighlight>
 <ul>
 <li>
 <p><code>canonicalUrlRegex</code></p>
@@ Zeile 36: / Zeile 42: @@
 </li>
 <li>
-<p><code>canonicalPackageRegex</code></p>
+<p><code>packageRegex</code></p>
 <ul>
 <li>this filter loads only packages whose <em>canonical package name</em> conforms to <code>&lt;regex&gt;</code>. The <em>canonical package name</em> ist defined as the form <code>&lt;name&gt;|&lt;version&gt;</code> where <code>name</code> and <code>version</code> are the properties in the package definition file
@@ Zeile 54: / Zeile 60: @@
 </ul>
 <h3 id="example">Example</h3>
-<pre>
+<syntaxhighlight lang="json">
+{
      "terminologyDesignator": "fhir-package",
      "canonicalUrlRegex": ".*(agerejec|exotic|einmalk).*",
-     "canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
+     "packageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
      "loadGrouping": true
+}
-</pre>
+</syntaxhighlight>
 <p>In this example only the terminologies for age rejection and the exotic one of the ICD as well as the one-time codes of the OPS package will be loaded.</p>
 <h2 id="rest-interface">REST interface</h2>

← Nächstältere Version		Version vom 24. September 2025, 10:50 Uhr
Zeile 1:		Zeile 1:
−	~~<h1 id="loading-bfarm-terminologies">Loading BfArM Terminologies</h1>~~
	<p>BfArM (Bundesinstitut für Arzneimittel und Medizinprodukte) provides the standard terminologies for Germany. To load these standard terminologies the customer has to create a dedicated directory (called <strong>LD</strong> in the following) together with a specification json file (<strong>SF</strong>). In context of docker, kubernetes etc. a dedicated volume should be used.</p>		<p>BfArM (Bundesinstitut für Arzneimittel und Medizinprodukte) provides the standard terminologies for Germany. To load these standard terminologies the customer has to create a dedicated directory (called <strong>LD</strong> in the following) together with a specification json file (<strong>SF</strong>). In context of docker, kubernetes etc. a dedicated volume should be used.</p>
	<h2 id="packages">Packages</h2>		<h2 id="packages">Packages</h2>

← Nächstältere Version		Version vom 24. September 2025, 10:48 Uhr
Zeile 66:		Zeile 66:
	<h2 id="rest-interface">REST interface</h2>		<h2 id="rest-interface">REST interface</h2>
	<p>The interface is exactly the same as described the context of <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface classical loading]</code> (non-BfArM).</p>		<p>The interface is exactly the same as described the context of <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface classical loading]</code> (non-BfArM).</p>
		+	<h2 id="remark">Remark</h2>
		+	<p>Standard terminologies should preferably be loaded in accordance with the specification described here, if they are offered by BfArM. For terminologies that are not included in BfArM, the <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies previous specification]</code> can be used.</p>

@@ Zeile 65: / Zeile 65: @@
 <p>In this example only the terminologies for age rejection and the exotic one of the ICD as well as the one-time codes of the OPS package will be loaded.</p>
 <h2 id="rest-interface">REST interface</h2>
-<p>The interface is exactly the same as described in section <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface here]</code>.</p>
+<p>The interface is exactly the same as described the context of <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface classical loading]</code> (non-BfArM).</p>

@@ Zeile 1: / Zeile 1: @@
-<h1 id="loading-bfarm-terminologies">Loading BfArM Terminologies</h1>
+            <h1 id="loading-bfarm-terminologies">Loading BfArM Terminologies</h1>
 <p>BfArM (Bundesinstitut für Arzneimittel und Medizinprodukte) provides the standard terminologies for Germany. To simplify the loading process, an extra Y is defined, which can be executed with the existing interface for loading standard terminologies.
 Due to license policies of standard terminology providers we do not make available provider input files. Customers have to download these files from provider sites.</p>
@@ Zeile 9: / Zeile 9: @@
 |_ packages
 |  |_ bfarm.terminologien.icd10gm-2025.0.0.tar.gz
-|  |  |_ CodeSystem-icd10gm-agelow-2025.json
+|  |  |_ package/CodeSystem-icd10gm-agelow-2025.json
-|  |  |_ CodeSystem-icd10gm-agereject-2025.json
+|  |  |_ package/CodeSystem-icd10gm-agereject-2025.json
-|  |  |_ package.json
+|  |  |_ package/package.json
 |  |  |_ ...
 |  |_ bfarm.terminologien.ops-2025.0.0.tar.gz
 |_ fhir-pack-icd.jsonc
 </pre>
@@ Zeile 51: / Zeile 52: @@
 <p><code>loadGrouping</code></p>
 <ul>
-<li>if enabled the grouping for the navigator is automatically set. Note that it overwrites the present grouping. If the grouping is to be integrated into an existing one, the REST interface for <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/Grouping#REST_calls read and write groupings]</code> can be used.</li>
+<li>if enabled the grouping for the navigator is automatically set. Note that it overwrites the present grouping. If the grouping has to be integrated into an existing one, the REST interface for <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/Grouping#REST_calls read and write groupings]</code> can be used.</li>
 </ul>
 </li>
@@ Zeile 64: / Zeile 65: @@
+}
 </pre>
 <h2 id="rest-interface">REST interface</h2>
 <p>The interface is exactly the same as described in section <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface here]</code>.</p>

@@ Zeile 37: / Zeile 37: @@
 </li>
 <li>
-<p><code>loadGrouping</code>: if enabled the grouping for the navigator is automatically set. Note that it overwrites the present grouping. If the grouping is to be integrated into an existing one, the interface for <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/Grouping#REST_calls read and write groupings]</code> can be used.</p>
+<p><code>loadGrouping</code>: if enabled the grouping for the navigator is automatically set. Note that it overwrites the present grouping. If the grouping is to be integrated into an existing one, the REST interface for <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/Grouping#REST_calls read and write groupings]</code> can be used.</p>
 </li>
 </ul>
@@ Zeile 50: / Zeile 50: @@
 </pre>
 <h2 id="rest-interface">REST interface</h2>
-<p>see !!!</p>
+<p>The interface is exactly the same as described in section <code>[https://websites.fraunhofer.de/CTS2-LE/index.php/CTS2-LE_Supported_Terminologies#REST_interface REST interface]</code>.</p>