Function Dispo Chronological(): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{LegacyContent
|explanation=[[Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc]]
|successor=various cross checks against [[Boarding Loc]] and [[Service tmp entry]]
|content=
{{Data Integrity Check
{{Data Integrity Check
|DIC_summary=Checks that the registry times are in a sensible chronological order.
|DIC_summary=Checks that the registry times are in a sensible chronological order.
|DIC_related_concepts= Arrive DtTm; Accept DtTm; Transfer Ready DtTm; Dispo DtTm
|DIC_related_concepts= Dispo DtTm
|DIC_firmness=hard check
|DIC_firmness=hard check
|DIC_timing=always
|DIC_timing=always
|DIC_coding=Function Dispo Chronological()
|DIC_coding=Function Dispo_Chronological()
|DIC_implementation_date=2016-05-25
|DIC_implementation_date=2016-05-25
|DIC_status=implemented
|DIC_status=retired
|DIC_app=CCMDB.mdb
|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.
The check will generate an error if:  
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 to ''Accept DtTm''
* [[Arrive DtTm]] has to be before or equal [[Transfer Ready DtTm]]
* ''Arrive DtTm'' has to be before or equal ''Transfer Ready DtTm''
* [[Arrive DtTm]] has to be before [[Dispo DtTm ]]  
* ''Arrive DtTm'' has to be before [[Dispo DtTm ]]  
* [[Transfer Ready DtTm]] has to be before [[Dispo DtTm ]]  
* ''Transfer Ready DtTm'' has to be before [[Dispo DtTm ]]  
* [[Dispo DtTm ]] has to be before Now() / today
* [[Dispo DtTm ]] has to be before Now() / today


Line 19: Line 29:


== Transfer vs (accept vs arrive) ==
== Transfer vs (accept vs arrive) ==
{{Discuss | who = all | question =
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.
* I just came across the error “Arrive_DtTm can't be greater than Transfer_Ready_DtTm.” in CCMDB. It made me wonder… I suppose that a TR could be before Arrive if it’s after Accept.  
** First, Trish, do you think I am right about that?
** Second, if so, do we need to adjust this? How does this work with Julie’s reports now, and how would it work if changed.  
}}
 
== Transfer time rule ==
{{DT | Will want to reconcile [[Transfer time rule]] }}


== Related checks ==
== Related checks ==
* [[Check Function Panelling admit transfer same]]
* [[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]]
[[Category:Registry checks]]
}}

Latest revision as of 15:48, 2022 April 21

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