Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF SEPTEMBER 09, 2016 FBO #5404
DOCUMENT

D -- Request for Information: Making iMedConsent™ Compatible With PIV Card Sign On and Linkage with VA CPRS - Attachment

Notice Date

9/7/2016
 

Notice Type

Attachment
 

NAICS

541511 — Custom Computer Programming Services
 

Contracting Office

Department of Veterans Affairs;Office of Acquisition Operations;Technology Acquisition Center - Austin;1701 Directors Blvd, Suite 600;Austin TX 78744
 

ZIP Code

78744
 

Solicitation Number

VA200P0009AP00022
 

Response Due

9/16/2016
 

Archive Date

10/16/2016
 

Point of Contact

Kari L Cozzens
 

E-Mail Address

1-4413<br
 

Small Business Set-Aside

N/A
 

Description

Request for Information: Making iMedConsent Compatible With Personal Identification Verification (PIV) Card Sign On and Linkage with the Veterans Administration Computerized Patient Record System (CPRS) National Center for Ethics in Health Care Veterans Health Administration (VHA) Department of Veterans Affairs August 31, 2016 This is a Request for Information (RFI) to conduct market research to determine the availability of vendors capable of providing the following requirement. This RFI does not guarantee the issuance of an RFQ/RFP. If your company has the ability to provide the services outlined below, please respond to this RFI with a statement of capabilities. Further, if you have a similar software/service that can provide the required set of capabilities, and is completely interoperable with the existing environment, please respond to this RFI with a capabilities statement and supporting documentation capable of validating the equivalent product/service. Please provide any information regarding General Services Administration (GSA) contracts or other contract vehicle, in your response. I. Scope of Work In support of the signature informed consent processes, Veterans Health Administration (VHA) is conducting market research across industry. The intent is to identify software solutions that support a needed change to the way the iMedConsent software logs users on and connects with the Computerized Patient Record System (CPRS). VHA needs a change to the iMedConsent software to allow it to facilitate user sign on using the VHA Personal Identification Verification (PIV) card, instead of CPRS log-on codes. The iMedConsent software is a client/server Commercial Off The Shelf (COTS) product, customized to meet VHA requirements for documenting signature informed consent for clinical treatments and procedures. iMedConsent software is provided to the VA and supported by Standard Register. The software is installed on all computers that run CPRS at all VA facilities. The iMedConsent software is currently launched on individual computers via a drop down link in the VA CPRS program. The software links to the VA CPRS log-on process requiring input of the user's CPRS access code and password. All actions take place within the VA firewall. The VA is currently making changes to the CPRS log-on to make it PIV card compliant. The iMedConsent software logon needs to be changed to be compatible with the forthcoming CPRS PIV card logon process. II. Technical Background The changes being made to CPRS to make it PIV compliant at the program level are still in development and the technical details are not yet completely defined. However, the VHA has been using PIV cards for computer-level log on for an extended period of time. The current iMedConsent software is proprietary, so any development approach pursued would require collaborative work with Standard Register, the iMedConsent vendor. III. Technical Challenges Any solution proposed will need to be able to fielded, tested and deployed by April 2017. Development, testing and deployment will need to be coordinated to be concurrent or nearly concurrent with CPRS development, testing and deployment. IV. Technical Approach Information is needed on vendor's proposed technical approach to support this requirement. This development, testing and deployment effort will require close coordination with VA OIT, the iMedConsent vendor, and the National Center for Ethics in Health Care. Timelines will need to coincide with concurrent development and deployment of CPRS with a new PIV capability within the next 4 - 6 months. Any technical approach proposing software not already approved for use in the VA architecture would have to complete all phases of VA software review and demonstrate the ability to meet information security requirements leading to a new "Authority to Operate". For software not already approved and deployed for use in the VA architecture, this will include the following, as a minimum: "Design approval oSystem design document oVersion description documentation oDisaster recovery plan oInstallation/back out capability oMaster test plan oSection 508 compliance approval oProduction and support operations manual "Software configuration management procedures documentation oSoftware documentation oUser guides "TRM (Technical Reference Model) Approval "Test and Evaluation plan "Development/integration "Software quality assurance documentation "Installation and testing in a test environment "Deployment in beta test at multiple VA facilities "VA Enterprise wide deployment Any technical approach proposing software already approved for use in the VA architecture would have to demonstrate the ability to meet information security requirements and document deployment history and use within the VA. V. Cost Projection This is being considered for a firm-fixed price acquisition. Interested parties shall provide estimated costs for development, testing, and deployment of a software solution within the timelines provided. VI. Replies The VA seeks white papers on this market research request for information by September 16, 2016. All correspondence submitted will be protected and controlled as proprietary. After reviewing the submitted white papers, the Government may request additional technical input to help refine market research. Electronic submission via email is requested. Response shall include company information, including socio-economic size, and DUNS number.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/notices/1bd6b731239972b7a5cde91630a817cb)
 

Document(s)

Attachment
 

File Name: VA200P0009 P00021 VA200P0009 P00021_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=2991787&FileName=VA200P0009-P00021000.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=2991787&FileName=VA200P0009-P00021000.docx

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN04259701-W 20160909/160907235235-1bd6b731239972b7a5cde91630a817cb (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |