intecomm-rando
Randomization for INTECOMM trial
A dependency of the INTECOMM trial EDC.
The INTECOMM trial is a cluster randomized trial where the unit of randomization is the patient group.
At screening, data for individual potential participants are stored in the intecomm_screening.PatientLog model. Eligible individual potential participants (model PatientLog) are added to a patient group (model intecomm_group.PatientGroup).
The data flow is PatientLog -> SubjectScreening -> if eligible -> SubjectConsent
Ideally, for a patient group to be considered for randomization, the group must contain between 9-14 screened and consented members where a count of chronic conditions of those in the group meets an approximate ratio of 2 : 1; that is, 2(DM/HTN) : 1(HIV). The site coordinators may override these values.
Once a PatientGroup is ready to randomize, the site staff open the PatientGroup form and click “randomize”.
In the background, the Randomizer class calls its method randomize_group. randomize_group picks the next available record from the randomization_list (‘’intecomm_rando.RandomizationList``) and inserts a unique group_identifier value. A records is available if group_identifier has not been set. Ordering is ascending by sid.
The PatientGroup is given its newly allocated group_identifier. The subjects in this group may now be followed longitudinally starting with visit 1000.
The group_identifier, for subjects in a PatientGroup, is updated on the PatientLog record as well.
The RegisteredGroup model holds the sid to group_identifier relationship
The RandomizationList model holds the sid to assignment to group_identifier relationship
PatientLog links group_identifier and subject_identifier
See also tables: • Intecomm_rando_registeredgroup • Intecomm_rando_randomizationlist • intecomm_screening_patientlog • intecomm_group_patientlog
Metadata
Release files for intecomm-rando 0.1.26
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 |
|---|---|---|---|---|
| intecomm_rando-0.1.26.tar.gz | 36.7 kB | Without provenance | Details for intecomm_rando-0.1.26.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intecomm_rando-0.1.26-py3-none-any.whl | Python 3 | none | any | Details for intecomm_rando-0.1.26-py3-none-any.whl |
Total release size: 77.1 kB
Release files / intecomm_rando-0.1.26.tar.gz
| Download URL | intecomm_rando-0.1.26.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08ae505eac8c4d7e94d43b3319b666da1fdf53d5522b1240535043c2a4c6e23a
|
|
BLAKE2b-256 checksum How to use checksums |
9b9d007df4df0b5809f8249d7ddc6d450e06be1a7e42005b8d9ec441e2d9dfbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / intecomm_rando-0.1.26-py3-none-any.whl
| Download URL | intecomm_rando-0.1.26-py3-none-any.whl |
|---|---|
| Size | 40.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55024ad5f0a52cd631487633c23cb225581818a6d7344ad7b6098089e7f54053
|
|
BLAKE2b-256 checksum How to use checksums |
13318f83b6068b42f6b9ce574c88a086f1bdf6b63a12382e852de75ba84dc8bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for intecomm-rando 0.1.26
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.