Admit DtTm: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "Definition of a Medicine Laptop Admission" to "Definition of a Medicine Program Admission"
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The {{PAGENAME}} is the start of a profile as per [[Definition of a Critical Care Laptop Admission]]/[[Definition of a Medicine Laptop Admission]].
The {{PAGENAME}} is the start of a profile as per [[Definition of a Critical Care Program Admission]]/[[Definition of a Medicine Program Admission]].


== Definition ==
== Definition ==
Admit DtTm is not as simple of a concept as it might seem, and it's definition and storage in our database has changed over time.
The derivation of Admit DtTm has changed over time, involving the fields [[Accept DtTm]], [[Arrive DtTm]] and [[Service tmp entry]] DtTm. Admit DtTm is defined as follows:
{{DJ |
* somewhere I read 2021-10-01, elsewhere -15, which one is right?
** I have looked at the tmp Service and the earliest date is Oct 17, 2019 (??) followed by Feb 12, 2020, then Mar 10,2020, etc.  even earlier than oct 15, 2020. there are 175 records with date earlier than Oct 1, 2020.  how about a cut-off OCT 1, 2020? --[[User:JMojica|JMojica]] 16:59, 2022 February 8 (CST) 
*** Agreed, we should use -10-01. I will need to update [[Created_AdmitDtTm query]] because it actually doesn't have a cut-off at all. Do we want to clean out any [[Service tmp entry]] from before Oct 1? We would need to update the start dttm on that page as well. Actually, now that I say this: didn't we start Oct 1 at GRA and everywhere else Oct 15? [[User:Ttenbergen|Ttenbergen]] 13:51, 2022 February 9 (CST) }}


SELECT L_Log.Pat_ID, CDate(Nz([Service_DtTm],Nz([Accept_dttm],[Arrive_Dttm]))) AS Admit_DtTm
FROM L_Log LEFT JOIN created_FirstService ON L_Log.Pat_ID = created_FirstService.Pat_ID;


If [[Visit Admit DtTm]] > #2020-10-01# then 
This is implemented as [[Created_AdmitDtTm query]].
    earliest [[Service tmp entry]] DtTm in profile
else
    if available, [[Accept DtTm]], else [[Arrive DtTm]]


This is implemented as [[Created_AdmitDtTm query]].
== Transition ==
GRA changed to this Oct 1 and everyone else Oct 15. Julie cleaned all the data so we don't need to worry about this: we can simply say if Service tmp DtTm is available, use it.  


{{Data Integrity Check List}}
{{Data Integrity Check List}}
Line 26: Line 22:
Also see "what links here"
Also see "what links here"
}}
}}
== Log ==
* 2022-04-04 confirmed that both CFE and CCMDB now use this as defined here.


== Related articles ==  
== Related articles ==  

Latest revision as of 09:41, 7 March 2025

The Admit DtTm is the start of a profile as per Definition of a Critical Care Program Admission/Definition of a Medicine Program Admission.

Definition

The derivation of Admit DtTm has changed over time, involving the fields Accept DtTm, Arrive DtTm and Service tmp entry DtTm. Admit DtTm is defined as follows:

SELECT L_Log.Pat_ID, CDate(Nz([Service_DtTm],Nz([Accept_dttm],[Arrive_Dttm]))) AS Admit_DtTm
FROM L_Log LEFT JOIN created_FirstService ON L_Log.Pat_ID = created_FirstService.Pat_ID;

This is implemented as Created_AdmitDtTm query.

Transition

GRA changed to this Oct 1 and everyone else Oct 15. Julie cleaned all the data so we don't need to worry about this: we can simply say if Service tmp DtTm is available, use it.

Data Integrity Checks (automatic list)

 AppStatus
Query check tmp Service and Boarding Loc during admission timeframeCCMDB.accdbimplemented
Function long LOS()CCMDB.accdbneeds review
Query check_tmp_AHCCCMDB.accdbneeds review
Query check_tmp_Overstay2CCMDB.accdbneeds review
Link suspect negative transit time queryCentralized data front end.accdbimplemented

Relevance

List of related concepts   

Also see "what links here"

Log

  • 2022-04-04 confirmed that both CFE and CCMDB now use this as defined here.

Related articles

Related articles: