location geo work

crud

this provides a basic way of managing adding and managing location (geo) data. The ‘d’ will be ignored - allowing users to delete a geo will need to require a manual step from engineering. Alternate idea: we could look at determining if a geo has sites attached to it, or is within a 5 minute window of creation to allow for deletion.

rate

Existing table location will be used for name/description and will have an accompanying rate table with date ranges to be able to indicate a location at a specific date.

First step will be to have a small conversion step that takes rate data from the data.hospital_region_geo_mapping table (which is populated automatically from a sharepoint spreadsheet) to populate rate info. Default ‘start’ date for these rates will be Jan 1, 2021, unless we’re told otherwise before launch.

Second step will be to modify the calls to getHospitalGeoRateNoDate (and similar) to point to getHospitalGeoRate and pass in a date parameter (typically, a shift’s date), to get the specific rate to use for the shift at a specific date.