AI-Rad Companion Chest CT Extractor
This is a python library and command line tool for extracting the results of Siemens' AI-Rad companion Chest CT software into a relational database.
NOTICE: Command line tool only for use with an appropriate DicomConquest PACS
To install, simply use
pip install airc_extract
This will install the package and the two necessary command line programs to your python environment.
Usage
Python API
If you simply want to use the extraction method stored
in the AIRCReport class, you can import and use it in any python script with
from airc_extract.airc_report import AIRCReport
# This is the list of structured report (SR) dicoms that make up the AIRC Chest CT output
report_dicoms = ['dcm1.dcm', 'dcm2.dcm', ...]
report = AIRCReport(report_dicoms)
report.extract_report() # This is the method to pull the data
print(report.report_data) # A dictionary containing the results
Command Line
If you are using a DicomConquest server, you can use the two command line tools provided in this package to automatically create and update a SQLite database, storing the AIRC results in 6 tables. More information on these tables can be found here.
To start, you will need to run airc-create-config.
airc-create-config \
--dicom-db /path/to/conquest.db3 \ # Required (usually dicomserver/data/dbase/conquest.db3)
--dicom-data-dir /path/to/conquest/data \ # Required (usually dicomserver/data)
--data-db /path/to/output/database.db3 \ # Required. Can NOT be on a network share.
--log-level-term INFO # Terminal logging level \
--log-level-file DEBUG # Log file logging level \
--log-dir . # Directory for log files to be stored
This will setup a package config.ini file that will be used for extraction, as well as test the connection to the DicomConquest database and the output database.
It will create a new output database with all necessary tables at the specified path if it does not exist.
After this, just run
airc-extract
and all the series not found in the output database will be extracted and inserted into the output database.
Metadata
Release files for airc-extract 0.2.3
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 |
|---|---|---|---|---|
| airc_extract-0.2.3.tar.gz | 11.0 kB | Without provenance | Details for airc_extract-0.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airc_extract-0.2.3-py3-none-any.whl | Python 3 | none | any | Details for airc_extract-0.2.3-py3-none-any.whl |
Total release size: 23.4 kB
Release files / airc_extract-0.2.3.tar.gz
| Download URL | airc_extract-0.2.3.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0720e44bc025703742938b0339a98da31334e6821db55850fc02ab4f135aa2c
|
|
BLAKE2b-256 checksum How to use checksums |
44e81b6ea091550750c4a433dd916047c1298f86f5462d957b21292e8ed0af52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.2
|
Release files / airc_extract-0.2.3-py3-none-any.whl
| Download URL | airc_extract-0.2.3-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4322f8c0189f9995a5aac29237298c5630a1a352a53bf843a64e3d99d5a6e93d
|
|
BLAKE2b-256 checksum How to use checksums |
23515f5152ee42cea6873c6cd4f772ee9733eb65252fa9135d6e9dbfee6b6f29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.2
|
Security for airc-extract 0.2.3
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.