Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields
Print Page as PDF
Global: ^RORDATA(798.3

Package: Clinical Case Registries

Global: ^RORDATA(798.3


Information

FileMan FileNo FileMan Filename Package
798.3 ROR PATIENT EVENTS Clinical Case Registries

Description

Accessed By FileMan Db Calls, Total: 3

Package Total Routines
Clinical Case Registries 3 RORDD01    RORUPP02    RORUTL17    

Pointer To FileMan Files, Total: 3

Package Total FileMan Files
Clinical Case Registries 2 ROR REGISTRY PARAMETERS(#798.1)[#798.31(.01)]    ROR DATA AREA(#799.33)[#798.32(1)]    
Registration 1 PATIENT(#2)[.01]    

Fields, Total: 3

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

  • INPUT TRANSFORM:  S:$D(X) DINUM=X
  • LAST EDITED:  APR 15, 2002
  • DESCRIPTION:  
    The PATIENT NAME field identifies the patient. You can add a patient from the PATIENT file.
    DELETE AUTHORITY: @
    WRITE AUTHORITY: @
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  798.3^B
    1)= S ^RORDATA(798.3,"B",$E(X,1,30),DA)=""
    2)= K ^RORDATA(798.3,"B",$E(X,1,30),DA)
    3)= Do not delete!
1 ERROR 1;0 POINTER Multiple #798.31 798.31

  • DESCRIPTION:  This multiple stores references to those registries that have the patient processed with errors and has not been added to the registry.
    When the problems are fixed, the data search must start not from the date of the previous run of the registry update process but from the date that was used when the problem arose. Otherwise, the data in the interval
    between those dates will not be checked and some important information may be missed.
    This date cannot be stored in the registry file (#798) because the patient has not been added to the registry yet. So, the date is stored in this multiple.
    Before the registry update process begins searching the data of the patient, it tries to find a record for that patient in this multiple. If it exists, the date from the record is used in the search instead of regular
    date (from the REGISTRY UPDATED UNTIL field of the REGISTRY PARAMETERS file.
    After successfully processing the patient data, the corresponding record is deleted from this multiple.
    Records of the multiple are uniquely identified by the registry IEN. The "A" primary key and the "B" uniqueness index are used for this purpose.
    Usually, records within this multiple should not be edited. Its content is handled automatically by entry points from the routine RORUPP01 during the registry update.
    However, if the errors are not corrected in the predefined time frame (2 weeks at the moment), patient data will not be analyzed by the subsequent registry updates until someone fixes the errors and resets the COUNTER
    field of the patient records in this multiple.
    WRITE AUTHORITY: @
  • SECONDARY KEY:  A (#21)
    Uniqueness Index: B (#156)
    File, Field: 1) REGISTRY (798.31,.01)
  • INDEXED BY:  REGISTRY (B)
2 EVENT 2;0 DATE Multiple #798.32 798.32

  • LAST EDITED:  APR 15, 2002
  • DESCRIPTION:  This multiple stores event references created by the event protocols. The registry update uses these references to speed up the processing.
    The event references are grouped by the data areas (protocols) and only one reference per associated date (the DATE field) for each data area is stored at the moment. The "AD" cross-reference is used by the $$ADD^RORUPP02
    function for this purpose.
    WRITE AUTHORITY: @
  • INDEXED BY:  DATA AREA & DATE (AD), DATA AREA & TIMESTAMP (AT)
Info |  Desc |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields