UKRDC-SQLA
SQLAlchemy models for the UKRDC and related databases.
Installation
pip install ukrdc-sqla
poetry add ukrdc-sqla
Example Usage
from datetime import datetime
from ukrdc_sqla.ukrdc import LabOrder, PatientNumber, PatientRecord, ResultItem
def commit_extra_resultitem(session):
patient_record = PatientRecord(
pid="PYTEST01:LABORDERS:00000000L",
sendingfacility="PATIENT_RECORD_SENDING_FACILITY_1",
sendingextract="PV",
localpatientid="00000000L",
ukrdcid="000000001",
repository_update_date=datetime(2020, 3, 16),
repository_creation_date=datetime(2020, 3, 16),
)
patient_number = PatientNumber(
id=2,
pid="PYTEST01:LABORDERS:00000000L",
patientid="111111111",
organization="NHS",
numbertype="NI",
)
laborder = LabOrder(
id="LABORDER_TEST2_1",
pid="PYTEST01:LABORDERS:00000000L",
external_id="EXTERNAL_ID_TEST2_1",
order_category="ORDER_CATEGORY_TEST2_1",
specimen_collected_time=datetime(2020, 3, 16),
)
resultitem = ResultItem(
id="RESULTITEM_TEST2_1",
order_id="LABORDER_TEST2_1",
service_id_std="SERVICE_ID_STD_TEST2_1",
service_id="SERVICE_ID_TEST2_1",
service_id_description="SERVICE_ID_DESCRIPTION_TEST2_1",
value="VALUE_TEST2_1",
value_units="VALUE_UNITS_TEST2_1",
observation_time=datetime(2020, 3, 16),
)
session.add(patient_record)
session.add(patient_number)
session.add(laborder)
session.add(resultitem)
session.commit()
Developer Notes
Computed Fields
Three field types for deriving values on SQLAlchemy models. All are defined inline on the model and delegate their logic to functions in post_calculations.py.
computed_field
Pure Python. No session required. Cached permanently on the instance — survives expire() and commit().
Use when the value is derivable from already-loaded columns only (arithmetic, date calculations, string formatting).
session_computed_field
Session-aware. Cache is cleared on expire() and commit() so DB-derived values are never stale.
Use when the calculation requires a DB query — joins, lookups against reference tables, aggregates over related rows.
computed_hybrid
Wraps hybrid_property. Not cached — recalculates on every access. The only type usable in queries (WHERE, ORDER BY, filter()).
Use when you need the value available at the query level, not just on loaded instances.
Quick Reference
computed_field |
session_computed_field |
computed_hybrid |
|
|---|---|---|---|
| Requires session | No | Yes | No |
| Cached | Yes — permanent | Yes — cleared on expiry | No |
| Usable in queries | No | No | Yes |
| Use for | Arithmetic, dates | Joins, DB lookups | Query-level filtering |
Example
# post_calculations.py
def _calc_age(self) -> Optional[int]:
if self.birthtime is None:
return None
today = date.today()
born = self.birthtime.date()
return today.year - born.year - ((today.month, today.day) < (born.month, born.day))
def _calc_prepost(self, session: Session) -> str:
# looks up sibling results on the same date to determine PRE/POST dialysis
...
def _numeric_value_py(self) -> Optional[float]:
return float(self.resultvalue) if self.resultvalue else None
def _numeric_value_expr(cls):
return cast(cls.resultvalue, Numeric)
# ukrdc.py
class ResultItem(Base):
...
# No DB query needed — birthtime is already loaded
age: int = computed_field(_calc_age)
# Queries sibling rows — cache cleared on expire/commit
prepost: str = session_computed_field(_calc_prepost)
# Usable in WHERE/ORDER BY across a patient cohort
numeric_value: float = computed_hybrid(_numeric_value_py, _numeric_value_expr)
# usage
record = session.get(ResultItem, "R1")
print(record.age) # 47 — from loaded columns, no query
print(record.prepost) # "PRE" — queried DB, cached until next commit
# computed_hybrid can be used in queries — the other two cannot
high_results = session.scalars(
select(ResultItem)
.where(ResultItem.numeric_value > 10.0)
.order_by(ResultItem.numeric_value.desc())
).all()
Publish Updates
- Iterate the version number (
poetry version major/minor/patch) - Push to GitHub repo
- Create a GitHub release
- GitHub Actions will automatically publish the release to PyPI
Metadata
Release files for ukrdc-sqla 4.9.0
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 |
|---|---|---|---|---|
| ukrdc_sqla-4.9.0.tar.gz | 26.3 kB | Without provenance | Details for ukrdc_sqla-4.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ukrdc_sqla-4.9.0-py3-none-any.whl | Python 3 | none | any | Details for ukrdc_sqla-4.9.0-py3-none-any.whl |
Total release size: 56.5 kB
Release files / ukrdc_sqla-4.9.0.tar.gz
| Download URL | ukrdc_sqla-4.9.0.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31ded573d557bb5c3ebd14b4261dc7f5736f0ce5601e4af7ee1c53ec7acd4769
|
|
BLAKE2b-256 checksum How to use checksums |
8aa03ca8c0854474e01cc51fcdfa31946ace52efbd3b712b71f36b2d7e23a6b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.10.21 Linux/6.17.0-1022-azure
|
Release files / ukrdc_sqla-4.9.0-py3-none-any.whl
| Download URL | ukrdc_sqla-4.9.0-py3-none-any.whl |
|---|---|
| Size | 30.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74c7c204682870da0943d157cf6c8a343a0d5ea6cbccb9782617a99ae54c2113
|
|
BLAKE2b-256 checksum How to use checksums |
3e560c06d3614a7eeb7afd6de480802984ee0ff97ddc3f312f01e05899db68d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.10.21 Linux/6.17.0-1022-azure
|
Security for ukrdc-sqla 4.9.0
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.