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 |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR  | All
Print Page as PDF
Global: ^RMPR(661.6

Package: Prosthetics

Global: ^RMPR(661.6


Information

FileMan FileNo FileMan Filename Package
661.6 PROSTHETIC INVENTORY TRANSACTION Prosthetics

Description

Accessed By FileMan Db Calls, Total: 2

Package Total Routines
Prosthetics 2 RMPRPIX6    RMPRPIXA    

Pointed To By FileMan Files, Total: 3

Package Total FileMan Files
Prosthetics 3 RECORD OF PROS APPLIANCE/REPAIR(#660)[4.6]    PROSTHETIC TRANSACTION PATIENT ISSUE(#661.63)[.01]    PROSTHETIC INVENTORY GAIN/LOSS(#661.69)[.01]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
Kernel 2 INSTITUTION(#4)[13]    NEW PERSON(#200)[9]    
IFCAP 1 VENDOR(#440)[12]    
Prosthetics 1 PROSTHETIC STOCK LOCATION(#661.5)[14]    

Fields, Total: 12

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

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<5) X
  • LAST EDITED:  SEP 08, 2005
  • HELP-PROMPT:  Answer must be 5-20 characters in length.
  • DESCRIPTION:  
    This field is the HCPCS code as defined by the .01 field in the PROSTHETIC HCPCS file (661.1).
  • CROSS-REFERENCE:  661.6^B
    1)= S ^RMPR(661.6,"B",$E(X,1,30),DA)=""
    2)= K ^RMPR(661.6,"B",$E(X,1,30),DA)
  • RECORD INDEXES:  ADHS (#30), ASHD (#31), ASTHIDS (#33), XHDS (#34)
2 DATE&TIME STAMP 0;2 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  MAR 20, 2002
  • DESCRIPTION:  This field is the date and time stamp (fileman standard format) of the transaction. This field will be automatically generated by the system and assumes users will record inventory transactions in a timely manner. It is
    one of the primary key fields and is also recorded on the barcode. It is a requirement that the date@time stamp should have a unique value for any given HCPCS. The reason for this is that HCPCS will also be recorded on an
    item's barcode and it is important that barcodes will not need changing if a site is integrated at some time in the future. Given the date&time stamp and HCPCS fields it is possible to generate a transactions IEN using
    the appropriate cross-reference.
  • CROSS-REFERENCE:  661.6^C
    1)= S ^RMPR(661.6,"C",$E(X,1,30),DA)=""
    2)= K ^RMPR(661.6,"C",$E(X,1,30),DA)
  • RECORD INDEXES:  ADHS (#30), ASHD (#31), ASLD (#32), ASTHIDS (#33), XHDS (#34), XSTD (#35)
3 SEQUENCE 0;3 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  JAN 17, 2001
  • HELP-PROMPT:  Type a number between 1 and 999999999, 0 Decimal Digits
  • DESCRIPTION:  This field is a sequence number starting at 1 and incremented by 1 for each transaction which has the same HCPCS and DATE&TIME STAMP fields. This situation should be very rare and only occurs at all after site
    integrations. The HCPCS, DATE&TIME STAMP and SEQUENCE fields together make up the primary key for this file. The rationale behind this design is to allow the HCPCS and DATE&TIME STAMP to be printed as a barcode for
    automated data entry on a stock issue form. Fileman IENs will be derived from appropriate cross-references and, of course, these IENs can all change if a site is integrated. On the rare occasions where there is more than
    1 SEQUENCE number associated with a HCPCS and DATE&TIME STAMP the user will have to be prompted to select from a list of transactions. We see no way round this inconvenience but hopefully it will be extremely rare!
  • RECORD INDEXES:  ADHS (#30), ASTHIDS (#33), XHDS (#34)
4 TRANSACTION TYPE 0;4 SET
  • '1' FOR RECEIPT;
  • '2' FOR ORDER;
  • '3' FOR PATIENT ISSUE;
  • '4' FOR ISSUE TO LAB;
  • '5' FOR RETURN TO VENDOR;
  • '6' FOR WRITE OFF;
  • '7' FOR TRANSFER;
  • '8' FOR RETURN IN;
  • '9' FOR RECONCILE;

  • LAST EDITED:  MAY 15, 2001
  • DESCRIPTION:  This field records the transaction type, which can be one of the following...
    Receipt - for receiving items into stock.
    Order - for when a stock item has been ordered from the vendor.
    Patient Issue - for when a stock item is issued to a veteran.
    Issue to Lab - this transaction should be used for those items which are
    used by the labs to fabricate items. An example would be a
    bag of plaster which could be used for treating several
    patients.
    Return to Vendor - if an item has been received into stock but is later
    returned to the vendor for some reason, then this
    transaction type should be used.
    Write Off - use this transaction type when an item is removed from stock
    and scrapped.
    Transfer - for transferring stock between locations. The transaction
    quantity will be -ve for the 'transfer from' location.
    Return In - for when a veteran returns a stock item previously issued.
    Reconcile - for when a stock check is done.
  • RECORD INDEXES:  ASTHIDS (#33), XSTD (#35)
5 QUANTITY 0;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999999)!(X<-999999)!(X?.E1"."1N.N) X
  • LAST EDITED:  APR 26, 2001
  • HELP-PROMPT:  Type a Number between -999999 and 99999999, 0 Decimal Digits
  • DESCRIPTION:  
    The number of items associated with the transaction.
6 VALUE 0;6 NUMBER

  • INPUT TRANSFORM:  S:X["$" X=$P(X,"$",2) K:X'?."-".N.1".".2N!(X>99999999)!(X<-999999) X
  • LAST EDITED:  APR 26, 2001
  • HELP-PROMPT:  Type a Dollar Amount between -999999 and 99999999, 2 Decimal Digits
  • DESCRIPTION:  
    The dollar value of the transaction.
8 COMMENT 0;8 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1) X
  • LAST EDITED:  NOV 29, 2000
  • HELP-PROMPT:  Answer must be 1-40 characters in length
  • DESCRIPTION:  
    A short comment can be entered, if required for a particular transaction.
9 USER 0;9 POINTER TO NEW PERSON FILE (#200) NEW PERSON(#200)

  • LAST EDITED:  NOV 29, 2000
  • DESCRIPTION:  
    This field points to the New Person file (200) and identifies the person responsible for creating the transaction on the system.
11 HCPCS ITEM 0;11 NUMBER
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:+X'=X!(X>9999999999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  FEB 20, 2001
  • HELP-PROMPT:  Type a Number between 1 and 9999999999, 0 Decimal Digits
  • DESCRIPTION:  
    This field is the HCPCS ITEM field held on the 661.12 sub field of the PROSTHETIC HCPCS file (661.1). The value held is the sub file's IEN not the ITEM text field.
  • RECORD INDEXES:  ASTHIDS (#33)
12 VENDOR 0;12 POINTER TO VENDOR FILE (#440) VENDOR(#440)

  • LAST EDITED:  JAN 18, 2001
  • HELP-PROMPT:  Answer must be 1-30 characters in length
  • DESCRIPTION:  This field is the FMS VENDOR CODE held on the VENDOR file (440). This field is guaranteed to be unique irrespective of where a database is located. The Vendor IEN should be derived from the 'D' cross-reference of the
    Vendor file.
13 STATION 0;13 POINTER TO INSTITUTION FILE (#4) INSTITUTION(#4)

  • LAST EDITED:  MAY 15, 2001
  • DESCRIPTION:  
    This field is a pointer to the INSTITUTION file (4).
  • RECORD INDEXES:  ASHD (#31), ASLD (#32), ASTHIDS (#33), XSTD (#35)
14 LOCATION 0;14 POINTER TO PROSTHETIC STOCK LOCATION FILE (#661.5) PROSTHETIC STOCK LOCATION(#661.5)

  • LAST EDITED:  APR 19, 2001
  • DESCRIPTION:  
    This field is a pointer to the PROSTHETIC STOCK LOCATION file (661.5).
  • RECORD INDEXES:  ASLD (#32)

ICR, Total: 1

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #6778
  • ADVANCED PROSTHETICS ACQ TOOL
  • PROSTHETICS VISION 4 SIGHT II
    		•  HCPCS (.01).
    Access: Read w/Fileman

    QUANTITY (5).
    Access: Read w/Fileman

    VALUE (6).
    Access: Read w/Fileman

    HCPCS ITEM (11).
    Access: Read w/Fileman

    VENDOR (12).
    Access: Read w/Fileman

    STATION (13).
    Access: Read w/Fileman

    LOCATION (14).
    Access: Read w/Fileman

    DATE&TIME STAMP (2).
    Access: Read w/Fileman

    SEQUENCE (3).
    Access: Read w/Fileman

    TRANSACTION TYPE (4).
    Access: Read w/Fileman

    COMMENT (8).
    Access: Read w/Fileman

    USER (9).
    Access: Read w/Fileman

    		 Used to look up the IEN of a HCPCSUsed to look up the IEN of a STATION & HCPCS & DATE&TIMESTAMPUsed to look up a DATE&TIME STAMP
    Info |  Desc |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR  | All