Pre-admit Inpatient Institution field: Difference between revisions
TOstryzniuk (talk | contribs) |
No edit summary |
||
| Line 3: | Line 3: | ||
| CCMDB_label = Pre-admit Inpatient Institution | | CCMDB_label = Pre-admit Inpatient Institution | ||
| CCMDB_tab = Dispo | | CCMDB_tab = Dispo | ||
| element_description = The '''previous ''inpatient'' location''' of patients who were already '''inpatients''' elsewhere and who have been under medical care continuously before coming to our unit. | | element_description = The most recent '''previous ''inpatient'' location''' of patients who were already '''inpatients''' elsewhere and who have been under medical care continuously before coming to our unit. | ||
| in_table = L_Log table | | in_table = L_Log table | ||
| data_type = number | | data_type = number | ||
Revision as of 11:25, 7 February 2019
| Data Element (edit) | |
| Field Name: | Pre_admit_Inpatient_Institution |
| CCMDB Label: | Pre-admit Inpatient Institution |
| CCMDB tab: | Dispo |
| Table: | L_Log table |
| Data type: | number |
| Length: | long integer |
| Program: | Med and CC |
| Created/Raw: | Raw |
| Start Date: | 2016-07-01 |
| End Date: | 2300-01-01 |
| Sort Index: | 36 |
The most recent previous inpatient location of patients who were already inpatients elsewhere and who have been under medical care continuously before coming to our unit.
This does not include patients who just arrived at an ER elsewhere and were not admitted as inpatient there.
If that location is already an inpatient location, then the pre admit inpatient institution will be the same the Previous Location.
For example, a patient arriving from Selkirk Hospital ward via the local ER would have the ER coded in the Previous Location field and Selkirk ward coded in the Pre-admit Inpatient Institution field.
Collection Instruction
For each patient,
- enter the most recent in-patient location where the patient has been admitted during this continuous episode of hospitalization at this or other hospitals.
- if you know the situation but nothing on the list matches closely, enter other - known but not listed
- if the situation is unknown, enter location missing/unknown
- if the patient did not come from an inpatient location, enter "not applicable", for example if they came from home or a clinic. The ER is not an inpatient location.
If you know how we code the location exactly, you can type it. Otherwise press the "?" button to take you to the S dispo chooser to help filter options if desired.
Example:
- VIC_ICU---family medicine ward at the Vic---HSC_ER---STB_ER---cath lab---HSC_MICU.
- Code the Pre-admit Inpatient Institution field as: VIC_Ward
Where to find this information
If patient came from a different Winnipeg hospital this will be recorded in the “Visit History” on the EPR.
EMIP/Bed borrow
see those articles
Ambiguous locations
The following ARE considered inpatient locations in this context:
- day-surgery patients ending up on our unit directly
The following ARE NOT considered inpatient locations, enter "NA / not applicable"
- care homes, including units with higher levels of care at any Chronic Health Facility
intra-facility and inter-facility transfers
If a patient gets transferred to another ward in the same or different hospital, enter the previous ward as both the Previous Location field and the Pre-admit Inpatient Institution field.
direct admit / transfer / parked in ER
see Direct admit / Parked in ER
Code Readmission from Grace Nursing Home Ward as NA
We consider admissions from there as re-admissions, so would be coded as if they had come from home. Consistent with that we will consider these not inpatient locations, so code them as "NA / not applicable". (As per meeting with Dr Roberts 2016-05-05)
several pre-admit locations
If a patient travels through several pre-admit inpatient locations we will only have data on the last one. We understand that. Just to be clear.
Example: Pt was on a ward as an inpatient then went to ICU, then was transferred to the ward you are collecting on. Previous location would be ICU and previous inpatient institution would also be ICU.
ward -> ER -> ICU
- Oaks_ICU_Collection_Guide#inpatients_go_from_ward_to_ER_then_ICU
- CON_ICU_Collection_Guide#inpatients_go_from_ward_to_ER_then_ICU
Data Use / Purpose
To document where those patients who were inpatients immediately before arriving on our ward/unit came from.
The detailed information will allow us also to distinguish between patients who were or were not inpatients before arrival. This is relevant to a patient's risk of bad outcomes.
The information will also give our administrators a better idea of which other hospitals are sending us patients, which they will use for planning.
Cross Checks
Data Integrity Checks (automatic list)
| App | Status | |
|---|---|---|
| Query check prev pre-admit consistent | CCMDB.accdb | implemented |
| Function Validate Pre admit Inpatient Institution | CCMDB.accdb | implemented |
| Check function preAdmit NE Location | CCMDB.accdb | implemented |
| Check Accept Loc Park | CCMDB.accdb | retired |
| Link suspect mismatch pre inpt ours incomplete query | Centralized data front end.accdb | implemented |
| Link suspect not same visitAdmitDtTm query | Centralized data front end.accdb | implemented |
Reports
- The information will be part of the Inter-facility transfer report (i.e. inpatients coming from other facility outside the region or within the region). Also the information will be useful for research projects where a patient will be tagged if already an inpatient before arrival to the unit or ward. JMojica 11:45, 2016 June 6 (CDT)
Implementation
The field is populated with options from the s_dispo table.
Legacy
This field is part of the 2016 Time and Place changes and did not previously exist.
Nursing stations
We used to collect nursing stations in hospital previous but would not include them under the new scheme because they are not inpatient locations. Julie and Tina met with Randy Martin 2016-04 and he confirmed he doesn't need them.