Definitions - NYU Langone Medical Center



Functional Requirements for RFPMarch 7 2016Contents TOC \o "1-3" \h \z \u Definitions PAGEREF _Toc434501955 \h 3Functional Requirements PAGEREF _Toc434501956 \h 41.1General PAGEREF _Toc434501957 \h 41.2Functional Requirements PAGEREF _Toc434501958 \h 4System Technical Requirements PAGEREF _Toc434501959 \h 5A.General PAGEREF _Toc434501960 \h 5B.Metadata PAGEREF _Toc434501961 \h 6C.Automated Metadata Acquisition PAGEREF _Toc434501962 \h 6D.Signal and File Types PAGEREF _Toc434501963 \h 7E.Encoding and Compression PAGEREF _Toc434501964 \h 8F.Source Coding, Decoding, and Transcoding PAGEREF _Toc434501965 \h 8G.Operational Functions PAGEREF _Toc434501966 \h 9H.Browse PAGEREF _Toc434501967 \h 9I.Edit - Simple PAGEREF _Toc434501968 \h 10J.Edit – Advanced PAGEREF _Toc434501969 \h 10K.File Transfer PAGEREF _Toc434501970 \h 11L.Play-Out PAGEREF _Toc434501971 \h 11M.Data Storage and Achive PAGEREF _Toc434501972 \h 11N.Disaster Recovery PAGEREF _Toc434501973 \h 13O. UPS PAGEREF _Toc434501974 \h 13P. Control PAGEREF _Toc434501975 \h 14Q. Data Security PAGEREF _Toc434501976 \h 14R. Interface to LAN Network(s) PAGEREF _Toc434501977 \h 16S. Usage Monitoring/Billing PAGEREF _Toc434501978 \h 16T. System Status Monitoring PAGEREF _Toc434501979 \h 16DefinitionsEDL – Edit Decision ListFIFO – First in, First OutFTP – File Transfer ProtocolMEDSIM – Medical Simulation SystemMRAMS – Media Recording and Asset Management SystemNear Line Archive – Storage that needs to be accessed quickly; typically through removable media. NLE – Non-Linear Editors; a video or audio editing tool.SSV – Specialist System VendorFunctional RequirementsGeneralThe following section outlines the functional design, capabilities and performance requirements for the system to be designed under the contract arising from this RFP.Functional RequirementsThe System shall include capabilities to collect data from students or learners, standardized patients, and/or evaluators through a customizable interface.The System shall include reporting functions that will allow the exporting of raw data collected, as well as standard item response and summary score reports from item A. The System shall interface with all commonly used medical Mannequins (e.g. Meti, Laerdal, Gaumard) as well as with medical equipment that provides telemetry. All mannequins and medical equipment will be provided by NYUHC under separate contracts.The system shall be capable of fully integrating and synchronizing an entire simulation and associated telemetry, including physiologic data logs, event logs, pharmacology data logs and patient monitoring data, into a complete record for debriefing, assessment and evaluation.The system shall be capable of recording multiple channels of real-time 30 FPS video and audio as well as telemetry information.The system software shall have its own Scheduling module. This module shall allow users with appropriate credentials the ability to schedule simulation rooms, systems and associated resources.The system software shall include capabilities for identity management such that students and visitors to the Simulation Center shall be able to establish a “user name” and password which shall then be used both to grant them access to certain system functions as well as logging their progress through the Center and identifying them as users. User credentials must be programmable to automatically expire after a pre-determined period. This functionality shall be provided through a web based interface, and shall be accessible through the Simulation Center’s web site as well as through on-site terminals.The system shall record and replay the entire simulation for facilitated debriefing and after-action review.The system shall be able to replay video recordings of simulation activities to internal (NYSIM) and external locations with appropriate authorized access.The system shall allow an operator to observe and switch between multiple camera views (real-time and time-shifted) with zooming capability.The system shall include media asset management and retrieval (MAMR) functions to allow users to easily find records and provide additional annotation in pre-defined fields.The system shall include redundant fault tolerant storage capabilities.System Technical RequirementsGeneralThe MEDSIM/MRAMS shall scale out horizontally and vertically at all tiers – Specific requirements for scalability include but are not limited to the following:The system shall include capability for scaling storage, servers and other hardware;The system shall have enough capacity for at least 100 concurrent users.The system shall be capable of load balancing;The system shall have capability to improve performance with clustered processors, distributed servers, etc.The MEDSIM/MRAMS shall be capable of additional expansion by a minimum of 10% in all areas of operation.The expansion of the system shall not impact performance of the system in any way detectable by the user(s).All administrative and end-user tools shall run on Microsoft Windows, MAC OS X or on modern browser/OS combination without proprietary plugins.It is required that session archives play back on any common browser/OS combination and mobile platforms.All videos shall be collected and stored on a centralized redundant storage rather than on one or multiple DVRs distributed across the center.The solution must support the individual identity management and access-control regimes of the various institutional partners, and the importing/exporting of photographs, barcodes, etc., as required for Center administration along with basic identity information.The system, if hosted internally, shall run within a virtualized environment.The system shall integrate with LDAP or and Microsoft’s Active Directory for user authentication. The system shall Support standardized Single-Sign-On with SAML 2.0 The system shall provide robust documentation for any APIs and interfaces to programmatically interact with the system or to get data into and out of the system.MetadataThe MRAMS shall allow for the creation, transmission and maintenance of metadata compliant including but not limited to the following standards:SMPTE 330M-2004SMPTE 335M-2001EBU Tech 3293EBU Tech 3295EBU Tech 3336ISO 158356 – 2009 (Dublin Core Metadata Element Set)The MEDSIM/MRAMS handling of metadata shall support editing, manipulation and production of finished packages integrated from multiple and varied sources.The MEDSIM/MRAMS systems shall manage parent child relationships of contents; version control; association and annotation of metadata and accessibility to distribution (playout) and dissemination systems.Automated Metadata AcquisitionThe MEDSIM/MRAMS shall provide capabilities to automate as much of the metadata acquisition process as feasible. Other types of automated data acquisition capabilities (e.g. speech to text, facial recognition) shall be considered when evaluating the responses to this RFP.The proposer shall provide a complete list of tools included to assist with the automated metadata acquisition process.The delivered MEDSIM/MRAMS shall include tools that permit the manual and automated importation from, exporting to, and synchronization with, third-party databases. Such tools shall provide the capability to:Define the mapping between the MEDSIM/MEDRAMS database elements/fields and the third-party database elements/fields.Define the schedule at which automated database synchronization shall occur.Define how database elements can be modified prior to insertion into either the MEDSIM/MRAMS database or the third-party database.The third-party databases with which the MEDSIM/MRAMS will synchronize shall include, but not limited to, the following:MS AccessMySQLMS SQLOracleSignal and File TypesThe MEDSIM/MRAMS shall support, at minimum, the following broadcast quality full motion video and audio signals:Standard Definition Composite Analog: NTSC 30FPSThe MEDSIM/MRAMS shall support rich media files including audio, video.The MEDSIM/MRAMS shall support, at minimum, the following file types:Audio files including, but not limited to, Audio Interchange File (AIF), MIDI (MID), MP3, PCM (Pulse Code Modulation), WAVE (WAV), and Windows Media Audio (WMA)Data files including, but not limited to, Microsoft Excel Spreadsheet (XLS), and Microsoft Excel Open XML Document (XLSs) ), comma separated value text files (CSV).Raster image files including but not limited to, Bitmap Image (BMP), Graphical Interchange Format (GIF), JPEG Image (JPG), Portable Network Graphic (PNG), Rich Text Format (RTF), and Plain Text (TXT).Video files including, but not limited to Apple QuickTime (MOV), MPEG-4 (MP4), Microsoft Silverlight and Windows Media Video (WMV).XML (eXtensible Markup Language).SOAP (Simple Object Access Protocol) JSONAny file format and/or type required to support the operation of the MEDSIM/MRAMS as specified elsewhere in this RFP.The SSV shall provide the client with a complete list of file formats supported by the MEDSIM/MRAMS.Encoding and CompressionThe MEDSIM/MRAMS shall utilize current industry standard encoding and compression technologies to reduce storage requirements while maintaining high quality content. MPEG4 AVC /H.264 @ 1000KBPS shall be the default.The proposer shall provide the client with a list of all encoding types and compression rates supported by the MEDSIM/MRAMS included in the proposer’s response to this RFP.Source Coding, Decoding, and TranscodingThe SSV shall supply Coders/Decoders/Transcoders (codecs) as required by the MEDSIM/MRAMS to ingest, playout, transfer files, and any other process required by the MEDSIM/MRAMS to fully support the operation required in this RFP.The SSV shall provide the quantity of each type of codecs required plus a minimum of (1) of each type of codec as a spare.The spare codecs shall be installed as patchable and/or routable spares to provide system redundancy in the event of a primary codec failure.Any reconfiguration shall not require the operator to access more than one (1) location within the facility, except the operator may be required to access configuration devices, such as system configuration workstations, in an adjacent room.Any such reconfiguration shall not require the operator to access the rear of any device(s).Operational FunctionsThe MEDSIM MRAMS shall support simultaneous operation of all functions as follows:The MEDSIM/MRAMS shall be capable of simultaneously ingesting and exporting the following types and number of sources:Nine (9) Simulation feeds with two (2) channels of video and two (2) channels of audio from small OSCE RoomsFive (5) Simulation feeds with two (2) channels of video, two (2) channels of audio and telemetry information from large OSCE Rooms.Three (3) Simulation feeds with three (3) channels of video, two (2) channels of audio and telemetry information from OR SIM Rooms. Two (2) Simulation feeds with two (2) channels of video, two (2) channels of audio and telemetry information from Medium SIM rooms.Five (5) Simulation feeds with two (2) channels of Video, two (2) channels of audio and telemetry information from Trauma/ICU suites.One (1) Simulation feeds with up to eight (8) channels of video, four (4) channels of audio and telemetry information from Wet Lab.Two (2) Simulation feeds from portable system to be used in Conference rooms and/or Small OSCE rooms.Two (2) workstations uploading image files.Two (2) workstations uploading document files.BrowseThe MEDSIM/MRAMS shall provide a method of producing low bandwidth proxies/thumbnails of all content to allow browsing via a web based interface from any Institutional Partner user with appropriate permissions using a modern web browser with no proprietary plugins. The low-bandwidth proxy/thumbnail version of all content shall also be available within the MEDSIM/MRAMS system, via the user interface.The MEDSIM/MRAMS shall include a reporting function to provide data on the browsing activities of users.Edit - SimpleThe MEDSIM/MRAMS shall support low resolution (proxy) simple real time editing on Microsoft Windows and Mac operating systems. The edit system(s) shall produce an Edit Decision List (EDL) that is video frame accurate, which can be used by the MEDSIM/MRAMS to assemble edit, content or effect rich programs.The MEDSIM/MRAMS editor shall not limit the number of independent source files that are used in any given session.The EDL generated by the session shall be the transferable to the MEDSIM/MRAMS for permanent storage and archiving.Using the EDL generated above, the MEDSIM/MRAMS shall allow scheduling a session for playout of the high resolution edited material.The MEDSIM/MRAMS shall provide the ability for the user to specify whether a separate file containing only the final edited content is created for MEDSIM/MRAMS storage, played out to any appropriate capture device tied to the system, such as a DVD recorder, video tape, data tape, or other removable storage.Edit – AdvancedThe MEDSIM/MRAMS shall support low resolution (proxy) editing on Microsoft Windows and/or Mac operating systems. The edit system(s) shall produce an edit decision list (EDL) that is video frame accurate.The EDL shall be exportable to one or more third party non-linear editors (NLEs) and shall include all parameters necessary to allow NLEs to produce high resolution final product including, but not limited to, scene selection, video transitions and audio transitions.The MEDSIM/MRAMS editor shall not limit the number of independent source files that are used in any given session.The EDL generated by the session shall be transferable to the MEDSIM/MRAMS for permanent storage and archiving.The responder shall include a list of supported third party NLEs with the response to this RFP.File TransferThe system shall support data export to all institutional partners using secure file transfer protocols (e.g. SFTP).Play-OutThe MEDSIM/MRAMS shall be capable of simultaneously playing out the following types and number of sources:Two (2) feeds of streaming video with two (2) channels of analog audio per feed for each of the simulations being run.Data Storage and ArchiveThe MEDSIM/MRAMS shall support tail mode access to files, allowing users to retrieve material as soon as the recording/ingest session has started.The MEDSIM/MRAMS shall support on-line, near-line, and off-line data storage. The storage requirements of the system shall be:Transfer of data between on-line and near-line storage shall not impact performance of the other functional operation(s) of the system in any way detectable by the user(s).The MEDSIM/MRAMS shall provide on-line storage capacity for a minimum of:5,000 hours of full motion video MPEG4 AVC 30FPS encoded at 1000KBPS with 2 channels of audio and associated telemetry data.One Terabyte of data, raster image, and text and document files.Sufficient additional storage to provide low-resolution proxy files, metadata files, and any other system files necessary for operation of the MEDSIM/MRAMS to meet the requirements in this RFP.The MEDSIM/MRAMS shall provide near-line storage capacity for a minimum of:25,000 hours of full motion video MPEG4 AVC 30FPS encoded at 1000KBPS with 2 channels of audio and associated telemetry data.10 Terabytes of data, raster image, and text and document files.The MEDSIM/MRAMS shall incorporate client configurable parameters to automate the process of moving data storage from on-line to near-line to off-line. Movement of data shall be based on a “first in, first out” (FIFO) priority and as further defined below.The parameters controlling automated movement of data shall be hierarchical with Boolean functions (if, and, or, not, etc.) and shall include, at minimum:“Do Not Move to Near-Line Archive” select function which shall override all other on-line to near-line automated processes.“Do Not Move to Off-Line Archive” select function which shall override all other near-line to off-line automated processes.Length of time in number of days for the data to remain on-line. This parameter shall be replicated for each type of material as listed in Source Type above. In addition, these parameters shall allow an automated offset to be applied based on file size and/or date the material was last accessed.Length of time in number of days for the data to remain near-line. This parameter shall be replicated for each type of material as listed insource Type above.Manually entered “Keep On-Line Until” date.Manually entered “Keep Near-Line Until” date.Manually entered “Minimum Free On-Line Storage Space”.Manually entered “Minimum Free Near-Line Storage Space”.Near-Line Storage Media HandlingThe near-line storage shall provide automated movement of the storage media to/from the near-line bin(s), slot(s), or disk(s) to/from Input/output bin(s).The Archive Operator(s) will manually insert or retrieve the media to/from the Input/output bin(s).The Input/output bin(s) shall be accessible to the Archive operator without interruption to the near-line activities including data storage/retrieval to/from on-line storage and movement of the robot in support of the near-line activated except the robot may be prevented from accessing the Input/output bin(s) when the operator is actively accessing the bin(s).Other than placing media in or removing media from the Input/output bin(s), the MEDSIM/MREAMS shall perform all functions required without requiring any person to handle the media.The SSV shall submit technical details of the proposed near-line architecture solution including removable media type, storage capacity for a single removable media, total data storage as configured for the MEDSIM/MRAMS, and total available expansion.Disaster RecoveryThe MEDSIM/MRAMS architecture shall support fault-tolerant, expandable storage.The MEDSIM/MRAMS near-line storage architecture shall utilize magnetic data tape, removable magnetic disc drives, and/or removable optical disks or drives or comparable snapshotting capabilities.The MEDSIM/MRAMS shall include the capability to remotely locate the near-line storage via interconnect technologies such as VLAN, dedicated point-to-point data line (T1, T3, etc.), or other common carrier technologies. The interconnect technology shall be agreed upon between the client and SSV.In the event the client elects to remotely locate this function, the SSV’s responsibility shall be limited to providing the interconnection specification(s) to maintain system operational requirements and to provide all necessary interface ports from the MEDSIM/MRAMS to the appropriate demark.O. UPSThe MEDSIM/MRAMS shall include battery Uninterruptable Power Supplies (UPS) sufficient for 45 minutes of operation under full load conditions for any equipment deemed necessary to be hosted on-site in NYSIM premises. P. ControlControl protocolsThe MEDSIM/MRAMS Shall provide serial (RS422 and RS485) and Ethernet (IP and MAC addressing) Control interfaces and communications.Custom Control InterfaceThe MEDSIM/MRAMS Must include an API development capability to allow for the creation of custom control interfaces to mannequins and other medical equipment provided under other contracts.Q. Data SecurityEncryption of Data FilesThe MEDSIM/MRAMS shall support data encryption (in-flight and at rest) for data file(s) ingested that contain sensitive, non-public material, such as recordings of closed meetings or sessions that may fall under FERPA.The MEDSIM/MRAMS is not required to encrypt data for file(s) that are not designed as non-public.The encryption method shall persist through the life of the file including on-line, files retrieved from near-line storage, and files retrieved from off-line storage, including files retrieved by non-MEDSIM/MRAMS devices.The client shall have the right to reject the SSV’s proposed solution. The client may suggest alternatives to the SSV’s proposed solution.The MEDSIM/MRAMS user rights management shall include:Individual user login accounts with encrypted password and/or biometric access controls. Where possible, the users’ institutional credentials will be leveraged.The system should exhibit principle of defense in depth (more than one subsystem needs to be compromised to compromise security).The system should support a hierarchical approval structure to control User Permissions for distribution and access.The MEDSIM/MRAMS shall be capable of assigning individual user’s rights by associating that user with a user group(s).The MEDSIM/MRAMS shall include a Master System Administrator group that shall have all rights to all areas of the MEDSIM/MRAMS system.WatermarkingThe MEDSIM/MRAMS shall support digital watermarking on all file types capable of being ingested by the MEDSIM/MRAMS including, but not limited to, video, audio, electronic document, and images.The Client shall be able to configure the MEDSIM/MRAMS to encode the digital watermark so as to be either visible or imperceptible to the end user/viewer.The MEDSIM/MRAMS shall include digital watermark embedding on all outbound files including download, play out, file transfer, or any other method of data transfer.The MEDSIM/MRAMS shall include detect/read of the client’s digital watermark information on any file returned to the client for analysis.The MEDSIM/MRAMS shall assign a unique digital watermark identifier to each media file.The digital watermark shall, at minimum, identify that the file and its contents are:The legal, copyrighted, property of the client.Unaltered from the information acquired from the client whether by download, play out, file transfer, or any other method of transfer of data.The digital watermark may provide copy protection to prevent unauthorized persons or entities from producing copies of the original file.The SSV shall submit a detailed matrix of the digital watermark system’s capabilities.Copy ProtectionThe MEDSIM/MRAMS shall provide copy protection to prevent unauthorized persons or entities from producing copies of the original file, whether accessed from on-line, near-line, or off-line storage.Copy protection may be included as part of the SSV’s proposed watermarking solution.SSV shall submit their proposal to implement copy protection.Version ControlThe MEDSIM/MRAMS shall provide version information on all data files. Version information shall include original file name, original date and time original author, new filename, new date and time, and new version author.Version control may optionally be implemented as part of the watermarking system and process.SSV shall submit their proposal to implement version control.R. Interface to LAN Network(s)The SSV shall provide all LAN connectivity required to operate and maintain the MEDSIM/MRAMS except:The SSV shall utilize the enterprise LAN to be installed and maintained by NYUHC as part of this project. A VLAN segment, sized appropriately to support the MEDSIM/MRAMS function will be provided.The MEDSIM/MRAMS system shall incorporate an open source Application Programming Interfaces (APIs) and Software Development KIT (SDK) to allow the development of all interfaces required to provide the designed functionality between the MEDSIM/MRAMS and all existing and new Institutional Partners systems applications. This information shall include the source code as described herein.S. Usage Monitoring/BillingThe MEDSIM/MRAMS shall incorporate the ability to report on the usage of all content, by user, bandwidth/file size, content type and specific content.The MEDSIM/MRAMS shall incorporate a billing module to allow usage charges to be automatically billed to users, including any necessary payments based on copyright. The billing module shall also include the ability to bill for materials consumed by users.T. System Status MonitoringThe MEDSIM/MRAMS shall provide real-time system status monitoring and error reporting. This shall include, but not be limited to:Status of all devices connected to MEDSIM/MRAMSStatus of Major software componentsIntegrity of databaseRemaining free storage levels for online storage systems.In the event of a fault or error being detected, the MEDSIM/MRAMS shall send an alert to designated users. Alerts shall be available as e-mail, cell phone, pager, SMS or other instant messaging formats as required. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download