MD TMDPARAMETER

TITLEVALUE
NAMEMD TMDPARAMETER
DESCRIPTIONUsed to set/retrieve/modify parameters in the Kernel ToolKit PARAMETERS
(XPAR) files.

RPC is called as follows:

Param[0] := OPTION
Param[1] := Entity
Param[2] := Parameter name
Param[3] := Instance
Param[4] := Value
TAGRPC
ROUTINEMDRPCOV
INPUT PARAMETERSSEQUENCE NUMBER1
INPUT PARAMETEROPTION
DESCRIPTIONContains the option for the RPC. RPC is called as shown:

Options and other required parameters include:

ENTVAL ENT
GETPAR ENT,PAR,INST
GETLST ENT,PAR
GETWP ENT,PAR,INST
SETPAR ENT,PAR,INST,VAL
SETLST ENT,PAR,,.VAL (Uses instance 0-n)
SETWP ENT,PAR,INST,.VAL
DELPAR ENT,PAR,INST
DELLST ENT,PAR
PARAMETER TYPELITERAL
REQUIREDYES
MAXIMUM DATA LENGTH10
INPUT PARAMETERSSEQUENCE NUMBER2
INPUT PARAMETERENTITY
DESCRIPTIONAn entity is a level at which you can define a parameter. The entities
allowed are stored in the Parameter Entity file (#8989.518). The list of
allowable entities at the time this utility was released were:

Prefix Message Points to File
PKG Package Package (9.4)
SYS System Domain (4.2)
DIV Division Institution (4)
SRV Service Service/Section (49)
LOC Location Hospital Location (44)
TEA Team Team (404.51)
CLS Class Usr Class (8930)
USR User New Person (200)
BED Room-Bed Room-Bed (405.4)
OTL Team (OE/RR) OE/RR List (101.21)

The entity may be referenced as follows:
1) The internal variable pointer (nnn;GLO(123,)
2) The external format of the variable pointer using the 3 character
prefix (prefix.entryname)
3) The prefix alone to set the parameter based on current entity selected.
(prefix)

Method 3 uses the following values for the following entities:
USR Current value of DUZ
DIV Current value of DUZ(2)
SYS System (domain)
PKG Package to which the parameter belongs
PARAMETER TYPELITERAL
REQUIREDNO
MAXIMUM DATA LENGTH20
INPUT PARAMETERSSEQUENCE NUMBER3
INPUT PARAMETERPAR
DESCRIPTIONA parameter is the actual name which values are stored under. The name of
the parameter must be namespaced and it must be unique. Parameters can be
defined to store the typical package parameter data (e.g. the default add
order screen), but they can also be used to store GUI application screen
settings a user has selected (e.g. font or window width). When a
parameter is defined, the entities, which may set that parameter, are also
defined. The definition of parameters is stored in the PARAMETER
DEFINITION file (#8989.51).

NOTE: This utility restricts the parameter name to those in the Clinical
Procedures namespace (MD*).
PARAMETER TYPELITERAL
REQUIREDNO
MAXIMUM DATA LENGTH30
INPUT PARAMETERSSEQUENCE NUMBER4
INPUT PARAMETERINST
DESCRIPTIONMost parameters will set instance to 1. Instances are used when more than
one value may be assigned to a given entity/parameter combination. An
example of this would be lab collection times at a division. A single
division may have multiple collection times. Each collection time would
be assigned a unique instance.
PARAMETER TYPELITERAL
REQUIREDNO
MAXIMUM DATA LENGTH30
INPUT PARAMETERSSEQUENCE NUMBER5
INPUT PARAMETERVAL
DESCRIPTIONA value may be assigned to every parameter for the entities allowed in the
parameter definition. Values are stored in the PARAMETERS file (#8989.5).
VAL may be passed in external or internal format. If using internal
format for a pointer type parameter, VAL must be preceded with the grave
(`) character. If VAL is being assigned to a word processing parameter,
the text is passed in the subordinate nodes of VAL (e.g. VAL(0-n)=Text).
PARAMETER TYPELITERAL
REQUIREDNO
MAXIMUM DATA LENGTH80
RETURN VALUE TYPEGLOBAL ARRAY
RETURN PARAMETER DESCRIPTIONReturns requested data from the specified option.
AVAILABILITYRESTRICTED
INACTIVE
CLIENT MANAGER
WORD WRAP ONTRUE
VERSION
SUPPRESS RDV USER SETUP
APP PROXY ALLOWED