Search NASA⌕ Search

Engineering topics

David Rubin

Publications and source records attributed to David Rubin.

9 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

Turning Limitations into Opportunities in the Development of the Orion Medical System: Incorporation of mHealth Devices

INTRODUCTION: Selection of medical devices for the Orion medical system is a complex task which is dependent on the current state of terrestrial technology. In this work we review the interplay between NASA requirements, constraints, and opportunities for synergy during the development of the Orion medical system. METHODS: The “plan to treat” list of conditions, and subsequently the medical resource list for the Orion Artemis II lunar flyby mission was completed using semi-quantitative methods. During this process, some medical resources were excluded to comply with mass and volume limits, while other resources applicable to multiple medical requirements were prioritized for inclusion. Choices were also examined considering NASA level of care standards for the Artemis design reference missions. As a means to optimize capabilities in spite of mass and volume constraints, ideas for integration of multiple devices into a single platform were explored, including a ‘hackathon’ challenge which was conducted to generate and evaluate concepts for combining medical devices into a single app-based mobile device (ultrasound, ECG, etc.). RESULTS: The Orion team identified 128 medical conditions that we “plan to treat”, with 139 unique medical resources to address these conditions, including 5 digital diagnostic devices (ECG, otoscope, stethoscope, pulse oximeter, and blood pressure monitor). During selection of these digital devices the team noted that miniaturized medical devices often use mobile device platforms (mHealth), some displaying and transmitting data exclusively via mobile device. Of the 5 initially selected devices, all are capable of mobile connection, one which cannot function without a mobile device (ECG). Furthermore, only one of these devices connects natively to a Windows platform, which is currently the only operating system available on Orion. DISCUSSION: Significant savings in mass and volume as well as training and usability improvements can be achieved by leveraging mHealth technologies. However, the platform presents significant challenges for deployment within the Artemis Program including lack of internet connectivity, incompatible operating systems, and radiation concerns. Each of these drawbacks are surmountable with investment in the supporting vehicle architecture, which may become necessary to support the technology trends seen in commercially available medical devices today. Objective: Learn about the opportunities and challenges of leveraging mHealth devices in the development of medical capabilities for austere environments. Learn about the constraints of the NASA spaceflight environment with regards to digital medical device integration.

Douglas Ebert↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, requirement engineers, clinicians (doctors, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling toolsor have never used these tools. Many of these individuals (clinicians, scientists, even program managers)may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeff Cohen↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

Jeffrey R. Cohen↗
NASA NTRSDate not supplied

Exploration Medical Capability Systems Engineering Overview and Update

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. The ExMC Systems Engineering (SE) team’s mission is to “Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds.” The Element’s work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS and what they are focusing on for the upcoming year.

Kerry McGuire↗
NASA NTRSDate not supplied

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeffrey R. Cohen↗
NASA NTRSDate not supplied

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

Mary Susan Kaetzer↗