Base classes for visit reports/tracking in clinicedc/edc
Project description
edc-visit-tracking
Track study participant visit reports.
Declaring a visit model
A visit_model is declared using the model mixin VisitModelMixin. Normally, a visit_model will be declared with additional model mixins, but VisitModelMixin must be there.
class SubjectVisit(VisitModelMixin, BaseUuidModel):
...
Also, ensure the Meta class attributes of VisitModelMixin are inherited. These include required constraints and ordering.
class SubjectVisit(VisitModelMixin, BaseUuidModel):
...
class Meta(VisitModelMixin.Meta):
pass
Among other features, VisitModelMixin adds a OneToOneField foreign key to the visit_model that points to edc_appointment.Appointment.
Important: A visit model is a special model in the EDC. A model declared with the model mixin, VisitModelMixin, is the definition of a visit model. CRFs and Requisitions have a foreign key pointing to a visit model. A number of methods on CRFs and Requisitions detect their visit model foreign key name, model class and value by looking for the FK declared with VisitModelMixin.
For a subject that requires ICF the visit model would use the RequiresConsentModelMixin:
class SubjectVisit(
VisitModelMixin,
RequiresConsentFieldsModelMixin,
BaseUuidModel,
):
class Meta(VisitModelMixin.Meta, BaseUuidModel.Meta):
pass
If the subject does not require ICF, such as an infant, don’t include the RequiresConsentModelMixin:
class InfantVisit(
VisitModelMixin,
BaseUuidModel
):
class Meta(VisitModelMixin.Meta, , BaseUuidModel.Meta):
pass
A more complete declaration will include model mixins from other libraries. For example:
from edc_consent.model_mixins import RequiresConsentFieldsModelMixin
from edc_metadata.model_mixins.creates import CreatesMetadataModelMixin
from edc_model.models import BaseUuidModel
from edc_offstudy.model_mixins import OffstudyVisitModelMixin
from edc_sites.managers import CurrentSiteManager
from edc_sites.model_mixins import SiteModelMixin
from edc_visit_tracking.managers import VisitModelManager
from edc_visit_tracking.model_mixins import VisitModelMixin
class SubjectVisit(
SiteModelMixin,
VisitModelMixin,
CreatesMetadataModelMixin,
RequiresConsentFieldsModelMixin,
OffstudyNonCrfModelMixin,
BaseUuidModel,
):
objects = VisitModelManager()
on_site = CurrentSiteManager()
history = edc_models.HistoricalRecords()
class Meta(VisitModelMixin.Meta, BaseUuidModel.Meta):
pass
Declaring a CRF
The CrfModelMixin is required for all CRF models. CRF models have a OneToOneField key to a visit model.
class CrfOne(CrfModelMixin, OffstudyCrfModelMixin, RequiresConsentModelMixin,
UpdatesCrfMetadataModelMixin, BaseUuidModel):
subject_visit = models.OneToOneField(SubjectVisit)
f1 = models.CharField(max_length=10, default='erik')
vl = models.CharField(max_length=10, default=NO)
rdb = models.CharField(max_length=10, default=NO)
class Meta:
consent_model = 'myapp.subjectconsent' # for RequiresConsentModelMixin
Declaring forms:
The VisitFormMixin includes a number of common validations in the clean method:
class SubjectVisitForm(VisitFormMixin, FormValidatorMixin, forms.ModelForm):
form_validator_cls = VisitFormValidator
class Meta:
model = SubjectVisit
PreviousVisitModelMixin
The PreviousVisitModelMixin ensures that visits are entered in sequence. It is included with the VisitModelMixin.
VisitTrackingModelFormMixin
see DEFAULT_REPORT_DATETIME_ALLOWANCE
Missed Visit Report
A detail report should be submitted for scheduled visits that are missed. By selecting the reason missed visit on SubjectVisit, only the missed visit CRF will be required for the timepoint. All other CRFs and requisitions will be excluded.
Unscheduled visits cannot be missed. (To change this behaviour see settings attrubute EDC_VISIT_TRACKING_ALLOW_MISSED_UNSCHEDULED)
The model mixin SubjectVisitMissedModelMixin provides the basic features of a SubjectVisitMissed model.
In your subject app declare:
from django.db.models import PROTECT
from edc_crf.model_mixins import CrfWithActionModelMixin
from edc_model import models as edc_models
from edc_visit_tracking.model_mixins import SubjectVisitMissedModelMixin
class SubjectVisitMissed(SubjectVisitMissedModelMixin, edc_models.BaseUuidModel):
missed_reasons = models.ManyToManyField(
SubjectVisitMissedReasons, blank=True, related_name="+"
)
class Meta(CrfWithActionModelMixin.Meta, edc_models.BaseUuidModel.Meta):
verbose_name = "Missed Visit Report"
verbose_name_plural = "Missed Visit Report"
In your list model app, e.g. meta_lists, declare the list model:
class SubjectVisitMissedReasons(ListModelMixin):
class Meta(ListModelMixin.Meta):
verbose_name = "Subject Missed Visit Reasons"
verbose_name_plural = "Subject Missed Visit Reasons"
… and update the list_data dictionary, for example:
list_data = {
...
"meta_lists.subjectvisitmissedreasons": [
("forgot", "Forgot / Can’t remember being told about appointment"),
("family_emergency", "Family emergency (e.g. funeral) and was away"),
("travelling", "Away travelling/visiting"),
("working_schooling", "Away working/schooling"),
("too_sick", "Too sick or weak to come to the centre"),
("lack_of_transport", "Transportation difficulty"),
(OTHER, "Other reason (specify below)",),
],
...
}
Window period
By default, the visit report_datetime is validated to stay within the same window period as the appointment. This may be too restrictive in some cases.
To bypass this override `validate_visit_datetime_in_window_period` in the `VisitFormValidator`
from edc_visit_tracking.form_validators import VisitFormValidator as BaseVisitFormValidator
class VisitFormValidator(BaseVisitFormValidator):
...
def validate_visit_datetime_in_window_period():
pass
...
Be sure that your appointment form validator is enforcing window periods before bypassing this check.
See also edc_appointment.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file edc-visit-tracking-0.3.91.tar.gz
.
File metadata
- Download URL: edc-visit-tracking-0.3.91.tar.gz
- Upload date:
- Size: 65.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.0.0 CPython/3.12.2
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 0726288981e4c962400a5ae3012cec37f63d7ac50a9fee7f984e53346e7e9d76 |
|
MD5 | 2728f48e764180a3f98e587e36373cbd |
|
BLAKE2b-256 | 0681883dd2c2717ae15ee22f4e40fa59bd419939d769bd8f3029914ab45e852d |
File details
Details for the file edc_visit_tracking-0.3.91-py3-none-any.whl
.
File metadata
- Download URL: edc_visit_tracking-0.3.91-py3-none-any.whl
- Upload date:
- Size: 87.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.0.0 CPython/3.12.2
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | b5591b98ade130782ebc6fd3ce14e3fcc583f6274f233c03e335f36c9e29f317 |
|
MD5 | 6b4cbe84ac7756c81f1e8b4cf629835d |
|
BLAKE2b-256 | 194593200171cc0a85b06c374dd2470b14430d22d2e43ae5b9846a0585d15859 |