Print Page as PDF
ELECTRONIC SIGNATURE-RELATED DATA IN THE NEW PERSON FILE ICR (4297)

ELECTRONIC SIGNATURE-RELATED DATA IN THE NEW PERSON FILE    ICR (4297)

Name Value
NUMBER 4297
IA # 4297
FILE NUMBER 200
GLOBAL ROOT VA(200,
DATE CREATED 2003/12/23
CUSTODIAL PACKAGE KERNEL
CUSTODIAL ISC San Francisco
USAGE Controlled Subscription
TYPE File
DBIC APPROVAL STATUS APPROVED
NAME ELECTRONIC SIGNATURE-RELATED DATA IN THE NEW PERSON FILE
GENERAL DESCRIPTION
Electronic Signature is a collection of Java APIs to
validate, retrieve, and save electronic signature codes and related data on
the M server, as well as APIs to encrypt and decrypt strings similar to the
APIs provided by the existing VA Kernel 8.0 electronic signature APIs.

The Java APIs provide HSD&D developers that are rehosting their applications
to a new Java environment a standardized method for migrating their electronic
signature functionality. It is hoped that this will reduce duplication of
effort, promote more efficient use of limited development resources, and
satisfy the VistA user's business needs.

This IA permits Electronic Signature to access electronic signature-related
data in the NEW PERSON file (#200) as listed in the GLOBAL REFERENCE section
of this Integration Agreement. All fields are accessed via VA FileMan calls,
such as $$GET1^DIQ and FILE^DIE, rather than direct global reads.
GLOBAL REFERENCE
GLOBAL REFERENCE FIELD NUMBER
VA(200,
FIELD NUMBER ACCESS FIELD NAME LOCATION
.132 Both R/W w/Fileman OFFICE PHONE .13;2
.137 Both R/W w/Fileman VOICE PAGER .13;7
.138 Both R/W w/Fileman DIGITAL PAGER .13;8
1 Both R/W w/Fileman INITIAL 0;2
20.2 Both R/W w/Fileman SIGNATURE BLOCK PRINTED NAME 20;2
20.3 Both R/W w/Fileman SIGNATURE BLOCK TITLE 20;3
20.4 Both R/W w/Fileman ELECTRONIC SIGNATURE CODE 20;4
STATUS Active
DURATION Till Otherwise Agreed
ID VA(200,
SUBSCRIBING PACKAGE
SUBSCRIBING PACKAGE ISC SUBSCRIBING DETAILS
ELECTRONIC SIGNATURE Oakland
ADVANCED PROSTHETICS ACQUISITION TOOL
Added 4/10/23, effective with patch DSSO*2.0*3, APAT
requests access to update SIGNATURE BLOCK PRINTED NAME (#20.2) using FileMan.
If the SIGNATURE BLOCK PRINTED NAME (#20.2) of the NEW PERSON (#200) file is
null, then the SIGNATURE BLOCK PRINTED NAME (#20.2) will be set to a
standardized value beginning with given name for display on the purchase order
report. Kernel Name Standardization APIs will be used for this formatting.
This is in the UP1^DSSOPN2 API.