MIRA
Multi-source Indication & Report Analytics
Harmonising clinical trials, regulatory approvals, drug indications, and safety evidence for drug discovery.
Mira turns records from clinical-data providers into traceable Clinical Reports and aggregated Clinical Indications, with drug and disease entities mapped to the identifiers used by Open Targets.
Start with How Mira works for the concepts, data flow, and links to the detailed documentation.
Installation
pip install "opentargets-mira[ner]"
The ner extra installs the named-entity recognition models (PyTorch and Transformers) that drug and disease mapping, the EMA and PMDA providers and the mira CLI need. Without it, only the parts of Mira that do not touch NER can be imported.
For the optional legacy ChEMBL Oracle curation utilities:
pip install "opentargets-mira[oracle]"
See the documentation index for data models, providers, Python usage, and CLI configuration.
1 maintainer
Metadata
1 maintainer
Release files for opentargets-mira 1.0.5
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 |
|---|---|---|---|---|
| opentargets_mira-1.0.5.tar.gz | 396.8 kB | With provenance | Details for opentargets_mira-1.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| opentargets_mira-1.0.5-py3-none-any.whl | Python 3 | none | any | Details for opentargets_mira-1.0.5-py3-none-any.whl |
Total release size: 463.5 kB
Release files / opentargets_mira-1.0.5.tar.gz
| Download URL | opentargets_mira-1.0.5.tar.gz |
|---|---|
| Size | 396.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a0930ddf479fd87b27299cda48396b6b0d77aa593bf3f95365a74f98f0ed763
|
|
BLAKE2b-256 checksum How to use checksums |
b772ee36ebc9c710dc7e48fcd359407359032c4f3ab8cc5dea28cbaf7b7581e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / opentargets_mira-1.0.5-py3-none-any.whl
| Download URL | opentargets_mira-1.0.5-py3-none-any.whl |
|---|---|
| Size | 66.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40047413bcb5618e963360956adc4ce6b7b28879cecf3676ee15627d07348e18
|
|
BLAKE2b-256 checksum How to use checksums |
d66114075312c281e38ea441e7c721142b982f831c779cf97c12c89ddeb7b246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logSecurity for opentargets-mira 1.0.5
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for opentargets_mira-1.0.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logA 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.
