BfArM Terminologies: Unterschied zwischen den Versionen

Aus CTS2-LE
Zur Navigation springen Zur Suche springen
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.
 
<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>
 
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 27: Zeile 27:
 
<ul>
 
<ul>
 
<li>
 
<li>
−
<p><code>canonicalUrlRegex</code>: this filter loads only terminologies whose <em>canonical URL</em> (<code>https://hl7.org/fhir/R4/datatypes.html#canonical</code>) conforms to <code>&lt;regex&gt;</code>. E.g., regex <code>.*(agerejec|agelow).*</code> will only load the terminologies <code>CodeSystem-icd10gm-agereject-2025.json</code> and <code>CodeSystem-icd10gm-agelow-2025.json</code> because its canonical URLs are</p>
+
<p><code>canonicalUrlRegex</code></p>
 +
<ul>
 +
<li>this filter loads only terminologies whose <em>canonical URL</em> (<code>https://hl7.org/fhir/R4/datatypes.html#canonical</code>) conforms to <code>&lt;regex&gt;</code>. E.g., regex <code>.*(agerejec|agelow).*</code> will only load the terminologies <code>CodeSystem-icd10gm-agereject-2025.json</code> and <code>CodeSystem-icd10gm-agelow-2025.json</code> because its canonical URLs are
 
<ul>
 
<ul>
 
<li><code>https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agereject|2025</code> and</li>
 
<li><code>https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agereject|2025</code> and</li>
 
<li><code>https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agelow|2025</code>, respectively.</li>
 
<li><code>https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agelow|2025</code>, respectively.</li>
 +
</ul>
 +
</li>
 
</ul>
 
</ul>
 
</li>
 
</li>
 
<li>
 
<li>
−
<p><code>canonicalPackageRegex</code>: this filter loads only terminologies whose <em>canonical package regex</em> conforms to <code>&lt;regex&gt;</code>. The <em>canonical package regex</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 <code>bfarm/packages/bfarm.terminologien.icd10gm-2025.0.0.tar.gz/package/package.json</code> (see section Packages above). E.g., regex <code>.*(icd10gm\\|2025|ops\\|2025).*</code> will only load the ICD and OPS package.</p>
+
<p><code>canonicalPackageRegex</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
 +
<ul>
 +
<li><code>bfarm/packages/bfarm.terminologien.icd10gm-2025.0.0.tar.gz/package/package.json</code> (see section Packages above).</li>
 +
<li>E.g., regex <code>.*(icd10gm\\|2025|ops\\|2025).*</code> will only load the ICD and OPS package.</li>
 +
</ul>
 +
</li>
 +
</ul>
 
</li>
 
</li>
 
<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 REST 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></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>
 +
</ul>
 
</li>
 
</li>
 
</ul>
 
</ul>
Zeile 44: Zeile 59:
 
{
 
{
 
     "terminologyDesignator": "fhir-package",
 
     "terminologyDesignator": "fhir-package",
−
     "canonicalUrlRegex": ".*(agerejec|exotic|einmalk|icf-q-anatomische-lokalisation).*",
+
     "canonicalUrlRegex": ".*(agerejec|exotic|einmalk).*",
 
     "canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
 
     "canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
 
     "loadGrouping": true
 
     "loadGrouping": true

Version vom 22. September 2025, 14:07 Uhr

Loading BfArM Terminologies

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.

To load these standard terminologies the customer has to create a dedicated directory (called LD in the following) together with a specification json file (SF). In context of docker, kubernetes etc. a dedicated volume should be used.

Packages

The packages downloaded from bfarm must be located in directory LD/packages. The following structure is an example for two packages (ICDGM, OPS) with the specification file fhir-pack-icd.jsonc (SF).

bfarm
|_ packages
|  |_ bfarm.terminologien.icd10gm-2025.0.0.tar.gz
|  |  |_ CodeSystem-icd10gm-agelow-2025.json
|  |  |_ CodeSystem-icd10gm-agereject-2025.json
|  |  |_ package.json
|  |  |_ ...
|  |_ bfarm.terminologien.ops-2025.0.0.tar.gz
|_ fhir-pack-icd.jsonc

Specification File (SF)

{
    "terminologyDesignator": "fhir-package",
    "canonicalUrlRegex": "<regex>", // optional
    "canonicalPackageRegex": "<regex>", // optional
    "loadGrouping": true // optional
}

  • canonicalUrlRegex

    • this filter loads only terminologies whose canonical URL (https://hl7.org/fhir/R4/datatypes.html#canonical) conforms to <regex>. E.g., regex .*(agerejec|agelow).* will only load the terminologies CodeSystem-icd10gm-agereject-2025.json and CodeSystem-icd10gm-agelow-2025.json because its canonical URLs are
      • https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agereject|2025 and
      • https: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agelow|2025, respectively.

  • canonicalPackageRegex

    • this filter loads only packages whose canonical package name conforms to <regex>. The canonical package name ist defined as the form <name>|<version> where name and version are the properties in the package definition file
      • bfarm/packages/bfarm.terminologien.icd10gm-2025.0.0.tar.gz/package/package.json (see section Packages above).
      • E.g., regex .*(icd10gm\\|2025|ops\\|2025).* will only load the ICD and OPS package.

  • loadGrouping

    • 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 read and write groupings can be used.

Example

{
    "terminologyDesignator": "fhir-package",
    "canonicalUrlRegex": ".*(agerejec|exotic|einmalk).*",
    "canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
    "loadGrouping": true
}

REST interface

The interface is exactly the same as described in section here.

Abgerufen von „https://websites.fraunhofer.de/CTS2-LE/index.php?title=BfArM_Terminologies&oldid=1363“