APPENDIX A-DETAILED SIMULATION LAB REQUIREMENTS.xlsx

XLSX spreadsheet 23 KB Posted

Attached to
9280-25-R-IFBD-00060
Solicitation number
3160007383
Issued by
Greene County, Mississippi

About this file

This document is Appendix A - Detailed Simulation Lab Requirements, outlining technical specifications for a comprehensive simulation lab software and hardware solution, likely for a medical training institution or healthcare education program. The requirements detail a robust system for managing medical simulation training across multiple rooms and floors, with specific focus on recording, tracking, assessing, and evaluating simulation scenarios. The solution must support eight simulation rooms and two OSCE-style rooms, with three control rooms and four debriefing rooms, fully integrating with Laerdal medical simulation products and requiring compatibility with existing hardware like Windows-based PCs and flat-screen televisions.

The proposed solution mandates a cloud-based, secure platform with extensive technical requirements including 4K camera support, real-time video synchronization, LMS integration with Canvas, mobile app availability, and comprehensive security features. Critical technical specifications include role-based access control, data encryption, privacy law compliance, ISO and accessibility standards, and the ability to track individual student usage with detailed metrics. The system must provide professional installation, comprehensive training for faculty and staff, ongoing support during business hours, and the capability to manage medical device data capture, including EKG, ultrasound, and electronic medical records (EMR). The solution requires seamless integration, scalability, and the ability to support current and future medical simulation training needs.

View the file

Other files

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

Sheet1

IdentifierReq/OptRequirements and FunctionsYes/NoDetails
Functionality and Compatibility
1RMust be able to effectively manage, record, debrief, and assess simulation training and medical exams on-site.
2RMust be able to effectively manage, record, debrief, and assess simulation training and medical exams in-situ.
3RMust be flexible or scalable and able to manage:
-One room
-Many rooms
-One floor
-Many floors
4RThe software must maintain a detailed historical log of log in, recording, playback, and administrative changes.
5OShould be captured in a single, reliable, and secure web-based interface.
6RMust create data metrics that can be used to:
-Give Feedback
-Debrief
-Track Progress
7OData should be able to adjust to fit program level needs on an individual and cohort level consistent with training needs.
8RMust automatically track usage and outcomes to include hours spent in simulation center.
9RMust track individual student usage with a clock-in and clock-out feature, allowing students to record their time in and out of the simulation center to monitor overall hours, and support comprehensive data collection
10RMust have scalable software that is able to be expanded when additional functionalities are needed with minimal disruption to usage or activities.
11OShould include customizable:
-Roles
-Scenarios
-Permissions
12RMust support medical device capture to include:
-EKG
-Ultrasound
-EMR
13RMust combine psycho-motor skills practice with digital assessment and evaluation tools in peer-to-peer or individual self-driven practice.
14RProvide LMS integration with Canvas
15RProvide scheduling feature to allow spaces in the facility to be schedueld for use.
Camera and Video Specifications
16REach video must be recorded in its entirety in a single file regardless of session length. The file must not be broken into individual segments based on time.
17RThe software must support groupings of multiple cameras together.
18RThe software must support synchronized start and stop recordings of grouped cameras and the population of all cameras that are grouped within the same meta data.
19RThe software must allow recording to be initiated via the user interface. A one click record button in the user interface shall start and stop the recording.
20OThe software should allow student ID numbers or employee ID numbers to be associated and used to locate recordings.
21RVideo recording must be avaliable immediately after recording. No rendering time shall be required in order to view a recording.
22RMust simultaneously manage and facilitate the use of multiple cameras and patient monitors.
23RIn the event that multiple cameras are associated with single rooms, video content must play back completely synchronized.
24OThe software should be able to create evaluation templates and forms which may be used to score and evaluate recordings.
25RRemote viewing capabilites for instructors to observe simulations in real-time without streaming to external platform
26RUser friendly interface for:
-Controlling cameras
-Viewing Feeds
-Controlling Cameras
27RIn the event that multiple cameras are located within the same room, the user will be able to launch all camera views by clicking a single room ID.
28RThe software must support all rooms being viewed simultaneously.
29OThe software should include support for cameras up to 4K resolution.
30RThe software must support digital pan tilt zoom on all live view cameras.
31RThe software must support all cameras to be recording simultaneously along with all rooms being viewed simultaneously without loss of system performance.
33OThe software should allow the ability to select preset positions for the cameras prior to recording.
33OThe software should include a built-in video editor that allows the user to create video clips and save them as independent files.
Equipment/Hardware
34RFully integrate with existing Laerdal products, seamlessly capturing data from any Laerdal manikin and LLEAP software or include costs of full replacement.
35RMust provide detailed hardware solution based on equipment list in Appendix C for the following rooms: Simulation Rooms (Laerdal Manikin-Equipped)

In all eight simulation rooms the A/V solution must be fully compatible with Laerdal manikin simulators—past, present, and future models—including, but not limited to: SimMom, SimBaby, SimMan3G Plus, and NursingAnne Simulator. The system must support seamless integration and real-time data capture from the manikin’s patient monitor, which operates using Laerdal Patient Monitor software on Windows-based All-in-One PCs.

OSCE-Style Rooms Two OSCE rooms must be supported and managed through the designated control infrastructure detailed throughout the requirements document.

36 R Must provide detailed hardware solution based on equipment list in Appendix C for the following rooms: Control Rooms Three separate control rooms located throughout the simulation lab must have full operational control over any connected spaces (i.e. both the Simulation Rooms and OSCE-Style Rooms). The A/V solution should enable remote control, monitoring (both audio and video), and communication capabilities for all connected spaces (Simulation Rooms and OSCE-Style rooms). Within the three control rooms, should be control stations allowing for simultaneous operation of each of the connected spaces. Furthermore, each control station should also allow for full operational control of any connected space throughout the simulation lab. Debriefing Rooms Four debriefing rooms are currently equipped with Windows-based micro form factor PCs and flat-screen televisions for remote viewing. The proposed solution must support real-time video and audio transmission to these rooms without the need for additional hardware. Compatibility with existing equipment is required.

Implementation/Professional/Training/On-Going Support
37RProfessional installation services must be provided
38RComprehensive training for faculty and staff on equipment usage, troubleshooting, and maintenance must be provided in both an in-person and virtual format
39RThe vendor must provide remote implementation support
40RThe vendor must provide detailed implementation timelines. (Should reflect all aspects and the phases through go-live)
41RThe vendor must provide phone, email and web support. Coverage must be available during working hours Monday through Friday, 8 to 5 Central time. Please describe user support models.
42RThe vendor must provide after hours support upon request
Other/Additional Features or Functions
43RMust offer a mobile app available compatible with both iOS and Android
44OThe application should support up to four devices as recording devices per session, ensuring seamless synchronization with cloud videos
45RMust store data in 100% cloud based system that can be accessed from any mobile device.
46OShould support ITIL.
47RMust support ISO 2000.
48RMust be 508 compliant.
49RShould support CMMI.
50RMust allow export of data to either a delimited file or CSV.
51RShould allow customizable session timeout capabilities.
52RShould have API availability to automate interface to and from other systems.
53OAuthenticate users with SAML/SSO, Shibboleth, or Microsoft Azure Active Directory.
54RMust have role-based security – to allow access to services.
Hosted Solution Requirements
55RMust secure data in transit and at rest. If encryption of data at rest is not available, please provide alternative measures. If encryption of data is available and imposes additional cost, that cost should be reflected in the proposal.
56RVendor shall have in place a system recovery plan, including policies around nightly backups and restoration and recovery of data within 24 hours of an outage or request.
Security, Storage and Access Control
57RMust provide centralized account management functionality (account creation, deletion, lock-outs, etc..).
58OShould have no restrictions on the number of users.
59OUser permissions and access to various system functions should be role-based with users allowed in multiple roles.
60RUser rights shall prevent other users from logging into the system and viewing a session which they have not initiated or have rights to view.
61RObservers, with appropriate rights, shall be able to talk to students via computer microphone or USB headset by clicking on an icon located within the video window during observation when optional talkback hardware is present.
62RRole-based permissions govern each user's right to add, edit, and view information within the system. There should be the capability to accomodate tiered access based on roles.
63OThe software should allow users to search only their content that they have been given access to.
64REncrypted data storage to ensure the confidentiality and integrity of recorded sessions.
65OShould allow the university administrator to view user data on system use, (logins, uploads, modifications, etc.).
66OShould provide an audit trail/logging for any action in the database, including real-time notifications.
67OShould provide a system capability for auditing/logging.
68RMust have the ability to track and display the history of information stored in the application.
69RMust have the ability to support current State and Federal privacy laws and general data protection (GDPR) policies.
70RWhere applicable, shall meet ISO/IEC 40500:2012 [Web Content Accessibility Guidelines (WCAG) 2.1 AA] at a minimum.
71RMust have the ability to encrypt data at rest. If this capability imposes additional cost, that cost should be reflected in the proposal.
72RMust have the ability to segment data according to a data security model.
73RMust provide read-only data fields, or the prevention of overwriting certain data fields.
74RMust provide a method for all data imports and exports, and must use a secure file transfer such as Secure File Transfer Protocol (SFTP).
75OShould support integration with third-party multi-factor authentication providers.
76OThe solution shall allow secure login leveraging SAML, Active Directory, or Shibboleth security integration and determine level of access via identified fields.
77OShould allow for granular role-based control of access to profile data and workflows; including full access, limited access, and view only access; based on the individual user.
78RMust allow the administrator to assign security roles to users.
79OShould not use or provide default credentials.

File details come from the government source that posted it. Updated .