s_dispo table
Jump to navigation
Jump to search
The s_dispo table in CCMDB.accdb contains the possible values for the following fields:
- Pre-admit Inpatient Institution field
- Previous Location field
- Dispo field
- Service/Location field - i.e. it contains the Site and Location table
|
|
Data Structure
| field | type | description |
|---|---|---|
| dispo_ID | text | unique ID |
| location_name | text | name as seen by collector |
| real_collection | text | unit name as collected by us, e.g. HSC_MICU vs HSC_MICa; this is used to link the Previous Location/Dispo to Service/Location |
| real_name | text | unit name as reported, e.g. STB_ICMU vs STB_MICU |
| site | text | our short hospital name, eg HSC |
| ward | text | ward name only, e.g. A1 for HSC_A1 |
| s_dispo.hospital | text | hospital if one where we collect |
| s_dispo.loc_type | text | S dispo.loc type |
| s_dispo.geog | text(20) | geographical area (in town, out of province, etc) |
| s_dispo.geoRegion | text(17) | geographical region |
| MB_RHA | text(7) | regional health authority the institution is administered by |
| notes | text | general notes about record |
| question | text | questions while we implement, can be deleted after |
| s_dispo.inpatient | yes/no | is an inpatient location, used by Pre-admit Inpatient Institution field drop-down and cross checks |
| previous_location | yes/no | can be used as Previous Location field |
| surgical | yes/no | is a location where actual surgeries happpen (used by e.g. Check ORDx) (ie not just a surgical ward) |
| meanLOS3STD | integer | used by LOS check |
| s_location | yes/no | can be used as location |
| dispo | yes/no | can be used in Dispo field |
| active | yes/no | logical delete from dropdowns |
| acuity_level | yes/no | logical delete from dropdowns |
| s_dispo.program | text | CC or Med, used for rows where real_name is one of our locations only |
| colour | text | colour code for patient list view |
| S_dispo.center | long integer | chronological order sequence of the site and ward used in generating report (e.g. teaching hospitals first followed by community hospitals); also used to combine old and new names of locations for reporting |
Inactivating locations
Before inactivating a location, make sure that it is not used in any incomplete profiles.
Before inactivating any entry, check Query z_s_dispo_inactivatable to make sure it is not currently used in any incomplete records (RecordStatus incomplete).
We can occasionally check query Query z_s_dispo_lastUsed for entries that have not been used in a long time. If it is never used it may be an entry we no longer need, but it may also just be an entry that is rarely used.
|
_wiki housekeeping
|
|
Log
- 2022-04-21 - updated s_dispo table.meanLOS3STD with data from Julie
- 2022-03-24 - removed field "service_type" since it's no longer used; as discussed at task around 2022-02-03