Skip to content

Functional Requirements

Jump to bottom
Benjamin Riggs edited this page Jul 14, 2017 · 1 revision

Functional Requirements

Create a standard & Develop a manikin that meets the standard

  • Display
    • Module display is constrained by supply of Fluids (pressure and flow rate), Power (battery or wall), & Data (50Hz message rate)
    • Module display can be either Virtual or Physical
  • Sense
    • Modules must be able to describe hardware performance characteristics (defibrillatable, submersible, shock resistance, etc.)
    • Modules cannot assume the performance of other modules. (Scenarios can specify required module performance but a module must be self-contained and cannot assume the feature set of another module)
  • Respond
    • The round trip time from an intervention to the resulting display must be no slower than the human body.
  • Power
    • Scenario dependent.
    • Connector must deliver enough power to drive the manikin
  • Modular
    • Modules must be interoperable through the resources provided with the standard connector.
    • Modules must be able to capture time synchronized video.
  • Updatable
    • There will be semantic versioning for all software modules as well as hardware components.

System Requirements

  • Data Types
    • Location (Voxel)
  • Data Models
    • Physiology (Heart Rate)
    • Based on OPB
    • Physical Findings (Swelling, Skin Color)
    • Learner Performance (Educational Telemetry)
    • Device Telemetry
    • Interventions (Patient Actions)
    • ICD10 codes
    • Alarms
    • Simulation Control (Start, Stop, Pause)
    • Simulator Configuration (Scenario)
  • System Component Manager (Simulator State Engine)
    • Module Manager
    • Tracks versions of modules
    • Enumerates and Launches Modules
    • Takes scenario configuration and configures modules
    • Boot
    • Ready for input in 30 seconds
    • Manages system health
  • Simulation Manager
    • Owns the clock
    • 50Hz Ticks (Could be 60Hz Ticks)
    • Orchestrates Rewind and Fast Forward
    • Drives the Scenario
    • Manages and scripts simulation state
    • Manages configuration and specifies version requirements
    • Modules must be able to specify software and hardware versions of components.
    • Modules must be able to describe hardware performance (defibrillatable, submersible, shock resistance, etc.)
  • Physiology Manager
    • Marshals Ticks from Simulation Manager, through the Physiology Wrapper to the Physiology Engine
    • Manages the Physiology Engine through the Wrapper
    • Loads and Physiology Wrapper
  • Physiology Wrapper
    • Translates Physiology Data Model & Intervention Data Model to specific Physiology Engine
    • Either OPB provides the model or we are limited to BioGears
  • Network Manager
    • Master/slave negotiation for DHCP
  • Power Manager
    • Recognize multiple batteries
    • Manages power usage and allocation
  • Fluid Manager (Gas or Liquid)
    • Controls flow of (blood, clear, air, vacuum, return) fluid from source to modules
    • Manages multiple fluid reservoirs
    • Manages fluid usage and allocation
    • Clean and Prime fluid lines
  • Network Controller
    • Supports DHCP, UDP Broadcast, PoE, DDS
    • Controls PoE Switches
  • Power Controller
    • Sense Battery Power Level, Temperature
    • Charge Batteries
  • Fluid Controller
    • Meters usage, purging, supply levels
Clone this wiki locally