S dispo table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m clean up |
Ttenbergen (talk | contribs) m →Data Structure: structure change |
||
| Line 14: | Line 14: | ||
|- | |- | ||
|| '''location_name''' || text || name as seen by collector | || '''location_name''' || text || name as seen by collector | ||
|- | |||
|| '''real_name''' || text || actual unit name, e.g. HSC_MICU vs HSC_MICa | |||
|- | |||
|| '''site''' || text || our short hospital name, eg HSC | |||
|- | |||
|| '''ward''' || text || ward name only, e.g. A1 for HSC_A1 | |||
|- | |- | ||
|| '''hospital''' || text || hospital if one where we collect | || '''hospital''' || text || hospital if one where we collect | ||
| Line 32: | Line 38: | ||
|- | |- | ||
|| '''surgical''' || yes/no || is a surgical location (used by e.g. [[Check ORDx]]) | || '''surgical''' || yes/no || is a surgical location (used by e.g. [[Check ORDx]]) | ||
|- | |||
|| '''meanLOS3STD''' || integer || used by LOS check | |||
|- | |- | ||
|| '''s_location''' || yes/no || can be used as [[location]] | || '''s_location''' || yes/no || can be used as [[location]] | ||
| Line 38: | Line 46: | ||
|- | |- | ||
|| '''active''' || yes/no || logical delete from dropdowns | || '''active''' || yes/no || logical delete from dropdowns | ||
|- | |||
|| '''acuity_level''' || yes/no || logical delete from dropdowns | |||
|- | |||
|| '''program''' || text || CC or Med for our locations only {{discussion}} need to change the program function etc to use these | |||
|- | |||
|| '''colour''' || text || colour code for patient list view {{discussion}} need to change the patient list to use this instead. | |||
|- | |||
|| '''center''' || long integer|| used by Julie for {{discussion}} what? | |||
|} | |} | ||
Some additional legacy and reporting fields are stored in the [[s_dispo_legacy_codes table]]. | Some additional legacy and reporting fields are stored in the [[s_dispo_legacy_codes table]]. {{discussion}} looks like we will keep all in s_dispo now, so need to clean that up. | ||
[[Category: Data structure]] | [[Category: Data structure]] | ||
[[Category: 2016 Time and Place changes]] | [[Category: 2016 Time and Place changes]] | ||
Revision as of 12:58, 2016 June 9
The S_dispo table in CCMDB.mdb contains the possible values for the following fields:
Data Structure
| field | type | description |
|---|---|---|
| dispo_ID | text | unique ID |
| location_name | text | name as seen by collector |
| real_name | text | actual unit name, e.g. HSC_MICU vs HSC_MICa |
| site | text | our short hospital name, eg HSC |
| ward | text | ward name only, e.g. A1 for HSC_A1 |
| hospital | text | hospital if one where we collect |
| loc_type | text | see #location types |
| geog | text | geographical area (in town, out of province, etc) |
| notes | text | general notes about record |
| question | text | questions while we implement, can be deleted after |
| inpatient | yes/no | is an inpatient location, used by Pre-admit Inpatient Institution field drop-down and cross checks |
| temporary | yes/no | is a temporary location, used by Pre-admit Inpatient Institution field cross checks |
| previous_location | yes/no | can be used as Previous Location field |
| surgical | yes/no | is a surgical location (used by e.g. Check ORDx) |
| 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 |
| program | text | CC or Med for our locations only Template:Discussion need to change the program function etc to use these |
| colour | text | colour code for patient list view Template:Discussion need to change the patient list to use this instead. |
| center | long integer | used by Julie for Template:Discussion what? |
Some additional legacy and reporting fields are stored in the s_dispo_legacy_codes table. Template:Discussion looks like we will keep all in s_dispo now, so need to clean that up.