Attachment B - RFI questions.pdf
PDF 270 KB Posted
- Attached to
- Johnson Space Center (JSC) Electronic Health Record (EHR) Replacement Request for Information (RFI)
- Solicitation number
- 80TECH25RFI0003
About this file
This document is an Attachment B containing Request for Information (RFI) questions related to a federal contract opportunity for the Johnson Space Center (JSC) Electronic Health Record (EHR) Replacement. The RFI solicits responses from vendors to verify the feasibility and reasonableness of NASA's requirements, which include providing an off-the-shelf EHR software solution that can be installed on-premises, supporting a virtual implementation process, and meeting NASA's interface and customization needs. The RFI questions cover topics such as the vendor's EHR solution capabilities, support model, implementation timeline, data migration, demonstration requirements, and FedRAMP approval status. NASA is planning to use the responses to finalize the Request for Quote (RFQ) for this multi-year EHR replacement project. Responses to the RFI questions are due by December 13, 2024.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 80TECH25RFI0003 JSC EHR Q-A.pdf | ||
| Attachment C - Interface Diagrams.pdf | ||
| Attachment A - Draft PWS v1.4.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment B RFI 80TECH25RFI0003
ATTACHMENT B
ATTACHMENT B
Request for Information (RFI) Questions
National Aeronautics and Space Administration Information Technology Procurement Office
1) Does your company offer an off- the- shelf EHR software solution that can be installed in an on-premises environment?
a) Does the solution have customizable features?
b) Is the solution a certified EHR through Office of the National Coordinator for Health Information Technology (ONC-HIT)
2) For access to NASA networks the required cybersecurity process can take 90-180 days.
Because of this, NASA will not badge the selected vendor. As a result, software implementations are handled by the NASA IT Support contractor with inputs from the software vendor in what is essentially a virtual over the shoulder process. From a vendor perspective, what concerns, if any, does your company have with this process?
3) Does your company understand our implementation strategy and how your company would support the software implementation? If not, what questions does your company have/what is unclear? (Ref Attachment A – Draft PWS Section 2.2, requirement 3.1.1.1.1., and figure 5 IT roles and responsibilities)
4) Our expectation is that at key points during implementation a technical rep (or reps) will be on site, for example during training and go-live. How much on-site support time does your company anticipate during implementation?
5) Our assumption is that 12 months is sufficient time to implement the new system. Given the information we have provided, is this an accurate assumption? Under what circumstances could this timeline be reduced without negatively impacting functionality?
6) For a given form or field within your company's system, how much customization is possible recognizing that care for astronauts differs from typical clinical requirements? If customization is available, can it be done by our IT team or must it be done by the vendor? If done by the vendor, what is the cost model and timeline for update requests to custom forms and fields?
7) What medical modules are included in your company baseline software and which modules are available at an additional cost?
8) With respect to the pharmacy operations identified in the draft PWS, does your company have questions that require further explanation in a future Request for Quote (RFQ)?
9) Given the interface documentation provided in Attachment A – Interface Diagrams, and draft PWS section 2.2, 2.6, 3.0, 3.1.1.2, and 7.0 Figures 1-4, what interface engine solutions exist to functionally replace BizTalk and are they native to your company's product or third-party software?
a) If interface engine solution is third party software, does your company include it in the price of your company’s EHR software or would it need to be purchased/licensed by NASA separately?
10) Given the information provided, what is an approximate cost for first year annual licensing and implementation? We are planning a multi-year relationship with an EHR vendor; what would the cost be for subsequent annual licenses? (Please provide a reasonable estimate for first year and subsequent year costs)
11) Given NASA’s expectation to continue to fully utilize the NASA IT Support contractor to support EHR maintenance, patches, and updates, can your company explain what higher level support is available? (ref Attachment A – Draft PWS Section 2.2, requirement 3.1.1.1.1., and Figure 5 IT roles and responsibilities)
a) Describe the support that is included with the basic annual license.
b) Are there any support scenarios that would incur cost?
c) What level/how many hours of tier 3 and tier 4 support do your company’s customers typically require?
d) If we require consulting services what is the hourly rate/flat rate?
e) With respect to software updates, are they pushed out or placed in a location that NASA can access to download and install. Given NASA’s IT security environment, the preference is to download and install.
12) Please explain how your company can guide NASA IT Support team through the process of data migration that doesn’t require your company’s personnel to have access to our network. Is it a standard practice for your company to build scripts for customers to utilize to migrate the data as part of the implementation process? Is this an additional fee or included in the implementation cost?
13) Demonstrations are necessary to see how key tasks are performed within an EHR system.
What does your company feel would be an adequate duration for a demonstration to highlight your company's product given the needs outlined in documents provide with the
RFI?
14) Would a procurement strategy using demonstrations as part of the evaluation process deter your company from responding to an RFQ? If so, why?
15) Would a procurement strategy requiring the submission of a recording of a demonstration as part of the evaluation process deter your company from responding to an RFQ? If so, why?
16) A master project plan covering definition phase, planning phase, and implementation phase will be required as part of the RFQ response. The plan will need to address a roadmap for project completion, milestones, expected travel, plan for implementation support, training plan, and a go-live plan. Given the information that is currently provided, does your company understand this requirement, if not what are the gaps?
a) Can your company provide a high-level overview of what a Master Project Plan would look like for this type of project?
b) What questions/concerns are there with formulating a master project plan that would show NASA how your company plans to support implementing your company's EHR software solution?
17) Is your EHR system FedRAMP approved? If not, does your company plan to meet FedRAMP requirements in the next 5 years for EHR on cloud?
18) Does your company see any requirement gaps in the provided documents that we should address?
19) What other information does your company feel would be helpful in responding to a future RFQ and allow for more accurate pricing by your company?
20) Would your company be interested in participating in a virtual industry day hosted by NASA for NASA to demonstrate the current environment and answer any questions? If so, what length of time would be needed to provide the most value to your firm in understanding NASA’s requirement?
File details come from the government source that posted it. Updated .