Skip to main content

pypi actions codecov downloads

edc-adverse-event

Create an AE application

Create an AE app that will house your AE concrete models, admin site, list data, and action items.

Adverse events models

Model mixins exist for you to create the following concrete models in your AE app:

  • AE Initial: The initial report of a adverse event

  • AE Followup: 1 or more follow-ups to the initial AE report

  • AE Special Interest

  • AE SUSAR

  • AE External Reviewer

  • Death Report

  • Death Report External Reviewer

TMG: Trial Management Group forms

  • AE Tmg:

Settings

These are the settings attributes you need to define for edc_adverse_event:

# settings.py

...

ADVERSE_EVENT_APP_LABEL="edc_adverse_event"  # replace with your AE app label
ADVERSE_EVENT_ADMIN_SITE="edc_adverse_event_admin"  # replave with your AE app admin site name

...

Define a list_data.py

There are a few FK fields on the AE models. You need to define a list_data.py that will be read to populate the FK list models.

The list model tables are: * edc_adverse_event.aeclassification (See AeInitial) * edc_adverse_event.saereason (See AeInitial)

# list_data.py

list_data = {
    "edc_adverse_event.aeclassification": [
        (ANAEMIA, "Anaemia"),
        ("diarrhoea", "Diarrhoea"),
        (RENAL_IMPAIRMENT, "Renal impairment"),
        (OTHER, "Other"),
    ],
    "edc_adverse_event.saereason": [
        (NOT_APPLICABLE, "Not applicable"),
        (DEAD, "Death"),
        ("life_threatening", "Life-threatening"),
        ("significant_disability", "Significant disability"),
        (
            "in-patient_hospitalization",
            (
                "In-patient hospitalization or prolongation "
                "(17 or more days from study inclusion)"
            ),
        ),
        (
            "medically_important_event",
            "Medically important event (e.g. recurrence of symptoms not requiring admission, "
            "Hospital acquired pneumonia)",
        ),
    ],
}

preload_data = PreloadData(
    list_data=list_data, model_data={}, unique_field_data=None)

Register AE Action Items

The AE action items are not registered by default. To register, in the root of your AE app add an action_items.py:

# action_items.py

from edc_adverse_event.action_items import AeInitialAction
from edc_adverse_event.action_items import AeFollowupAction
from edc_adverse_event.action_items import AeSusarAction
from edc_adverse_event.action_items import AeTmgAction

site_action_items.register(AeInitialAction)
site_action_items.register(AeFollowupAction)
site_action_items.register(AeTmgAction)
site_action_items.register(AeSusarAction)

Metadata

Release files for edc-adverse-event 1.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for edc-adverse-event 1.1.2
File Size Uploaded Provenance Actions
edc_adverse_event-1.1.2.tar.gz 77.3 kB Without provenance Details for edc_adverse_event-1.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for edc-adverse-event 1.1.2
File Interpreter ABI Platform Actions
edc_adverse_event-1.1.2-py3-none-any.whl Python 3 none any Details for edc_adverse_event-1.1.2-py3-none-any.whl

Total release size: 238.6 kB

Release files / edc_adverse_event-1.1.2.tar.gz

Download URL edc_adverse_event-1.1.2.tar.gz
Size 77.3 kB
Tags Source
SHA-256 checksum
How to use checksums
afda43d5cdfdfafb672a31428512a1026c0168c8f87b51418eaeab7102db97a3
BLAKE2b-256 checksum
How to use checksums
1ec0b88e61a2fa03b430afe4baae495be453aaf9435eb0bef436f850b282f0b9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.4

Release files / edc_adverse_event-1.1.2-py3-none-any.whl

Download URL edc_adverse_event-1.1.2-py3-none-any.whl
Size 161.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
40e93576613dcaae0a80b380c2be684119da6d4b0198a8afc94898cfa1977143
BLAKE2b-256 checksum
How to use checksums
abec8edc1aa09c750fcdc14d4af102c16f4cf12092e76fd8e9d83a6034f13039
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.4

Security for edc-adverse-event 1.1.2

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.

Release history Release notifications | RSS feed

This release

1.1.2 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page