Mississippi State University RFP Enterprise Imaging Informatics Solutions Questions and Answers September 13, 2017

Transcription

1 Mississippi State University RFP Enterprise Imaging Informatics Solutions Questions and Answers September 13, 2017 The list of questions below were received. Please use this information when preparing your proposal. Q1. Is an included RIS solution a required element of the bid, or an optional element? A1. The PACs, VNA, and Viewer must integrate with our existing Hospital/Lab information system, VetView. Q2. If a joint proposal is not feasible, will MSU consider proposal offerings for only one/two of the solutions (i.e., PACS and VNA, no RIS)? A2. The PACs, VNA, and RIS must be submitted together. Different vendors can supply different parts, but the coordination of the install must be defined in the submitted proposal. Q3. Please clarify if MSU is still using the UVIS RIS? A3. No. We use Vetview as our Hospital/Lab information system. Q4. Is MSU open to supplying its own workstations, if needed? A4. Yes. We would just need the required specifications for the workstations. Q5. Please confirm that the existing ordering system is manual, and that there is no existing HL7 functionality. A5. The current ordering system is manual, but the proposed new system would need to communicate via HL7 with VetView to automate ordering. Q6. How many other bidders were invited to submit a proposal? Is it possible to name them individually? A6. Not answered Q7. What payment model is MSU most interested in? A7. Annual Q8. What is the intended implementation timeframe? A8. Q2 or Q3 of 2018, with the planning phase starting Q4 of 2017 or Q1 of Q9. Please indicate the number of users that require training (e.g., super users, etc). A9. Three faculty radiologists, two residents, two technicians, four IT support staff, and

2 upwards of 100 viewer users. Q10. Please indicate if any 3D reconstruction capabilities are required. A10. We would love 3D construction capabilities and we would use it in conjunction with a 3D printer. Q11. Requirement V-1 states Does your integration strategy provide the ability to update and synchronize the metadata in the RIS and VNA, on an as needed basis. Typically, the synchronization between the RIS and VNA is in real-time over HL7. Please clarify if MSU is asking for an alternative synchronization method? A11. No. HL7 is the synchronization method expected. Q12. Requirement V-8 states How does your VNA solution support the development of a true Level-3 enterprise image management and archiving strategy? Please confirm if MSU is seeking the VNA solution s ability to support non-dicom clinical data using industry standards. A12. Yes. We may need house reports and scanned images/documents on the VNA. Q13. Will dictation be part of the quote? A13. Yes. Our radiologists currently use Dragon naturally speaking voice to text software. Q14. How many radiologist reading workstation will need to be accounted for? A14. There will be four reading/dictation stations used in radiology. There will be three more throughout the hospital that will need to only view images in high resolution. Q15. How Many Radiologist? A15. Refer to question 9. Q16. How many radiology residents? A16. Refer to question 9. Q17. How many total dictation stations will be required? A17. Refer to question 14. Q18. Do we need to set up resident workflow for dictation and reports? A18. Yes Q19. Besides PACS and Vet View what other interfaces need to be included in the proposal? A19. Communication with the modalities. Also laptops and pcs to view images/studies. Osirix is currently used as a viewer by Mac users. We also upload images to other

3 universities and IDEXX. We accept images/studies from off-site PACs systems. Q20. How many DICOM SR modalities do you have that will need data extracted from? A20. CR, CT, DR, DX, MR, NM, OT, RF, RG, US, XA. Q21. What is the current or anticipated monthly number of exams? A21. About 700 Q22. What is the volume of existing studies to be migrated? (Approximate number of exams and storage size). A22. About 62,000 taking up about 3.5Tb. Q23. What is the approximate total number of users of the system? A23. About 120 Q24. What is the approximate number of concurrent users of the system? A24. Can t pull that information with our current PACs. Q25. What PACS and archive solutions are currently in use in the facility? A25. Mckession PACS and archive is being saved to a Dell Equalogic SAN. Q26. What PACS and archive solutions were in use prior to your existing solutions? A26. This was the original solution. Q27. Do you intend to store imaging indefinitely? If not, what is your data retention policy for maintaining/purging prior imaging? A27. Indefinitely. Q28. We can configure a system with the ability to access information from multiple locations and types of devices. Indicate what which of the listed device types you would want to access the archive from. A28. Desktops, laptops and tablets/smartphones Q29. VNA can be backed up in a variety of different ways. Indicate which of the following options you would prefer: A29. Redundant systems, Cloud Server and Windows file share or NFS Mount Q30. Will you want to query from the archive and retrieve images down to dedicated DICOM viewers? *If interested, please confirm that the viewers have licenses and capability to connect to an additional DICOM node. A30. We will want to retrieve down to dedicated viewer. Part of the RFP mandate is to provide a solution of VNA, PACs, and zero footprint Viewer.

4 Q31. We offer a web viewer that can display patient studies on HTML5 compliant web browsers, for display on devices that may not have a DICOM viewer installed. This web viewer is for reference (non-diagnostic) use only. Would you be interested in this option? A31. Yes, but we are also interested in web based viewers that can offer diagnostic capabilities on reading workstations. Q32. What sources of data are we going to be importing from? PACS, other department silos, etc? A32. PACs and document archive from another file server. Q33. Will we need to bring in any data not currently residing on PACS? For example, from scanning modalities or workstations that have been standalone (ex: mobile ultrasounds or x-rays). A33. PACS archive and document server. Q34. Will we have access to your vendor support if we run into problems when importing? A34. That would have to be coordinated between you and our current vendor. Q35. What are we importing that isn't DICOM data? A35. PDF documents and Dragon Naturally Speaking user profiles Q36. Is a separate digitization/import station desired to bring in both DICOM and non-dicom data? A36. No Q37. Are we expected to receive info from other systems such as RIS/HIS/HER/PACS? Hospital/Lab IS If so, are we send to or receiving from them? Both Please specify systems and their desired communications protocol. VetView, HL7 Q38. Do you want EMR linkage for web and if so, what types of linking from the list below? A38. All Records for Patient ID / Medical Records Number, All Records for Patient Name / Date of Birth, All records for an Accession Number / Order, A Specific Study, Auto-Display a Specific Study, Import for Patient ID / Medical Records Number Q39. Does your EMR support APIs for integrated session authentication to save users needing to log-in when linking from the EMR? A39. Yes Q40. Are there existing tasks that take a significant amount of time and effort that you would like to see automated?

5 A40. QA notification/resolution. Communication between PACs and modalities. Q41. Do you have any specific search-ability requirements? We support: Medical Records Number / Patient ID, Name (wildcard), Date of Birth, Sex, Date of Service, Type, Description (wildcard) A41. Would like to search by all of the above Q42. Out of the options given, what is your preference for managing data once it is in the aycan VNA? A42. Keep Everything Q43. Which is preferred for your site? A43. VMware on physical hardware. Can reside in cloud for production system, but must have on site fail-over solution in case of power/data loss to cloud. Q44. Do you have the ability to provide a client-based (on-demand) VPN for technical support, upgrades, and maintenance? A44. Yes Q45. If SAN storage is desired (optional for stand-alone hardware, required for VMware support): A45. We want all data on our current archive to be migrated to new VNA hardware. Amount needed with past growth listed above. Q46. Will you require any special logging interfaces? (Example: EMR audit API, database, log management tool) A46. We would like to pull a log file on anything about any current, past, or future case. We would also like to pull data logs for all of the listed above. Q47. Both the aycan store web viewer and the ControlCenter administrative application have access controls on what users can do. What type of user access controls are you looking for separate from an integrated EMR link? A47. A link in the EMR directly to the image with View rights only, or with the user rights configurable. Q48. If possible, in addition to providing the TB amounts of legacy data, please provide a breakdown of storage volumes by modality type over the last five years. (For example, of 50,000 studies, indicate that 20,000 are x-ray, 10,000 are MRI, 5,000 are mammography, etc.) A48. See below

6 Modality Data: Modality Total Studies Total Size (GB) Max Size (MB) Avg Size (MB) CR CT DR DX MR NM OT RF RG US XA Total Archive Space Taken up= approximately 3.6TB Storage Trend over the past 5 years Date Total Bags Total GB Online Bags Online % Online GB Offline Bags Offline % Offline GB 2011/ %.38 GB % GB 2011/ %.79 GB % GB 2011/ % 1.29 GB % GB 2011/ %.19 GB % GB 2011/ % 2.02 GB % GB 2011/ % 1.58 GB % GB 2011/ %.92 GB % GB 2011/ % 1.34 GB % GB 2011/ %.35 GB % GB 2011/ % 2.34 GB % GB 2011/ % 4.79 GB % GB 2011/ %.4 GB % GB 2012/ % 1.37 GB % GB 2012/ % 2.18 GB % 30.5 GB 2012/ % 1.5 GB % GB 2012/ %.87 GB % GB 2012/ %.91 GB % GB 2012/ %.94 GB % GB 2012/ % 1.23 GB % GB 2012/ % 1.24 GB % GB 2012/ % 1.64 GB % GB 2012/ % 1.53 GB % GB 2012/ % 1.58 GB % GB 2012/ % 1.5 GB % GB 2013/ % 5.26 GB % GB 2013/ % 3.02 GB % GB 2013/ % 3.05 GB % GB 2013/ % 2.95 GB % GB 2013/ % 1.31 GB % GB

7 2013/ % 1.24 GB % GB 2013/ % 2.66 GB % GB 2013/ % 4.37 GB % 25.1 GB 2013/ % 2.16 GB % GB 2013/ % 3.03 GB % 28.5 GB 2013/ % GB % GB 2013/ % 2.02 GB % GB 2014/ % 3.51 GB % GB 2014/ % 2.2 GB % GB 2014/ % 5.74 GB % GB 2014/ % 5 GB % GB 2014/ % 7.18 GB % GB 2014/ % 2.54 GB % GB 2014/ % 2.54 GB % GB 2014/ % 5.64 GB % 35.5 GB 2014/ % 8 GB % GB 2014/ % 7.23 GB % GB 2014/ % 4.57 GB % GB 2014/ % 4.05 GB % GB 2015/ % 4.87 GB % GB 2015/ % 5.71 GB % GB 2015/ % GB % GB 2015/ % 6.94 GB % GB 2015/ % 3.96 GB % GB 2015/ % 2.8 GB % GB 2015/ % 6.52 GB % 42.2 GB 2015/ % 5.67 GB % GB 2015/ % 6.87 GB % GB 2015/ % 6.49 GB % GB 2015/ % GB % GB 2015/ % 7.72 GB % GB 2016/ % 7.4 GB % GB 2016/ % 9.02 GB % GB 2016/ % 8.17 GB % GB 2016/ % 6.71 GB % GB 2016/ % 9.41 GB % 29.6 GB 2016/ % GB % GB 2016/ % GB % GB 2016/ % GB % GB 2016/ % GB % GB 2016/ % GB % GB 2016/ % 7.1 GB % 35 GB 2016/ % 3.03 GB % GB 2017/ % GB % GB 2017/ % 8.19 GB % GB 2017/ % GB % GB 2017/ % GB % GB 2017/ % 7.61 GB % GB 2017/ % 39.4 GB %.8 GB 2017/ % GB 0 0 % 0 GB 2017/ % GB 0 0 % 0 GB 2017/ % 2.61 GB 0 0 % 0 GB TOTAL GB % GB % GB