← Back to NASA Technology Projects
Active TRL 3 (started at 1, targeting 6)
The goal of the MAVRIIC product is to develop a robust software application tool that visualizes crew health and performance (CHP) data and provides decision support capabilities to assist users in optimizing countermeasure efficacy
The application will serve as an integrated “hub” for visualizing crew health and performance data and will be a valuable resource for both crew members as well as crew support personnel, such as Astronaut Strength, Conditioning, and Rehabilitation Specialists (ASCRs), flight surgeons, and medical testing operators, during all mission phases. The intent of the application and the product overall is to fill an operational gap, streamlining the process of delivering data to crucial end-users and increasing the operational utility of said data. Crewmembers will be forced to make countless operational decisions while on a long duration exploration mission – MAVRIIC seeks to synthesize the myriad cross-functional data inputs related to the human body to ensure CHP decisions are data driven and readily apparent to ensure the greatest impact.
Two versions of the application are being planned as part of the MAVRIIC product: a cloud-based ground tool that is currently in development, as well as an in-vehicle flight tool targeted for Mars missions with the possibility of being extensible to Artemis missions. The MAVRIIC ground tool will visualize existing crew health and performance data from ISS missions and grow to include data from lunar and exploration missions once available. A “coalition” of stakeholders including ASCRs, flight surgeons, and crew members has been formed to provide input and feedback on data visualizations within MAVRIIC using nominally collected CHP data and to help guide the development of more sophisticated decision support tools and algorithms.
Development work has been completed to connect the MAVRIIC ground tool to the Information Management Platform for Analytics & Aggregation (IMPALA). This integration gives MAVRIIC access to exercise, sensorimotor, radiation, nutrition, extravehicular activity (EVA), bone, and functional fitness data, allowing for multidisciplinary data visualizations and decision support tools that stimulate cross-functional actionable insights that are currently less visible to the crew care team.
In addition, the ground tool will serve as a testbed for determining what data visualizations and decision support tools are most useful for crew self-monitoring and should be incorporated into an in-vehicle tool. This in-vehicle tool will be built on the Crew Health and Performance (CHP-DATA ARCHITECTURE) as a backend data source. As Design Reference Missions (DRMs) become better defined, additional capabilities can be planned for the MAVRIIC flight tool that are specific to increasing crew autonomy and reducing reliance on ground support.
Historically, there has not been an application available that allows crew members, Flight Surgeons, ASCRs, and other crew care personnel to view countermeasure data in one centralized location. Instead, data is either shared through MEDB reports, which typically comprise data from a single domain, or it needs to be retrieved from the Electronic Medical Record (EMR). MAVRIIC will be able to monitor and optimize crew health and performance via improved use of exploration countermeasures during increasingly Earth-independent, resource-constrained, and long-duration mission operations.
Listed on TechPort itself — the most direct way to ask about this specific project.
This is early/mid-stage (TRL 3) — the most realistic path in is NASA SBIR/STTR, which funds small businesses and research institutions to develop technology aligned with NASA's needs (equity-free, phased funding). Check whether a current SBIR/STTR solicitation topic overlaps with this project's technology area, or contact the project directly (above) to ask.
None of these are guaranteed paths for this specific project — TechPort itself doesn't have an "apply" button. Reaching out to the contact(s) above with a specific question is usually the fastest way to find out what's actually open.