|Data Element (edit)|
|CCMDB Label:||Service Location|
|Program:||Med and CC|
Collection location a patient is admitted to.
Enter the physical location of the patient.
If you know the location exactly, you can type it. otherwise use the "?" button. The dropdown is limited to locations where a laptop collects.
Only service locations allowed to be collected on this laptop based on its Settings (CCMBD.mdb) will be listed.
Patients in bed borrow locations on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
Minimal Data Set
This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.
Adding a new service/location entry
- add to s_dispo table
- add to s_locations_allowed_collection table
- consider all checks in Category:Service/Location check to see if they need to be modified to work right for the new location.
Data Use / Purpose
See Site and Location table for possible entries.
Use to determine the location or services the patient went during a hospital stay.
Use to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.
Data Integrity Checks (SMW)
|Query s tmp ABO TEE checks||CCMDB.accdb||implemented|
|Query check minimal data set incomplete||CCMDB.accdb||implemented|
|Query send check centralized is owner||CCMDB.accdb||implemented|
|Check function location NE dispo||CCMDB.accdb||implemented|
|Check function previous NE Location||CCMDB.accdb||implemented|
|Check function preAdmit NE Location||CCMDB.accdb||implemented|
|Query check ER Delay not too big||CCMDB.accdb||implemented|
|PL SameCHART Site Diff PHIN||Centralized data front end.accdb||implemented|
|PL SamePHIN Site Diff chart||Centralized data front end.accdb||implemented|
|PL 1orphans||Centralized data front end.accdb||implemented|
|Link suspect mismatch pre inpt ours incomplete query||Centralized data front end.accdb||implemented|
The field is populated with options from the s_dispo table.
Retiring an available Service/Location field entry
Sometimes a ward may close or change names, or we may stop collecting somewhere. In that case, an entry for Service/Location needs to be made unavailable by editing the s_locations_allowed_collection table.
If a location is no longer available on a laptop records with that location can't be set to "complete". So, if we transition from one location to a new one, we need to get collectors to change the locations for all existing records to the new one, and change the number to using the new number series. Another option might be to keep old location available, at risk of manual mistakes and continuing to use the old location, and of location-numberPool mix-ups. Either way, needs to be planned.
This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.