Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^AUPNVPRV

Package: PCE Patient Care Encounter

Global: ^AUPNVPRV


Information

FileMan FileNo FileMan Filename Package
9000010.06 V PROVIDER PCE Patient Care Encounter

Description

Directly Accessed By Routines, Total: 30

Package Total Routines
PCE Patient Care Encounter 19 PX10118P    PXAI    PXAIPOV    PXAIPRV    PXAPIOE    PXBPPRV    PXBSTOR    PXBSTOR1
PXBUTL    PXCEVFI4    PXICLN27    PXICLN9B    PXQUTL3    PXQUTL3A    PXRRECSE    PXRRFDSE
PXRRWLSE    PXSCH3    PXUTL1    
Scheduling 8 SCMCTSK    SCMCTSK1    SCMCTSK9    SDCED    SDEC44    SDECAPI4    SDECV    SDPFSS2
Clinical Reminders 2 PXRMMST    PXRMVSIT    
Enterprise Health Management Platform 1 HMPDJ04    

Accessed By FileMan Db Calls, Total: 7

Package Total Routines
Scheduling 4 SCMCENCT    SDEC25B    SDECINI2    SDECV    
PCE Patient Care Encounter 2 PXCEPRV    PXRRMDR    
Clinical Information Resource Network 1 RGHOUT    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Scheduling 1 SDEC APPOINTMENT(#409.84)[.15]    

Pointer To FileMan Files, Total: 6

Package Total FileMan Files
Kernel 3 PACKAGE(#9.4)[81202]    PERSON CLASS(#8932.1)[.06]    NEW PERSON(#200)[.01]    
PCE Patient Care Encounter 3 PATIENT/IHS(#9000001)[.02]    VISIT(#9000010)[.03]    PCE DATA SOURCE(#839.7)[81203]    

Fields, Total: 13

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

  • LAST EDITED:  MAY 13, 1996
  • HELP-PROMPT:  Enter the provider of the patient encounter.
  • DESCRIPTION:  
    This is the provider giving patient care at this encounter.
  • CROSS-REFERENCE:  9000010.06^B
    1)= S ^AUPNVPRV("B",$E(X,1,30),DA)=""
    2)= K ^AUPNVPRV("B",$E(X,1,30),DA)
.02 PATIENT NAME 0;2 POINTER TO PATIENT/IHS FILE (#9000001)
************************REQUIRED FIELD************************
PATIENT/IHS(#9000001)

  • LAST EDITED:  AUG 10, 1995
  • HELP-PROMPT:  Enter the patient name.
  • DESCRIPTION:  
    Patient Name.
  • TECHNICAL DESCR:  
    Pointer to the Patient file.  Always stuffed by data entry, no editing allowed.
    UNEDITABLE
  • CROSS-REFERENCE:  9000010.06^C
    1)= S ^AUPNVPRV("C",$E(X,1,30),DA)=""
    2)= K ^AUPNVPRV("C",$E(X,1,30),DA)
    This cross reference allows lookup by Patient in this file.
.03 VISIT 0;3 POINTER TO VISIT FILE (#9000010)
************************REQUIRED FIELD************************
VISIT(#9000010)

  • INPUT TRANSFORM:  S DIC("S")="I $P(^(0),U,5)=$P(^AUPNVPRV(DA,0),U,2)" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X
  • LAST EDITED:  MAR 04, 1994
  • HELP-PROMPT:  Enter the encounter from the Visit file. Always stuffed.
  • DESCRIPTION:  
    The encounter entry in the Visit file where the provider gave clinical care to the patient.
  • TECHNICAL DESCR:  
    Pointer to the Visit file. Always stuffed by data entry, no editing allowed.
  • SCREEN:  S DIC("S")="I $P(^(0),U,5)=$P(^AUPNVPRV(DA,0),U,2)"
  • EXPLANATION:  VISIT MUST BE FOR CURRENT PATIENT
    UNEDITABLE
  • CROSS-REFERENCE:  9000010.06^AD
    1)= S ^AUPNVPRV("AD",$E(X,1,30),DA)=""
    2)= K ^AUPNVPRV("AD",$E(X,1,30),DA)
    This is used for programmed lookup by visit internal entry number.
  • CROSS-REFERENCE:  9000010.06^AV10^MUMPS
    1)= D ADD^AUPNVSIT
    2)= D SUB^AUPNVSIT
    This cross reference is used to add "1" to the Dependent Entry Count field (#.09) of the related Visit file (9000010) entry to indicate that there is a file (in this case V Provider) pointing to the Visit.
    When the measurement entry is deleted, this cross reference is used to subtract "1" from the Dependent Entry Count field (#.09) of the related Visit file (9000010) entry.
.04 PRIMARY/SECONDARY 0;4 SET
************************REQUIRED FIELD************************
  • 'P' FOR PRIMARY;
  • 'S' FOR SECONDARY;

  • LAST EDITED:  APR 27, 1994
  • HELP-PROMPT:  Enter a P if the provider is the primary care giver for the encounter, otherwise enter S.
  • DESCRIPTION:  This field indicates the provider was the primary or secondary care giver for the encounter. The primary provider is usually the physician responsible for the patients care at THIS PARTICULAR encounter, where clinical
    decisions were being made.  The primary provider for this encounter may or may not be the "Primary Care Provider" for this patient for overall care.
    Secondary providers are those providers, who were also providing care where clinical decisions were being made.  This may be nurses, social workers, pharmacists,...
    There may be more than one "primary" and "secondary" V Provider entries for a particular encounter in the Visit file.
  • TECHNICAL DESCR:  In the VA's PCE interfaces, "primary" is the default for provider entries where a provider has not been entered yet for the visit. "Secondary" is the default for provider entries where a provider already exist for the
    visit.
    SOURCE OF DATA:   028/PSPRIME
.05 OPERATING/ATTENDING 0;5 SET
  • 'A' FOR ATTENDING;
  • 'O' FOR OPERATING;

  • LAST EDITED:  APR 27, 1994
  • HELP-PROMPT:  Enter A if the provider was "Attending" at this encounter. Enter O if the provider was "Operating" at this encounter.
  • DESCRIPTION:  
    A Provider may be furthur identified as the "Attending" provider or an "Operating" provider for the encounter.
.06 PERSON CLASS 0;6 POINTER TO PERSON CLASS FILE (#8932.1) PERSON CLASS(#8932.1)

  • LAST EDITED:  JUN 13, 1996
  • DESCRIPTION:  
    This is the class of the provider at the time of the encounter.
1201 EVENT DATE AND TIME 12;1 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  APR 03, 1996
  • HELP-PROMPT:  Enter the date and time the provider had the encounter with the patient.
  • DESCRIPTION:  This is the date and time the provider had the encounter with the patient. This date and time may be different from the visit date and time. For example, for clinic appointment visits, the visit date and time is the date
    and time of the appointment, not the time the provider performed the clinical event.
    The date may be an imprecise date.
    Date and time may be within 30 days before or after the visit date, with the restriction the date cannot be a future date.
  • TECHNICAL DESCR:  The PCE User Interface, which allows manual entry of data, will be the primary source of the event date and time. The event date prompt defaults to the visit date, and the time is entered to reflect the actual time the
    provider had the encounter.  The event date does not have to be the visit date, but it must be within 30 days before or after the visit, and not be a future date.
    If a user wants to enter a historical provider encounter, the user should use the Historical Encounter entry action to document the historical encounter with the provider. Historical entries will not be eligible for
    credit.
    PCE Data Sources for automatic (scanning) data capture will be blank unless the event date and time are passed to PCE for filing.
80101 EDITED FLAG 801;1 SET
  • '1' FOR EDITED;

  • LAST EDITED:  MAR 14, 1994
  • HELP-PROMPT:  Answer is automatically entered by PCE filing logic.
  • DESCRIPTION:  
    This field is automatically set to 1 if PCE detects that any original provider data is being edited.
  • TECHNICAL DESCR:  
    PCE filing logic automatically compares the before and after pictures of the record to ddetermine if the edited flag should be set to "1".
80102 AUDIT TRAIL 801;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>85!($L(X)<2) X
  • LAST EDITED:  MAY 09, 1996
  • HELP-PROMPT:  Answer is automatically entered by the PCE filing logic.
  • DESCRIPTION:  
    This field is populated automatically by the PCE filing logic.  The formt of the field is as follows:  Pointer to PCE data source file_"-"_A for Add or E for Edit_"-"DUZ of the persion who entered the data_";"...
  • TECHNICAL DESCR:  The PCE filing logic requires a pointer to the PCE data source file. If this is not passed, then PCE filing logic will not process the data.
    If the record is a new record, then an "A" is used to specify the source that added the data.  If the record existed previously, PCE filing logic compares the old and new records of information.  An "E" will be
    automatically used if the filing logic finds the data has been edited.  If "E" is used, then the Edited Flag field is automatically set to 1.
    The DUZ is stored in its internal format to represent the user who performed the addition or editing of data for this record.
    Iterations of editing will be concatenated to the previous data source value, up to 85 characters.
81101 COMMENTS 811;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>245!($L(X)<1) X
  • LAST EDITED:  JUL 12, 1995
  • HELP-PROMPT:  Enter a comment 1-245 characters in length.
  • DESCRIPTION:  
    This is a comment related to the patient's provider.  The provider may enter this manually via the PCE User Interface.
81201 VERIFIED 812;1 SET
  • '1' FOR ELECTONICALLY SIGNED;
  • '2' FOR VERIFIED BY PACKAGE;

  • LAST EDITED:  MAY 09, 1996
    UNEDITABLE
81202 PACKAGE 812;2 POINTER TO PACKAGE FILE (#9.4) PACKAGE(#9.4)

  • LAST EDITED:  MAY 09, 1996
    UNEDITABLE
81203 DATA SOURCE 812;3 POINTER TO PCE DATA SOURCE FILE (#839.7) PCE DATA SOURCE(#839.7)

  • LAST EDITED:  MAY 09, 1996
    UNEDITABLE

ICR, Total: 2

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #2673
  • Clinical Information Resource Network
  • POINTER TO VISIT FILE (.03).
    Access: Read w/Fileman

    PRIMARY/SECONDARY (.04).
    Access: Read w/Fileman

    ICR #3455
  • Clinical Reminders
  • PROVIDER (.01).
    Access: Direct Global Read & w/Fileman

    VISIT (.03).
    Access: Direct Global Read & w/Fileman

    PATIENT NAME (.02).
    Access: Direct Global Read & w/Fileman

    PRIMARY/SECONDARY (.04).
    Access: Direct Global Read & w/Fileman

    External References

    Name Field # of Occurrence
    ^%DT 1201+1
    ADD^AUPNVSIT .03(XREF 2S)
    SUB^AUPNVSIT .03(XREF 2K)
    ^DIC .03+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^AUPNVPRV("AD" .03(XREF 1S), .03(XREF 1K)
    ^AUPNVPRV("B" .01(XREF 1S), .01(XREF 1K)
    ^AUPNVPRV("C" .02(XREF 2S), .02(XREF 2K)
    ^AUPNVSIT - [#9000010] ID.03+1
    ^DD("DD" ID.03+1
    ^DPT - [#2] ID.02+1

    Naked Globals

    Name Field # of Occurrence
    ^(0 ID.02+1, ID.03+1

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> %DT 1201+1*
    AIHSY ID.03+1*!
    >> DA .01(XREF 1S), .01(XREF 1K), .02(XREF 2S), .02(XREF 2K), .03(XREF 1S), .03(XREF 1K)
    DIC ID.02+1, ID.03+1, .03+1!*
    DIC("S" .03+1*, .03SCR+1*
    >> DIE .03+1
    U ID.02+1, ID.03+1
    X .01(XREF 1S), .01(XREF 1K), .02(XREF 2S), .02(XREF 2K), .03+1*!, .03(XREF 1S), .03(XREF 1K), 1201+1*!, 80102+1!, 81101+1!
    >> Y ID.03+1*, .03+1, 1201+1
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All