Therapy Normalization
Services and guidelines for normalizing drug (and non-drug therapy) terms
Developer instructions
The following sections include instructions specifically for developers.
Installation
For a development install, we recommend using Pipenv. See the pipenv docs for direction on installing pipenv in your compute environment.
Once installed, from the project root dir, just run:
pipenv sync
Deploying DynamoDB Locally
We use Amazon DynamoDB for data storage. To deploy locally, follow these instructions.
Initialize development environment
Code style is managed by flake8 and checked prior to commit.
We use pre-commit to run conformance tests.
This ensures:
- Style correctness
- No large files
- AWS credentials are present
- Private key is present
Pre-commit must be installed before your first commit. Use the following command:
pre-commit install
Running tests
Unit tests are run with pytest.
pipenv run pytest
We also provide Tox settings to test in multiple environments and check for proper type annotations and code style. If interpreters for Python 3.8 and Python 3.9 are present, the following will run all tests for all environments:
tox
Updating the database
Before you use the CLI to update the database, run the following in a separate terminal to start DynamoDB on port 8000:
java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb
To change the port, simply add -port value.
Setting Environment Variables
RxNorm requires a UMLS license, which you can register for one here.
You must set the RxNORM_API_KEY environment variable to your API key. This can be found in the UTS 'My Profile' area after singing in.
export RXNORM_API_KEY={rxnorm_api_key}
HemOnc.org data requires a Harvard Dataverse API key. After creating a user account on the Harvard Dataverse website, you can follow these instructions to generate a key. Once you have a key, set the following environment variable:
export DATAVERSE_API_KEY={your api key}
Update source(s)
The Therapy Normalizer currently aggregates therapy data from:
- ChEMBL
- ChemIDPlus
- DrugBank (using CC0 data only)
- Drugs@FDA
- The IUPHAR/BPS Guide to PHARMACOLOGY
- HemOnc.org (using CC-BY data only).
- The National Cancer Institute Thesaurus
- RxNorm
- Wikidata
To update source(s), simply set --normalizer to the source(s) you wish to update separated by spaces. For example, the following command updates ChEMBL and Wikidata:
python3 -m therapy.cli --normalizer="chembl wikidata"
You can update all sources at once with the --update_all flag:
python3 -m therapy.cli --update_all
The data/ subdirectory within the package source should house all desired input data. Files for all sources should follow the naming convention demonstrated below (with version numbers/dates changed where applicable).
therapy/data
├── chembl
│ └── chembl_27.db
├── chemidplus
│ └── chemidplus_20200327.xml
├── drugbank
│ └── drugbank_5.1.8.csv
├── guidetopharmacology
│ ├── guidetopharmacology_ligand_id_mapping_2021.3.tsv
│ └── guidetopharmacology_ligands_2021.3.tsv
├── hemonc
│ ├── hemonc_concepts_20210225.csv
│ ├── hemonc_rels_20210225.csv
│ └── hemonc_synonyms_20210225.csv
├── ncit
│ └── ncit_20.09d.owl
├── rxnorm
│ ├── drug_forms.yaml
│ └── rxnorm_20210104.RRF
└── wikidata
└── wikidata_20210425.json
Updates to the HemOnc source depend on the Disease Normalizer service. If the Disease Normalizer database appears to be empty or incomplete, updates to HemOnc will also trigger a refresh of the Disease Normalizer database. See its README for additional data requirements.
Create Merged Concept Groups
The /normalize endpoint relies on merged concept groups. The --update_merged flag generates these groups:
python3 -m therapy.cli --update_merged
Specifying the database URL endpoint
The default URL endpoint is http://localhost:8000.
There are two different ways to specify the database URL endpoint.
The first way is to set the --db_url flag to the URL endpoint.
python3 -m therapy.cli --update_all --db_url="http://localhost:8001"
The second way is to set the environment variable THERAPY_NORM_DB_URL to the URL endpoint.
export THERAPY_NORM_DB_URL="http://localhost:8001"
python3 -m therapy.cli --update_all
Starting the therapy normalization service
From the project root, run the following:
uvicorn therapy.main:app --reload
Next, view the OpenAPI docs on your local machine:
Metadata
Release files for thera-py 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| thera-py-0.3.1.tar.gz | 45.1 kB | Without provenance | Details for thera-py-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| thera_py-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for thera_py-0.3.1-py3-none-any.whl |
Total release size: 100.3 kB
Release files / thera-py-0.3.1.tar.gz
| Download URL | thera-py-0.3.1.tar.gz |
|---|---|
| Size | 45.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c900196354e6ab6b00c3175d3061930280ee415b32ae866f1fc5da6778f637d
|
|
BLAKE2b-256 checksum How to use checksums |
fa5f94d6cf1009df2467b5fa62a5bd8ea524637aac5f0caf65dd64d032641f2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Release files / thera_py-0.3.1-py3-none-any.whl
| Download URL | thera_py-0.3.1-py3-none-any.whl |
|---|---|
| Size | 55.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1cdf803637df9ce1a57d6cfcfabed8dbfaa9c88408b835698196cbf07b039f5
|
|
BLAKE2b-256 checksum How to use checksums |
d17f143433ebde7e81b511a91abc625830dd0074e45bf2fa131a5cd30d19fb4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.0
|
Security for thera-py 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.