Function Dispo Chronological(): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
m struct
m Text replacement - "cross checks" to "cross checks"
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Function Dispo_Chronological checks that the times in [[:Category:2016 Time and Place changes]] are in a sensible chronological order.
{{LegacyContent
|explanation=[[Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc]]
|successor=various [[cross check]]s against [[Boarding Loc]] and [[Service tmp entry]]
|content=


The check will run each time one of the following is edited, and will generate an error if:
* [[Visit Admit DtTm field]] - error if > than any other time
* [[Accept DtTm field]] - error if >Transfer Ready DtTm field or >Dispo DtTm field
* [[Arrive DtTm field]] - error if >Transfer Ready DtTm field or >Dispo DtTm
* [[Transfer Ready DtTm field]] - error if < arrive/accept (as above) or >Dispo DtTm
* [[Dispo DtTm field]] - error if in future (don't need to check for others because they need to be before this) and all other errors are taken care off by other pair checks above.


== Arrive vs Accept ==
{{Data Integrity Check
* will arrive always be after accept? is this sensible to check?
|DIC_summary=Checks that the registry times are in a sensible chronological order.
**  Re: Arrive after Accept: Intuitively should be yes however docs will send patients direct to wards for admission from clinic/s and only get to ward after clinics are over to write their orders...timing their admission orders will then be later than arrival. We have been adjusting their admit times to be same or 5 min earlier in order to avoid errors in these cases.--[[User:Llemoine|Llemoine]] 07:47, 2016 May 26 (CDT)
|DIC_related_concepts= Dispo DtTm
|DIC_firmness=hard check
|DIC_timing=always
|DIC_coding=Function Dispo_Chronological()
|DIC_implementation_date=2016-05-25
|DIC_status=retired
|DIC_app=CCMDB.accdb
|DIC_backlogged=No
}}


Retired as part of [[Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc]] as there is nothing left to check here, and all the tmp based checks are already done elsewhere.


== Transfer time rule ==
The check will generate an error if:
Will want to reconcile [[Transfer time rule]]
* ''Arrive DtTm'' has to be before or equal to ''Accept DtTm''
* ''Arrive DtTm'' has to be before or equal ''Transfer Ready DtTm''
* ''Arrive DtTm'' has to be before [[Dispo DtTm ]]
* ''Transfer Ready DtTm'' has to be before [[Dispo DtTm ]]
* [[Dispo DtTm ]] has to be before Now() / today


No checks on [[Visit Admit DtTm field]] since taken direct from [[EPR]], so it is what it is.
== Transfer vs (accept vs arrive) ==
In the real world, the ''Transfer Ready DtTm'' could well be between ''Accept DtTm'' and ''Arrive DtTm''. Our check would flag this as an error. As per [[Task Team Meeting - Rolling Agenda and Minutes 2019|ICU Database Task Group Meeting – January 24, 2019 | Task Meeting 209-01-24]] point 8 it was decided to continue to only allow a transfer date after arrival date. The rationale was that we don't care about time wasted outside of our units/wards, only on our units.
== Related checks ==
* [[Check Function Panelling admit transfer same]]
== Log ==
* 2022-04-21 - removed check
* 2020-10-15 - removed checks against [[Transfer Ready DtTm]] since that field is being retired, see [[Transfer Ready DtTm tmp entry]] for any replacements


[[Category:2016 Time and Place changes]]
[[Category:2016 Time and Place changes]]
[[Category:Registry checks]]
}}

Latest revision as of 13:25, 20 June 2025

Legacy Content

This page contains Legacy Content.

Click Expand to show legacy content.

Data Integrity Checks
Summary: Checks that the registry times are in a sensible chronological order.
Related: Dispo DtTm
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: Function Dispo_Chronological()
Uses L Problem table: not relevant for this app
Status: retired
Implementation Date: 2016-05-25
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

Retired as part of Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc as there is nothing left to check here, and all the tmp based checks are already done elsewhere.

The check will generate an error if:

  • Arrive DtTm has to be before or equal to Accept DtTm
  • Arrive DtTm has to be before or equal Transfer Ready DtTm
  • Arrive DtTm has to be before Dispo DtTm
  • Transfer Ready DtTm has to be before Dispo DtTm
  • Dispo DtTm has to be before Now() / today

No checks on Visit Admit DtTm field since taken direct from EPR, so it is what it is.

Transfer vs (accept vs arrive)

In the real world, the Transfer Ready DtTm could well be between Accept DtTm and Arrive DtTm. Our check would flag this as an error. As per ICU Database Task Group Meeting – January 24, 2019 | Task Meeting 209-01-24 point 8 it was decided to continue to only allow a transfer date after arrival date. The rationale was that we don't care about time wasted outside of our units/wards, only on our units.

Related checks

Log

Retrieved from "https://ccmdb.kuality.ca/index.php?title=Function_Dispo_Chronological()&oldid=164144"