Global: ^APCDTKW

FileMan FileNo	FileMan Filename	Package
9001001	RPMS PCC DATA ENTRY CONTROL	Patient Care Component

Description

The APCD INPUT TEMPLATES are defined to run in conjunction with the RPMS PCC Data Entry program (APCD routines). These routines create several variables that can be used within a template to stuff fields where appropriate. The ADD mode variables that are always set are: APCDPAT .. The DFN of the current patient. APCDDOB .. The current patient's date of birth. APCDDOB .. The current patient's date of death. APCDSEX .. The current patient's sex. APCDLOC .. The DFN of the current facility. APCDTYPE .. The current VISIT type. APCDCAT .. The current VISIT service category. APCDDATE .. The current VISIT date in CYYMMDD format. APCDVSIT .. The DFN of the newly created VISIT. When FileMan creates a new entry in a file he asks for all IDENTIFIERS. Many of the identifiers for the various files have already been asked by the APCD routines, therefore, to prevent FileMan from reasking, a mechanism has been provided that circumvents that process. For each appropriate file, on the .01 field, is a MUMPS xref (AZ9) which accomplishes this, but only when an APCD INPUT TEMPLATE is running. To specify that this is an APCD INPUT TEMPLATE the template must 'S APCDLOOK=""' prior to the context switch. The APCD routines KILL APCDLOOK after each mnemonic. When FileMan does a context switch from file 'A' to file 'B', he stuffs the LINK field in file 'B' and fires any xrefs associated with that field. We have MUMPS xrefs on many LINK fields that concatenate data from multiple identifier fields. That creates problems when we prevent FileMan from asking for identifiers, so those xrefs have been modified to exit if the other fields are missing, and a TRIGGER has been added to the other fields to cause the xref to be fired when the data is added. What this means to the creator of an APCD INPUT TEMPLATE is care must be taken to assure the other identifier fields are stuffed by the template. To force an add to a file without quoting the key value attach the add mode INPUT TEMPLATE to a file logically above the file to which the entry is to be added, and use context switching to force a new entry in the target file. Use the previously mentioned context switching technique to eliminate the need for screens. For example: to add a 'note' to a problem in the PROBLEM file you must first select the appropriate problem. If the INPUT TEMPLATE is attached to the PROBLEM file you must set a screen to limit the lookup to the current patient. If the INPUT TEMPLATE is attached to the PATIENT file, the context switch will take care of the screen for you. ---------- In ADD mode, for some files, one wants to force, or default, the value of a field to the same value as a previously entered field. To accomplish this, immediately after entering the original value, set an APCD variable to some derivitive of X. At this point in time X will contain the internal representation of the value just entered. Then set the second field equal to the APCD variable just created. After the last use of the APCD variable it must be KILLED. To see an example see the APCD PO (ADD) template attached to the PATIENT file. ---------- ***** Use the variable APCDL for 'forever loops' but never KILL it. The APCD add routines always create a VISIT to which the files affected by the entry of mnemonics, are linked. If a mnemonic is going to create a different VISIT entry, certain variables must be set prior to the context switch. These variables are used by ^AUPNVSIT for relational edit purposes. The setting of these variables is accomplished with the following code: S AUPNDA=APCDPAT,AUPNDOB=APCDDOB,AUPNDOD=APCDDOD,AUPNSEX=APCDSEX ^AUPNVIST always KILLS the AUPN variables listed above prior to exiting, so they must be set each time a new VISIT entry is created. ---------- Any mnemonic that creates a V POV entry, or a V PROVIDER entry, for the current VISIT must set a subscripted variable to let the APCD add routines know that such entries have been accomplished. The reason this must be done is an entry in each of those files is required for each VISIT. The APCD add routines will not allow the user to exit if those entries have not been made. The code to set the subscripted variable for a V POV follows: S APCDH("PV")="" The "PV" represents the mnemonic that normally creates the V POV entry. ---------- To generate an entry in a VISIT related file (e.g. 'A') based on data entered into some other VISIT related file (e.g. 'B') you must create a MUMPS xref on the field in file 'B' that sets the variable APCDLOOK to the key value in the file into which you are going to generate a new entry 'A'. Then, after returning to the VISIT file, do a context switch to file 'A' using the following syntax: LOOKUP:A: Name these special MUMPS xrefs AZn where n is some number not previously used. ----------

Package	Total	Routines
Patient Care Component	11	APCDEA2 APCDEA3 APCDEFL APCDEH APCDEH1 APCDEL APCDEL1 APCDPE APCDPE1 APCDPE2 APCDPTKW
PCC New Encounter Form	1	VENPCCQY

Package	Total	Routines
Patient Care Component	33	APCD2010 APCD20P2 APCD20P3 APCD20P4 APCD20P5 APCD20P6 APCD20P7 APCD20P8 APCD20P9 APCDEA2 APCDEAP APCDEAPC APCDEATC APCDECPT APCDEDTC APCDEGP1 APCDEH1 APCDEHI2 APCDEHTC APCDEL1 APCDELAB APCDEM APCDENV APCDEPO APCDERAD APCDPE2 BJPC1EC1 BJPC2ENP BJPC2ENV BJPC2P1 BJPC2P11 BJPC2P5 BJPC2P7
Asthma Tracking System	1	BATPOST
IHS Changes To ADT	1	ADGPCAC0
IHS Support HL7 Interfaces	1	BHL3MS
PCC New Encounter Form	1	VENPCCQY

Package	Total	FileMan Files
PCC New Encounter Form	2	VEN EHP KB CLINICAL DOMAIN(#19707.13)[.03] VEN EHP EF TEMPLATES(#19707.41)[10.01]
Patient Care Component	1	PCC DATA ENTRY SITE PARAMETERS(#9001001.2)[#9001001.21201(.01)]

Package	Total	FileMan Files
VA Fileman	1	FILE(#1)[.03, .09, .14]

Fields, Total: 19

Field #	Name	Loc	Type	Details
.01	MNEMONIC	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>8!($L(X)<2)!'(X'?1P.E) X` LAST EDITED: `AUG 02, 1990` HELP-PROMPT: `ANSWER MUST BE 2-8 CHARACTERS IN LENGTH` DESCRIPTION: `This field contains the 'data entry mnemonic', or a psuedo INPUT TEMPLATE for entering data from the various logs. If the MNEMONIC name is 2-3 characters long it is considered a MNEMONIC (e.g. 'BP' or 'TON'). If the` MNEMONIC name is >=4 characters long it is considered a psuedo INPUT TEMPLATE. DELETE TEST: `.01,0)= I 1` CROSS-REFERENCE: `9001001^B` 1)= S ^APCDTKW("B",$E(X,1,30),DA)="" 2)= K ^APCDTKW("B",$E(X,1,30),DA)
.02	MODE	0;2	SET	'S' FOR SPECIAL; DESCRIPTION: `The primary MODE (i.e. ADD or MODIFY) is determined at the menu level. However, within the primary ADD MODE, which is the data entry operator's view, the MODE, as viewed by FileMan, may change on a mnemonic by menmonic` basis. For example, while in ADD MODE an operator may add a VISIT using the standard logic which does not ask for the CLINIC TYPE field. If the CLINIC TYPE is on the form, the operator will enter mnemonic 'CL' to add the CLINIC TYPE. The primary mode is still ADD but the VISIT entry now exists, so to FileMan it is a MODIFY. Additionally, in general, in MODIFY MODE, the operator has the opportunity to modify any allowable field in the dictionary being modified. If the only field the operator wanted to modify was the CLINIC TYPE, the mnemonic 'CL' could be entered and only that field would be asked for. To accomodate this functionality, the RPMS PCC Data Entry routines execute INPUT TEMPLATEs which have the same name with (ADD), (MOD), or (ss) appended, where 'ss' represents the special mnemonic (e.g. 'CL').
.03	FILE	0;3	POINTER TO FILE FILE (#1)	FILE(#1) DESCRIPTION: This is the file to which the 'ADD' mode INPUT TEMPLATE is attached. All 'MODIFYs' are attached to the PATIENT file, and switch context from there.
.04	TEMPLATE	0;4	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<3)!'(X?1"[".E1"]") X` HELP-PROMPT: `ANSWER MUST BE 3-30 CHARACTERS IN LENGTH` DESCRIPTION: `This is the general INPUT TEMPLATE name enclosed by []. Attached to the appropriate file will be a template with this name_(ADD), or name_(ss) as appropriate. Attached to the PATIENT file will be a template with this` name_(MOD).
.05	KEY VALUE	0;5	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<1) X` LAST EDITED: `JUL 30, 1986` HELP-PROMPT: `ANSWER MUST BE 1-30 CHARACTERS IN LENGTH` DESCRIPTION: `If the KEY value for the destination file is known, based on the mnemonic, that value goes here. If the value is to be asked at data entry time this field will be NULL.` Only string or non-canonic values can be used here. Canonic numbers will be interpreted as 'internal entry numbers' so be careful.
.06	DESCRIPTION	0;6	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>30!($L(X)<3) X` LAST EDITED: `MAR 30, 1987` HELP-PROMPT: `ANSWER MUST BE 3-30 CHARACTERS IN LENGTH` CROSS-REFERENCE: `9001001^C` 1)= S ^APCDTKW("C",$E(X,1,30),DA)="" 2)= K ^APCDTKW("C",$E(X,1,30),DA)
.07	ALLOWED/NOT ALLOWED	0;7	SET	'0' FOR ALLOWED; '1' FOR NOT ALLOWED; LAST EDITED: `MAY 22, 1990`
.08	VISIT RELATED	0;8	SET	**********************REQUIRED FIELD********************** '1' FOR VISIT RELATED ONLY; '0' FOR NON-VISIT/VISIT MNEMONIC; '2' FOR SPECIAL; LAST EDITED: `JUL 08, 1992`
.09	V FILE UPDATED	0;9	POINTER TO FILE FILE (#1)	FILE(#1) LAST EDITED: `SEP 21, 1996`
.11	PRIMARY LIST ORDER	0;11	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `OCT 12, 1998` HELP-PROMPT: `Type a Number between 1 and 999, 0 Decimal Digits` CROSS-REFERENCE: `9001001^AD` 1)= S ^APCDTKW("AD",$E(X,1,30),DA)="" 2)= K ^APCDTKW("AD",$E(X,1,30),DA)
.12	MENU TEXT	0;12	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>21!($L(X)<2) X` LAST EDITED: `SEP 21, 1996` HELP-PROMPT: `Answer must be 2-21 characters in length.`
.13	SECONDARY LIST ORDER	0;13	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `OCT 12, 1998` HELP-PROMPT: `Type a Number between 1 and 999, 0 Decimal Digits` CROSS-REFERENCE: `9001001^ASEC` 1)= S ^APCDTKW("ASEC",$E(X,1,30),DA)="" 2)= K ^APCDTKW("ASEC",$E(X,1,30),DA)
.14	ASSOCIATED FILE	0;14	POINTER TO FILE FILE (#1)	FILE(#1) LAST EDITED: `SEP 23, 1996` CROSS-REFERENCE: `9001001^F` 1)= S ^APCDTKW("F",$E(X,1,30),DA)="" 2)= K ^APCDTKW("F",$E(X,1,30),DA)
.15	HISTORICAL LIST ORDER	0;15	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>9999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `OCT 12, 1998` HELP-PROMPT: `Type a Number between 1 and 9999, 0 Decimal Digits` CROSS-REFERENCE: `9001001^AH` 1)= S ^APCDTKW("AH",$E(X,1,30),DA)="" 2)= K ^APCDTKW("AH",$E(X,1,30),DA)
.16	NON-VISIT DATA ITEM ORDER	0;16	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `OCT 12, 1998` HELP-PROMPT: `Type a Number between 1 and 999, 0 Decimal Digits` CROSS-REFERENCE: `9001001^ANVI` 1)= S ^APCDTKW("ANVI",$E(X,1,30),DA)="" 2)= K ^APCDTKW("ANVI",$E(X,1,30),DA)
.17	COHORT ENTRY LIST ORDER 1	0;17	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."2N.N) X` LAST EDITED: `SEP 07, 2000` HELP-PROMPT: `Type a Number between 1 and 999, 1 Decimal Digit` CROSS-REFERENCE: `9001001^FP` 1)= S ^APCDTKW("FP",$E(X,1,30),DA)="" 2)= K ^APCDTKW("FP",$E(X,1,30),DA)
.18	COHORT ENTRY LIST ORDER 2	0;18	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999)!(X<1)!(X?.E1"."2N.N) X` LAST EDITED: `SEP 07, 2000` HELP-PROMPT: `Type a Number between 1 and 999, 1 Decimal Digit` CROSS-REFERENCE: `9001001^SP` 1)= S ^APCDTKW("SP",$E(X,1,30),DA)="" 2)= K ^APCDTKW("SP",$E(X,1,30),DA)
2101	REMARKS	21;0	WORD-PROCESSING #9001001.21
999999901	PATCH ADDED	9999999;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>5!($L(X)<1) X` LAST EDITED: `JAN 28, 2008` HELP-PROMPT: `Answer must be 1-5 characters in length.`

Customize PDF page

Package: Patient Care Component

Global: ^APCDTKW

Information

Description

Directly Accessed By Routines, Total: 12

Accessed By FileMan Db Calls, Total: 37

Pointed To By FileMan Files, Total: 3

Pointer To FileMan Files, Total: 1

Fields, Total: 19