Indivo Fields.
Custom-defined Django Model Field subclasses used for representing Medical Data via the Django ORM.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a physical address.
Creating an AddressField named ‘address’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original address field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a blood pressure measurement.
Creating a BloodPressureField named ‘bp’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original bp field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing coded data elements.
Creating a CodedValueField named ‘value’, for example, will (under the hood) create thee fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original value field name.
Bases: django.db.models.fields.Field
A field that should be replaced by other fields.
replacements should be a mapping from field_suffix to (fieldclass, field_kwargs). This instructs the datamodel loader to remove this field, and for each entry in the mapping, to add a new field with the original name concatenated with field_suffix, which is an instance of class fieldclass instantiated with field_kwargs.
Eventually, when Django supports fields mapping to multiple database columns, these fields should actually manage multiple DB columns, but for now we’re just using strict substitution.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a person’s name.
Creating a NameField named ‘name’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original name field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing an organization.
Creating an OrganizationField named ‘organization’, for example, will (under the hood) create two fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original organization field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a pharmacy.
Creating a PharmacyField named ‘pharmacy’, for example, will (under the hood) create three fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original pharmacy field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a medical provider.
Creating a ProviderField named ‘doc’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original doc field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a quantitative result, and expected ranges for that result.
Creating a QuantitativeResultField named ‘lab_result’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original lab_result field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a telephone number.
Creating a TelephoneField named ‘phone’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original phone field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing data elements with both a value and a unit.
Creating a ValueAndUnitField named ‘frequency’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original frequency field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a range of values.
Creating a ValueRangeField named ‘normal_range’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original normal_range field name.
Bases: indivo.fields.dummy_fields.DummyField
A field for representing a single measurement of a vital sign.
Creating a VitalSignField named ‘bp’, for example, will (under the hood) create the fields:
When describing instances of your model (either when defining a transform output or when referencing fields using the Indivo Query API), you must refer to these field names, not the original bp field name.