Name | Value | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NUMBER | 4955 | ||||||||||||||||||||||||
IA # | 4955 | ||||||||||||||||||||||||
CUSTODIAL PACKAGE | ELECTRONIC SIGNATURE | ||||||||||||||||||||||||
USAGE | Supported | ||||||||||||||||||||||||
TYPE | Other | ||||||||||||||||||||||||
DBIC APPROVAL STATUS | APPROVED | ||||||||||||||||||||||||
NAME | ELECTRONIC SIGNATURE | ||||||||||||||||||||||||
GENERAL DESCRIPTION | As HealtheVet-VistA developers migrate VistA applications to modern technologies, interim solutions may be required until enterprise solutions are mature and stable. The Electronic Signature (ESig) service provides an interim solution for the use of electronic codes in place of wet signatures while HealtheVet-VistA s security infrastructure and architecture are being defined. The service duplicates for Java applications (J2EE or J2SE) the Kernel 8.0 electronic signature functionality currently used by VistA/M applications. ESig furnishes a standard, consistent set of APIs that HealtheVet-VistA developers can implement to provide users access to electronic signature data stored on VistA/M systems. ESig APIs make calls from Java applications to VistA/M systems to retrieve, validate, and store office phone, etc.). Additional Java APIs provide encoding/decoding, hash, and checksum calculation utilities, but do not interact with the VistA/M system. This integration agreement describes the supported ESig Java APIs that are contained in the esig-x.x.x.xxx.jar file. This JAR file can be included in a HealtheVet package distribution. SUMMARY JAR: esig-x.x.x.xxx.jar Package: gov.va.med.esig.utilities Class: ESigDataAccess Methods: isDefined getESigCode saveESigCode getESigData saveESigData Class: ESigEncryption Methods: checksum encrypt decrypt hash Class: ESigValidation Methods: isValid isValidFormat |
||||||||||||||||||||||||
STATUS | Active | ||||||||||||||||||||||||
COMPONENT/ENTRY POINT |
|