BfArM Terminologies: Unterschied zwischen den Versionen
Billig (Diskussion | Beiträge) |
Billig (Diskussion | Beiträge) |
||
| 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. | + | <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> | ||
<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>. 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> | ||
Version vom 22. September 2025, 14:24 Uhr
Inhaltsverzeichnis
Loading BfArM Terminologies
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 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 | | |_ package/CodeSystem-icd10gm-agelow-2025.json | | |_ package/CodeSystem-icd10gm-agereject-2025.json | | |_ package/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 terminologiesCodeSystem-icd10gm-agereject-2025.jsonandCodeSystem-icd10gm-agelow-2025.jsonbecause its canonical URLs arehttps: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agereject|2025andhttps: //terminologien.bfarm.de/fhir/CodeSystem/icd10gm-agelow|2025, respectively.
- this filter loads only terminologies whose canonical URL (
-
canonicalPackageRegex- this filter loads only packages whose canonical package name conforms to
<regex>. The canonical package name ist defined as the form<name>|<version>wherenameandversionare the properties in the package definition filebfarm/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.
- this filter loads only packages whose canonical package name conforms to
-
loadGrouping- 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
read and write groupingscan be used.
- 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
Example
{
"terminologyDesignator": "fhir-package",
"canonicalUrlRegex": ".*(agerejec|exotic|einmalk).*",
"canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
"loadGrouping": true
}
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.
REST interface
The interface is exactly the same as described in section here.