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 |  Pointer To FileMan Files |  Fields  | All
Print Page as PDF
Global: ^AUPNVSC

Package: PCE Patient Care Encounter

Global: ^AUPNVSC


Information

FileMan FileNo FileMan Filename Package
9000010.71 V STANDARD CODES PCE Patient Care Encounter

Description

Directly Accessed By Routines, Total: 9

Package Total Routines
PCE Patient Care Encounter 8 PXAISC    PXBGSC    PXCESC    PXKMCODE    PXMCEVNT    PXMCLINK    PXPXRM    PXPXRMI2
Clinical Reminders 1 PXRMVSC    

Accessed By FileMan Db Calls, Total: 4

Package Total Routines
PCE Patient Care Encounter 4 PXCESC    PXP211I    PXPXRMI2    PXVSCSM    

Pointer To FileMan Files, Total: 7

Package Total FileMan Files
PCE Patient Care Encounter 3 PATIENT/IHS(#9000001)[.02]    VISIT(#9000010)[.03]    PCE DATA SOURCE(#839.7)[81203]    
Kernel 2 PACKAGE(#9.4)[81202]    NEW PERSON(#200)[12021204]    
Lexicon Utility 1 UCUM CODES(#757.5)[221]    
Problem List 1 PROBLEM(#9000011)[.06]    

Fields, Total: 17

Field # Name Loc Type Details
.01 CODE 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  JAN 07, 2019
  • HELP-PROMPT:  Enter a code, 3 to 40 characters.
  • DESCRIPTION:  This is a code such as SNOMED CT.
  • CROSS-REFERENCE:  9000010.71^B
    1)= S ^AUPNVSC("B",$E(X,1,30),DA)=""
    2)= K ^AUPNVSC("B",$E(X,1,30),DA)
  • RECORD INDEXES:  ACR (#1037), SCC (#1039)
.02 PATIENT NAME 0;2 POINTER TO PATIENT/IHS FILE (#9000001)
************************REQUIRED FIELD************************
PATIENT/IHS(#9000001)

  • LAST EDITED:  AUG 11, 2017
  • HELP-PROMPT:  Enter the patient.
  • DESCRIPTION:  This is the patient for whom the code is being recorded.
  • RECORD INDEXES:  ACR (#1037)
.03 VISIT 0;3 POINTER TO VISIT FILE (#9000010)
************************REQUIRED FIELD************************
VISIT(#9000010)

  • LAST EDITED:  AUG 11, 2017
  • HELP-PROMPT:  Enter the visit date/time for the encounter/visit.
  • DESCRIPTION:  This is the encounter or occasion of service defined in the Visit file that represents when and where the standardized code was recorded for the patient.
  • CROSS-REFERENCE:  9000010.71^AV10^MUMPS
    1)= D ADD^AUPNVSIT
    2)= D SUB^AUPNVSIT
    This cross-reference adds and subtracts from the dependent entry count in the VISIT file.
  • FIELD INDEX:  AD (#1038) MUMPS IR ACTION
    Short Descr: VISIT index
    Description: This cross-reference is used for searches by the visit pointer and internal entry number.
    Set Logic: S ^AUPNVSC("AD",X,DA)=""
    Kill Logic: K ^AUPNVSC("AD",X,DA)
    X(1): VISIT (9000010.71,.03) (Subscr 1) (forwards)
  • RECORD INDEXES:  ACR (#1037)
.05 CODING SYSTEM 0;5 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:($L(X)>7!($L(X)<3))!('$$VCODESYS^PXINPTR(.X)) X
    MAXIMUM LENGTH: 7
  • LAST EDITED:  JAN 07, 2019
  • HELP-PROMPT:  Enter the coding system, 3 to 7 characters.
  • DESCRIPTION:  A coding system is stored as one of the standard three-character abbreviations as defined in the Lexicon Coding Systems file #757.03.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • RECORD INDEXES:  ACR (#1037), SCC (#1039)
.06 PROBLEM LIST ENTRY 0;6 POINTER TO PROBLEM FILE (#9000011) PROBLEM(#9000011)

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter the problem entry from the patient's problem list for the problem treated.
  • DESCRIPTION:  This field identifies what Problem List entry is related to the problem treated at the visit.
  • TECHNICAL DESCR:  This field is populated automatically and should not be edited.
220 MAGNITUDE 220;1 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999999999999)!(X<-99999999999999)!(X?.E1"."10N.N) X
  • LAST EDITED:  DEC 06, 2018
  • HELP-PROMPT:  Enter the magnitude of the measurement, a positive or negative number, up to 14 digits and 9 decimal places.
  • DESCRIPTION:  If a measurement has been recorded for an entry in this file, this is the magnitude of the measurement.
221 UCUM CODE 220;2 POINTER TO UCUM CODES FILE (#757.5) UCUM CODES(#757.5)

  • LAST EDITED:  SEP 09, 2015
  • HELP-PROMPT:  Enter the UCUM code of the measurement.
  • DESCRIPTION:  If a measurement has been recorded for an entry in this file, this is the unit of the measurement.
300 MAPPED SOURCE 300;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<3) X
    MAXIMUM LENGTH: 40
  • LAST EDITED:  MAR 01, 2016
  • HELP-PROMPT:  Answer must be 3-40 characters in length.
  • DESCRIPTION:  If this entry was created because of codes that were mapped to PCE data types such as Education Topics, Exams, Health Factors, Immunizations, and Skin Tests this field will contain the file number and internal entry number
    of the corresponding data type entry in the format: file number;IEN.
  • RECORD INDEXES:  SCC (#1039)
1201 EVENT DATE AND TIME 12;1 DATE

  • INPUT TRANSFORM:  S %DT="ESTX" D ^%DT S X=Y K:(Y<1)!(Y>$$NOW^XLFDT) X
  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter the date and time the code was given.
  • DESCRIPTION:  This is the date and time the code was recorded by the provider. 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 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 NOW. The Event Date does not have to be the Visit Date, but it cannot be a
    future date.
    If a user wants to enter an historical measurement, the user should use the Historical Encounter entry action to document the historical measurement. 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.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • RECORD INDEXES:  ACR (#1037)
1202 ORDERING PROVIDER 12;2 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter the provider who ordered this code recorded.
  • DESCRIPTION:  This field can be used to document the provider who ordered the code recorded.
1204 ENCOUNTER PROVIDER 12;4 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  SEP 09, 2015
  • HELP-PROMPT:  Enter the provider who recorded the code.
  • DESCRIPTION:  This is the provider who recorded the code.
80101 EDITED FLAG 801;1 SET
  • '1' FOR EDITED;

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter 1 if the original standard codes data is being edited.
  • DESCRIPTION:  This field is automatically set to 1 if PCE detects that any original standard codes data is being edited.
  • TECHNICAL DESCR:  PCE filing logic automatically compares the before and after pictures of the record to determine 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:  JAN 04, 2019
  • HELP-PROMPT:  Answer must be 2-85 characters in length.
  • DESCRIPTION:  This field is populated automatically by the PCE filing logic. The format of the field is as follows: Pointer to PCE data source file_"-"_A for Add or E for Edit_" "_DUZ of the person 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 automatically be
    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 adding 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:  JAN 04, 2019
  • HELP-PROMPT:  Answer must be 1-245 characters in length.
  • DESCRIPTION:  This is a comment related to the standard code given to the patient. The provider may enter this manually via the PCE User Interface.
81201 VERIFIED 812;1 SET
  • '1' FOR FOR ELECTRONICALLY SIGNED;
  • '2' FOR FOR VERIFIED BY PACKAGE;

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter 1 if verified by electronic signature or 2 if verified by package.
  • DESCRIPTION:  This is used to note how the event was verified and is automatically entered by the software.
  • TECHNICAL DESCR:  This is automatically entered by the software and is uneditable for users.
81202 PACKAGE 812;2 POINTER TO PACKAGE FILE (#9.4) PACKAGE(#9.4)

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Enter the VistA package from which this standard code originated.
  • DESCRIPTION:  This is the VistA package from which this standard code originated through PCE.
    This is automatically entered by the software and uneditable by users.
81203 DATA SOURCE 812;3 POINTER TO PCE DATA SOURCE FILE (#839.7) PCE DATA SOURCE(#839.7)

  • LAST EDITED:  JAN 04, 2019
  • HELP-PROMPT:  Select the data source for this standard code entry through PCE.
  • DESCRIPTION:  This is the data source for this standard code. It is set automatically and uneditable by users.
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields  | All