CFE Data Integrity Checks

From CCMDB Wiki
Jump to navigation Jump to search

This page lists pages that have CFE Data Integrity Checks on them, the status of those checks if available. See also the following for the order in which these checks are run and how they are used:

See Template:Data Integrity Check for how to get things on this list.

Currently active checks

edit page Status Timing Firmness Summary question who
edit page Status Timing Firmness Summary question who
edit PL SamePhin Diff DOB Sex implemented always hard check Another record exists with the same PHIN but a different Date of Birth, Sex
edit Reconnect check Completes query implemented complete hard check Shows any records in that have RecordStatus "Complete", indicating failed send.
edit Link suspect mismatch pre inpt should be ours incomplete query implemented always hard check What is description
edit Query NDC Postal Code over time implemented hard check Cross check of postal codes for consistency during a continuous hospital admission
edit Link suspect not same visitAdmitDtTm query implemented always soft check Checks for records that are likely part of the same admission but have different Visit Admit DtTm field.
edit Link suspect mismatch pre inpt ours incomplete query implemented always soft check Checks for patients where Pre-admit Inpatient Institution is one of ours but we don't have a corresponding record.
edit PL 2Phin Fake or Blank implemented always hard check Finds blank PHINs and those entered to meet function Validate_PHIN so Data Processor can apply PseudoPHIN via Generating PseudoPHINs.
edit PL Chart 9 Digit implemented always hard check Finds any chart numbers that have >8 digits. This would usually mean someone confused a PHIN and a Chart number
edit PL Diff Phin SameLN FN DOB implemented always soft check Checks that there are no likely matches of this patient with a different PHIN (ie typos)
edit PL SameCHART Site Diff PHIN implemented always hard check A record with this Chart number already exists for this service/Location and it has a different PHIN.
edit PL SamePHIN Site Diff chart implemented always soft check Another record exists for this site with the same PHIN and a different Chart number.
edit Link suspect negative transit time query implemented always hard check Used in Correcting suspect links to find records where an earlier record for a patient with that PHIN has a Dispo DtTm that is later than the next record's Admit DtTm.
edit Link suspect mismatch to ours incomplete query implemented always hard check Used in Correcting suspect links to find records where an earlier record with that PHIN has a dispo entry corresponding to one of our sites as per the s_dispo table.real_collection, but a later corresponding entry doesn't exist for that location.
edit Link suspect mismatch from ours incomplete query implemented always hard check Used in Correcting suspect links to find records where a later record with that PHIN has a Previous Location entry corresponding to one of our sites as per the s_dispo table.real_collection table, but an earlier corresponding entry doesn't exist for that location.
edit Link suspect dead then alive query implemented always hard check Used in Correcting suspect links to find records where an earlier record with that PHIN was listed as dispo field deceased, but a later entry then shows up.
edit Reconnect check orphans query implemented always hard check Record meets following conditions
edit Reconnect check missing L Tables content query implemented complete hard check Complete patients must have entries in all of
  • L_ICD10 table
  • L_CCI_Picklist table
  • L_Labs_Flowsheet table
  • L_Pharm_Flowsheet table
  • edit Query NDC dx implying death across encounters implemented always hard check Category:Diagnosis implying death across encounters
    edit Query NDC Bad Postal Code implemented hard check Cross check of postal codes against known postal codes
  • I think this is the process where you said you are having problems with copy/pasting. Copy pasting isn't even mentioned here, so maybe update the process to show how you actually do this, so that someone like Sheila Rusnak would be able to follow the instructions. Ttenbergen 15:45, 2022 March 17 (CDT)
    • Do you create that query each time? Would we be able to update the NDC query that finds these in the first place to include the info you need? We can discuss at our next meeting. Ttenbergen 16:23, 2022 March 17 (CDT)
      • Taking this off Pagasa's list for now, since if we can get this data from DSS we won't need to do this any more. Ttenbergen 15:36, 2022 March 24 (CDT)
  • Tina
    edit Query cardiac arrest throughout admission needs review complete hard check Any patient who is admitted to ICU from Med or another ICU with a #Cardiac Arrest dx should have one in their immediately preceeding Med or ICU record also. JALT Review after 2023-09-15
  • Lisa flagged that, if we do this for Cardiac Arrest, we should really do it for other dxs as well. And if we did that, it could result in a lot of work since it would need to be mediated by Pagasa for now. So we decided to see where the SF implementation goes and review the definition of this check once we have a centralized tool where the data collector would not need to mediate this. Ttenbergen 15:43, 2023 July 13 (CDT)
  • all

    All checks

    see all checks

    Related articles

    Related articles: