S AdmitDischarge: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) m →to do before de-stubbing: never mind |
||
| Line 7: | Line 7: | ||
* active - boolean - logical delete, yes if field can currently be chosen by collectors; field became necessary when legacy locations were imported | * active - boolean - logical delete, yes if field can currently be chosen by collectors; field became necessary when legacy locations were imported | ||
* old code - text(3) - location code used by [[TMSX]] *1 | * old code - text(3) - location code used by [[TMSX]] *1 | ||
* hosp - hospital it is at, if applicable | |||
* ward - ward that we collect that this is, if applicable | |||
* notes - notes... | |||
== location code used by TMSX - *1 == | == location code used by TMSX - *1 == | ||
Revision as of 14:03, 22 June 2015
The S_AdmitDischarge table contains the possible values for the Admit From & Discharged To fields in CCMDB.mdb.
to do before de-stubbing
- Location - text(60) - full name of location
- Code (no duplicates) - text(2) - location code used by TMSX *1
- surgical - boolean - is this an admit-from location that indicates a surgical patient? Template:Discussion can't remember what actually uses this... might be apache type on import?
- active - boolean - logical delete, yes if field can currently be chosen by collectors; field became necessary when legacy locations were imported
- old code - text(3) - location code used by TMSX *1
- hosp - hospital it is at, if applicable
- ward - ward that we collect that this is, if applicable
- notes - notes...
location code used by TMSX - *1
TMSX used one 3-letter variable, "oth"; current system could not accomodate that so added a column that can. Used by TMSX import into Centralized (Centralized import from Ed.mdb).