FTR from CSV
Prerequisites
Download zen-ftr CLI: Download link
Creating Aidbox Configuration project
Create a directory project
with following structure:
This ValueSet definition confirms to zen.fhir ValueSet schema and has a :ftr
property, it contains an FTR manifest that defines a csv source via :source-url
property to create an expanded version of the ValueSet to be stored in the resulting FTR. For details about FTR manifest, please, refer to this page.
Create resources/icd-10.csv
file, containing CSV source for your ValueSet:
Initialize this directory as a git repository, commit your initial set-up
Generate FTR
Replace <PATH_TO_JAR>
placeholder with absolute path to zen.jar
.
Execute command listed below in project directory:
Commit FTR directory:
Now you can run Aidbox with the following configuration project and use FHIR Terminology API methods like $validate-code/$lookup
on generated diagnosis-vs
ValueSet. Resource validation performed when someone invocates a FHIR REST operations will also validate ValueSet binding via FTR.
Initialize this directory as a git repository and commit your initial set-up:
Instruct Aidbox to load terminologies into the DB
Set the following environment variable:
By default, Aidbox does not load terminologies into the database as that can take a lot of disk space. This means that full terminology functionality won’t be available until you enable it manually. BOX_FEATURES_FTR_PULL_ENABLE environment variable is just for that. When you set it to true
, Aidbox will load terminologies into the database on the next startup and start functioning as a fully-featured terminology server.
Further steps
For guidance on development and production usage, visit the links below:
For customizing Aidbox startup behavior when using FTR, read about FTR environment variables.
Last updated