SOLICITATION NOTICE
L -- Technical Services
- Notice Date
- 5/15/2006
- Notice Type
- Solicitation Notice
- NAICS
- 541990
— All Other Professional, Scientific, and Technical Services
- Contracting Office
- Department of Health and Human Services, National Institutes of Health, Office of Administration, 6011 Executive Blvd, Rm 538, Rockville, MD, 20892-7663
- ZIP Code
- 20892-7663
- Solicitation Number
- 263-2006-Q-DT-0118
- Response Due
- 5/24/2006
- Archive Date
- 6/8/2006
- Description
- The National Institutes of Health (NIH) is comprised of the Office of the Director (OD) and 27 Institutes and Centers. The National Eye Institute is one of the components of the NIH. Their main function is to protect and prolong the vision of the American people by conducting and supporting research that helps prevent and treat eye diseases and other disorders of vision. The National Eye Institute is in need of molecular biology services to further its mission. The National Institutes of Health intends to negotiate on a sole source basis with Dr. David E. Scheim of 3300 Old Farm Rd Blacksburg, VA 24060 for the following services: The contractor shall: 1. The contractor shall provide an information infrastructure for the National Ophthalmic Disease Genotyping Network (eyeGENE). 2. The contractor shall assure that the eyeGENE system architecture runs on any common web browser. 3. The contractor shall assure that the eyeGENE system maintains high performance at anticipated future usage levels of hundreds of thousands of patient records and hundreds of concurrent transactions. 4. The contractor shall assure that the eyeGENE system possesses stirage capability of hundreds of gigabytes of structured dataza plus several terabytyes of iomage data. 5. The contractor shall assure that the eyeGENE system satisfies all applicable security and patient privacy requirements set forth herein; the Computer Security Act of 1987 (website: http://csrc.ncsl.nist.gov/secplcy/csa_87.txt); Office of Management and Budget Circular A-130, Appendix III, ?Security of Federal Automated Information Systems,? (wevbsite: http://csrc.ncsl.nist.gov/secplcy/al130app3.txt); DHHS Automated Information Systems Security Program (AISSP) Handbook (website: http://irm.cit.nih.gov/policy/aissp.html). 6. The contractor shall complete the eyeGENE system documentation, including documentation of newly added capabilities to include an overview document, in-line comments in source file code, a description of all database objects used, and any other items as directed by the NEI. The contractor shall include documentation of in-line comments for all modules and module-level variables and for all stored procedures, descriptions of logical approach and location of supporting program files, a database diagram, and descriptions of all tables used. 7. The contractor shall include system logging and implement functionality via a common set of subroutines to log all changes to the database, and all read operations involving patient data. The contractor shall assure that aforementioned actions are logged in an audit log capturing user ID, patient ID for all operations involving patient data, table changed, and other details desired by the NIH Project Officer. The contractor shall assure system logging of all successful or failed logins, password changes, other security-related operations, and system errors, including originating IP Addresses and other detailed information. 8. The contractor shall implement the file upload capability provided now in the system interface and the underlying database structure. 9. The contractor shall make whatever minor refinements are needed to fully support usage outside the US, for example, add a dropdown list for countries and be sure sizes and character string checks are correct for various address fields, and be sure all instructions are clear in International English usage. 10. The contractor shall provide a capability for clinicians and CLIA (Clinical Lab Improvement Amendment) lab users to upload data files such as on the clinical side, a fundus scan, or on the CLIA side, a file associated with maximum flexibility to that needed for future reprogramming to accommodate new file types in minimized. The contractor shall provide the ability to display icons on the patient grid representing various types when uploaded, the ability for an eyeGENE user to quickly view a low-resolution for images when practical, and support of common file types used by medical imaging and other devices. 11. The contractor shall add the capability to automatically generate email messages, for example, to notify a clinician when genetic testing results are ready for one of his or her practice?s patients. 12 The contractor shall implement system capability to send email and deploy this to complete the functionality for the ?forgotten password? action. 13. The contractor shall develop a pedigree tracking capability after NIH Steering Committee approval of the concept. 14. The contractor shall conduct extensive testing of the eyeGENEe system and make program fixes and refinements to resolve system bugs, fix errors in messages to users, and to enhance system function to be more intuitive to the user or to catch any identity gaps in system capabilities for certain needed functions. The contractor shall perform this testing through contractor?s own staff, by hiring additional temporary staff previously unfamiliar with the program. The contractor shall provide system administration support and instruction to NEI staff to perform additional system testing. The contractor shall make additional changes as emerge during the preliminary testing period and during production use. The contractor shall implement other minor system enhancements and fixes as directed by the NEI Project Officer and as identified as helpful during testing, when practical within the initial deployment deadline. 15. The contractor shall develop new web pages to support optimal system usages, specifically a web page for the individual CLIA lab, specific to that laboratory, and for the central administrator, for all CLIA labs, to provide an aggregate view of all gene mutations identified, with counts for each. 16. The contractor shall develop a new system module to track all interactions between eyeGENE users and NEI support staff, including reports of bugs, and questions or suggestions about eyeGENE, both system and non-system related. The contractor shall assure that the module tracks information such as reporting user?s name, contract information, and organization, interaction type, status, person staff ID taking the inquiry, staff ID resolving the problem, date of report, date of resolution, and other usefull data fields, automatically filled-in where possible. 17. The contractor shall add the capability, which can be turned on or off by a system setting (without reprogramming), to require a special system key for any eyeGENE self-registration in order to assure that steering committee members and other individuals designated by eyeGENE staff to enter the system for test purposes after security clearance for public usages has been obtained, but prior to the date that all clearances for specimen handling and research activities use have been received. 18. The contractor shall add a new column for accession number, column head RefSeq, format ?NM? plus up to 6 digits, for each row in the genetic testing module. 19. The contractor shall add a new system to provide a warning to the user at least once per session when a link provided within eyeGENE takes the user outside the eyeGENE system. 20. The contractor shall change the eyeGENE database and several system pages to track two consent forms. The contractor shall change the tracking designations to use checkboxes on the main patient grid, both for clinicians ansd CLIA users, for the most intuitive presentation. 21. The contractor shall change clinician functions as controlled from the clinician patient grid to require a diagnosis with clinical findings be entered (not necessarily complete) before the ship-blood operation can be performed. The contractor shall assure that the system warns the clinician if an attempt is made to ship blood before the consent-for checkboxes are checked. 22. The contractor shall provide a printable variant of the patient profile form, completing the capability for a physician to enter all clinical data on printed forms (which can then be entered by a clerical person in the clinical organization, or eyeGENE Coordinating Center. 23. The contractor shall change the designation ?inconclusive? to ?variant? in the genetic testing module. 24. The contractor shall implement the text note feature in the genetic testing module, with different color icons denoting empty or contains text, editable or not (depending upon access mode). The contractor shall adjust text not icons in the clinical findings to use the same icons designating full or empty fields, faded in color if not accessible in a particular system mode. 25. The contractor shall add a capability for the clinician to enter a text note for a diagnosis as a whole in addition to for each clinical question. 26. The contractor shall add capabilities and additional messages in the clinician patient grid to make the clinical interface even more intuitive and capable of use by a wide variety of users without the need for some form of help support. 27. The contractor shall implement validation of Clinical Findings per each clinical question. 28. The contractor shall add and EDIT/SAVE column header that changes in context without increasing column width, to put a helpful image on the dropdown selection buttons, and to preclude showing coding for an individual patient when in gene/group management mode. 29. The contractor shall provide a mechanism for each CLIA lab to select genes of particular interest to that lab and change the view of genes displayed to match the particular interest of the lab, or of a particular testing context. 30. The contractor shall provide read-only access of CLIA lab personnel to clinical information for the patient being tested by the particular CLIA lab, w/o patient contact information. 31. The contractor shall add a basic capability to track families of patients. 32. The contractor shall prepare an instruction manuals for CLIA users and for eyeGENE central system administrators. The contractor shall develop any documents and online capabilities to facilitate usage as determined by the NIH Project Officer. 33. The contractor shall develop a PowerPoint overview of eyeGENE system capabilities putting the system in broad perspective, demonstrating the capabilities of eyeGENE to the eye research community and other users. The contractor shall communicate with NEI staff to determine key features of interest, easy to implement in near future releases that could be included in this presentation, with the designation that such features are planned and not yet implemented. 34. The contractor shall consult with the subcontractor about best approaches to system help for initial deployment, management of image and other files, system warning languages, and meshing eyeGENE?s definition of diagnoses and clinical findings with standard thesauri such as SNOMED-CT if practical. 35. The contractor shall meet with NEI staff involved in eyeGENE development and attend major meetings by eyeGENE steering committee members and others as required to access system directions desired and to interact with the eyeGENE user community. 36. The contractor shall prepare documents requested in conjunction with the process of developing required reports for security certification, as requested by NEI Information Technology staff and contractors. The contractor shall meet with NEI Information Technology staff to examine central administration functions without the ability to change any data settings. 37. The contractor shall change validation of passwords to be consistent with the NIH policy. 38. The contractor shall test all clinical pages of eyeGENE in the Firefox, Netscape, Internet Explorer and other web browsers identified by the NIH Project Officer, and make changes as identified to support clear presentation in those browsers. 39. The contractor shall comply with the Information Technology systems security and privacy specifications set forth in item number 5, (the Computer Security Act of 1987, OMB A-130, Appendix III, and DHHS AISSP Handbook). 40. The contractor shall include the provisions of the Computer Security Act of 1987 OMB A-130, Appendix III, and DHHS AISSP Handbook in any subcontract awarded pursuant to this contract. 41. The contractor shall properly protect all information used, gathered or developed and shall establish and implement appropriate administrative, technical, and physical safeguards to ensure the security and confidentiality of sensitive Government information, data, and equipment. 42. The period of performance shall be date of award to August 31, 2006. This proposed action is for services for which the Government intends to solicit and negotiate with only one source. Interested parties may identify their interest and capability to respond to the requirement or submit proposals. This notice of intent is not a request for competitive quotations. However, all quotes received within ten days after the date of publication of this synopsis will be considered by the Government . A determination by the Government not to compete this proposed simplified acquisition requirement based upon responses to this notice is solely within the discretion of the Government. Information received will normally be considered solely for the purpose of determining whether to conduct a competitive acquisition.
- Place of Performance
- Address: 9000 Rockville Pike, Bethesda, MD
- Zip Code: 20892
- Country: USA
- Zip Code: 20892
- Record
- SN01048044-W 20060517/060515220231 (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 |