Gaps and overlaps: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(4 intermediate revisions by one other user not shown)
Line 2: Line 2:


==Current state==
==Current state==
[[Main office]] maintains several files that deal with known (and not fixed) gaps and overlaps. They are stored at S:\WRHA\WRHA_CCMED\GAPS_OVERLAP_OVERS .
The [[Data Processor]] maintains [[L Problem table]] to track data with known (and not fixed) gaps and overlaps.  
 
{{Discuss | who = Pagasa | question =
*Pulled this from [[Known data errors]]:
::The [[Data processor]] keeps an Excel workbook that includes: reason some profiles are missing data elements (APACHE - 8 ICU profiles),  gaps in database because of deletions including reasons for deletions, overlaps, overs. Example missing all [[APACHE]] elements ... and reason why could never be obtained.   
* It sounds like there might be other known error types in addition to lost, gap and overlap. Feel free to add them to L_Problems as well, just put here what any additional options mean. If needed I will pull the wiki pages apart. [[User:Ttenbergen|Ttenbergen]] 15:41, 2022 March 31 (CDT)
}}


==Future state==
==Future state==
Line 14: Line 8:
* Gap
* Gap
* Overlap
* Overlap
{{Discuss | who = Pagasa |
* Pagasa, we discussed this today, and you said you would put this into L_Problems and then delete the info from the excel sheet (or the whole excel sheet if all has been transitioned). Putting this here so it is on your list. [[User:Ttenbergen|Ttenbergen]] 15:34, 2022 March 31 (CDT)
* when all has been moved to l_problem, the "current state" above can be deleted and we can just leave the "future state" portion as documentation. [[User:Ttenbergen|Ttenbergen]] 15:45, 2022 March 31 (CDT)
}}


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

Latest revision as of 09:53, 4 January 2023

There are some gaps between or overlaps within Admit DtTm and Dispo DtTm in some of our older records. These were identified, but never corrected. To prevent having to re-check this data we are keeping track of this.

Current state

The Data Processor maintains L Problem table to track data with known (and not fixed) gaps and overlaps.

Future state

This information will transition to the L Problem table. That table was initially just meant to whitelist problems with queries, but to group these gaps and overlaps together we will use the "Query" field as a marker as follows:

  • Gap
  • Overlap

Related articles

Related articles: