| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 4955 | ELECTRONIC SIGNATURE | Other | ELECTRONIC SIGNATURE | APPROVED | Active | Supported | 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 |
|||||
| 7096 | XOBE ESIG GET DATA | Remote Procedure | ELECTRONIC SIGNATURE | 2019/09/13 | APPROVED | Active | Private | The WebVRAM package needs access to the XOBE ESIG GET DATA RPC. This RPC returns electronic signature block-related fields from File 200 from the home facility tracked by the WebVRAM administrative tools. "Kernel understands this ICR was created to track which application is using the Kernel resource. The WebVRAM team has been working with IAM and the Kernel team for future official alternatives." |
XOBE ESIG GET DATA | 2019/09/20 | ||
| 7097 | XOBE ESIG IS DEFINED | Remote Procedure | ELECTRONIC SIGNATURE | 2019/09/13 | APPROVED | Active | Private | The WebVRAM package needs access to the XOBE ESIG IS DEFINED RPC. This RPC will support WebVRAM electronic signature processing that checks if the electronic signature is defined for the user/visitor. "Kernel understands this ICR was created to track which application is using the Kernel resource. The WebVRAM team has been working with IAM and the Kernel team for future official alternatives." |
XOBE ESIG IS DEFINED | 2019/09/20 | ||
| 7098 | XOBE ESIG SET CODE | Remote Procedure | ELECTRONIC SIGNATURE | 2019/09/13 | APPROVED | Active | Private | The WebVRAM package needs to access the XOBE ESIG SET CODE RPC to support saving the electronic signature code on VistA systems that the visitor is authorized to access. "Kernel understands this ICR was created to track which application is using the Kernel resource. The WebVRAM team has been working with IAM and the Kernel team for future official alternatives." |
XOBE ESIG SET CODE | 2019/09/20 | ||
| 7099 | XOBE ESIG SET DATA | Remote Procedure | ELECTRONIC SIGNATURE | 2019/09/13 | APPROVED | Active | Private | The WebVRAM package needs access to the XOBE ESIG SET DATA RPC. This RPC will support saving the electronic signature block on the VistA systems that the user/visitor is authorized to access. The signature block comes from the home facility's electronic signature block and is propagated by WebVRAM. "Kernel understands this ICR was created to track which application is using the Kernel resource. The WebVRAM team has been working with IAM and the Kernel team for future official alternatives." |
XOBE ESIG SET DATA | 2019/09/20 |