BfArM Terminologies: Unterschied zwischen den Versionen
Billig (Diskussion | Beiträge) |
Billig (Diskussion | Beiträge) |
||
| Zeile 37: | Zeile 37: | ||
</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, interface [ | + | <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> |
</li> | </li> | ||
</ul> | </ul> | ||
Version vom 22. September 2025, 13:46 Uhr
Inhaltsverzeichnis
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 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.
-
canonicalPackageRegex: this filter loads only terminologies whose canonical package regex conforms to<regex>. The canonical package regex 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. -
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 interface forread and write groupingscan be used.
Example
{
"terminologyDesignator": "fhir-package",
"canonicalUrlRegex": ".*(agerejec|exotic|einmalk|icf-q-anatomische-lokalisation).*",
"canonicalPackageRegex": ".*(icd10gm\\|2025|ops\\|2025).*",
"loadGrouping": true
}
REST interface
see !!!