Gaps and overlaps: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
|||
| Line 2: | Line 2: | ||
==Current state== | ==Current state== | ||
[[ | The [[Data Processor]] maintains [[L Problem table]] to track data with known (and not fixed) gaps and overlaps. | ||
==Future state== | ==Future state== | ||
| Line 12: | Line 8: | ||
* Gap | * Gap | ||
* Overlap | * Overlap | ||
== Related articles == | == Related articles == | ||
Latest revision as of 10: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: |