Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Source Information |  Call Graph |  External References |  All
Print Page as PDF
Remote Procedure: PSB TRANSACTION

Package: Barcode Medication Administration

Remote Procedure: PSB TRANSACTION


Source Information

Name Value
NAME PSB TRANSACTION
TAG RPC
ROUTINE PSBML
RETURN VALUE TYPE ARRAY
AVAILABILITY PUBLIC
VERSION 3
DESCRIPTION
This is the filing RPC for all data returning from the client
sequence 1). If a '+1^MEDPASS' is encountered it is a complete new med 
-------------------------------------------------------------------------
TRANSACTION = PRN EFFECTIVENESS
 [0] = Effective Comment
   Note: will be filed as entered now by current user
 -------------------------------------------------------------------------
TRANSACTION = STATUS UPDATE
pass and is validated as such.  Transaction type MEDPASS is the only type 
 [0] = New Status
   Note: If status is Given, Date/Time administered D/T will be set to NOW
         If status is Held/Refused administered D/T will be set to null
         Status on med log must be <> null to execute.
         New status must NOT match current status or G will overwrite 
         administration DT.
 [1] = Comment
   Note: Comment *IS* Required
that requires a +1 in the first piece of the header, all other 
 [2] = Injection Site
 [3] =
 [4] = RecordType^IEN^Units Ordered^Units Given^Units Type^^HR code^MRR
       code
          1) Record Type = DD:  Dispense Drug
                          SOL:  Solution
                          ADD:  Additive
transactions MUST supply a valid medication log entry in the IENS.
          2) IEN = Internal Entry Number of the following
                   if Record Type = DD:  DRUG (FILE #50)
                                SOL: IV SOLUTIONS (FILE #??)
                                ADD: IV ADDITIVES (FILE #??)
          3) Units Ordered = Number of units in the Inpt Meds Order
          4) Units Given = Number of units scanned/entered by the user
          5) Units Type = Type of administration unit (i.e. TAB, CAP,ML)
          6) n/a
          7) Orderable Item High Risk/High Alert code value
                (HR = 1, 2, or 3)
          8) Orderable Item Prompt For Removal In BCMA code value
                (MRR = 0, 1, or 3)
The data for filing is passed in as a list in Param[1] as shown below.
-------------------------------------------------------------------------
TRANSACTION = EDIT   (This is the MEDLOG Edit an existing transaction)
 [0] = Action Status
 [1] = Patient DFN
 [2] = Inf/Inj Site
 [3] = IV Unique ID
 [4] = Admin Date/Time (fileman format)
 [5] = Prn Reason
 [6] = Prn Effectiveness
 [7] = Comment
       Note: comment data is required!
 [8] = "DD/ADD/SOL^ Drug IEN ^ Dose Ordered ^ Dose Given ^ Unit of 
        Administration" ^ High Risk High Alert code ^ Prompt For Removal
        In BCMA code
 [n] = "additional data per DD/ADD/SOL associated with order."
Example Delphi Call
  with RPCBroker1 do
regarding the medication log.  Filing is handled by business rules on
    begin
    RemoteProcedure := 'PSB TRANSACTION';
    Param[0].Value := '88484^COMMENT';
    Param[0].PType := Literal;
    Param[1].Mult['0'] := 'Comment for the med pass';
    Param[1].Ptype := List;
    Call;
    end;
BUSINESS LOGIC controlled by Param[0]:
the server and this RPC will return either '1^Data Filed' or
Param[0] = MEDLOG IEN ^ TRANSACTION ^ INSTRUCTOR DUZ ^ WITNESS DUZ
           ^ WITNESS COMMENT ^ WITNESS HR ORDER LEVEL CODE
-------------------------------------------------------------------------
TRANSACTION = MEDPASS  (this is the MEDLOG ADD a new transaction)
   Note: Entries 1-6 are required, 7,8,9 are required depending on 
         item [2] order type...
 [0] = Patient IEN
'-1^reason for not filing data' to the client.  Results of the 
 [1] = IV/Unit Dose Order Number ^ Clinic Name (if a clinic order)
   Note: will be passed in as I;#### for IV and U;#### for Unit Dose
         future release will allow P;#### for pending
 [2] = Schedule
   Note: C:Continuous P:PRN 1:One Time O:On Call
 [3] = Status
processed transaction is communicated via the RESULTS array.  The 
   Note: G:Given H:Held R:Refused
 [4] = Orderable Item
   Note: IEN to 'PHARMACY ORDERABLE ITEM' (#50.7)
 [5] = Scheduled Administration Date/Time
   Note: This is when the med is scheduled, med is entered as GIVEN NOW!
 [6] = Reason Given PRN^PRN Reason Flag
   Note: Required if given PRN must be null if not PRN
number of RESULTS subscripts used (n) will be presented in RESULTS[0].  
 [7] = Comment
   Note: 1-200 characters
 [8] = Injection Site
 [9] = Tab^Unique ID #
[10] = Schedule Removal Date/Time
       Note:This is when the med is scheduled to be removed and not the 
            actual removal transaction date/time.  
RESULTS [1..n] will contain the RESULTS message.  
[11..n] = RecordType^IEN^Units Ordered^Units Given^Units Type^^HR code^MRR
          code
          1) Record Type = DD:  Dispense Drug
                          SOL:  Solution
                          ADD:  Additive
          2) IEN = Internal Entry Number of the following
                   if Record Type = DD:  DRUG (FILE #50)  
                                SOL: IV SOLUTIONS (FILE #??)
                                ADD: IV ADDITIVES (FILE #??)
          3) Units Ordered = Number of units in the Inpt Meds Order
          4) Units Given = Number of units scanned/entered by the user
          5) Units Type = Type of administration unit (i.e. TAB, CAP,ML)
          6) n/a
Business rules are conducted via the [0] node data (Input parameter 
          7) Orderable Item High Risk/High Alert code value
                (HR = 1, 2, or 3)
          8) Orderable Item Prompt For Removal In BCMA code value
                (MRR = 0, 1, or 3)
-------------------------------------------------------------------------
TRANSACTION = COMMENT
 [0] = Comment to append to the log entry
   Note: Will be appended to the log with user ien and NOW as a date
INPUT PARAMETER
  1. INPUT PARAMETER:   PSBHDR
    PARAMETER TYPE:   LITERAL
    REQUIRED:   YES
    SEQUENCE NUMBER:   1
    DESCRIPTION:   
    Contains the IEN or +1 up-arrow transaction.  See RPC description.
    
  2. INPUT PARAMETER:   PSBREC
    PARAMETER TYPE:   LIST
    REQUIRED:   YES
    SEQUENCE NUMBER:   2
    DESCRIPTION:   
    See description.
    
RETURN PARAMETER DESCRIPTION
See description.

Call Graph

Call Graph

Call Graph Total: 1

Package Total Call Graph
Barcode Medication Administration 1 RPC^PSBML  

External References

Name Field # of Occurrence
RPC^PSBML 1
Source Information |  Call Graph |  External References |  All