Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Details
Print Page as PDF
Sub-Field: 6001.01

Package: Lab Service

VBECS DATA INTEGRITY/CONVERSION STATISTICS(#6001)-->6001.01

Sub-Field: 6001.01


Information

Parent File Name Number Package
VBECS DATA INTEGRITY/CONVERSION STATISTICS(#6001) DATA INTEGRITY ISSUES 6001.01 Lab Service

Details

Field # Name Loc Type Details
.01 FILE 0;1 POINTER TO FILE FILE (#1)
************************REQUIRED FIELD************************
FILE(#1)

  • INPUT TRANSFORM:  S DIC("S")="I Y=2!(Y=63)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  FEB 11, 2004
  • HELP-PROMPT:  System generated, tracks data integrity issues by file.
  • DESCRIPTION:  System generated, tracks data integrity issues. This multiple identifies the data integrity issue as well as the file where the integrity issue exists. This points to the file where the process originally navigated
    from.
    In the case of data integrity issues between the Patient (#2) and Lab Data (#63) files, this field will store the file number of the Patient (#2) file.
  • TECHNICAL DESCR:  
    Will screen for the following files: Patient (#2) and Lab Data (#63) by Application Group.
  • SCREEN:  S DIC("S")="I Y=2!(Y=63)"
  • EXPLANATION:  Only the Patient (#2) and Lab Data (#63) files are being evaluated.
  • CROSS-REFERENCE:  6001.01^B
    1)= S ^VBEC(6001,DA(1),"ERR","B",$E(X,1,30),DA)=""
    2)= K ^VBEC(6001,DA(1),"ERR","B",$E(X,1,30),DA)
.02 IEN OF INVALID RECORD 0;2 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  MAY 09, 2008
  • HELP-PROMPT:  Type a number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field is system generated and contains the IEN of the record with invalid or questionable data.
.03 ASSOCIATED FILE 0;3 POINTER TO FILE FILE (#1) FILE(#1)

  • INPUT TRANSFORM:  S DIC("S")="I Y=63!(Y=65)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  FEB 25, 2003
  • HELP-PROMPT:  System generated, file number of associated file.
  • DESCRIPTION:  
    If two files are involved in the data validation problem, this field will contain the associated file number (expected to be the Lab Data (#63) or Blood Inventory (#65) file).
  • SCREEN:  S DIC("S")="I Y=63!(Y=65)"
  • EXPLANATION:  Lab Data (#63) and Blood Inventory (#65) are the only valid files.
.04 IEN OF INVALID ASSOC'D REC 0;4 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  MAY 09, 2008
  • HELP-PROMPT:  Type a number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field is system generated and tracks the IEN of the record of the associated file.
.05 LRDFN ONE 0;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  MAY 09, 2008
  • HELP-PROMPT:  Type a number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field will store the IEN of a record in the Lab Data (#63) file. From this information, patient information can be derived.
  • TECHNICAL DESCR:  The intent is to keep a record of which Lab Data (#63) patient or patients, in the TRANSFUSION RECORD sub-file have duplicate Component and Component ID data.
    If duplicate Component/Component ID data exist for a single patient, only the LRDFN ONE (#.05) field will be populated. If there are two different patients experiencing this problem, then both the LRDFN ONE and LRDFN
    TWO (#.06) fields will be populated.
.06 LRDFN TWO 0;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  MAY 09, 2008
  • HELP-PROMPT:  Type a number between 1 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field will store the IEN of a record in the Lab Data (#63) file. From this information, patient information can be derived.
  • TECHNICAL DESCR:  The intent is to keep a record of which Lab Data (#63) patient or patients, in the TRANSFUSION RECORD sub-file have duplicate Component and Component ID data.
    If duplicate Component/Component ID data exist for a single patient, only the LRDFN ONE (#.05) field will be populated. If there are two different patients experiencing this problem, then both the LRDFN ONE and LRDFN
    TWO (#.06) fields will be populated.
.07 COMPONENT 0;7 POINTER TO BLOOD PRODUCT FILE (#66) BLOOD PRODUCT(#66)

  • LAST EDITED:  APR 23, 2002
  • HELP-PROMPT:  System generated, this is a duplicate Blood Product Component stored for reporting purposes.
  • DESCRIPTION:  
    This field contains the Component that is duplicated along with the Component ID for either a single patient, or, multiple patients.
  • TECHNICAL DESCR:  Part of the invalid data tracking process for duplicate component/component ID data for a single or multiple patients.
    Not screened because data captured is expected to be screened in the TRANSFUSION RECORD (#63.017) sub-file.
.08 COMPONENT ID 0;8 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>13!($L(X)<2) X
  • LAST EDITED:  APR 23, 2002
  • HELP-PROMPT:  System generated, this is a duplicate Blood Product Component ID stored for reporting purposes.
  • DESCRIPTION:  
    This field contains the Component that is duplicated along with the Component ID for either a single patient, or, multiple patients.
  • TECHNICAL DESCR:  Part of the invalid data tracking process for duplicate component/component ID data for a single or multiple patients. Not screened because data captured is expected to be screened in the TRANSFUSION RECORD (#63.017)
    sub-file.
.09 DATA INTEGRITY ISSUE 0;9 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>100!($L(X)<3) X
  • LAST EDITED:  APR 23, 2002
  • HELP-PROMPT:  System generated, this field tracks the relevant information as to why the data integrity issue exists.
  • DESCRIPTION:  
    This field is system generated and tracks the relevant information as to why the data integrity issue exists.
Info |  Details