Pre-admit Inpatient Institution field

From CCMDB Wiki
Jump to navigation Jump to search
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
Data Dependencies(Reports/Indicators/Data Elements):

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.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


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
    • for patients who were accepted by a service at the previous site, but never left the site's ER to get to the ward ("EMIP" concept), consider these in-patients
    • for places where we collect, use the Service/Location used by the counterpart laptop: <site>_Med, GH-CC, HSC MICU , HSC SICU, HSC_IICU, STB MICU, STB_ICCS, STB_ACCU
    • for wards where we don't collect: <site>_Ward or other external entry e.g. home
Example:   
  • HSC MICU --- family medicine ward at the Vic --- HSC_ER --- STB_ER --- cath lab --- HSC_MICU.
    • Code the Pre-admit Inpatient Institution field as: VIC_Ward
  • 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 (at your site or elsewhere) is not an inpatient location, so enter "not applicable"

Where to find this information

If patient came from a different Winnipeg hospital this will be recorded in the “Visit History” on the EPR.

Ambiguous locations

  • Day-surgery locations - use "<hosp> ambulatory care"
  • The following ARE NOT considered inpatient locations, enter "NA / not applicable"
    • Any PCH (see Chronic Health Facility for additional instructions)
    • Nursing stations - they are not inpatient locations, and Julie and Tina met with Randy Martin 2016-04 and he confirmed he doesn't need them.

Chronic Care Facilities

They are a changing and complicated case, see Chronic Health Facility.

Intra-facility and inter-facility transfers

If a patient gets transferred to another ward in the same or different hospital, enter <site>_Med, <site>_Ward or <site>_CC (as appropriate) as both the Previous Location field and the Pre-admit Inpatient Institution field.

Arrivals from a borrowed bed

See and follow Previous Location field#Borrowed Bed Or Boarding Loc

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.

"Can we remove the items that are no longer Service/Locations, Previous Locations, Pre-admit Inpatient Institutions or dispo locations from the dropdowns?"

We can and will remove them, but that can only happen once no more laptops use them. We will need to keep track of this and then remove them when ready. If I removed them now, then any box that currently has them enter would misbehave.

SQL query of what is currently available    
SELECT s_dispo.location_name, s_dispo.Site, s_dispo.active, s_dispo.inpatient, s_dispo.previous_location, s_dispo.s_location, s_dispo.dispo
FROM s_dispo
WHERE (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.inpatient)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.previous_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.s_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.dispo)=True));
  • query of what is currently used: query z_s_dispo_inactivatable

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)

 AppStatus
Query check prev pre-admit consistentCCMDB.accdbimplemented
Function Validate Pre admit Inpatient InstitutionCCMDB.accdbimplemented
Check function preAdmit NE LocationCCMDB.accdbimplemented
Check Accept Loc ParkCCMDB.accdbretired
Link suspect mismatch pre inpt ours incomplete queryCentralized data front end.accdbimplemented
Link_suspect_not_same_visitAdmitDtTm queryCentralized data front end.accdbimplemented

Reports

The information is part of the Critical Care Program Quality Indicator Report and the ICU Interfacility Report. Also the information will be useful for research projects where it will mark a patient as inpatient before arrival to the unit or ward.

Implementation

The field is populated with options from the s_dispo table.

Legacy

This field is part of the 2016 Time and Place changes. Some of the data previously existed in hospital previous but it is not a 1-to-1 mapping.

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Pre-admit_Inpatient_Institution_field&oldid=163822"