Science.gov

Sample records for healthcare software assurance

  1. Healthcare Software Assurance

    PubMed Central

    Cooper, Jason G.; Pauley, Keith A.

    2006-01-01

    Software assurance is a rigorous, lifecycle phase-independent set of activities which ensure completeness, safety, and reliability of software processes and products. This is accomplished by guaranteeing conformance to all requirements, standards, procedures, and regulations. These assurance processes are even more important when coupled with healthcare software systems, embedded software in medical instrumentation, and other healthcare-oriented life-critical systems. The current Food and Drug Administration (FDA) regulatory requirements and guidance documentation do not address certain aspects of complete software assurance activities. In addition, the FDA’s software oversight processes require enhancement to include increasingly complex healthcare systems such as Hospital Information Systems (HIS). The importance of complete software assurance is introduced, current regulatory requirements and guidance discussed, and the necessity for enhancements to the current processes shall be highlighted. PMID:17238324

  2. Software assurance standard

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This standard specifies the software assurance program for the provider of software. It also delineates the assurance activities for the provider and the assurance data that are to be furnished by the provider to the acquirer. In any software development effort, the provider is the entity or individual that actually designs, develops, and implements the software product, while the acquirer is the entity or individual who specifies the requirements and accepts the resulting products. This standard specifies at a high level an overall software assurance program for software developed for and by NASA. Assurance includes the disciplines of quality assurance, quality engineering, verification and validation, nonconformance reporting and corrective action, safety assurance, and security assurance. The application of these disciplines during a software development life cycle is called software assurance. Subsequent lower-level standards will specify the specific processes within these disciplines.

  3. Software Quality Assurance Metrics

    NASA Technical Reports Server (NTRS)

    McRae, Kalindra A.

    2004-01-01

    Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

  4. Software Quality Assurance Audits Guidebooks

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes that are used in software development. The Software Assurance Guidebook, NASA-GB-A201, issued in September, 1989, provides an overall picture of the NASA concepts and practices in software assurance. Second level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the second level Software Quality Assurance Audits Guidebook that describes software quality assurance audits in a way that is compatible with practices at NASA Centers.

  5. NASA's Approach to Software Assurance

    NASA Technical Reports Server (NTRS)

    Wetherholt, Martha

    2015-01-01

    NASA defines software assurance as: the planned and systematic set of activities that ensure conformance of software life cycle processes and products to requirements, standards, and procedures via quality, safety, reliability, and independent verification and validation. NASA's implementation of this approach to the quality, safety, reliability, security and verification and validation of software is brought together in one discipline, software assurance. Organizationally, NASA has software assurance at each NASA center, a Software Assurance Manager at NASA Headquarters, a Software Assurance Technical Fellow (currently the same person as the SA Manager), and an Independent Verification and Validation Organization with its own facility. An umbrella risk mitigation strategy for safety and mission success assurance of NASA's software, software assurance covers a wide area and is better structured to address the dynamic changes in how software is developed, used, and managed, as well as it's increasingly complex functionality. Being flexible, risk based, and prepared for challenges in software at NASA is essential, especially as much of our software is unique for each mission.

  6. Modernization of software quality assurance

    NASA Technical Reports Server (NTRS)

    Bhaumik, Gokul

    1988-01-01

    The customers satisfaction depends not only on functional performance, it also depends on the quality characteristics of the software products. An examination of this quality aspect of software products will provide a clear, well defined framework for quality assurance functions, which improve the life-cycle activities of software development. Software developers must be aware of the following aspects which have been expressed by many quality experts: quality cannot be added on; the level of quality built into a program is a function of the quality attributes employed during the development process; and finally, quality must be managed. These concepts have guided our development of the following definition for a Software Quality Assurance function: Software Quality Assurance is a formal, planned approach of actions designed to evaluate the degree of an identifiable set of quality attributes present in all software systems and their products. This paper is an explanation of how this definition was developed and how it is used.

  7. Improving Software Quality Assurance Methods.

    DTIC Science & Technology

    1982-04-01

    by software quality assurance consist of the following: e Incorporation of software quality assurance into the overall software program planning...Systems t , 81 Division and the Air Force Contract Management Division: e • Determine the formal and informal methods of communication; 0 Determine the ...CoopumiWIa~tkoa6 and- TIntettgenc~ e (C 31) ad~viteA6. Tech*.eAL i6 ptwded to EnP Pntopm~ OjjiceA (POe6) and otheA ESP’ et’meta. The ptbiecipal technical

  8. Making the Business Case for Software Assurance

    DTIC Science & Technology

    2009-04-01

    Structure 5.2 Using the Dashboard Process Improvement and Secure Software 6.1 Ensuring a Capable Process 6.2 Adapting the CMMI to Secure Software Assurance ...Secure Software Assurance 6.6 The Business Case for Certifying Trust 6.6.1 Certification: Ensuring a Trusted Relationship vvith an Anonymous Partner...Conclusion and Recommendations 10.1 Getting Started 10.2 Conclusion Appendix A : The "Security" in Software Assurance Appendix B: Cost/Benefit Exam pies

  9. SWiFT Software Quality Assurance Plan.

    SciTech Connect

    Berg, Jonathan Charles

    2016-01-01

    This document describes the software development practice areas and processes which contribute to the ability of SWiFT software developers to provide quality software. These processes are designed to satisfy the requirements set forth by the Sandia Software Quality Assurance Program (SSQAP). APPROVALS SWiFT Software Quality Assurance Plan (SAND2016-0765) approved by: Department Manager SWiFT Site Lead Dave Minster (6121) Date Jonathan White (6121) Date SWiFT Controls Engineer Jonathan Berg (6121) Date CHANGE HISTORY Issue Date Originator(s) Description A 2016/01/27 Jon Berg (06121) Initial release of the SWiFT Software Quality Assurance Plan

  10. Software Safety Assurance of Programmable Logic

    NASA Technical Reports Server (NTRS)

    Berens, Kalynnda

    2002-01-01

    Programmable Logic (PLC, FPGA, ASIC) devices are hybrids - hardware devices that are designed and programmed like software. As such, they fall in an assurance gray area. Programmable Logic is usually tested and verified as hardware, and the software aspects are ignored, potentially leading to safety or mission success concerns. The objective of this proposal is to first determine where and how Programmable Logic (PL) is used within NASA and document the current methods of assurance. Once that is known, raise awareness of the PL software aspects within the NASA engineering community and provide guidance for the use and assurance of PL form a software perspective.

  11. Tool Use Within NASA Software Quality Assurance

    NASA Technical Reports Server (NTRS)

    Shigeta, Denise; Port, Dan; Nikora, Allen P.; Wilf, Joel

    2013-01-01

    As space mission software systems become larger and more complex, it is increasingly important for the software assurance effort to have the ability to effectively assess both the artifacts produced during software system development and the development process itself. Conceptually, assurance is a straightforward idea - it is the result of activities carried out by an organization independent of the software developers to better inform project management of potential technical and programmatic risks, and thus increase management's confidence in the decisions they ultimately make. In practice, effective assurance for large, complex systems often entails assessing large, complex software artifacts (e.g., requirements specifications, architectural descriptions) as well as substantial amounts of unstructured information (e.g., anomaly reports resulting from testing activities during development). In such an environment, assurance engineers can benefit greatly from appropriate tool support. In order to do so, an assurance organization will need accurate and timely information on the tool support available for various types of assurance activities. In this paper, we investigate the current use of tool support for assurance organizations within NASA, and describe on-going work at JPL for providing assurance organizations with the information about tools they need to use them effectively.

  12. Software quality assurance plan for GCS

    NASA Technical Reports Server (NTRS)

    Duncan, Stephen E.; Bailey, Elizabeth K.

    1990-01-01

    The software quality assurance (SQA) function for the Guidance and Control Software (GCS) project which is part of a software error studies research program is described. The SQA plan outlines all of the procedures, controls, and audits to be carried out by the SQA organization to ensure adherence to the policies, procedures, and standards for the GCS project.

  13. New Directions in Software Quality Assurance Automation

    DTIC Science & Technology

    2009-06-01

    Experimental Design", Edited by Don Clausing. New York : UNIPUB /Krass International Publications, Volume 1 & 2, 1987 [24] Software Safety, NASA Technical...Stufken, Orthogonal Arrays: Theory and Applications, Springer Verlag, 1999 [21] G. J. Myers, The Art of Software Testing, Wiley, New York , 1979 [22... New Directions in Software Quality Assurance Automation Mikhail Auguston Department of Computer Science Naval Postgraduate School Monterey

  14. Assuring NASA's Safety and Mission Critical Software

    NASA Technical Reports Server (NTRS)

    Deadrick, Wesley

    2015-01-01

    What is IV&V? Independent Verification and Validation (IV&V) is an objective examination of safety and mission critical software processes and products. Independence: 3 Key parameters: Technical Independence; Managerial Independence; Financial Independence. NASA IV&V perspectives: Will the system's software: Do what it is supposed to do?; Not do what it is not supposed to do?; Respond as expected under adverse conditions?. Systems Engineering: Determines if the right system has been built and that it has been built correctly. IV&V Technical Approaches: Aligned with IEEE 1012; Captured in a Catalog of Methods; Spans the full project lifecycle. IV&V Assurance Strategy: The IV&V Project's strategy for providing mission assurance; Assurance Strategy is driven by the specific needs of an individual project; Implemented via an Assurance Design; Communicated via Assurance Statements.

  15. Health equity monitoring for healthcare quality assurance.

    PubMed

    Cookson, R; Asaria, M; Ali, S; Shaw, R; Doran, T; Goldblatt, P

    2018-02-01

    Population-wide health equity monitoring remains isolated from mainstream healthcare quality assurance. As a result, healthcare organizations remain ill-informed about the health equity impacts of their decisions - despite becoming increasingly well-informed about quality of care for the average patient. We present a new and improved analytical approach to integrating health equity into mainstream healthcare quality assurance, illustrate how this approach has been applied in the English National Health Service, and discuss how it could be applied in other countries. We illustrate the approach using a key quality indicator that is widely used to assess how well healthcare is co-ordinated between primary, community and acute settings: emergency inpatient hospital admissions for ambulatory care sensitive chronic conditions ("potentially avoidable emergency admissions", for short). Whole-population data for 2015 on potentially avoidable emergency admissions in England were linked with neighborhood deprivation indices. Inequality within the populations served by 209 clinical commissioning groups (CCGs: care purchasing organizations with mean population 272,000) was compared against two benchmarks - national inequality and inequality within ten similar populations - using neighborhood-level models to simulate the gap in indirectly standardized admissions between most and least deprived neighborhoods. The modelled inequality gap for England was 927 potentially avoidable emergency admissions per 100,000 people, implying 263,894 excess hospitalizations associated with inequality. Against this national benchmark, 17% of CCGs had significantly worse-than-benchmark equity, and 23% significantly better. The corresponding figures were 11% and 12% respectively against the similar populations benchmark. Deprivation-related inequality in potentially avoidable emergency admissions varies substantially between English CCGs serving similar populations, beyond expected statistical

  16. Software for Optimizing Quality Assurance of Other Software

    NASA Technical Reports Server (NTRS)

    Feather, Martin; Cornford, Steven; Menzies, Tim

    2004-01-01

    Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software.

  17. Introduction: Cybersecurity and Software Assurance Minitrack

    SciTech Connect

    Burns, Luanne; George, Richard; Linger, Richard C

    2015-01-01

    Modern society is dependent on software systems of remarkable scope and complexity. Yet methods for assuring their security and functionality have not kept pace. The result is persistent compromises and failures despite best efforts. Cybersecurity methods must work together for situational awareness, attack prevention and detection, threat attribution, minimization of consequences, and attack recovery. Because defective software cannot be secure, assurance technologies must play a central role in cybersecurity approaches. There is increasing recognition of the need for rigorous methods for cybersecurity and software assurance. The goal of this minitrack is to develop science foundations, technologies, and practices that canmore » improve the security and dependability of complex systems.« less

  18. The NASA Software Management and Assurance Program

    NASA Technical Reports Server (NTRS)

    Hall, D. L.; Wilson, W. M.

    1983-01-01

    A committee of experienced managers representing each major NASA organization guides a major development effort which seeks to ensure the acquisition of economical and reliable software for more complex future programs. The primary, near-term development objectives of the NASA Software Management and Assurance Program are: (1) to provide the best management and technical guidance available; (2) to facilitate the use of proven tools, techniques, and information; and (3) to maintain a pool of highly qualified software personnel. The software development tasks addressed involve such problems as satellite end-to-end architecture and advanced aircraft guidance and control systems.

  19. Software Process Assurance for Complex Electronics (SPACE)

    NASA Technical Reports Server (NTRS)

    Plastow, Richard A.

    2007-01-01

    Complex Electronics (CE) are now programmed to perform tasks that were previously handled in software, such as communication protocols. Many of the methods used to develop software bare a close resemblance to CE development. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that looks at using standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques can be used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that will be more easily maintained, consistent and configurable based on the device used.

  20. Software Process Assurance for Complex Electronics

    NASA Technical Reports Server (NTRS)

    Plastow, Richard A.

    2007-01-01

    Complex Electronics (CE) now perform tasks that were previously handled in software, such as communication protocols. Many methods used to develop software bare a close resemblance to CE development. Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. With CE devices obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that used standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques were used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that was more easily maintained, consistent and configurable based on the device used.

  1. Software Assurance Curriculum Project Volume 1: Master of Software Assurance Reference Curriculum

    DTIC Science & Technology

    2010-08-01

    life- cycle process and adapted to current software engineering practices and methodologies . Program graduates will understand and be able to judge...regulations; privacy and compliance; software architecture; software development methodologies ; legal; standards; security models (e.g., Bell...modeling [3.1.2, 3.3.1, 3.3.2] OWASP Software Assurance Maturity Model (SAMM), construction [3] Threat assessment: identify high-level

  2. Training, Quality Assurance Factors, and Tools Investigation: a Work Report and Suggestions on Software Quality Assurance

    NASA Technical Reports Server (NTRS)

    Lee, Pen-Nan

    1991-01-01

    Previously, several research tasks have been conducted, some observations were obtained, and several possible suggestions have been contemplated involving software quality assurance engineering at NASA Johnson. These research tasks are briefly described. Also, a brief discussion is given on the role of software quality assurance in software engineering along with some observations and suggestions. A brief discussion on a training program for software quality assurance engineers is provided. A list of assurance factors as well as quality factors are also included. Finally, a process model which can be used for searching and collecting software quality assurance tools is presented.

  3. APPLICATION OF SOFTWARE QUALITY ASSURANCE CONCEPTS AND PROCEDURES TO ENVIORNMENTAL RESEARCH INVOLVING SOFTWARE DEVELOPMENT

    EPA Science Inventory

    As EPA’s environmental research expands into new areas that involve the development of software, quality assurance concepts and procedures that were originally developed for environmental data collection may not be appropriate. Fortunately, software quality assurance is a ...

  4. Survey of Software Assurance Techniques for Highly Reliable Systems

    NASA Technical Reports Server (NTRS)

    Nelson, Stacy

    2004-01-01

    This document provides a survey of software assurance techniques for highly reliable systems including a discussion of relevant safety standards for various industries in the United States and Europe, as well as examples of methods used during software development projects. It contains one section for each industry surveyed: Aerospace, Defense, Nuclear Power, Medical Devices and Transportation. Each section provides an overview of applicable standards and examples of a mission or software development project, software assurance techniques used and reliability achieved.

  5. Product assurance policies and procedures for flight dynamics software development

    NASA Technical Reports Server (NTRS)

    Perry, Sandra; Jordan, Leon; Decker, William; Page, Gerald; Mcgarry, Frank E.; Valett, Jon

    1987-01-01

    The product assurance policies and procedures necessary to support flight dynamics software development projects for Goddard Space Flight Center are presented. The quality assurance and configuration management methods and tools for each phase of the software development life cycles are described, from requirements analysis through acceptance testing; maintenance and operation are not addressed.

  6. Incorporating cost-benefit analyses into software assurance planning

    NASA Technical Reports Server (NTRS)

    Feather, M. S.; Sigal, B.; Cornford, S. L.; Hutchinson, P.

    2001-01-01

    The objective is to use cost-benefit analyses to identify, for a given project, optimal sets of software assurance activities. Towards this end we have incorporated cost-benefit calculations into a risk management framework.

  7. NASA Software Assurance's Roles in Research and Technology

    NASA Technical Reports Server (NTRS)

    Wetherholt, Martha

    2010-01-01

    This slide presentation reviews the interactions between the scientist and engineers doing research and technology and the software developers and others who are doing software assurance. There is a discussion of the role of the Safety and Mission Assurance (SMA) in developing software to be used for research and technology, and the importance of this role as the technology moves to the higher levels of the technology readiness levels (TRLs). There is also a call to change the way the development of software is developed.

  8. Quality measures and assurance for AI (Artificial Intelligence) software

    NASA Technical Reports Server (NTRS)

    Rushby, John

    1988-01-01

    This report is concerned with the application of software quality and evaluation measures to AI software and, more broadly, with the question of quality assurance for AI software. Considered are not only the metrics that attempt to measure some aspect of software quality, but also the methodologies and techniques (such as systematic testing) that attempt to improve some dimension of quality, without necessarily quantifying the extent of the improvement. The report is divided into three parts Part 1 reviews existing software quality measures, i.e., those that have been developed for, and applied to, conventional software. Part 2 considers the characteristics of AI software, the applicability and potential utility of measures and techniques identified in the first part, and reviews those few methods developed specifically for AI software. Part 3 presents an assessment and recommendations for the further exploration of this important area.

  9. Assuring Software Cost Estimates: Is it an Oxymoron?

    NASA Technical Reports Server (NTRS)

    Hihn, Jarius; Tregre, Grant

    2013-01-01

    The software industry repeatedly observes cost growth of well over 100% even after decades of cost estimation research and well-known best practices, so "What's the problem?" In this paper we will provide an overview of the current state oj software cost estimation best practice. We then explore whether applying some of the methods used in software assurance might improve the quality of software cost estimates. This paper especially focuses on issues associated with model calibration, estimate review, and the development and documentation of estimates as part alan integrated plan.

  10. SAPHIRE 8 Quality Assurance Software Metrics Report

    SciTech Connect

    Kurt G. Vedros

    2011-08-01

    The purpose of this review of software metrics is to examine the quality of the metrics gathered in the 2010 IV&V and to set an outline for results of updated metrics runs to be performed. We find from the review that the maintenance of accepted quality standards presented in the SAPHIRE 8 initial Independent Verification and Validation (IV&V) of April, 2010 is most easily achieved by continuing to utilize the tools used in that effort while adding a metric of bug tracking and resolution. Recommendations from the final IV&V were to continue periodic measurable metrics such as McCabe's complexity measuremore » to ensure quality is maintained. The four software tools used to measure quality in the IV&V were CodeHealer, Coverage Validator, Memory Validator, Performance Validator, and Thread Validator. These are evaluated based on their capabilities. We attempted to run their latest revisions with the newer Delphi 2010 based SAPHIRE 8 code that has been developed and was successful with all of the Validator series of tools on small tests. Another recommendation from the IV&V was to incorporate a bug tracking and resolution metric. To improve our capability of producing this metric, we integrated our current web reporting system with the SpiraTest test management software purchased earlier this year to track requirements traceability.« less

  11. Software Assurance Measurement -- State of the Practice

    DTIC Science & Technology

    2013-11-01

    NET 39 ActionScript 39 Ada 40 C/C++ 40 Java 41 JavaScript 42 Objective-C 42 Opa 42 Packages 42 Perl 42 PHP 42 Python 42 Formal Methods...2000]. Measurements of structural correctness assess how well the software satisfies environmental or business requirements, which support the actual...Java, C# /.NET, ASP.NET, PHP, C/C++, ASP, Android Java, Objective C (iOS), Visual Basic 6, JavaScript, Ruby, Python , Perl, PL/SQL, APEX, and HTML5

  12. Technology Transfer Challenges for High-Assurance Software Engineering Tools

    NASA Technical Reports Server (NTRS)

    Koga, Dennis (Technical Monitor); Penix, John; Markosian, Lawrence Z.

    2003-01-01

    In this paper, we describe our experience with the challenges thar we are currently facing in our effort to develop advanced software verification and validation tools. We categorize these challenges into several areas: cost benefits modeling, tool usability, customer application domain, and organizational issues. We provide examples of challenges in each area and identrfj, open research issues in areas which limit our ability to transfer high-assurance software engineering tools into practice.

  13. Factors affecting the adoption of quality assurance technologies in healthcare.

    PubMed

    Storey, John

    2013-01-01

    In the light of public concern and of strong policy emphasis on quality and safety in the nursing care of patients in hospital settings, this paper aims to focus on the factors affecting the adoption of innovative quality assurance technologies. Two sets of complementary literature were mined for key themes. Next, new empirical insights were sought. Data gathering was conducted in three phases. The first involved contact with NHS Technology Hubs and other institutions which had insights into leading centres in quality assurance technologies. The second phase was a series of telephone interviews with lead nurses in those hospitals which were identified in the first phase as comprising the leading centres. The third phase comprised a series of face to face interviews with innovators and adopters of healthcare quality assurance technologies in five hospital trusts. There were three main sets of findings. First, despite the strong policy push and the templates established at national level, there were significant variations in the nature and robustness of the quality assurance toolkits that were developed, adapted and adopted. Second, in most of the adopting cases there were important obstacles to the full adoption of the toolkits that were designed. Third, the extent and nature of the ambition of the developers varied dramatically - some wished to see their work impacting widely across the health service; others had a number of different reasons for wanting to restrict the impact of their work. The general concerns about front-line care and the various inquiries into care quality failures emphasise the need for improved and consistent care quality assurance methodologies and practice. The technology adoption literature gives only partial insight into the nature of the challenges; this paper offers specific insights into the factors inhibiting the full adoption of quality assurance technologies in ward-based care.

  14. A Survey and Evaluation of Software Quality Assurance.

    DTIC Science & Technology

    1984-09-01

    fhuction. xe to which acces to software or data by unauthorized Peron can be controled. Effort required to lemr, operate prepare wopw. and interpret output...skills of personnel involved with soft- ware quality assurance. These programs will also provide the v-. basis for Air Force career development

  15. Software Assurance Challenges for the Commercial Crew Program

    NASA Technical Reports Server (NTRS)

    Cuyno, Patrick; Malnick, Kathy D.; Schaeffer, Chad E.

    2015-01-01

    This paper will provide a description of some of the challenges NASA is facing in providing software assurance within the new commercial space services paradigm, namely with the Commercial Crew Program (CCP). The CCP will establish safe, reliable, and affordable access to the International Space Station (ISS) by purchasing a ride from commercial companies. The CCP providers have varying experience with software development in safety-critical space systems. NASA's role in providing effective software assurance support to the CCP providers is critical to the success of CCP. These challenges include funding multiple vehicles that execute in parallel and have different rules of engagement, multiple providers with unique proprietary concerns, providing equivalent guidance to all providers, permitting alternates to NASA standards, and a large number of diverse stakeholders. It is expected that these challenges will exist in future programs, especially if the CCP paradigm proves successful. The proposed CCP approach to address these challenges includes a risk-based assessment with varying degrees of engagement and a distributed assurance model. This presentation will describe NASA IV&V Program's software assurance support and responses to these challenges.

  16. A Framework for Modeling the Software Assurance Ecosystem: Insights from the Software Assurance Landscape Project

    DTIC Science & Technology

    2010-08-01

    The quantity of assurance services provided by an organization (e.g., market share, annual sales, sales, installed base of underlying technology...organization with respect to the assurance products it builds (e.g., perceived pene- tration of market , perceived influence of products on...contin- ue as vendors understand its importance for maintaining and growing their market share. This trend can push vendors toward more proactive

  17. Fault Management Architectures and the Challenges of Providing Software Assurance

    NASA Technical Reports Server (NTRS)

    Savarino, Shirley; Fitz, Rhonda; Fesq, Lorraine; Whitman, Gerek

    2015-01-01

    Fault Management (FM) is focused on safety, the preservation of assets, and maintaining the desired functionality of the system. How FM is implemented varies among missions. Common to most missions is system complexity due to a need to establish a multi-dimensional structure across hardware, software and spacecraft operations. FM is necessary to identify and respond to system faults, mitigate technical risks and ensure operational continuity. Generally, FM architecture, implementation, and software assurance efforts increase with mission complexity. Because FM is a systems engineering discipline with a distributed implementation, providing efficient and effective verification and validation (V&V) is challenging. A breakout session at the 2012 NASA Independent Verification & Validation (IV&V) Annual Workshop titled "V&V of Fault Management: Challenges and Successes" exposed this issue in terms of V&V for a representative set of architectures. NASA's Software Assurance Research Program (SARP) has provided funds to NASA IV&V to extend the work performed at the Workshop session in partnership with NASA's Jet Propulsion Laboratory (JPL). NASA IV&V will extract FM architectures across the IV&V portfolio and evaluate the data set, assess visibility for validation and test, and define software assurance methods that could be applied to the various architectures and designs. This SARP initiative focuses efforts on FM architectures from critical and complex projects within NASA. The identification of particular FM architectures and associated V&V/IV&V techniques provides a data set that can enable improved assurance that a system will adequately detect and respond to adverse conditions. Ultimately, results from this activity will be incorporated into the NASA Fault Management Handbook providing dissemination across NASA, other agencies and the space community. This paper discusses the approach taken to perform the evaluations and preliminary findings from the research.

  18. Fault Management Architectures and the Challenges of Providing Software Assurance

    NASA Technical Reports Server (NTRS)

    Savarino, Shirley; Fitz, Rhonda; Fesq, Lorraine; Whitman, Gerek

    2015-01-01

    The satellite systems Fault Management (FM) is focused on safety, the preservation of assets, and maintaining the desired functionality of the system. How FM is implemented varies among missions. Common to most is system complexity due to a need to establish a multi-dimensional structure across hardware, software and operations. This structure is necessary to identify and respond to system faults, mitigate technical risks and ensure operational continuity. These architecture, implementation and software assurance efforts increase with mission complexity. Because FM is a systems engineering discipline with a distributed implementation, providing efficient and effective verification and validation (VV) is challenging. A breakout session at the 2012 NASA Independent Verification Validation (IVV) Annual Workshop titled VV of Fault Management: Challenges and Successes exposed these issues in terms of VV for a representative set of architectures. NASA's IVV is funded by NASA's Software Assurance Research Program (SARP) in partnership with NASA's Jet Propulsion Laboratory (JPL) to extend the work performed at the Workshop session. NASA IVV will extract FM architectures across the IVV portfolio and evaluate the data set for robustness, assess visibility for validation and test, and define software assurance methods that could be applied to the various architectures and designs. This work focuses efforts on FM architectures from critical and complex projects within NASA. The identification of particular FM architectures, visibility, and associated VVIVV techniques provides a data set that can enable higher assurance that a satellite system will adequately detect and respond to adverse conditions. Ultimately, results from this activity will be incorporated into the NASA Fault Management Handbook providing dissemination across NASA, other agencies and the satellite community. This paper discusses the approach taken to perform the evaluations and preliminary findings from the

  19. A Discussion of the Software Quality Assurance Role

    NASA Technical Reports Server (NTRS)

    Kandt, Ronald Kirk

    2010-01-01

    The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).

  20. Daily quality assurance software for a satellite radiometer system

    NASA Technical Reports Server (NTRS)

    Keegstra, P. B.; Smoot, G. F.; Bennett, C. L.; Aymon, J.; Backus, C.; Deamici, G.; Hinshaw, G.; Jackson, P. D.; Kogut, A.; Lineweaver, C.

    1992-01-01

    Six Differential Microwave Radiometers (DMR) on COBE (Cosmic Background Explorer) measure the large-angular-scale isotropy of the cosmic microwave background (CMB) at 31.5, 53, and 90 GHz. Quality assurance software analyzes the daily telemetry from the spacecraft to ensure that the instrument is operating correctly and that the data are not corrupted. Quality assurance for DMR poses challenging requirements. The data are differential, so a single bad point can affect a large region of the sky, yet the CMB isotropy requires lengthy integration times (greater than 1 year) to limit potential CMB anisotropies. Celestial sources (with the exception of the moon) are not, in general, visible in the raw differential data. A 'quicklook' software system was developed that, in addition to basic plotting and limit-checking, implements a collection of data tests as well as long-term trending. Some of the key capabilities include the following: (1) stability analysis showing how well the data RMS averages down with increased data; (2) a Fourier analysis and autocorrelation routine to plot the power spectrum and confirm the presence of the 3 mK 'cosmic' dipole signal; (3) binning of the data against basic spacecraft quantities such as orbit angle; (4) long-term trending; and (5) dipole fits to confirm the spacecraft attitude azimuth angle.

  1. Moving Secure Software Assurance into Higher Education: A Roadmap for Change

    DTIC Science & Technology

    2011-06-02

    safe, and secure? Why not make every system a “Trustable System?” 6/2/20117 Out of 100 web app development projects ….. Jeff Williams: OWASP 8...failures. “ – Master of Software Assurance Reference Curriculum 10 More Context: Software Assurance 6/2/201110 The OWASP Software Assurance Maturity...that was the product of this year long study Documented and categorized all commonly accepted practices, principles, methodologies and tools for

  2. Assuring measurement quality in person-centred healthcare

    NASA Astrophysics Data System (ADS)

    Pendrill, L. R.

    2018-03-01

    Is it realistic to aspire to the same kind of quality-assurance of measurement in person-centred care, currently being implemented in healthcare globally, as is established in the physical sciences and engineering? Ensuring metrological comparability (‘traceability’) and reliably declaring measurement uncertainty when assessing patient ability or increased social capital are however challenging for subjective measurements often characterised by large dispersion. Drawing simple analogies between ‘instruments’ in the social sciences—questionnaires, ability tests, etc—and engineering instruments such as thermometers does not go far enough. A possible way forward, apparently equally applicable to both physical and social measurement, seems to be to model inferences in terms of performance metrics of a measurement system. Person-centred care needs person-centred measurement and a full picture of the measurement process when man acts as a measurement instrument is given in the present paper. This complements previous work by presenting the process, step by step, from the observed indication (e.g. probability of success, P success, of achieving a task), through restitution with Rasch measurement theory, to the measurand (e.g. task difficulty). Rasch invariant measure theory can yield quantities—‘latent’ (or ‘explanatory’) variables such as task challenge or person ability—with characteristics akin to those of physical quantities. Metrological references for comparability via traceability and reliable estimates of uncertainty and decision risks are then in reach even for perceptive measurements (and other qualitative properties). As a case study, the person-centred measurement of cognitive ability is examined, as part of the EU project EMPIR 15HLT04 NeuroMet, for Alzheimer’s, where better analysis of correlations with brain atrophy is enabled thanks to the Rasch metrological approach.

  3. The software product assurance metrics study: JPL's software systems quality and productivity

    NASA Technical Reports Server (NTRS)

    Bush, Marilyn W.

    1989-01-01

    The findings are reported of the Jet Propulsion Laboratory (JPL)/Software Product Assurance (SPA) Metrics Study, conducted as part of a larger JPL effort to improve software quality and productivity. Until recently, no comprehensive data had been assembled on how JPL manages and develops software-intensive systems. The first objective was to collect data on software development from as many projects and for as many years as possible. Results from five projects are discussed. These results reflect 15 years of JPL software development, representing over 100 data points (systems and subsystems), over a third of a billion dollars, over four million lines of code and 28,000 person months. Analysis of this data provides a benchmark for gauging the effectiveness of past, present and future software development work. In addition, the study is meant to encourage projects to record existing metrics data and to gather future data. The SPA long term goal is to integrate the collection of historical data and ongoing project data with future project estimations.

  4. European Psychiatric Association (EPA) guidance on quality assurance in mental healthcare.

    PubMed

    Gaebel, W; Großimlinghaus, I; Heun, R; Janssen, B; Johnson, B; Kurimay, T; Montellano, P; Muijen, M; Munk-Jorgensen, P; Rössler, W; Ruggeri, M; Thornicroft, G; Zielasek, J

    2015-03-01

    To advance the quality of mental healthcare in Europe by developing guidance on implementing quality assurance. We performed a systematic literature search on quality assurance in mental healthcare and the 522 retrieved documents were evaluated by two independent reviewers (B.J. and J.Z.). Based on these evaluations, evidence tables were generated. As it was found that these did not cover all areas of mental healthcare, supplementary hand searches were performed for selected additional areas. Based on these findings, fifteen graded recommendations were developed and consented by the authors. Review by the EPA Guidance Committee and EPA Board led to two additional recommendations (on immigrant mental healthcare and parity of mental and physical healthcare funding). Although quality assurance (measures to keep a certain degree of quality), quality control and monitoring (applying quality indicators to the current degree of quality), and quality management (coordinated measures and activities with regard to quality) are conceptually distinct, in practice they are frequently used as if identical and hardly separable. There is a dearth of controlled trials addressing ways to optimize quality assurance in mental healthcare. Altogether, seventeen recommendations were developed addressing a range of aspects of quality assurance in mental healthcare, which appear usable across Europe. These were divided into recommendations about structures, processes and outcomes. Each recommendation was assigned to a hierarchical level of analysis (macro-, meso- and micro-level). There was a lack of evidence retrievable by a systematic literature search about quality assurance of mental healthcare. Therefore, only after further topics and search had been added it was possible to develop recommendations with mostly medium evidence levels. Evidence-based graded recommendations for quality assurance in mental healthcare were developed which should next be implemented and evaluated for

  5. Lessons learned from development and quality assurance of software systems at the Halden Project

    SciTech Connect

    Bjorlo, T.J.; Berg, O.; Pehrsen, M.

    1996-03-01

    The OECD Halden Reactor Project has developed a number of software systems within the research programmes. These programmes have comprised a wide range of topics, like studies of software for safety-critical applications, development of different operator support systems, and software systems for building and implementing graphical user interfaces. The systems have ranged from simple prototypes to installations in process plants. In the development of these software systems, Halden has gained much experience in quality assurance of different types of software. This paper summarises the accumulated experience at the Halden Project in quality assurance of software systems. The different software systemsmore » being developed at the Halden Project may be grouped into three categories. These are plant-specific software systems (one-of-a-kind deliveries), generic software products, and safety-critical software systems. This classification has been found convenient as the categories have different requirements to the quality assurance process. In addition, the experience from use of software development tools and proprietary software systems at Halden, is addressed. The paper also focuses on the experience gained from the complete software life cycle, starting with the software planning phase and ending with software operation and maintenance.« less

  6. [Current challenges of external quality assurance in the German healthcare system].

    PubMed

    Willms, Gerald; Bramesfeld, Anke; Pottkämper, Karen; Broge, Björn; Szecsenyi, Joachim

    2013-01-01

    External quality assurance has three main aims: to make service provision in medicine and nursing comparable, to systematically identify deficits in service quality and to support the introduction of measures for quality improvement. This article reflects on three major developments in mandatory external quality assurance in the German healthcare system that took place during the last five years. These developments include the implementation of cross-sectoral quality assurance, the utilisation of new data sources and a new focus on quality deficits and practicability. The article highlights the challenges that come along with these developments. Copyright © 2013. Published by Elsevier GmbH.

  7. Quality Assurance of Software Used In Aircraft Or Related Products

    DOT National Transportation Integrated Search

    1993-02-01

    This advisory circular (AC) provides an acceptable means, but not the only means, to show compliance with the quality assurance requirements of Federal Aviation Regulations (FAR) Part 21, Certification Procedures for Products and Parts, as applicable...

  8. Software Assurance Curriculum Project Volume 4: Community College Education

    DTIC Science & Technology

    2011-09-01

    copyright, and plagiarism ; “Ten Commandments for Computer Ethics” C Overview of operating systems (1 hour): role and purpose of operating systems; simple... plagiarism , and software piracy. Chooses to respond professionally to ethical issues in computing, such as intellectual property, plagiarism

  9. Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

  10. Analytical Design of Evolvable Software for High-Assurance Computing

    DTIC Science & Technology

    2001-02-14

    air traffic control, avionics, and nuclear power plant control [32,105]. These applications require software that is highly reliable and safe as well...defense systems, nuclear power plant management, air traffic control, aircraft control, on-line invest- ment reports and transactions, and patient...Approach to Architecture, Ph.D. Dissertation, School of Computer Science, Car- negie Mellon University, Pittsburgh, PA, 1998. [7] Allen, R. and D. Garlan

  11. Critical Thinking Skills of Students through Mathematics Learning with ASSURE Model Assisted by Software Autograph

    NASA Astrophysics Data System (ADS)

    Kristianti, Y.; Prabawanto, S.; Suhendra, S.

    2017-09-01

    This study aims to examine the ability of critical thinking and students who attain learning mathematics with learning model ASSURE assisted Autograph software. The design of this study was experimental group with pre-test and post-test control group. The experimental group obtained a mathematics learning with ASSURE-assisted model Autograph software and the control group acquired the mathematics learning with the conventional model. The data are obtained from the research results through critical thinking skills tests. This research was conducted at junior high school level with research population in one of junior high school student in Subang Regency of Lesson Year 2016/2017 and research sample of class VIII student in one of junior high school in Subang Regency for 2 classes. Analysis of research data is administered quantitatively. Quantitative data analysis was performed on the normalized gain level between the two sample groups using a one-way anova test. The results show that mathematics learning with ASSURE assisted model Autograph software can improve the critical thinking ability of junior high school students. Mathematical learning using ASSURE-assisted model Autograph software is significantly better in improving the critical thinking skills of junior high school students compared with conventional models.

  12. 76 FR 54800 - International Business Machines (IBM), Software Group Business Unit, Quality Assurance Group, San...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-09-02

    ... DEPARTMENT OF LABOR Employment and Training Administration [TA-W-74,554] International Business Machines (IBM), Software Group Business Unit, Quality Assurance Group, San Jose, California; Notice of Negative Determination on Reconsideration On January 21, 2011, the Department of Labor (Department) issued an Affirmative Determination Regarding...

  13. Software archeology: a case study in software quality assurance and design

    SciTech Connect

    Macdonald, John M; Lloyd, Jane A; Turner, Cameron J

    2009-01-01

    Ideally, quality is designed into software, just as quality is designed into hardware. However, when dealing with legacy systems, demonstrating that the software meets required quality standards may be difficult to achieve. As the need to demonstrate the quality of existing software was recognized at Los Alamos National Laboratory (LANL), an effort was initiated to uncover and demonstrate that legacy software met the required quality standards. This effort led to the development of a reverse engineering approach referred to as software archaeology. This paper documents the software archaeology approaches used at LANL to document legacy software systems. A case studymore » for the Robotic Integrated Packaging System (RIPS) software is included.« less

  14. Quality Assurance in Software Development: An Exploratory Investigation in Software Project Failures and Business Performance

    ERIC Educational Resources Information Center

    Ichu, Emmanuel A.

    2010-01-01

    Software quality is perhaps one of the most sought-after attributes in product development, however; this goal is unattained. Problem factors in software development and how these have affected the maintainability of the delivered software systems requires a thorough investigation. It was, therefore, very important to understand software…

  15. Implementation of Oak Ridge National Laboratory Software Quality Assurance Requirements for COMSOL 3.4

    SciTech Connect

    Freels, James D

    2008-01-01

    It is desirable for nuclear safety-related calculations to be performed at the Oak Ridge National Laboratory (ORNL) using COMSOL. The Department of Energy (DOE) has mandated that ORNL will incorporate software quality assurance (SQA) with special attention to nuclear safety-related software applications. The author has developed a procedure for implementing these DOE-mandated SQA requirements on nuclear safety-related software applicable to the High Flux Isotope Reactor (HFIR). This paper will describe how this procedure will be implemented for COMSOL so that nuclear safety-related calculations may be performed.

  16. Risk-Informed Safety Assurance and Probabilistic Assessment of Mission-Critical Software-Intensive Systems

    NASA Technical Reports Server (NTRS)

    Guarro, Sergio B.

    2010-01-01

    This report validates and documents the detailed features and practical application of the framework for software intensive digital systems risk assessment and risk-informed safety assurance presented in the NASA PRA Procedures Guide for Managers and Practitioner. This framework, called herein the "Context-based Software Risk Model" (CSRM), enables the assessment of the contribution of software and software-intensive digital systems to overall system risk, in a manner which is entirely compatible and integrated with the format of a "standard" Probabilistic Risk Assessment (PRA), as currently documented and applied for NASA missions and applications. The CSRM also provides a risk-informed path and criteria for conducting organized and systematic digital system and software testing so that, within this risk-informed paradigm, the achievement of a quantitatively defined level of safety and mission success assurance may be targeted and demonstrated. The framework is based on the concept of context-dependent software risk scenarios and on the modeling of such scenarios via the use of traditional PRA techniques - i.e., event trees and fault trees - in combination with more advanced modeling devices such as the Dynamic Flowgraph Methodology (DFM) or other dynamic logic-modeling representations. The scenarios can be synthesized and quantified in a conditional logic and probabilistic formulation. The application of the CSRM method documented in this report refers to the MiniAERCam system designed and developed by the NASA Johnson Space Center.

  17. A survey of Canadian medical physicists: software quality assurance of in-house software.

    PubMed

    Salomons, Greg J; Kelly, Diane

    2015-01-05

    This paper reports on a survey of medical physicists who write and use in-house written software as part of their professional work. The goal of the survey was to assess the extent of in-house software usage and the desire or need for related software quality guidelines. The survey contained eight multiple-choice questions, a ranking question, and seven free text questions. The survey was sent to medical physicists associated with cancer centers across Canada. The respondents to the survey expressed interest in having guidelines to help them in their software-related work, but also demonstrated extensive skills in the area of testing, safety, and communication. These existing skills form a basis for medical physicists to establish a set of software quality guidelines.

  18. A tool to include gamma analysis software into a quality assurance program.

    PubMed

    Agnew, Christina E; McGarry, Conor K

    2016-03-01

    To provide a tool to enable gamma analysis software algorithms to be included in a quality assurance (QA) program. Four image sets were created comprising two geometric images to independently test the distance to agreement (DTA) and dose difference (DD) elements of the gamma algorithm, a clinical step and shoot IMRT field and a clinical VMAT arc. The images were analysed using global and local gamma analysis with 2 in-house and 8 commercially available software encompassing 15 software versions. The effect of image resolution on gamma pass rates was also investigated. All but one software accurately calculated the gamma passing rate for the geometric images. Variation in global gamma passing rates of 1% at 3%/3mm and over 2% at 1%/1mm was measured between software and software versions with analysis of appropriately sampled images. This study provides a suite of test images and the gamma pass rates achieved for a selection of commercially available software. This image suite will enable validation of gamma analysis software within a QA program and provide a frame of reference by which to compare results reported in the literature from various manufacturers and software versions. Copyright © 2015. Published by Elsevier Ireland Ltd.

  19. A survey of Canadian medical physicists: software quality assurance of in‐house software

    PubMed Central

    Kelly, Diane

    2015-01-01

    This paper reports on a survey of medical physicists who write and use in‐house written software as part of their professional work. The goal of the survey was to assess the extent of in‐house software usage and the desire or need for related software quality guidelines. The survey contained eight multiple‐choice questions, a ranking question, and seven free text questions. The survey was sent to medical physicists associated with cancer centers across Canada. The respondents to the survey expressed interest in having guidelines to help them in their software‐related work, but also demonstrated extensive skills in the area of testing, safety, and communication. These existing skills form a basis for medical physicists to establish a set of software quality guidelines. PACS number: 87.55.Qr PMID:25679168

  20. The role of reliability graph models in assuring dependable operation of complex hardware/software systems

    NASA Technical Reports Server (NTRS)

    Patterson-Hine, F. A.; Davis, Gloria J.; Pedar, A.

    1991-01-01

    The complexity of computer systems currently being designed for critical applications in the scientific, commercial, and military arenas requires the development of new techniques for utilizing models of system behavior in order to assure 'ultra-dependability'. The complexity of these systems, such as Space Station Freedom and the Air Traffic Control System, stems from their highly integrated designs containing both hardware and software as critical components. Reliability graph models, such as fault trees and digraphs, are used frequently to model hardware systems. Their applicability for software systems has also been demonstrated for software safety analysis and the analysis of software fault tolerance. This paper discusses further uses of graph models in the design and implementation of fault management systems for safety critical applications.

  1. Earth Observing System (EOS)/Advanced Microwave Sounding Unit-A (AMSU-A) software assurance plan

    NASA Technical Reports Server (NTRS)

    Schwantje, Robert; Smith, Claude

    1994-01-01

    This document defines the responsibilities of Software Quality Assurance (SOA) for the development of the flight software installed in EOS/AMSU-A instruments, and the ground support software used in the test and integration of the EOS/AMSU-A instruments.

  2. Visualization and animation as a technique to assist in the construction of high assurance software

    SciTech Connect

    Winter, V.L.

    1996-07-01

    The software construction process consists of a mixture of informal and formal steps. By their very nature, informal steps cannot be formally verified. Empirical evidence suggests that a majority of software errors originate in the informal steps of the software development process. For this reason, when constructing high assurance software, it is essential that a significant effort be made to increase one`s confidence (i.e., to validate) that the informal steps have been made correctly. Visualization and animation can be used to provide an `intuitive proof` that the informal steps in the software construction process are correct. In addition, the formalmore » portion of software construction often permits/demands artistic (informal) decisions to be made (e.g., design decisions). Such decisions often have unexpected/unforeseen consequences that are only discovered later in the development process. Visualization and animation techniques can be brought to bear on this aspect of the software construction process by providing a better intuitive understanding of the impact of the informal decisions that are made in program development. This increases the likelihood that undesirable decisions can be avoided or at least detected earlier in the development process.« less

  3. Software Quality Assurance, One of the Software Acquisition Engineering Guidebook Series

    DTIC Science & Technology

    1979-01-01

    d. Is the detailed definition of the common data base content, structure and control completed? e. Are methods of accessing data base elements ...NUMBER D180-24700-1 CONTRACT OR GRANT NUMBERf*; F33657-76-C-0723 **£**’ 10. PROGRAM ELEMENT . PROJECT, TASK AREA A WORK UNIT NUMBERS 11...alternative recommendations concerning methods for cost-effective software acquisition. The intent is that the reader determine the degree of

  4. A Suitable Software Process Improvement Model for the UK Healthcare Industry

    NASA Astrophysics Data System (ADS)

    Nguyen, Tien D.; Guo, Hong; Naguib, Raouf N. G.

    Over the recent years, the UK Healthcare sector has been the prime focus of many reports and industrial surveys, particularly in the field of software development and management issues. This signals the importance of growing concerns regarding quality issues in the Healthcare domain. In response to this, a new tailored Healthcare Process Improvement (SPI) model is proposed, which takes into consideration both signals from the industry and insights from literature.

  5. Assure

    Integrated Risk Information System (IRIS)

    Assure ; CASRN 76578 - 14 - 8 Human health assessment information on a chemical substance is included in the IRIS database only after a comprehensive review of toxicity data , as outlined in the IRIS assessment development process . Sections I ( Health Hazard Assessments for Noncarcinogenic Effects

  6. An empirical evaluation of software quality assurance practices and challenges in a developing country: a comparison of Nigeria and Turkey.

    PubMed

    Sowunmi, Olaperi Yeside; Misra, Sanjay; Fernandez-Sanz, Luis; Crawford, Broderick; Soto, Ricardo

    2016-01-01

    The importance of quality assurance in the software development process cannot be overemphasized because its adoption results in high reliability and easy maintenance of the software system and other software products. Software quality assurance includes different activities such as quality control, quality management, quality standards, quality planning, process standardization and improvement amongst others. The aim of this work is to further investigate the software quality assurance practices of practitioners in Nigeria. While our previous work covered areas on quality planning, adherence to standardized processes and the inherent challenges, this work has been extended to include quality control, software process improvement and international quality standard organization membership. It also makes comparison based on a similar study carried out in Turkey. The goal is to generate more robust findings that can properly support decision making by the software community. The qualitative research approach, specifically, the use of questionnaire research instruments was applied to acquire data from software practitioners. In addition to the previous results, it was observed that quality assurance practices are quite neglected and this can be the cause of low patronage. Moreover, software practitioners are neither aware of international standards organizations or the required process improvement techniques; as such their claimed standards are not aligned to those of accredited bodies, and are only limited to their local experience and knowledge, which makes it questionable. The comparison with Turkey also yielded similar findings, making the results typical of developing countries. The research instrument used was tested for internal consistency using the Cronbach's alpha, and it was proved reliable. For the software industry in developing countries to grow strong and be a viable source of external revenue, software assurance practices have to be taken seriously

  7. Software requirements elicitation to support internal monitoring of quality assurance system for higher education in Indonesia

    NASA Astrophysics Data System (ADS)

    Amalia, A.; Gunawan, D.; Hardi, S. M.; Rachmawati, D.

    2018-02-01

    The Internal Quality Assurance System (in Indonesian: SPMI (Sistem Penjaminan Mutu Internal) is a systemic activity of quality assurance of higher education in Indonesia. SPMI should be done by all higher education or universities in Indonesia based on the Regulation of the Minister of Research, Technology and Higher Education of the Republic of Indonesia Number 62 of 2016. Implementation of SPMI must refer to the principle of SPMI that is independent, standardize, accurate, well planned and sustainable, documented and systematic. To assist the SPMI cycle properly, universities need a supporting software to monitor all the activities of SPMI. But in reality, many universities are not optimal in building this SPMI monitoring system. One of the obstacles is the determination of system requirements in support of SPMI principles is difficult to achieve. In this paper, we observe the initial phase of the engineering requirements elicitation. Unlike other methods that collect system requirements from users and stakeholders, we find the system requirements of the SPMI principles from SPMI guideline book. The result of this paper can be used as a choice in determining SPMI software requirements. This paper can also be used by developers and users to understand the scenario of SPMI so that could overcome the problems of understanding between this two parties.

  8. Implementing Quality Assurance for the Numerical Research Software Dune / PDELab / DuMux

    NASA Astrophysics Data System (ADS)

    Flemisch, B.; Bastian, P.; Kempf, D.; Koch, T.; Helmig, R.

    2015-12-01

    Quality assurance and, in particular, automated testing, should be one of the key elements of modern software development. However, applying common techniques from software engineering to numerical frameworks, such as Dune, may be challenging since the requirements for a test might be very different to standard software. This talk gives an overview of our work in describing system tests for numerical software and developing test tools to ensure that qualitative and quantitative properties of PDE discretizations are preserved. The developed tools are employed in the Dune discretization module Dune-PDELab and the porous-media simulator DuMux.The newly developed module dune-testtools provides the following components: A domain specific language for feature modelling, which is naturally integrated into the workflow of numerical simulation. Tools to test whether a given PDE discretization does still yield the correct result without performance (or scalability) regressions. Integration of the above tools into a CMake based build system. Extensions to the Dune core modules to support the development of system tests.

  9. The impact of software quality characteristics on healthcare outcome: a literature review.

    PubMed

    Aghazadeh, Sakineh; Pirnejad, Habibollah; Moradkhani, Alireza; Aliev, Alvosat

    2014-01-01

    The aim of this study was to discover the effect of software quality characteristics on healthcare quality and efficiency indicators. Through a systematic literature review, we selected and analyzed 37 original research papers to investigate the impact of the software indicators (coming from the standard ISO 9126 quality characteristics and sub-characteristics) on some of healthcare important outcome indicators and finally ranked these software indicators. The results showed that the software characteristics usability, reliability and efficiency were mostly favored in the studies, indicating their importance. On the other hand, user satisfaction, quality of patient care, clinical workflow efficiency, providers' communication and information exchange, patient satisfaction and care costs were among the healthcare outcome indicators frequently evaluated in relation to the mentioned software characteristics. Regression Logistic Method was the most common assessment methodology, and Confirmatory Factor Analysis and Structural Equation Modeling were performed to test the structural model's fit. The software characteristics were considered to impact the healthcare outcome indicators through other intermediate factors (variables).

  10. Software Quality Assurance and Verification for the MPACT Library Generation Process

    SciTech Connect

    Liu, Yuxuan; Williams, Mark L.; Wiarda, Dorothea

    2017-05-01

    This report fulfills the requirements for the Consortium for the Advanced Simulation of Light-Water Reactors (CASL) milestone L2:RTM.P14.02, “SQA and Verification for MPACT Library Generation,” by documenting the current status of the software quality, verification, and acceptance testing of nuclear data libraries for MPACT. It provides a brief overview of the library generation process, from general-purpose evaluated nuclear data files (ENDF/B) to a problem-dependent cross section library for modeling of light-water reactors (LWRs). The software quality assurance (SQA) programs associated with each of the software used to generate the nuclear data libraries are discussed; specific tests within the SCALE/AMPX andmore » VERA/XSTools repositories are described. The methods and associated tests to verify the quality of the library during the generation process are described in detail. The library generation process has been automated to a degree to (1) ensure that it can be run without user intervention and (2) to ensure that the library can be reproduced. Finally, the acceptance testing process that will be performed by representatives from the Radiation Transport Methods (RTM) Focus Area prior to the production library’s release is described in detail.« less

  11. Software engineering principles applied to large healthcare information systems--a case report.

    PubMed

    Nardon, Fabiane Bizinella; de A Moura, Lincoln

    2007-01-01

    São Paulo is the largest city in Brazil and one of the largest cities in the world. In 2004, São Paulo City Department of Health decided to implement a Healthcare Information System to support managing healthcare services and provide an ambulatory health record. The resulting information system is one of the largest public healthcare information systems ever built, with more than 2 million lines of code. Although statistics shows that most software projects fail, and the risks for the São Paulo initiative were enormous, the information system was completed on-time and on-budget. In this paper, we discuss the software engineering principles adopted that allowed to accomplish that project's goals, hoping that sharing the experience of this project will help other healthcare information systems initiatives to succeed.

  12. How can GPs drive software changes to improve healthcare for Aboriginal and Torres Strait Islanders peoples?

    PubMed

    Kehoe, Helen

    2017-01-01

    Changes to the software used in general practice could improve the collection of the Aboriginal and Torres Strait Islander status of all patients, and boost access to healthcare measures specifically for Aboriginal and Torres Strait Islander peoples provided directly or indirectly by general practitioners (GPs). Despite longstanding calls for improvements to general practice software to better support Aboriginal and Torres Strait Islander health, little change has been made. The aim of this article is to promote software improvements by identifying desirable software attributes and encouraging GPs to promote their adoption. Establishing strong links between collecting Aboriginal and Torres Strait Islander status, clinical decision supports, and uptake of GP-mediated health measures specifically for Aboriginal and Torres Strait Islander peoples - and embedding these links in GP software - is a long overdue reform. In the absence of government initiatives in this area, GPs are best placed to advocate for software changes, using the model described here as a starting point for action.

  13. Quality Assurance Testing of Version 1.3 of U.S. EPA Benchmark Dose Software (Presentation)

    EPA Science Inventory

    EPA benchmark dose software (BMDS) issued to evaluate chemical dose-response data in support of Agency risk assessments, and must therefore be dependable. Quality assurance testing methods developed for BMDS were designed to assess model dependability with respect to curve-fitt...

  14. A survey of quality assurance practices in biomedical open source software projects.

    PubMed

    Koru, Günes; El Emam, Khaled; Neisa, Angelica; Umarji, Medha

    2007-05-07

    Open source (OS) software is continuously gaining recognition and use in the biomedical domain, for example, in health informatics and bioinformatics. Given the mission critical nature of applications in this domain and their potential impact on patient safety, it is important to understand to what degree and how effectively biomedical OS developers perform standard quality assurance (QA) activities such as peer reviews and testing. This would allow the users of biomedical OS software to better understand the quality risks, if any, and the developers to identify process improvement opportunities to produce higher quality software. A survey of developers working on biomedical OS projects was conducted to examine the QA activities that are performed. We took a descriptive approach to summarize the implementation of QA activities and then examined some of the factors that may be related to the implementation of such practices. Our descriptive results show that 63% (95% CI, 54-72) of projects did not include peer reviews in their development process, while 82% (95% CI, 75-89) did include testing. Approximately 74% (95% CI, 67-81) of developers did not have a background in computing, 80% (95% CI, 74-87) were paid for their contributions to the project, and 52% (95% CI, 43-60) had PhDs. A multivariate logistic regression model to predict the implementation of peer reviews was not significant (likelihood ratio test = 16.86, 9 df, P = .051) and neither was a model to predict the implementation of testing (likelihood ratio test = 3.34, 9 df, P = .95). Less attention is paid to peer review than testing. However, the former is a complementary, and necessary, QA practice rather than an alternative. Therefore, one can argue that there are quality risks, at least at this point in time, in transitioning biomedical OS software into any critical settings that may have operational, financial, or safety implications. Developers of biomedical OS applications should invest more effort

  15. Summary of Documentation for DYNA3D-ParaDyn's Software Quality Assurance Regression Test Problems

    SciTech Connect

    Zywicz, Edward

    2016-08-18

    The Software Quality Assurance (SQA) regression test suite for DYNA3D (Zywicz and Lin, 2015) and ParaDyn (DeGroot, et al., 2015) currently contains approximately 600 problems divided into 21 suites, and is a required component of ParaDyn’s SQA plan (Ferencz and Oliver, 2013). The regression suite allows developers to ensure that software modifications do not unintentionally alter the code response. The entire regression suite is run prior to permanently incorporating any software modification or addition. When code modifications alter test problem results, the specific cause must be determined and fully understood before the software changes and revised test answers can bemore » incorporated. The regression suite is executed on LLNL platforms using a Python script and an associated data file. The user specifies the DYNA3D or ParaDyn executable, number of processors to use, test problems to run, and other options to the script. The data file details how each problem and its answer extraction scripts are executed. For each problem in the regression suite there exists an input deck, an eight-processor partition file, an answer file, and various extraction scripts. These scripts assemble a temporary answer file in a specific format from the simulation results. The temporary and stored answer files are compared to a specific level of numerical precision, and when differences are detected the test problem is flagged as failed. Presently, numerical results are stored and compared to 16 digits. At this accuracy level different processor types, compilers, number of partitions, etc. impact the results to various degrees. Thus, for consistency purposes the regression suite is run with ParaDyn using 8 processors on machines with a specific processor type (currently the Intel Xeon E5530 processor). For non-parallel regression problems, i.e., the two XFEM problems, DYNA3D is used instead. When environments or platforms change, executables using the current source code and

  16. Software quality assurance documentation for the release of NUFT 2.0 for HP platforms

    SciTech Connect

    Fernandez, Michael W.; Johnson, Gary L.; Preckshot, Gary G.

    1998-08-28

    identified in section 1.1 above, to meet the applicableiequirements of 033-YMP-QP 3.2, and to establish a Version 2.0 baseline for subsequent qualifications of NUFT for additional problems or for use on additional platforms. The detailed requirements applicable to the class of problems for which this release is applicable will be defined in the NUFT 2.0 Requirements Document. The scope of this ISP is limited to NUFT. Auxiliary software such as the post-processing tool XTOOL, YMESH, -and RADPRO, which are often used in conjunction with NUFT, will be addressed separately as needed. Version 2.0 is the first quality controlled release for the NUFT software. Additional releases are anticipated. NUFT Version 2.0 is "acquired software," as defined by 033- YMP-QP 3.2. Version 1 .O was released in February 1998, but that certification is being withdrawn based upon the quality assurance surveillance findings described in LLNL-98- D-065.« less

  17. Quality assurance software inspections at NASA Ames: Metrics for feedback and modification

    NASA Technical Reports Server (NTRS)

    Wenneson, G.

    1985-01-01

    Software inspections are a set of formal technical review procedures held at selected key points during software development in order to find defects in software documents--is described in terms of history, participants, tools, procedures, statistics, and database analysis.

  18. Conceptualization and application of an approach for designing healthcare software interfaces.

    PubMed

    Kumar, Ajit; Maskara, Reena; Maskara, Sanjeev; Chiang, I-Jen

    2014-06-01

    The aim of this study is to conceptualize a novel approach, which facilitates us to design prototype interfaces for healthcare software. Concepts and techniques from various disciplines were used to conceptualize an interface design approach named MORTARS (Map Original Rhetorical To Adapted Rhetorical Situation). The concepts and techniques included in this approach are (1) rhetorical situation - a concept of philosophy provided by Bitzer (1968); (2) move analysis - an applied linguistic technique provided by Swales (1990) and Bhatia (1993); (3) interface design guidelines - a cognitive and computer science concept provided by Johnson (2010); (4) usability evaluation instrument - an interface evaluation questionnaire provided by Lund (2001); (5) user modeling via stereotyping - a cognitive and computer science concept provided by Rich (1979). A prototype interface for outpatient clinic software was designed to introduce the underlying concepts of MORTARS. The prototype interface was evaluated by thirty-two medical informaticians. The medical informaticians found the designed prototype interface to be useful (73.3%), easy to use (71.9%), easy to learn (93.1%), and satisfactory (53.2%). MORTARS approach was found to be effective in designing the prototype user interface for the outpatient clinic software. This approach might be further used to design interfaces for various software pertaining to healthcare and other domains. Copyright © 2014 Elsevier Inc. All rights reserved.

  19. Software Assurance in Acquisition: Mitigating Risks to the Enterprise. A Reference Guide for Security-Enhanced Software Acquisition and Outsourcing

    DTIC Science & Technology

    2009-02-01

    is the first process in the risk management methodology . Risk assessment (synonymous with risk analysis) is the process of identifying the risks to...manage the assurance case’s development and acceptance into operational service. All elements of any project management methodology that an acquirer...Budget OS Operating System OWASP Open Web Application Security Project PDA Parental Drug Association PITAC President’s Information Technology Advisory

  20. A Health Surveillance Software Framework to deliver information on preventive healthcare strategies.

    PubMed

    Macedo, Alessandra Alaniz; Pollettini, Juliana Tarossi; Baranauskas, José Augusto; Chaves, Julia Carmona Almeida

    2016-08-01

    A software framework can reduce costs related to the development of an application because it allows developers to reuse both design and code. Recently, companies and research groups have announced that they have been employing health software frameworks. This paper presents the design, proof-of-concept implementations and experimentation of the Health Surveillance Software Framework (HSSF). The HSSF is a framework that tackles the demand for the recommendation of surveillance information aiming at supporting preventive healthcare strategies. Examples of such strategies are the automatic recommendation of surveillance levels to patients in need of healthcare and the automatic recommendation of scientific literature that elucidates epigenetic problems related to patients. HSSF was created from two systems we developed in our previous work on health surveillance systems: the Automatic-SL and CISS systems. The Automatic-SL system aims to assist healthcare professionals in making decisions and in identifying children with developmental problems. The CISS service associates genetic and epigenetic risk factors related to chronic diseases with patient's clinical records. Towards evaluating the HSSF framework, two new systems, CISS+ and CISS-SW, were created by means of abstractions and instantiations of the framework (design and code). We show that HSSF supported the development of the two new systems given that they both recommend scientific papers using medical records as queries even though they exploit different computational technologies. In an experiment using simulated patients' medical records, we show that CISS, CISS+, and CISS-SW systems recommended more closely related and somewhat related documents than Google, Google Scholar and PubMed. Considering recall and precision measures, CISS+ surpasses CISS-SW in terms of precision. Copyright © 2016 Elsevier Inc. All rights reserved.

  1. Revalidation and quality assurance: the application of the MUSIQ framework in independent verification visits to healthcare organisations

    PubMed Central

    Griffin, Ann; Viney, Rowena; Welland, Trevor; Gafson, Irene

    2017-01-01

    Objectives We present a national evaluation of the impact of independent verification visits (IVVs) performed by National Health Service (NHS) England as part of quality assuring medical revalidation. Organisational visits are central to NHS quality assurance. They are costly, yet little empirical research evidence exists concerning their impact, and what does exist is conflicting. Setting The focus was on healthcare providers in the NHS (in secondary care) and private sector across England, who were designated bodies (DBs). DBs are healthcare organisations that have a statutory responsibility, via the lead clinician, the responsible officer (RO), to implement medical revalidation. Participants All ROs who had undergone an IVV in England in 2014 and 2015 were invited to participate. 46 ROs were interviewed. Ethnographic data were gathered at 18 observations of the IVVs and 20 IVV post visit reports underwent documentary analysis. Primary and secondary outcome measures Primary outcomes were the findings pertaining to the effectiveness of the IVV system in supporting the revalidation processes at the DBs. Secondary outcomes were methodological, relating to the Model for Understanding Success in Quality (MUSIQ) and how its application to the IVV reveals the relevance of contextual factors described in the model. Results The impact of the IVVs varied by DB according to three major themes: the personal context of the RO; the organisational context of the DB; and the visit and its impact. ROs were largely satisfied with visits which raised the status of appraisal within their organisations. Inadequate or untimely feedback was associated with dissatisfaction. Conclusions Influencing teams whose prime responsibility is establishing processes and evaluating progress was crucial for internal quality improvement. Visits acted as a nudge, generating internal quality review, which was reinforced by visit teams with relevant expertise. Diverse team membership, knowledge transfer

  2. Revalidation and quality assurance: the application of the MUSIQ framework in independent verification visits to healthcare organisations.

    PubMed

    Griffin, Ann; McKeown, Alex; Viney, Rowena; Rich, Antonia; Welland, Trevor; Gafson, Irene; Woolf, Katherine

    2017-02-14

    We present a national evaluation of the impact of independent verification visits (IVVs) performed by National Health Service (NHS) England as part of quality assuring medical revalidation. Organisational visits are central to NHS quality assurance. They are costly, yet little empirical research evidence exists concerning their impact, and what does exist is conflicting. The focus was on healthcare providers in the NHS (in secondary care) and private sector across England, who were designated bodies (DBs). DBs are healthcare organisations that have a statutory responsibility, via the lead clinician, the responsible officer (RO), to implement medical revalidation. All ROs who had undergone an IVV in England in 2014 and 2015 were invited to participate. 46 ROs were interviewed. Ethnographic data were gathered at 18 observations of the IVVs and 20 IVV post visit reports underwent documentary analysis. Primary outcomes were the findings pertaining to the effectiveness of the IVV system in supporting the revalidation processes at the DBs. Secondary outcomes were methodological, relating to the Model for Understanding Success in Quality (MUSIQ) and how its application to the IVV reveals the relevance of contextual factors described in the model. The impact of the IVVs varied by DB according to three major themes: the personal context of the RO; the organisational context of the DB; and the visit and its impact. ROs were largely satisfied with visits which raised the status of appraisal within their organisations. Inadequate or untimely feedback was associated with dissatisfaction. Influencing teams whose prime responsibility is establishing processes and evaluating progress was crucial for internal quality improvement. Visits acted as a nudge, generating internal quality review, which was reinforced by visit teams with relevant expertise. Diverse team membership, knowledge transfer and timely feedback made visits more impactful. Published by the BMJ Publishing Group

  3. Software for primary healthcare in a developing country. Background and problem statement.

    PubMed

    Blignaut, P J

    1999-01-01

    Nurses in primary healthcare (PHC) clinics carry a heavy administrative burden, much of which can be computerized. Advantages and disadvantages of computerization and issues related to patient records and other requirements of computerized systems are well documented. However, not much attention has been given to users' needs in PHC environments in developing countries. Users in township areas have very specific needs because of a lack of previous exposure to computers and a reluctance to change working habits. Some general software requirements that system developers should consider are discussed.

  4. Specification Improvement Through Analysis of Proof Structure (SITAPS): High Assurance Software Development

    DTIC Science & Technology

    2016-02-01

    Distribution Unlimited 5 Hotel room locks and card keys use a simple protocol to manage the transition of rooms from one guest to the next. The lock...STATEMENT. FOR THE DIRECTOR: / S / / S / STEVEN DRAGER MARK LINDERMAN Work Unit Manager Technical...16 iii Table of Tables Table 1 Initial assurance case metrics for the hotel example

  5. Value of Investment as a Key Driver for Prioritization and Implementation of Healthcare Software.

    PubMed

    Bata, Seth A; Richardson, Terry

    2018-01-01

    Health systems across the nation are recovering from massive financial and resource investments in electronic health record applications. In the midst of these recovery efforts, implementations of new care models, including accountable care organizations and population health initiatives, are underway. The shift from fee-for-service to fee-for-outcomes and fee-for-value payment models calls for care providers to work in new ways. It also changes how physicians are compensated and reimbursed. These changes necessitate that healthcare systems further invest in information technology solutions. Selecting which information technology (IT) projects are of most value is vital, especially in light of recent expenditures. Return-on-investment analysis is a powerful tool used in various industries to select the most appropriate IT investments. It has proven vital in selecting, justifying, and implementing software projects. Other financial metrics, such as net present value, economic value added, and total economic impact, also quantify the success of expenditures on information systems. This paper extends the concept of quantifying project value to include clinical outcomes and nonfinancial value as investment returns, applying a systematic approach to healthcare software projects. We term this inclusive approach Value of Investment. It offers a necessary extension for application in clinical settings where a strictly financial view may fall short in providing a complete picture of important benefits. This paper outlines the Value of Investment process and its attributes, and uses illustrative examples to explore the efficacy of this methodology within a midsized health system.

  6. Value of Investment as a Key Driver for Prioritization and Implementation of Healthcare Software

    PubMed Central

    Bata, Seth A.; Richardson, Terry

    2018-01-01

    Health systems across the nation are recovering from massive financial and resource investments in electronic health record applications. In the midst of these recovery efforts, implementations of new care models, including accountable care organizations and population health initiatives, are underway. The shift from fee-for-service to fee-for-outcomes and fee-for-value payment models calls for care providers to work in new ways. It also changes how physicians are compensated and reimbursed. These changes necessitate that healthcare systems further invest in information technology solutions. Selecting which information technology (IT) projects are of most value is vital, especially in light of recent expenditures. Return-on-investment analysis is a powerful tool used in various industries to select the most appropriate IT investments. It has proven vital in selecting, justifying, and implementing software projects. Other financial metrics, such as net present value, economic value added, and total economic impact, also quantify the success of expenditures on information systems. This paper extends the concept of quantifying project value to include clinical outcomes and nonfinancial value as investment returns, applying a systematic approach to healthcare software projects. We term this inclusive approach Value of Investment. It offers a necessary extension for application in clinical settings where a strictly financial view may fall short in providing a complete picture of important benefits. This paper outlines the Value of Investment process and its attributes, and uses illustrative examples to explore the efficacy of this methodology within a midsized health system. PMID:29618963

  7. Healthcare

    DTIC Science & Technology

    2001-01-01

    HEALTHCARE ABSTRACT Healthcare is the largest industry in the United States, accounting for approximately $1.4 trillion in sales of goods...works in the healthcare industry. In addition to its economic importance, healthcare remains a critical element of national security. The state of...U.S. healthcare industry sets the quality standard for the world, nonetheless there are significant concerns about rising medical costs, the number of

  8. SU-G-BRB-02: An Open-Source Software Analysis Library for Linear Accelerator Quality Assurance

    SciTech Connect

    Kerns, J; Yaldo, D

    2016-06-15

    Purpose: Routine linac quality assurance (QA) tests have become complex enough to require automation of most test analyses. A new data analysis software library was built that allows physicists to automate routine linear accelerator quality assurance tests. The package is open source, code tested, and benchmarked. Methods: Images and data were generated on a TrueBeam linac for the following routine QA tests: VMAT, starshot, CBCT, machine logs, Winston Lutz, and picket fence. The analysis library was built using the general programming language Python. Each test was analyzed with the library algorithms and compared to manual measurements taken at the timemore » of acquisition. Results: VMAT QA results agreed within 0.1% between the library and manual measurements. Machine logs (dynalogs & trajectory logs) were successfully parsed; mechanical axis positions were verified for accuracy and MLC fluence agreed well with EPID measurements. CBCT QA measurements were within 10 HU and 0.2mm where applicable. Winston Lutz isocenter size measurements were within 0.2mm of TrueBeam’s Machine Performance Check. Starshot analysis was within 0.2mm of the Winston Lutz results for the same conditions. Picket fence images with and without a known error showed that the library was capable of detecting MLC offsets within 0.02mm. Conclusion: A new routine QA software library has been benchmarked and is available for use by the community. The library is open-source and extensible for use in larger systems.« less

  9. Healthcare

    MedlinePlus

    ... communication between homecare workers and their clients. Related Industries Dentistry Home Healthcare Hospitals Laboratories Nursing Homes and ... communication between homecare workers and their clients. Related Industries Dentistry Home Healthcare Hospitals Laboratories Nursing Homes and ...

  10. NRC (Nuclear Regulatory Commission) perspective of software QA (quality assurance) in the nuclear history

    SciTech Connect

    Weiss, S.H.

    1988-01-01

    Computer technology has been a part of the nuclear industry since its inception. However, it is only recently that computers have been integrated into reactor operations. During the early history of commercial nuclear power in the United States, the US Nuclear Regulatory Commission (NRC) discouraged the use of digital computers for real-time control and monitoring of nuclear power plant operation. At the time, this position was justified since software engineering was in its infancy, and horror stories on computer crashes were plentiful. Since the advent of microprocessors and inexpensive computer memories, significant advances have been made in fault-tolerant computer architecturemore » that have resulted in highly reliable, durable computer systems. The NRC's requirement for safety parameter display system (SPDS) stemmed form the results of studies and investigations conducted on the Three Mile Island Unit 2 (TMI-2) accident. An NRC contractor has prepared a handbook of software QA techniques applicable to the nuclear industry, published as NUREG/CR-4640 in August 1987. Currently, the NRC is considering development of an inspection program covering software QA. Future efforts may address verification and validation as applied to expert systems and artificial intelligence programs.« less

  11. Independent Verification and Validation (IV and V) - Adding Mission Assurance to NASA Flight Software

    NASA Technical Reports Server (NTRS)

    Savarino, Shirley; Krasner, Sanford; Huy, Frank

    2011-01-01

    The NASA Independent Verification and Validation (IV&V) Facility objective is to identify potential defects in flight software using independent analysis techniques. This paper describes the tailored IV&V techniques that have been developed in support of critical interactions on the Mars Science Laboratory (MSL) project, scheduled to launch in November, 2011. The IV&V techniques for interface analysis use independently developed sequence diagrams of critical scenarios. The results from these analyses have had a positive impact on the requirements flow down, consistency amongst MSL requirements and identification of missing requirements. The results of these analyses and the positive impact to the MSL project are provided.

  12. Healthcare

    ERIC Educational Resources Information Center

    Carnevale, Anthony P.; Smith, Nicole; Gulish, Artem; Beach, Bennett H.

    2012-01-01

    This report, provides detailed analyses and projections of occupations in healthcare fields, and wages earned. In addition, the important skills and work values associated with workers in those fields of healthcare are discussed. Finally, the authors analyze the implications of research findings for the racial, ethnic, and class diversity of the…

  13. Adopting best practices: "Agility" moves from software development to healthcare project management.

    PubMed

    Kitzmiller, Rebecca; Hunt, Eleanor; Sproat, Sara Breckenridge

    2006-01-01

    It is time for a change in mindset in how nurses operationalize system implementations and manage projects. Computers and systems have evolved over time from unwieldy mysterious machines of the past to ubiquitous computer use in every aspect of daily lives and work sites. Yet, disconcertingly, the process used to implement these systems has not evolved. Technology implementation does not need to be a struggle. It is time to adapt traditional plan-driven implementation methods to incorporate agile techniques. Agility is a concept borrowed from software development and is presented here because it encourages flexibility, adaptation, and continuous learning as part of the implementation process. Agility values communication and harnesses change to an advantage, which facilitates the natural evolution of an adaptable implementation process. Specific examples of agility in an implementation are described, and plan-driven implementation stages are adapted to incorporate relevant agile techniques. This comparison demonstrates how an agile approach enhances traditional implementation techniques to meet the demands of today's complex healthcare environments.

  14. Impact assessment on patients' satisfaction and healthcare professionals' commitment of software supporting Directly Observed Treatment, Short-course: A protocol proposal.

    PubMed

    Rijo, Rui Pedro Charters Lopes; Crepaldi, Nathalia Yukie; Bergamini, Fernanda; Rodrigues, Lídia Maria Lourençon; de Lima, Inácia Bezerra; da Silva Castro Perdoná, Gleici; Alves, Domingos

    2017-06-01

    Doctors, nurses, and other healthcare professionals use software that affects the patients. Directly Observed Treatment, Short-course is the name given to the tuberculosis control strategy recommended by the World Health Organization. The main goal of this work is to propose a protocol for evaluating the impact of healthcare software supporting Directly Observed Treatment, Short-course on patients, healthcare professionals, and services. The proposed protocol consists of a set of instruments and steps. The instruments are reliable and validated existing questionnaires to be applied before and after using the software tool. The literature points out the need for standards on the software assessment. This is particularly critical when software affects patients directly. The present protocol is a universal tool to assess the impact of software used to support the fight against the tragedy of tuberculosis where a rigorous evaluation of IT in healthcare is highly recommended and of great importance.

  15. Processing tracking in jMRUI software for magnetic resonance spectra quantitation reproducibility assurance.

    PubMed

    Jabłoński, Michał; Starčuková, Jana; Starčuk, Zenon

    2017-01-23

    Proton magnetic resonance spectroscopy is a non-invasive measurement technique which provides information about concentrations of up to 20 metabolites participating in intracellular biochemical processes. In order to obtain any metabolic information from measured spectra a processing should be done in specialized software, like jMRUI. The processing is interactive and complex and often requires many trials before obtaining a correct result. This paper proposes a jMRUI enhancement for efficient and unambiguous history tracking and file identification. A database storing all processing steps, parameters and files used in processing was developed for jMRUI. The solution was developed in Java, authors used a SQL database for robust storage of parameters and SHA-256 hash code for unambiguous file identification. The developed system was integrated directly in jMRUI and it will be publically available. A graphical user interface was implemented in order to make the user experience more comfortable. The database operation is invisible from the point of view of the common user, all tracking operations are performed in the background. The implemented jMRUI database is a tool that can significantly help the user to track the processing history performed on data in jMRUI. The created tool is oriented to be user-friendly, robust and easy to use. The database GUI allows the user to browse the whole processing history of a selected file and learn e.g. what processing lead to the results, where the original data are stored, to obtain the list of all processing actions performed on spectra.

  16. A Java-based electronic healthcare record software for beta-thalassaemia.

    PubMed

    Deftereos, S; Lambrinoudakis, C; Andriopoulos, P; Farmakis, D; Aessopos, A

    2001-01-01

    Beta-thalassaemia is a hereditary disease, the prevalence of which is high in persons of Mediterranean, African, and Southeast Asian ancestry. In Greece it constitutes an important public health problem. Beta-thalassaemia necessitates continuous and complicated health care procedures such as daily chelation; biweekly transfusions; and periodic cardiology, endocrinology, and hepatology evaluations. Typically, different care items are offered in different, often-distant, health care units, which leads to increased patient mobility. This is especially true in rural areas. Medical records of patients suffering from beta-thalassaemia are inevitably complex and grow in size very fast. They are currently paper-based, scattered over all units involved in the care process. This hinders communication of information between health care professionals and makes processing of the medical records difficult, thus impeding medical research. Our objective is to provide an electronic means for recording, communicating, and processing all data produced in the context of the care process of patients suffering from beta-thalassaemia. We have developed - and we present in this paper - Java-based Electronic Healthcare Record (EHCR) software, called JAnaemia. JAnaemia is a general-purpose EHCR application, which can be customized for use in all medical specialties. Customization for beta-thalassaemia has been performed in collaboration with 4 Greek hospitals. To be capable of coping with patient record diversity, JAnaemia has been based on the EHCR architecture proposed in the ENV 13606:1999 standard, published by the CEN/TC251 committee. Compliance with the CEN architecture also ensures that several additional requirements are fulfilled in relation to clinical comprehensiveness; to record sharing and communication; and to ethical, medico-legal, and computational issues. Special care has been taken to provide a user-friendly, form-based interface for data entry and processing. The

  17. Advanced Software Quality Assurance

    DTIC Science & Technology

    1977-03-01

    sciences has been urged to apply. Basically, it prevents apples being assigned to oranges , miles being assigned to feet, dollars being added to pounds...c- i* H > C K . 0 O -J u •• * ’ .* o. .J i ; ci U .J A i. * • ■ ii > U .J f • » . V r. u, ^ o. t...L-> b v t b i’- </ v i/’ i’ y b1 J a «f r • *> ’’ «< ri r rj r.» fi r- r-. f1 ’ »^ c o o o i b (/> b bi b» f b» b v ’ K J i; >f K

  18. Assuring Software Reliability

    DTIC Science & Technology

    2014-08-01

    based analysis for complex systems, consider the re- lease of methyl isocyanate (MIC) from a Union Carbide chemical plant in Bhopal , India in 1984. A...the root cause as an opera- tor error. Charles Perrow’s2 analysis of the Bhopal incident concluded that there was no root cause, and that given the

  19. SU-E-J-199: A Software Tool for Quality Assurance of Online Replanning with MR-Linac

    SciTech Connect

    Chen, G; Ahunbay, E; Li, X

    2015-06-15

    Purpose: To develop a quality assurance software tool, ArtQA, capable of automatically checking radiation treatment plan parameters, verifying plan data transfer from treatment planning system (TPS) to record and verify (R&V) system, performing a secondary MU calculation considering the effect of magnetic field from MR-Linac, and verifying the delivery and plan consistency, for online replanning. Methods: ArtQA was developed by creating interfaces to TPS (e.g., Monaco, Elekta), R&V system (Mosaiq, Elekta), and secondary MU calculation system. The tool obtains plan parameters from the TPS via direct file reading, and retrieves plan data both transferred from TPS and recorded during themore » actual delivery in the R&V system database via open database connectivity and structured query language. By comparing beam/plan datasets in different systems, ArtQA detects and outputs discrepancies between TPS, R&V system and secondary MU calculation system, and delivery. To consider the effect of 1.5T transverse magnetic field from MR-Linac in the secondary MU calculation, a method based on modified Clarkson integration algorithm was developed and tested for a series of clinical situations. Results: ArtQA is capable of automatically checking plan integrity and logic consistency, detecting plan data transfer errors, performing secondary MU calculations with or without a transverse magnetic field, and verifying treatment delivery. The tool is efficient and effective for pre- and post-treatment QA checks of all available treatment parameters that may be impractical with the commonly-used visual inspection. Conclusion: The software tool ArtQA can be used for quick and automatic pre- and post-treatment QA check, eliminating human error associated with visual inspection. While this tool is developed for online replanning to be used on MR-Linac, where the QA needs to be performed rapidly as the patient is lying on the table waiting for the treatment, ArtQA can be used as a general

  20. Architecture Design of Healthcare Software-as-a-Service Platform for Cloud-Based Clinical Decision Support Service.

    PubMed

    Oh, Sungyoung; Cha, Jieun; Ji, Myungkyu; Kang, Hyekyung; Kim, Seok; Heo, Eunyoung; Han, Jong Soo; Kang, Hyunggoo; Chae, Hoseok; Hwang, Hee; Yoo, Sooyoung

    2015-04-01

    To design a cloud computing-based Healthcare Software-as-a-Service (SaaS) Platform (HSP) for delivering healthcare information services with low cost, high clinical value, and high usability. We analyzed the architecture requirements of an HSP, including the interface, business services, cloud SaaS, quality attributes, privacy and security, and multi-lingual capacity. For cloud-based SaaS services, we focused on Clinical Decision Service (CDS) content services, basic functional services, and mobile services. Microsoft's Azure cloud computing for Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) was used. The functional and software views of an HSP were designed in a layered architecture. External systems can be interfaced with the HSP using SOAP and REST/JSON. The multi-tenancy model of the HSP was designed as a shared database, with a separate schema for each tenant through a single application, although healthcare data can be physically located on a cloud or in a hospital, depending on regulations. The CDS services were categorized into rule-based services for medications, alert registration services, and knowledge services. We expect that cloud-based HSPs will allow small and mid-sized hospitals, in addition to large-sized hospitals, to adopt information infrastructures and health information technology with low system operation and maintenance costs.

  1. Architecture Design of Healthcare Software-as-a-Service Platform for Cloud-Based Clinical Decision Support Service

    PubMed Central

    Oh, Sungyoung; Cha, Jieun; Ji, Myungkyu; Kang, Hyekyung; Kim, Seok; Heo, Eunyoung; Han, Jong Soo; Kang, Hyunggoo; Chae, Hoseok; Hwang, Hee

    2015-01-01

    Objectives To design a cloud computing-based Healthcare Software-as-a-Service (SaaS) Platform (HSP) for delivering healthcare information services with low cost, high clinical value, and high usability. Methods We analyzed the architecture requirements of an HSP, including the interface, business services, cloud SaaS, quality attributes, privacy and security, and multi-lingual capacity. For cloud-based SaaS services, we focused on Clinical Decision Service (CDS) content services, basic functional services, and mobile services. Microsoft's Azure cloud computing for Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) was used. Results The functional and software views of an HSP were designed in a layered architecture. External systems can be interfaced with the HSP using SOAP and REST/JSON. The multi-tenancy model of the HSP was designed as a shared database, with a separate schema for each tenant through a single application, although healthcare data can be physically located on a cloud or in a hospital, depending on regulations. The CDS services were categorized into rule-based services for medications, alert registration services, and knowledge services. Conclusions We expect that cloud-based HSPs will allow small and mid-sized hospitals, in addition to large-sized hospitals, to adopt information infrastructures and health information technology with low system operation and maintenance costs. PMID:25995962

  2. Software Quality Assurance Plan for GoldSim Models Supporting the Area 3 and Area 5 Radioactive Waste Management Sites Performance Assessment Program

    SciTech Connect

    Gregory J. Shott, Vefa Yucel

    2007-01-03

    This Software Quality Assurance Plan (SQAP) applies to the development and maintenance of GoldSim models supporting the Area 3 and Area 5 Radioactive Waste Management Sites (RWMSs) performance assessments (PAs) and composite analyses (CAs). Two PA models have been approved by the U.S. Department of Energy (DOE), National Nuclear Security Administration Nevada Site Office (NNSA/NSO) as of November 2006 for the PA maintenance work undertaken by National Security Technologies, LLC (NSTec). NNSA/NSO asked NSTec to assume the custodianship of the models for future development and maintenance. The models were initially developed by Neptune and Company (N&C).

  3. ECLIPSE, an Emerging Standardized Modular, Secure and Affordable Software Toolset in Support of Product Assurance, Quality Assurance and Project Management for the Entire European Space Industry (from Innovative SMEs to Primes and Institutions)

    NASA Astrophysics Data System (ADS)

    Bennetti, Andrea; Ansari, Salim; Dewhirst, Tori; Catanese, Giuseppe

    2010-08-01

    The development of satellites and ground systems (and the technologies that support them) is complex and demands a great deal of rigor in the management of both the information it relies upon and the information it generates via the performance of well established processes. To this extent for the past fifteen years Sapienza Consulting has been supporting the European Space Agency (ESA) in the management of this information and provided ESA with ECSS (European Cooperation for Space Standardization) Standards based Project Management (PM), Product Assurance (PA) and Quality Assurance (QA) software applications. In 2009 Sapienza recognised the need to modernize, standardizing and integrate its core ECSS-based software tools into a single yet modularised suite of applications named ECLIPSE aimed at: • Fulfilling a wider range of historical and emerging requirements, • Providing a better experience for users, • Increasing the value of the information it collects and manages • Lowering the cost of ownership and operation • Increasing collaboration within and between space sector organizations • Aiding in the performance of several PM, PA, QA, and configuration management tasks in adherence to ECSS standards. In this paper, Sapienza will first present the toolset, and a rationale for its development, describing and justifying its architecture, and basic modules composition. Having defined the toolset architecture, this paper will address the current status of the individual applications. A compliance assessment will be presented for each module in the toolset with respect to the ECSS standard it addresses. Lastly experience from early industry and Institutional users will be presented.

  4. Software.

    ERIC Educational Resources Information Center

    Journal of Chemical Education, 1989

    1989-01-01

    Presented are reviews of two computer software packages for Apple II computers; "Organic Spectroscopy," and "Videodisc Display Program" for use with "The Periodic Table Videodisc." A sample spectrograph from "Organic Spectroscopy" is included. (CW)

  5. Software service history report

    DOT National Transportation Integrated Search

    2002-01-01

    The safe and reliable operation of software within civil aviation systems and equipment has historically been assured through the application of rigorous design assurance applied during the software development process. Increasingly, manufacturers ar...

  6. Development and validation of a novel large field of view phantom and a software module for the quality assurance of geometric distortion in magnetic resonance imaging.

    PubMed

    Torfeh, Tarraf; Hammoud, Rabih; McGarry, Maeve; Al-Hammadi, Noora; Perkins, Gregory

    2015-09-01

    To develop and validate a large field of view phantom and quality assurance software tool for the assessment and characterization of geometric distortion in MRI scanners commissioned for radiation therapy planning. A purpose built phantom was developed consisting of 357 rods (6mm in diameter) of polymethyl-methacrylat separated by 20mm intervals, providing a three dimensional array of control points at known spatial locations covering a large field of view up to a diameter of 420mm. An in-house software module was developed to allow automatic geometric distortion assessment. This software module was validated against a virtual dataset of the phantom that reproduced the exact geometry of the physical phantom, but with known translational and rotational displacements and warping. For validation experiments, clinical MRI sequences were acquired with and without the application of a commercial 3D distortion correction algorithm (Gradwarp™). The software module was used to characterize and assess system-related geometric distortion in the sequences relative to a benchmark CT dataset, and the efficacy of the vendor geometric distortion correction algorithms (GDC) was also assessed. Results issued from the validation of the software against virtual images demonstrate the algorithm's ability to accurately calculate geometric distortion with sub-pixel precision by the extraction of rods and quantization of displacements. Geometric distortion was assessed for the typical sequences used in radiotherapy applications and over a clinically relevant 420mm field of view (FOV). As expected and towards the edges of the field of view (FOV), distortion increased with increasing FOV. For all assessed sequences, the vendor GDC was able to reduce the mean distortion to below 1mm over a field of view of 5, 10, 15 and 20cm radius respectively. Results issued from the application of the developed phantoms and algorithms demonstrate a high level of precision. The results indicate that this

  7. Impact of electronic healthcare-associated infection surveillance software on infection prevention resources: a systematic review of the literature.

    PubMed

    Russo, P L; Shaban, R Z; Macbeth, D; Carter, A; Mitchell, B G

    2018-05-01

    Surveillance of healthcare-associated infections is fundamental for infection prevention. The methods and practices for surveillance have evolved as technology becomes more advanced. The availability of electronic surveillance software (ESS) has increased, and yet adoption of ESS is slow. It is argued that ESS delivers savings through automation, particularly in terms of human resourcing and infection prevention (IP) staff time. To describe the findings of a systematic review on the impact of ESS on IP resources. A systematic search was conducted of electronic databases Medline and the Cumulative Index to Nursing and Allied Health Literature published between January 1 st , 2006 and December 31 st , 2016 with analysis using the Newcastle-Ottawa Scale. In all, 2832 articles were reviewed, of which 16 studies met the inclusion criteria. IP resources were identified as time undertaken on surveillance. A reduction in IP staff time to undertake surveillance was demonstrated in 13 studies. The reduction proportion ranged from 12.5% to 98.4% (mean: 73.9%). The remaining three did not allow for any estimation of the effect in terms of IP staff time. None of the studies demonstrated an increase in IP staff time. The results of this review demonstrate that adopting ESS yields considerable dividends in IP staff time relating to data collection and case ascertainment while maintaining high levels of sensitivity and specificity. This has the potential to enable reinvestment into other components of IP to maximize efficient use of scarce IP resources. Copyright © 2017 The Healthcare Infection Society. Published by Elsevier Ltd. All rights reserved.

  8. First experiences with the implementation of the European standard EN 62304 on medical device software for the quality assurance of a radiotherapy unit

    PubMed Central

    2014-01-01

    Background According to the latest amendment of the Medical Device Directive standalone software qualifies as a medical device when intended by the manufacturer to be used for medical purposes. In this context, the EN 62304 standard is applicable which defines the life-cycle requirements for the development and maintenance of medical device software. A pilot project was launched to acquire skills in implementing this standard in a hospital-based environment (in-house manufacture). Methods The EN 62304 standard outlines minimum requirements for each stage of the software life-cycle, defines the activities and tasks to be performed and scales documentation and testing according to its criticality. The required processes were established for the pre-existent decision-support software FlashDumpComparator (FDC) used during the quality assurance of treatment-relevant beam parameters. As the EN 62304 standard implicates compliance with the EN ISO 14971 standard on the application of risk management to medical devices, a risk analysis was carried out to identify potential hazards and reduce the associated risks to acceptable levels. Results The EN 62304 standard is difficult to implement without proper tools, thus open-source software was selected and integrated into a dedicated development platform. The control measures yielded by the risk analysis were independently implemented and verified, and a script-based test automation was retrofitted to reduce the associated test effort. After all documents facilitating the traceability of the specified requirements to the corresponding tests and of the control measures to the proof of execution were generated, the FDC was released as an accessory to the HIT facility. Conclusions The implementation of the EN 62304 standard was time-consuming, and a learning curve had to be overcome during the first iterations of the associated processes, but many process descriptions and all software tools can be re-utilized in follow-up projects

  9. First experiences with the implementation of the European standard EN 62304 on medical device software for the quality assurance of a radiotherapy unit.

    PubMed

    Höss, Angelika; Lampe, Christian; Panse, Ralf; Ackermann, Benjamin; Naumann, Jakob; Jäkel, Oliver

    2014-03-21

    According to the latest amendment of the Medical Device Directive standalone software qualifies as a medical device when intended by the manufacturer to be used for medical purposes. In this context, the EN 62304 standard is applicable which defines the life-cycle requirements for the development and maintenance of medical device software. A pilot project was launched to acquire skills in implementing this standard in a hospital-based environment (in-house manufacture). The EN 62304 standard outlines minimum requirements for each stage of the software life-cycle, defines the activities and tasks to be performed and scales documentation and testing according to its criticality. The required processes were established for the pre-existent decision-support software FlashDumpComparator (FDC) used during the quality assurance of treatment-relevant beam parameters. As the EN 62304 standard implicates compliance with the EN ISO 14971 standard on the application of risk management to medical devices, a risk analysis was carried out to identify potential hazards and reduce the associated risks to acceptable levels. The EN 62304 standard is difficult to implement without proper tools, thus open-source software was selected and integrated into a dedicated development platform. The control measures yielded by the risk analysis were independently implemented and verified, and a script-based test automation was retrofitted to reduce the associated test effort. After all documents facilitating the traceability of the specified requirements to the corresponding tests and of the control measures to the proof of execution were generated, the FDC was released as an accessory to the HIT facility. The implementation of the EN 62304 standard was time-consuming, and a learning curve had to be overcome during the first iterations of the associated processes, but many process descriptions and all software tools can be re-utilized in follow-up projects. It has been demonstrated that a

  10. Technology Infusion of CodeSonar into the Space Network Ground Segment (RII07): Software Assurance Symposium Technical Summary

    NASA Technical Reports Server (NTRS)

    Benson, Markland J.

    2008-01-01

    Presents a source code analysis tool (CodeSonar) for use in the Space Network Ground Segment. The Space Network requires 99.9% proficiency and 97.0% availability of systems. Software has historically accounted for an annual average of 28% of the Space Network loss of availability and proficiency. CSCI A and CSCI B account for 42% of the previous eight months of software data loss. The technology infusion of CodeSonar into the Space Network Ground segment is meant to aid in determining the impact of the technology on the project both in the expenditure of effort and the technical results of the technology. Running a CodeSonar analysis and performing a preliminary review of the results averaged 3.5 minutes per finding (approximately 20 hours total). An additional 40 hours is estimated to analyze the 37 findings deemed too complex for the initial review. Using CodeSonar's tools to suppress known non-problems, delta tool runs will not repeat findings that have been marked as non-problems, further reducing the time needed for review. The 'non-interesting' finding rate of 70% is a large number, but filtering, search, and detailed contextual features of CodeSonar reduce the time per finding. Integration of the tool into the build process may also provide further savings by preventing developers from having to configure and operate the tool separately. These preliminary results show the tool to be easy to use and incorporate into the engineering process. These findings also provide significant potential improvements in proficiency and availability on the part of the software. As time-to-fix data become available a better cost trade can be made on person hours saved versus tool cost. Selective factors may be necessary to determine where best to apply CodeSonar to balance cost and benefits.

  11. Software Configuration Management Guidebook

    NASA Technical Reports Server (NTRS)

    1995-01-01

    The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes which are used in software development. The Software Assurance Guidebook, SMAP-GB-A201, issued in September, 1989, provides an overall picture of the concepts and practices of NASA in software assurance. Lower level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the Software Configuration Management Guidebook which describes software configuration management in a way that is compatible with practices in industry and at NASA Centers. Software configuration management is a key software development process, and is essential for doing software assurance.

  12. Technical Note: Development and performance of a software tool for quality assurance of online replanning with a conventional Linac or MR-Linac

    SciTech Connect

    Chen, Guang-Pei, E-mail: gpchen@mcw.edu; Ahunbay, Ergun; Li, X. Allen

    2016-04-15

    Purpose: To develop an integrated quality assurance (QA) software tool for online replanning capable of efficiently and automatically checking radiation treatment (RT) planning parameters and gross plan quality, verifying treatment plan data transfer from treatment planning system (TPS) to record and verify (R&V) system, performing a secondary monitor unit (MU) calculation with or without a presence of a magnetic field from MR-Linac, and validating the delivery record consistency with the plan. Methods: The software tool, named ArtQA, was developed to obtain and compare plan and treatment parameters from both the TPS and the R&V system database. The TPS data aremore » accessed via direct file reading and the R&V data are retrieved via open database connectivity and structured query language. Plan quality is evaluated with both the logical consistency of planning parameters and the achieved dose–volume histograms. Beams in between the TPS and R&V system are matched based on geometry configurations. To consider the effect of a 1.5 T transverse magnetic field from MR-Linac in the secondary MU calculation, a method based on modified Clarkson integration algorithm was developed and tested for a series of clinical situations. Results: ArtQA has been used in their clinic and can quickly detect inconsistencies and deviations in the entire RT planning process. With the use of the ArtQA tool, the efficiency for plan check including plan quality, data transfer, and delivery check can be improved by at least 60%. The newly developed independent MU calculation tool for MR-Linac reduces the difference between the plan and calculated MUs by 10%. Conclusions: The software tool ArtQA can be used to perform a comprehensive QA check from planning to delivery with conventional Linac or MR-Linac and is an essential tool for online replanning where the QA check needs to be performed rapidly.« less

  13. Technical Note: Development and performance of a software tool for quality assurance of online replanning with a conventional Linac or MR-Linac.

    PubMed

    Chen, Guang-Pei; Ahunbay, Ergun; Li, X Allen

    2016-04-01

    To develop an integrated quality assurance (QA) software tool for online replanning capable of efficiently and automatically checking radiation treatment (RT) planning parameters and gross plan quality, verifying treatment plan data transfer from treatment planning system (TPS) to record and verify (R&V) system, performing a secondary monitor unit (MU) calculation with or without a presence of a magnetic field from MR-Linac, and validating the delivery record consistency with the plan. The software tool, named ArtQA, was developed to obtain and compare plan and treatment parameters from both the TPS and the R&V system database. The TPS data are accessed via direct file reading and the R&V data are retrieved via open database connectivity and structured query language. Plan quality is evaluated with both the logical consistency of planning parameters and the achieved dose-volume histograms. Beams in between the TPS and R&V system are matched based on geometry configurations. To consider the effect of a 1.5 T transverse magnetic field from MR-Linac in the secondary MU calculation, a method based on modified Clarkson integration algorithm was developed and tested for a series of clinical situations. ArtQA has been used in their clinic and can quickly detect inconsistencies and deviations in the entire RT planning process. With the use of the ArtQA tool, the efficiency for plan check including plan quality, data transfer, and delivery check can be improved by at least 60%. The newly developed independent MU calculation tool for MR-Linac reduces the difference between the plan and calculated MUs by 10%. The software tool ArtQA can be used to perform a comprehensive QA check from planning to delivery with conventional Linac or MR-Linac and is an essential tool for online replanning where the QA check needs to be performed rapidly.

  14. Defense Healthcare Information Assurance Program

    DTIC Science & Technology

    2001-06-01

    systems. This "survivability simulator" was developed to enable stakeholders to better understand the risks and consequences of potential threats, such...of sustaining the pre- and post-implementation environments was available from the Information Management Officers (IMOs), Information Management...system sustainment . 3.2.2 Emerging Technologies Task Overview: Based on the ISE findings, knowledge of emerging technology, and MTF policies, the DHIAP

  15. High assurance SPIRAL

    NASA Astrophysics Data System (ADS)

    Franchetti, Franz; Sandryhaila, Aliaksei; Johnson, Jeremy R.

    2014-06-01

    In this paper we introduce High Assurance SPIRAL to solve the last mile problem for the synthesis of high assurance implementations of controllers for vehicular systems that are executed in today's and future embedded and high performance embedded system processors. High Assurance SPIRAL is a scalable methodology to translate a high level specification of a high assurance controller into a highly resource-efficient, platform-adapted, verified control software implementation for a given platform in a language like C or C++. High Assurance SPIRAL proves that the implementation is equivalent to the specification written in the control engineer's domain language. Our approach scales to problems involving floating-point calculations and provides highly optimized synthesized code. It is possible to estimate the available headroom to enable assurance/performance trade-offs under real-time constraints, and enables the synthesis of multiple implementation variants to make attacks harder. At the core of High Assurance SPIRAL is the Hybrid Control Operator Language (HCOL) that leverages advanced mathematical constructs expressing the controller specification to provide high quality translation capabilities. Combined with a verified/certified compiler, High Assurance SPIRAL provides a comprehensive complete solution to the efficient synthesis of verifiable high assurance controllers. We demonstrate High Assurance SPIRALs capability by co-synthesizing proofs and implementations for attack detection and sensor spoofing algorithms and deploy the code as ROS nodes on the Landshark unmanned ground vehicle and on a Synthetic Car in a real-time simulator.

  16. ‘Have you seen what is on Facebook?’ The use of social networking software by healthcare professions students

    PubMed Central

    White, Jonathan; Kirwan, Paul; Lai, Krista; Walton, Jennifer; Ross, Shelley

    2013-01-01

    Objective The use of social networking software has become ubiquitous in our society. The aim of this study was to explore the attitudes and experiences of healthcare professional students using Facebook at our school, to determine if there is a need for development of policy to assist students in this area. Design A mixed-methods approach was employed, using semistructured interviews to identify themes which were explored using an online survey. A combination of descriptive statistics and thematic analysis was used for analysis. Setting Healthcare professions education programmes at a large Canadian university. Participants Students of medicine, nursing, pharmacy, speech and language pathology, occupational therapy, physical therapy, dentistry, dental hygiene and medical laboratory Science were invited to participate. 14 participants were interviewed, and 682 participants responded to an online survey; the female:male balance was 3 : 1. Results 14 interviews were analysed in-depth, and 682 students responded to the survey (17% response rate). 93% reported current Facebook use. Themes identified included patterns of use and attitudes to friendship, attitudes to online privacy, breaches of professional behaviour on Facebook and attitudes to guidelines relating to Facebook use. A majority considered posting of the following material unprofessional: use of alcohol/drugs, crime, obscenity/nudity/sexual content, patient/client information, criticism of others. 44% reported seeing such material posted by a colleague, and 27% reported posting such material themselves. A majority of participants agreed that guidelines for Facebook use would be beneficial. Conclusions Social networking software use, specifically Facebook use, was widespread among healthcare students at our school who responded to our survey. Our results highlight some of the challenges which can accompany the use of this new technology and offer potential insights to help understand the pedagogy and

  17. Building Assured Systems Framework

    DTIC Science & Technology

    2010-09-01

    methodologies differ, such as the Open Web Application Security Project ( OWASP ) Comprehensive, Lightweight Application Security Process (CLASP), the...Reference Model 11 3.3 Open Web Application Security Project ( OWASP ) Software Assurance Maturity Model (SAMM) 12 3.4 DHS SwA Measurement Work by Bartol...1: BSIMM Software Security Framework [McGraw 2010] 10 Table 2: OWASP SAMM Business Functions and Security Practices [ OWASP 2009] 13 Table 3: RTSE

  18. Detection of Temporal Clusters of Healthcare-Associated Infections or Colonizations with Pseudomonas aeruginosa in Two Hospitals: Comparison of SaTScan and WHONET Software Packages

    PubMed Central

    Lefebvre, Annick; Bertrand, Xavier; Vanhems, Philippe; Lucet, Jean-Christophe; Chavanet, Pascal; Astruc, Karine; Thouverez, Michelle; Quantin, Catherine; Aho-Glélé, Ludwig Serge

    2015-01-01

    The identification of temporal clusters of healthcare-associated colonizations or infections is a challenge in infection control. WHONET software is available to achieve these objectives using laboratory databases of hospitals but it has never been compared with SaTScan regarding its detection performance. This study provided the opportunity to evaluate the performance of WHONET software in comparison with SaTScan software as a reference to detect clusters of Pseudomonas aeruginosa. A retrospective study was conducted in two French university hospitals. Cases of P. aeruginosa colonizations or infections occurring between 1st January 2005 and 30th April 2014 in the first hospital were analyzed overall and by medical ward/care unit. Poisson temporal and space-time permutation models were used. Analyses were repeated for the second hospital on data from 1st July 2007 to 31st December 2013 to validate WHONET software (in comparison with SaTScan) in another setting. During the study period, 3,946 isolates of P. aeruginosa were recovered from 2,996 patients in the first hospital. The incidence rate was 89.8 per 100,000 patient-days (95% CI [87.0; 92.6]). Several clusters were observed overall and at the unit level and some of these were detected whatever the method used. WHONET results were consistent with the analyses that took patient-days and temporal trends into account in both hospitals. Because it is more flexible and easier to use than SaTScan, WHONET software seems to be a useful tool for the prospective surveillance of hospital data although it does not take populations at risk into account. PMID:26448036

  19. Detection of Temporal Clusters of Healthcare-Associated Infections or Colonizations with Pseudomonas aeruginosa in Two Hospitals: Comparison of SaTScan and WHONET Software Packages.

    PubMed

    Lefebvre, Annick; Bertrand, Xavier; Vanhems, Philippe; Lucet, Jean-Christophe; Chavanet, Pascal; Astruc, Karine; Thouverez, Michelle; Quantin, Catherine; Aho-Glélé, Ludwig Serge

    2015-01-01

    The identification of temporal clusters of healthcare-associated colonizations or infections is a challenge in infection control. WHONET software is available to achieve these objectives using laboratory databases of hospitals but it has never been compared with SaTScan regarding its detection performance. This study provided the opportunity to evaluate the performance of WHONET software in comparison with SaTScan software as a reference to detect clusters of Pseudomonas aeruginosa. A retrospective study was conducted in two French university hospitals. Cases of P. aeruginosa colonizations or infections occurring between 1st January 2005 and 30th April 2014 in the first hospital were analyzed overall and by medical ward/care unit. Poisson temporal and space-time permutation models were used. Analyses were repeated for the second hospital on data from 1st July 2007 to 31st December 2013 to validate WHONET software (in comparison with SaTScan) in another setting. During the study period, 3,946 isolates of P. aeruginosa were recovered from 2,996 patients in the first hospital. The incidence rate was 89.8 per 100,000 patient-days (95% CI [87.0; 92.6]). Several clusters were observed overall and at the unit level and some of these were detected whatever the method used. WHONET results were consistent with the analyses that took patient-days and temporal trends into account in both hospitals. Because it is more flexible and easier to use than SaTScan, WHONET software seems to be a useful tool for the prospective surveillance of hospital data although it does not take populations at risk into account.

  20. Headway Separation Assurance Subsystem (HSAS)

    DOT National Transportation Integrated Search

    1975-07-01

    This report discusses the design, fabrication, test and evaluation of a Headway Separation Assurance Subsystem (HSAS) capable of reliable, failsafe performance in PRT systems. The items designed include both hardware and software packages. These pack...

  1. Information Assurance Study

    DTIC Science & Technology

    1998-01-01

    be a giant step forward. We are aware that the DOD already sponsors 13 Information Analysis Centers (IAC) and the Information Assurance Technology...Norton Anti-Virus Symantec Corporation http://www.symantec.com OfficeScan Trend Micro http://www.antivirus.com Panda Antivirus Panda Software http

  2. Software Engineering Guidebook

    NASA Technical Reports Server (NTRS)

    Connell, John; Wenneson, Greg

    1993-01-01

    The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

  3. Quality Assurance.

    ERIC Educational Resources Information Center

    Massachusetts Career Development Inst., Springfield.

    This booklet is one of six texts from a workplace literacy curriculum designed to assist learners in facing the increased demands of the workplace. The booklet contains five sections that cover the following topics: (1) importance of reliability; (2) meaning of quality assurance; (3) historical development of quality assurance; (4) statistical…

  4. Understanding and Evaluating Assurance Cases

    NASA Technical Reports Server (NTRS)

    Rushby, John; Xu, Xidong; Rangarajan, Murali; Weaver, Thomas L.

    2015-01-01

    Assurance cases are a method for providing assurance for a system by giving an argument to justify a claim about the system, based on evidence about its design, development, and tested behavior. In comparison with assurance based on guidelines or standards (which essentially specify only the evidence to be produced), the chief novelty in assurance cases is provision of an explicit argument. In principle, this can allow assurance cases to be more finely tuned to the specific circumstances of the system, and more agile than guidelines in adapting to new techniques and applications. The first part of this report (Sections 1-4) provides an introduction to assurance cases. Although this material should be accessible to all those with an interest in these topics, the examples focus on software for airborne systems, traditionally assured using the DO-178C guidelines and its predecessors. A brief survey of some existing assurance cases is provided in Section 5. The second part (Section 6) considers the criteria, methods, and tools that may be used to evaluate whether an assurance case provides sufficient confidence that a particular system or service is fit for its intended use. An assurance case cannot provide unequivocal "proof" for its claim, so much of the discussion focuses on the interpretation of such less-than-definitive arguments, and on methods to counteract confirmation bias and other fallibilities in human reasoning.

  5. QRev—Software for computation and quality assurance of acoustic doppler current profiler moving-boat streamflow measurements—Technical manual for version 2.8

    USGS Publications Warehouse

    Mueller, David S.

    2016-06-21

    The software program, QRev applies common and consistent computational algorithms combined with automated filtering and quality assessment of the data to improve the quality and efficiency of streamflow measurements and helps ensure that U.S. Geological Survey streamflow measurements are consistent, accurate, and independent of the manufacturer of the instrument used to make the measurement. Software from different manufacturers uses different algorithms for various aspects of the data processing and discharge computation. The algorithms used by QRev to filter data, interpolate data, and compute discharge are documented and compared to the algorithms used in the manufacturers’ software. QRev applies consistent algorithms and creates a data structure that is independent of the data source. QRev saves an extensible markup language (XML) file that can be imported into databases or electronic field notes software. This report is the technical manual for version 2.8 of QRev.

  6. Home Healthcare Medical Devices: A Checklist

    MedlinePlus

    ... not using it. Contact your doctor and home healthcare team often to review your health condition. * Check ... assurance of their safety and effectiveness. A home healthcare medical device is any product or equipment used ...

  7. NASA Software Documentation Standard

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

  8. NASA software documentation standard software engineering program

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

  9. QRev—Software for computation and quality assurance of acoustic doppler current profiler moving-boat streamflow measurements—User’s manual for version 2.8

    USGS Publications Warehouse

    Mueller, David S.

    2016-05-12

    The software program, QRev computes the discharge from moving-boat acoustic Doppler current profiler measurements using data collected with any of the Teledyne RD Instrument or SonTek bottom tracking acoustic Doppler current profilers. The computation of discharge is independent of the manufacturer of the acoustic Doppler current profiler because QRev applies consistent algorithms independent of the data source. In addition, QRev automates filtering and quality checking of the collected data and provides feedback to the user of potential quality issues with the measurement. Various statistics and characteristics of the measurement, in addition to a simple uncertainty assessment are provided to the user to assist them in properly rating the measurement. QRev saves an extensible markup language file that can be imported into databases or electronic field notes software. The user interacts with QRev through a tablet-friendly graphical user interface. This report is the manual for version 2.8 of QRev.

  10. Read Code Quality Assurance

    PubMed Central

    Schulz, Erich; Barrett, James W.; Price, Colin

    1998-01-01

    As controlled clinical vocabularies assume an increasing role in modern clinical information systems, so the issue of their quality demands greater attention. In order to meet the resulting stringent criteria for completeness and correctness, a quality assurance system comprising a database of more than 500 rules is being developed and applied to the Read Thesaurus. The authors discuss the requirement to apply quality assurance processes to their dynamic editing database in order to ensure the quality of exported products. Sources of errors include human, hardware, and software factors as well as new rules and transactions. The overall quality strategy includes prevention, detection, and correction of errors. The quality assurance process encompasses simple data specification, internal consistency, inspection procedures and, eventually, field testing. The quality assurance system is driven by a small number of tables and UNIX scripts, with “business rules” declared explicitly as Structured Query Language (SQL) statements. Concurrent authorship, client-server technology, and an initial failure to implement robust transaction control have all provided valuable lessons. The feedback loop for error management needs to be short. PMID:9670131

  11. CrossTalk: The Journal of Defense Software Engineering. Volume 27, Number 5, September/October 2014

    DTIC Science & Technology

    2014-10-01

    software at different phases of the software development lifecycle; however, these assurance cases are difficult to write, communicate and...Oriented Architecture application. Their development process included steps for: 1. Preliminary design 2. Design Phase Software Security Assurance Case...touchpoint) 3. Design Phase Software Security Assurance Case Review, moderated by a student Software Quality Assurance (SQA) leader 4

  12. Systemic Assurance

    DTIC Science & Technology

    2015-07-31

    for assessment of architecture-derived quality attributes. Develop requirements and management approaches for assurance objectives. Augment existing...requirements and architectural decisions. Technical Quality Attributes Augment and collaborate with diverse existing efforts focused on technical...devices (IOS and Android , principally) each include more than a million different available applications from thousands of different sources world-wide

  13. LACIE quality assurance

    NASA Technical Reports Server (NTRS)

    Gutschewski, G. L. (Principal Investigator)

    1979-01-01

    Topics covered include (1) development of the LACIE quality assurance program; (2) LACIE quality assurance responsibilities of all organizational elements; (3) internal quality assurance support; and (4) accomplishments.

  14. Introduction of Syphilis Point-of-Care Tests, from Pilot Study to National Programme Implementation in Zambia: A Qualitative Study of Healthcare Workers’ Perspectives on Testing, Training and Quality Assurance

    PubMed Central

    Ansbro, Éimhín M.; Gill, Michelle M.; Reynolds, Joanna; Shelley, Katharine D.; Strasser, Susan; Sripipatana, Tabitha; Ncube, Alexander Tshaka; Tembo Mumba, Grace; Terris-Prestholt, Fern; Peeling, Rosanna W.; Mabey, David

    2015-01-01

    Syphilis affects 1.4 million pregnant women globally each year. Maternal syphilis causes congenital syphilis in over half of affected pregnancies, leading to early foetal loss, pregnancy complications, stillbirth and neonatal death. Syphilis is under-diagnosed in pregnant women. Point-of-care rapid syphilis tests (RST) allow for same-day treatment and address logistical barriers to testing encountered with standard Rapid Plasma Reagin testing. Recent literature emphasises successful introduction of new health technologies requires healthcare worker (HCW) acceptance, effective training, quality monitoring and robust health systems. Following a successful pilot, the Zambian Ministry of Health (MoH) adopted RST into policy, integrating them into prevention of mother-to-child transmission of HIV clinics in four underserved Zambian districts. We compare HCW experiences, including challenges encountered in scaling up from a highly supported NGO-led pilot to a large-scale MoH-led national programme. Questionnaires were administered through structured interviews of 16 HCWs in two pilot districts and 24 HCWs in two different rollout districts. Supplementary data were gathered via stakeholder interviews, clinic registers and supervisory visits. Using a conceptual framework adapted from health technology literature, we explored RST acceptance and usability. Quantitative data were analysed using descriptive statistics. Key themes in qualitative data were explored using template analysis. Overall, HCWs accepted RST as learnable, suitable, effective tools to improve antenatal services, which were usable in diverse clinical settings. Changes in training, supervision and quality monitoring models between pilot and rollout may have influenced rollout HCW acceptance and compromised testing quality. While quality monitoring was integrated into national policy and training, implementation was limited during rollout despite financial support and mentorship. We illustrate that new

  15. Introduction of Syphilis Point-of-Care Tests, from Pilot Study to National Programme Implementation in Zambia: A Qualitative Study of Healthcare Workers' Perspectives on Testing, Training and Quality Assurance.

    PubMed

    Ansbro, Éimhín M; Gill, Michelle M; Reynolds, Joanna; Shelley, Katharine D; Strasser, Susan; Sripipatana, Tabitha; Tshaka Ncube, Alexander; Tembo Mumba, Grace; Terris-Prestholt, Fern; Peeling, Rosanna W; Mabey, David

    2015-01-01

    Syphilis affects 1.4 million pregnant women globally each year. Maternal syphilis causes congenital syphilis in over half of affected pregnancies, leading to early foetal loss, pregnancy complications, stillbirth and neonatal death. Syphilis is under-diagnosed in pregnant women. Point-of-care rapid syphilis tests (RST) allow for same-day treatment and address logistical barriers to testing encountered with standard Rapid Plasma Reagin testing. Recent literature emphasises successful introduction of new health technologies requires healthcare worker (HCW) acceptance, effective training, quality monitoring and robust health systems. Following a successful pilot, the Zambian Ministry of Health (MoH) adopted RST into policy, integrating them into prevention of mother-to-child transmission of HIV clinics in four underserved Zambian districts. We compare HCW experiences, including challenges encountered in scaling up from a highly supported NGO-led pilot to a large-scale MoH-led national programme. Questionnaires were administered through structured interviews of 16 HCWs in two pilot districts and 24 HCWs in two different rollout districts. Supplementary data were gathered via stakeholder interviews, clinic registers and supervisory visits. Using a conceptual framework adapted from health technology literature, we explored RST acceptance and usability. Quantitative data were analysed using descriptive statistics. Key themes in qualitative data were explored using template analysis. Overall, HCWs accepted RST as learnable, suitable, effective tools to improve antenatal services, which were usable in diverse clinical settings. Changes in training, supervision and quality monitoring models between pilot and rollout may have influenced rollout HCW acceptance and compromised testing quality. While quality monitoring was integrated into national policy and training, implementation was limited during rollout despite financial support and mentorship. We illustrate that new

  16. Safety and Mission Assurance: A NASA Perspective

    NASA Technical Reports Server (NTRS)

    Higginbotham, Scott Alan

    2011-01-01

    Safety and Mission Assurance (S&MA) consists of the safety, reliability, maintainability, software assurance and quality disciplines, which are applied to reduce the probability of mishaps and ensure mission success. NASA uses a risk management process which requires various organizations to identify, analyze and mitigate/control risks associated with operations and decision making processes.

  17. The quality assurance role in the Deep Space Network

    NASA Technical Reports Server (NTRS)

    Sirpilla, R. L.

    1981-01-01

    The quality assurance section provides skilled personnel who perform the following functions: quality hardware engineering, quality software engineering, inspection and testing, and an independent assessment to quality, engineering and project requirements. The quality assurance section provides specifications, workmanship standards, process specifications and quality assurance procedures in support of DSN equipment. In addition, the quality assurance section reviews DSN engineering documents to ensure that appropriate and adequate quality provisions are included.

  18. Proceedings of Tenth Annual Software Engineering Workshop

    NASA Technical Reports Server (NTRS)

    1985-01-01

    Papers are presented on the following topics: measurement of software technology, recent studies of the Software Engineering Lab, software management tools, expert systems, error seeding as a program validation technique, software quality assurance, software engineering environments (including knowledge-based environments), the Distributed Computing Design System, and various Ada experiments.

  19. Software Assurance of PLCs Training Course

    NASA Technical Reports Server (NTRS)

    Threatt, Jamarr

    2004-01-01

    Being heavily visually-oriented, I am a firm believer in communication and conveying emotions through the art of color, motion, and transformation. A four-part online training course was created in PowerPoint and needed to be translated over into a Flash format. Issues with the Powerpoint were that the size of the files caused noticeable delays when placed online, there were compatibility issues, and from a composition and design perspective, color schemes and layout left much to be desired. High contrast, pixilated yellow text spiraling and flying on to a background of overly rich hues of blue with cheesy gradient patterns was just not appeasing to my eye, along with the menu directory buttons located at the top resembling blue pills of NyQuil on top of a stale gray border that had nothing to do with the background. The course itself is extremely broad and verbose, and will get monotonous very soon after starting. Moving about the course was very cumbersome as well. efficient by drastically reducing the size (The file size of all four parts of the actual course combined will ultimately not even be a fifth as big as one part of the original PowerPoint alone!); along with that, the course was made to be more interactive and user-friendly, as well as pleasing to the eye. Upon being viewed by fellow co-workers, nothing but positive feedback has been received. When beginning the presentation, onscreen comes a 3' 2" chubby, balding professor, who is a master in his knowledge of Programmable Logic Controllers (PLCs). He introduces himself and presents all of his vast knowledge over PLCs in a fun and innovative manner, making it much easier to acquire the information presented. A Scene Selection feature has been added making it a lot easier to jump from part to part and the back and forth arrows are much easier to utilize, and they are both less obtrusive than its PowerPoint predecessor. The user can also go at their pace, as the presentation pauses after at the end of each statement. computer animation, it was.. .still. ..animation done on a computer. I was able to incorporate my artistic talent and intuitive creativity into it, one thing I am very proficient at doing when it comes to what I do and what I will do in my profession as an artist/computer animator. At first, I felt that there was no place for an artist within a faculty of scientists, engineers, chemists, mathematicians, and programmers, but I managed to fit in quite successfully. My task was to convert the course into a Flash format, which would make it much more My project surprisingly somewhat dealt with my field of interest-though it was not

  20. Construction of a Drug Safety Assurance Information System Based on Clinical Genotyping

    PubMed Central

    Springer, John A.; Iannotti, Nicholas V.; Sprague, Jon E.; Kane, Michael D.

    2012-01-01

    To capitalize on the vast potential of patient genetic information to aid in assuring drug safety, a substantial effort is needed in both the training of healthcare professionals and the operational enablement of clinical environments. Our research aims to satisfy these needs through the development of a drug safety assurance information system (GeneScription) based on clinical genotyping that utilizes patient-specific genetic information to predict and prevent adverse drug responses. In this paper, we present the motivations for this work, the algorithms at the heart of GeneScription, and a discussion of our system and its uses. We also describe our efforts to validate GeneScription through its evaluation by practicing pharmacists and pharmacy professors and its repeated use in training pharmacists. The positive assessment of the GeneScription software tool by these domain experts provides strong validation of the importance, accuracy, and effectiveness of GeneScription. PMID:25969745

  1. A comprehensive framework for quality assurance in clinical trials

    NASA Astrophysics Data System (ADS)

    El Gazzar, Omar; Onken, Michael; Eichelberg, Marco; Hein, Andreas; Kotter, Elmar

    2012-02-01

    Biomarkers captured by medical images are increasingly used as indicators for the efficacy or safety of a certain drug or treatment for clinical trials. For example, medical images such as CT or MR are often used for extracting quantitative measurements for the assessment of tumor treatment response while evaluating a chemotherapy drug for therapeutic cancer trials. Quality assurance is defined as "All those planned and systematic actions that are established to ensure that the trial is performed and the data are generated, documented (recorded), and reported in compliance with good clinical practice (GCP) and the applicable regulatory requirement(s)" [1]. Our objective is to build a generalized and an automated framework for quality assurance within the clinical trials workflow. In order to reach this goal, a set of standardized software tools have been developed for quality assurance. Furthermore, we outline some guidelines as recommendations for the users handling the image data within the research workflow. The software tools developed include tools for image selection, image pseudonymization and image quality conformance check. The export tools are developed based on the specifications of the Integrating the Healthcare Enterprise (IHE) Teaching and Clinical Trial Export (TCE) profile. A DICOM-based quality conformance approach has been developed by validating the DICOM header attributes required for a certain imaging application (e.g. CAD, MPR, 3D) and comparing imaging acquisition parameters against the protocol specification. A formal description language is used to represent such quality requirements. For evaluation, imaging data collected from a clinical trial site were validated against Multi-Planar Reconstruction (MPR). We found that out of 60 studies, about 30% of image series volumes failed the MPR check for some common reasons.

  2. Healthcare Cost and Utilization Project (HCUP)

    Cancer.gov

    The Healthcare Cost and Utilization Project is a family of health care databases and related software tools and products developed through a Federal-State-Industry partnership and sponsored by the Agency for Healthcare Research and Quality.

  3. Software quality: Process or people

    NASA Technical Reports Server (NTRS)

    Palmer, Regina; Labaugh, Modenna

    1993-01-01

    This paper will present data related to software development processes and personnel involvement from the perspective of software quality assurance. We examine eight years of data collected from six projects. Data collected varied by project but usually included defect and fault density with limited use of code metrics, schedule adherence, and budget growth information. The data are a blend of AFSCP 800-14 and suggested productivity measures in Software Metrics: A Practioner's Guide to Improved Product Development. A software quality assurance database tool, SQUID, was used to store and tabulate the data.

  4. Assurance: the power behind PCASSO security.

    PubMed Central

    Baker, D. B.; Masys, D. R.; Jones, R. L.; Barnhart, R. M.

    1999-01-01

    The need for security protection in Internet-based healthcare applications is generally acknowledged. Most healthcare applications that use the Internet have at least implemented some kind of encryption. Most applications also enforce user authentication and access control policies, and many audit user actions. However, most fall short on providing strong assurances that the security mechanisms are behaving as expected and that they cannot be subverted. While no system can claim to be totally "bulletproof," PCASSO provides assurance of correct operation through formal, disciplined design and development methodologies, as well as through functional and penetration testing. Through its security mechanisms, backed by strong system assurances, PCASSO is demonstrating "safe" use of public data networks for health care. PMID:10566443

  5. Final Report of the NASA Office of Safety and Mission Assurance Agile Benchmarking Team

    NASA Technical Reports Server (NTRS)

    Wetherholt, Martha

    2016-01-01

    To ensure that the NASA Safety and Mission Assurance (SMA) community remains in a position to perform reliable Software Assurance (SA) on NASAs critical software (SW) systems with the software industry rapidly transitioning from waterfall to Agile processes, Terry Wilcutt, Chief, Safety and Mission Assurance, Office of Safety and Mission Assurance (OSMA) established the Agile Benchmarking Team (ABT). The Team's tasks were: 1. Research background literature on current Agile processes, 2. Perform benchmark activities with other organizations that are involved in software Agile processes to determine best practices, 3. Collect information on Agile-developed systems to enable improvements to the current NASA standards and processes to enhance their ability to perform reliable software assurance on NASA Agile-developed systems, 4. Suggest additional guidance and recommendations for updates to those standards and processes, as needed. The ABT's findings and recommendations for software management, engineering and software assurance are addressed herein.

  6. Using the iBook in medical education and healthcare settings--the iBook as a reusable learning object; a report of the author's experience using iBooks Author software.

    PubMed

    Payne, Karl Fb; Goodson, Alexander Mc; Tahim, Arpan; Wharrad, Heather J; Fan, Kathleen

    2012-12-01

    The recently launched iBooks 2 from Apple has created a new genre of 'interactive multimedia eBook'. This article aims to dscribe the benefit of the iBook in a medical education and healthcare setting. We discuss the attributes of an iBook as compared with the requirements of the conventional web-based Reusable Learning Object. The structure and user interface within an iBook is highlighted, and the iBook-creating software iBooks Author is discussed in detail. A report of personal experience developing and distributing an iBook for junior trainees in oral and maxillofacial surgery is provided, with discussion of the limitations of this approach and the need for further evidence-based studies.

  7. Quality assurance in diabetic retinal screening in South Africa.

    PubMed

    Cook, Steve; Staff, Roger T; Goatman, Keith A; Olson, John A

    2014-09-03

    Diabetic retinopathy (DR) is an important biomarker for microvascular disease and blindness. Digital fundus photography is a cost-effective way of screening for DR. Access to DR screening is difficult for many South Africans with diabetes. To perform external quality assurance (EQA) on graders registered in the Ophthalmological Society of South Africa DR screening programme. Graders registered on the South African (SA) Diabetic Register website were invited to participate in the study. The Scottish EQA software system was used to enable on-line grading of 100 retinal photographs. Expert National Health Service graders provided the consensus expert grading for the image set. Two hundred and sixty-one participants completed the EQA process, including nine ophthalmologists, 243 optometrists, and nine other graders. A wide range of outcomes were demonstrated, with a mean sensitivity of 0.905 (range 0.286 - 1.000) and mean specificity of 0.507 (0.000 - 0.935). The mean diagnostic odds ratio was calculated to be 12.3 (range 0.147 - 148.2). This is the first quality assurance study conducted with SA healthcare professionals. The outcomes are of interest to all stakeholders dealing with the diabetes epidemic. The disparity in grader performance indicates room for improvement. The results demonstrate a high referral rate to ophthalmology, suggesting that on average graders are performing safely, but with a high number of inappropriate referrals.

  8. Compliance Assurance Monitoring

    EPA Pesticide Factsheets

    Compliance assurance monitoring is intended to provide a reasonable assurance of compliance with applicable requirements under the Clean Air Act for large emission units that rely on pollution control device equipment to achieve compliance.

  9. Multinational Quality Assurance

    ERIC Educational Resources Information Center

    Kinser, Kevin

    2011-01-01

    Multinational colleges and universities pose numerous challenges to the traditional models of quality assurance that are designed to validate domestic higher education. When institutions cross international borders, at least two quality assurance protocols are involved. To guard against fraud and abuse, quality assurance in the host country is…

  10. Lean healthcare.

    PubMed

    Weinstock, Donna

    2008-01-01

    As healthcare organizations look for new and improved ways to reduce costs and still offer quality healthcare, many are turning to the Toyota Production System of doing business. Rather than focusing on cutting personnel and assets, "lean healthcare" looks to improve patient satisfaction through improved actions and processes.

  11. Software Assurance Curriculum Project Volume 3: Master of Software Assurance Course Syllabi

    DTIC Science & Technology

    2011-07-01

    power, telecommuni- cations, water, and air-traffic-control systems • Group exercise to identify security risks in a nuclear power plant system...their abilities, for both legal and ethical reasons • Group exercise concerning Privacy and Surveillance: The Carnivore case (http

  12. Validation in daily clinical situations of Diascope®, a software developed to help healthcare professionals individualize antidiabetic treatment in type 2 diabetes.

    PubMed

    Ampudia-Blasco, Francisco Javier; García-Soidán, Francisco Javier; Rubio Sánchez, Manuela; Phan, Tra-Mi

    2017-03-01

    DiaScope ® is a software to help in individualized prescription of antidiabetic treatment in type 2 diabetes. This study assessed its value and acceptability by different professionals. DiaScope ® was developed based on the ADA-EASD 2012 algorithm and on the recommendation of 12 international diabetes experts using the RAND/UCLA appropriateness method. The current study was performed at a single session. In the first phase, 5 clinical scenarios were evaluated, selecting the most appropriated therapeutic option among 4 possibilities (initial test). In a second phase, the same clinical cases were evaluated with DiaScope ® (final test).Opinion surveys on DiaScope ® were also performed (questionnaire). DiaScope ® changed the selected option 1 or more times in 70.5% of cases. Among 275 evaluated questionnaires, 54.0% strongly agree that DiaScope ® allowed finding easily a similar therapeutic scenario to the corresponding patient, and 52.5 among the obtained answers were clinically plausible. Up to 58.3% will recommend it to a colleague. In particular, primary care physicians with >20 years of professional dedication found with DiaScope ® the most appropriate option for a particular situation against specialists or those with less professional dedication (p<.05). DiaScope ® is an easy to use tool for antidiabetic drug prescription that provides plausible solutions and is especially useful for primary care physicians with more years of professional practice. Copyright © 2017 SEEN. Publicado por Elsevier España, S.L.U. All rights reserved.

  13. Assuring health coverage for all in India.

    PubMed

    Patel, Vikram; Parikh, Rachana; Nandraj, Sunil; Balasubramaniam, Priya; Narayan, Kavita; Paul, Vinod K; Kumar, A K Shiva; Chatterjee, Mirai; Reddy, K Srinath

    2015-12-12

    Successive Governments of India have promised to transform India's unsatisfactory health-care system, culminating in the present government's promise to expand health assurance for all. Despite substantial improvements in some health indicators in the past decade, India contributes disproportionately to the global burden of disease, with health indicators that compare unfavourably with other middle-income countries and India's regional neighbours. Large health disparities between states, between rural and urban populations, and across social classes persist. A large proportion of the population is impoverished because of high out-of-pocket health-care expenditures and suffers the adverse consequences of poor quality of care. Here we make the case not only for more resources but for a radically new architecture for India's health-care system. India needs to adopt an integrated national health-care system built around a strong public primary care system with a clearly articulated supportive role for the private and indigenous sectors. This system must address acute as well as chronic health-care needs, offer choice of care that is rational, accessible, and of good quality, support cashless service at point of delivery, and ensure accountability through governance by a robust regulatory framework. In the process, several major challenges will need to be confronted, most notably the very low levels of public expenditure; the poor regulation, rapid commercialisation of and corruption in health care; and the fragmentation of governance of health care. Most importantly, assuring universal health coverage will require the explicit acknowledgment, by government and civil society, of health care as a public good on par with education. Only a radical restructuring of the health-care system that promotes health equity and eliminates impoverishment due to out-of-pocket expenditures will assure health for all Indians by 2022--a fitting way to mark the 75th year of India

  14. Flight Dynamics Mission Support and Quality Assurance Process

    NASA Technical Reports Server (NTRS)

    Oh, InHwan

    1996-01-01

    This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

  15. NASA's Software Safety Standard

    NASA Technical Reports Server (NTRS)

    Ramsay, Christopher M.

    2005-01-01

    NASA (National Aeronautics and Space Administration) relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft (manned or unmanned) launched that did not have a computer on board that provided vital command and control services. Despite this growing dependence on software control and monitoring, there has been no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Led by the NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard (STD-18l9.13B) has recently undergone a significant update in an attempt to provide that consistency. This paper will discuss the key features of the new NASA Software Safety Standard. It will start with a brief history of the use and development of software in safety critical applications at NASA. It will then give a brief overview of the NASA Software Working Group and the approach it took to revise the software engineering process across the Agency.

  16. Small satellite product assurance

    NASA Astrophysics Data System (ADS)

    Demontlivault, J.; Cadelec, Jacques

    1993-01-01

    In order to increase the interest in small satellites, their cost must be reduced; reducing product assurance costs induced by quality requirements is a major objective. For a logical approach, small satellites are classified in three main categories: satellites for experimental operations with a short lifetime, operational satellites manufactured in small mass with long lifetime requirements, operational satellites (long lifetime required), of which only a few models are produced. The various requirements as regards the product assurance are examined for each satellite category: general requirements for space approach, reliability, electronic components, materials and processes, quality assurance, documentation, tests, and management. Ideal product assurance system integrates quality teams and engineering teams.

  17. Assurance Cases for Proofs as Evidence

    NASA Technical Reports Server (NTRS)

    Chaki, Sagar; Gurfinkel, Arie; Wallnau, Kurt; Weinstock, Charles

    2009-01-01

    Proof-carrying code (PCC) provides a 'gold standard' for establishing formal and objective confidence in program behavior. However, in order to extend the benefits of PCC - and other formal certification techniques - to realistic systems, we must establish the correspondence of a mathematical proof of a program's semantics and its actual behavior. In this paper, we argue that assurance cases are an effective means of establishing such a correspondence. To this end, we present an assurance case pattern for arguing that a proof is free from various proof hazards. We also instantiate this pattern for a proof-based mechanism to provide evidence about a generic medical device software.

  18. Reducing software security risk through an integrated approach

    NASA Technical Reports Server (NTRS)

    Gilliam, D. P.; Powell, J. D.; Bishop, M.; Kelly, J.

    2001-01-01

    This paper presents research on the generation of a software security assessment instrument to aid developers in assessing and assuring the security of software in the development and maintenance lifecycles.

  19. Standardized development of computer software. Part 2: Standards

    NASA Technical Reports Server (NTRS)

    Tausworthe, R. C.

    1978-01-01

    This monograph contains standards for software development and engineering. The book sets forth rules for design, specification, coding, testing, documentation, and quality assurance audits of software; it also contains detailed outlines for the documentation to be produced.

  20. Software: Radio Pulsar Software

    NASA Astrophysics Data System (ADS)

    Bailes, M.; Murdin, P.

    2000-11-01

    Software used to process radio pulsar data is almost all written in Fortran, C and C++ and runs mainly on UNIX platforms. The size of the user base is such that most of the major groups have their own home-grown solutions to what are very similar problems. However, there are generic features in the software used in the discovery, timing and understanding of the statistical properties of PULSAR...

  1. Evaluating and Mitigating Software Supply Chain Security Risks

    DTIC Science & Technology

    2010-05-01

    model [SAPPWG 2008]. In addition, the Open Web Applications Security Project ( OWASP ) has developed a Software Assurance Maturity Model (SAMM) for...software security [ OWASP 2009]. Finally, the build-security-in website8 con- tains a growing set of reference materials on software security practices...publications/nistpubs/800-30/sp800-30.pdf. [ OWASP 2009] Open Web Applications Security Project. Software Assurance Maturity Model. http://www.owasp.org

  2. Healthcare Systems and Motivation

    PubMed Central

    Loewy, Erich H.

    2007-01-01

    Despite the fact that most American physicians, at least until around the 1970s, stood in the way of developing a universal healthcare system, most are generally not happy with the current state of healthcare – or its lack thereof – today. The primary reasons for this general unhappiness are that insurance companies and managed care have successfully conspired to remove much of the physician's autonomy (via imposed time constraints, burdensome paperwork, the time-consuming chore of having to defend going against stringent treatment algorithms that are often inappropriate for some patients) and the satisfaction of knowing their patients. Few physicians in managed care organizations (MCOs) are able to practice without constant and blindly algorithmic interference concerning the diagnostic tests and therapeutic interventions they order. As copayments have increased, they often find that patients, even though “covered,” cannot afford the therapy they deem necessary. While physicians expect to earn sufficient to pay back their not insignificant educational debts, provide their children with help through college, and assure retirements sufficient for themselves and their spouses, these should not be considered unreasonable expectations. Most physicians today do favor universal healthcare – to the point of having included such language in their various professional codes of ethics (which, perversely enough, bioethicists as a group have failed to do). Contrary to the claims of our colleagues, Altom and Churchill, physicians seem to be genuinely frustrated as to what else they can do to change the current inequitable system. PMID:17435646

  3. PPEPR for Enterprise Healthcare Integration

    NASA Astrophysics Data System (ADS)

    Fox, Ronan; Sahay, Ratnesh; Hauswirth, Manfred

    PPEPR is software to connect healthcare enterprises. Healthcare is a complex domain and any integration system that connects healthcare enterprise applications must facilitate heterogeneous healthcare systems at all levels - data, services, processes, healthcare vendors, standards, legacy systems, and new information systems, all of which must interoperate to provide healthcare services. The lack of interoperability within healthcare standards (e.g. HL7) adds complexity to the interoperability initiatives. HL7’s user base has been growing since the early 2000s. There are many interoperability issues between the widely adopted HL7 v2 and its successor, HL7 v3, in terms of consistency, data/message modeling, precision, and useability. We have proposed an integration platform called PPEPR: (Plug and Play Electronic Patient Records) which is based on a semantic Service-oriented Architecture (sSOA). PPEPR connects HL7 (v2 & v3) compliant healthcare enterprises. Our main goal is to provide seamless integration between healthcare enterprises without imposing any constraint on existing or proposed EPRs.

  4. Quality assurance of metabolomics.

    PubMed

    Bouhifd, Mounir; Beger, Richard; Flynn, Thomas; Guo, Lining; Harris, Georgina; Hogberg, Helena; Kaddurah-Daouk, Rima; Kamp, Hennicke; Kleensang, Andre; Maertens, Alexandra; Odwin-DaCosta, Shelly; Pamies, David; Robertson, Donald; Smirnova, Lena; Sun, Jinchun; Zhao, Liang; Hartung, Thomas

    2015-01-01

    Metabolomics promises a holistic phenotypic characterization of biological responses to toxicants. This technology is based on advanced chemical analytical tools with reasonable throughput, including mass-spectroscopy and NMR. Quality assurance, however - from experimental design, sample preparation, metabolite identification, to bioinformatics data-mining - is urgently needed to assure both quality of metabolomics data and reproducibility of biological models. In contrast to microarray-based transcriptomics, where consensus on quality assurance and reporting standards has been fostered over the last two decades, quality assurance of metabolomics is only now emerging. Regulatory use in safety sciences, and even proper scientific use of these technologies, demand quality assurance. In an effort to promote this discussion, an expert workshop discussed the quality assurance needs of metabolomics. The goals for this workshop were 1) to consider the challenges associated with metabolomics as an emerging science, with an emphasis on its application in toxicology and 2) to identify the key issues to be addressed in order to establish and implement quality assurance procedures in metabolomics-based toxicology. Consensus has still to be achieved regarding best practices to make sure sound, useful, and relevant information is derived from these new tools.

  5. Quality Assurance in Radiotherapy

    NASA Astrophysics Data System (ADS)

    Mckenzie, Alan

    A common feature of the Radiotherapy Centres where there have been major accidents involving incorrect radiotherapy treatment is that they did not operate good Quality Assurance systems. A Quality Assurance system is sometimes called a Quality Management system, and it is designed to give assurance that quality standards are being met. One of the "spin offs" from operating a Quality Management system is that it reduces the likelihood of a radiotherapy accident. A detailed account of how to set up a quality system in radiotherapy has been given in an ESTRO booklet.2

  6. Healthcare leadership's diversity paradox.

    PubMed

    Silver, Reginald

    2017-02-06

    Purpose The purpose of this research study was to obtain healthcare executives' perspectives on diversity in executive healthcare leadership. The study focused on identifying perspectives about diversity and its potential impact on the access of healthcare services by people of color. The study also identified perspectives about factors that influence the attainment of executive healthcare roles by people of color. Design/methodology/approach A convenience sample of healthcare executives was obtained. The executives identified themselves as belonging to one of two subgroups, White healthcare executives or executives of color. Participants were interviewed telephonically in a semi-structured format. The interviews were transcribed and entered into a qualitative software application. The data were codified and important themes were identified. Findings The majority of the study participants perceive that diversity of the executive healthcare leadership team is important. There were differences in perspective among the subgroups as it relates to solutions to improve access to healthcare by people of color. There were also differences in perspective among the subgroups, as it relates to explaining the underrepresentation of people of color in executive healthcare leadership roles. Research limitations/implications This research effort benefited from the subject matter expertise of 24 healthcare executives from two states. Expansion of the number of survey participants and broadening the geographical spread of where participants were located may have yielded more convergence and/or more divergence in perspectives about key topics. Practical implications The findings from this research study serve to add to the existing body of literature on diversity in executive healthcare leadership. The findings expand on the importance of key elements in contemporary literature such as diversity, cultural competency and perspectives about the need for representation of people of

  7. ALMA quality assurance: concepts, procedures, and tools

    NASA Astrophysics Data System (ADS)

    Chavan, A. M.; Tanne, S. L.; Akiyama, E.; Kurowski, R.; Randall, S.; Vila Vilaro, B.; Villard, E.

    2016-07-01

    Data produced by ALMA for the community undergoes a rigorous quality assurance (QA) process, from the initial observation ("QA0") to the final science-ready data products ("QA2"), to the QA feedback given by the Principal Investigators (PIs) when they receive the data products ("QA3"). Calibration data is analyzed to measure the performance of the observatory and predict the trend of its evolution ("QA1"). The procedure develops over different steps and involves several actors across all ALMA locations; it is made possible by the support given by dedicated software tools and a complex database of science data, meta-data and operational parameters. The life-cycle of each involved entity is well-defined, and it prevents for instance that "bad" data (that is, data not meeting the minimum quality standards) is ever processed by the ALMA pipeline. This paper describes ALMA's quality assurance concepts and procedures, including the main enabling software components.

  8. F-35 Engine Quality Assurance Inspection

    DTIC Science & Technology

    2015-04-27

    Instruction 7650.03. If possible, please send a PDF file containing your comments to . Copies of your comments must have the actual signature of the...00-00-2015 to 00-00-2015 4. TITLE AND SUBTITLE F-35 Engine Quality Assurance Inspection ( REDACTED ) 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c...log files , software versions, and configuration of the EVB. Pratt & Whitney’s lack of formal configuration management control in the EVB laboratory

  9. EMC Compliance Assurance Monitoring

    EPA Pesticide Factsheets

    The Compliance Assurance Monitoring, or CAM, rule is designed to satisfy the requirements for monitoring and compliance certification in the Part 70 operating permits program and Title VII of the 1990 Clean Air Act Amendments

  10. RAVEN Quality Assurance Activities

    SciTech Connect

    Cogliati, Joshua Joseph

    2015-09-01

    This report discusses the quality assurance activities needed to raise the Quality Level of Risk Analysis in a Virtual Environment (RAVEN) from Quality Level 3 to Quality Level 2. This report also describes the general RAVEN quality assurance activities. For improving the quality, reviews of code changes have been instituted, more parts of testing have been automated, and improved packaging has been created. For upgrading the quality level, requirements have been created and the workflow has been improved.

  11. 38 CFR 17.508 - Access to quality assurance records and documents within the agency.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 38 Pensions, Bonuses, and Veterans' Relief 1 2014-07-01 2014-07-01 false Access to quality assurance records and documents within the agency. 17.508 Section 17.508 Pensions, Bonuses, and Veterans' Relief DEPARTMENT OF VETERANS AFFAIRS MEDICAL Confidentiality of Healthcare Quality Assurance Review...

  12. 38 CFR 17.508 - Access to quality assurance records and documents within the agency.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 38 Pensions, Bonuses, and Veterans' Relief 1 2010-07-01 2010-07-01 false Access to quality assurance records and documents within the agency. 17.508 Section 17.508 Pensions, Bonuses, and Veterans' Relief DEPARTMENT OF VETERANS AFFAIRS MEDICAL Confidentiality of Healthcare Quality Assurance Review...

  13. 38 CFR 17.508 - Access to quality assurance records and documents within the agency.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... 38 Pensions, Bonuses, and Veterans' Relief 1 2012-07-01 2012-07-01 false Access to quality assurance records and documents within the agency. 17.508 Section 17.508 Pensions, Bonuses, and Veterans' Relief DEPARTMENT OF VETERANS AFFAIRS MEDICAL Confidentiality of Healthcare Quality Assurance Review...

  14. 38 CFR 17.508 - Access to quality assurance records and documents within the agency.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 38 Pensions, Bonuses, and Veterans' Relief 1 2011-07-01 2011-07-01 false Access to quality assurance records and documents within the agency. 17.508 Section 17.508 Pensions, Bonuses, and Veterans' Relief DEPARTMENT OF VETERANS AFFAIRS MEDICAL Confidentiality of Healthcare Quality Assurance Review...

  15. 38 CFR 17.508 - Access to quality assurance records and documents within the agency.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 38 Pensions, Bonuses, and Veterans' Relief 1 2013-07-01 2013-07-01 false Access to quality assurance records and documents within the agency. 17.508 Section 17.508 Pensions, Bonuses, and Veterans' Relief DEPARTMENT OF VETERANS AFFAIRS MEDICAL Confidentiality of Healthcare Quality Assurance Review...

  16. NASA Software Engineering Benchmarking Study

    NASA Technical Reports Server (NTRS)

    Rarick, Heather L.; Godfrey, Sara H.; Kelly, John C.; Crumbley, Robert T.; Wifl, Joel M.

    2013-01-01

    To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths

  17. Technology and Tool Development to Support Safety and Mission Assurance

    NASA Technical Reports Server (NTRS)

    Denney, Ewen; Pai, Ganesh

    2017-01-01

    The Assurance Case approach is being adopted in a number of safety-mission-critical application domains in the U.S., e.g., medical devices, defense aviation, automotive systems, and, lately, civil aviation. This paradigm refocuses traditional, process-based approaches to assurance on demonstrating explicitly stated assurance goals, emphasizing the use of structured rationale, and concrete product-based evidence as the means for providing justified confidence that systems and software are fit for purpose in safely achieving mission objectives. NASA has also been embracing assurance cases through the concepts of Risk Informed Safety Cases (RISCs), as documented in the NASA System Safety Handbook, and Objective Hierarchies (OHs) as put forth by the Agency's Office of Safety and Mission Assurance (OSMA). This talk will give an overview of the work being performed by the SGT team located at NASA Ames Research Center, in developing technologies and tools to engineer and apply assurance cases in customer projects pertaining to aviation safety. We elaborate how our Assurance Case Automation Toolset (AdvoCATE) has not only extended the state-of-the-art in assurance case research, but also demonstrated its practical utility. We have successfully developed safety assurance cases for a number of Unmanned Aircraft Systems (UAS) operations, which underwent, and passed, scrutiny both by the aviation regulator, i.e., the FAA, as well as the applicable NASA boards for airworthiness and flight safety, flight readiness, and mission readiness. We discuss our efforts in expanding AdvoCATE capabilities to support RISCs and OHs under a project recently funded by OSMA under its Software Assurance Research Program. Finally, we speculate on the applicability of our innovations beyond aviation safety to such endeavors as robotic, and human spaceflight.

  18. NASA guidelines for assuring the adequacy and appropriateness of security safeguards in sensitive applications

    NASA Technical Reports Server (NTRS)

    Tompkins, F. G.

    1984-01-01

    The Office of Management and Budget (OMB) Circular A-71, transmittal Memorandum No. 1, requires that each agency establish a management control process to assure that appropriate administrative, physical and technical safeguards are incorporated into all new computer applications. In addition to security specifications, the management control process should assure that the safeguards are adequate for the application. The security activities that should be integral to the system development process are examined. The software quality assurance process to assure that adequate and appropriate controls are incorporated into sensitive applications is also examined. Security for software packages is also discussed.

  19. [Quality assurance in Europe].

    PubMed

    Vuori, H

    1993-01-01

    The development of quality assurance in Europe can be divided into three periods: "In the beginning", "half-way through", and "almost there". In the beginning, the early 1970s, Europeans became interested in the US's concern for quality assurance. Pioneering clinicians and health services researchers, a few politicians and managers failed to make quality assurance a going concern. Halfway through, during the 1980's the situation started to change. Health care costs started to rise, and critical voices gained strength. Health authorities, and perhaps more importantly, the clinicians were shocked to see the variation in performance revealed by studies. Awareness, and training programs produced a critical mass of people interested in quality of care. In 1989, we the almost there era started. Formal political will and professional commitment for quality assurance gave rise to routine programs supported by the administration in many health care institutions. Now, the patient's right to quality care is recognized. Many professional groups have adopted quality assurance, some feeling obliged by the professional ethos, others believing it to provide them with a competitive edge. Furthermore, the biomedical research programme of the European Community has given a high priority to research on quality of care. Five main factors seem to explain most of the change: ethics, safety, efficiency, system and economics.

  20. Healthcare Lean.

    PubMed

    Long, John C

    2003-01-01

    Lean Thinking is an integrated approach to designing, doing and improving the work of people that have come together to produce and deliver goods, services and information. Healthcare Lean is based on the Toyota production system and applies concepts and techniques of Lean Thinking to hospitals and physician practices.

  1. Predictors of home healthcare nurse retention.

    PubMed

    Ellenbecker, Carol Hall; Porell, Frank W; Samia, Linda; Byleckie, James J; Milburn, Michael

    2008-01-01

    To examine the level of job satisfaction and test a theoretical model of the direct and indirect effects of job satisfaction, and individual nurse and agency characteristics, on intent to stay and retention for home healthcare nurses. A descriptive correlation study of home healthcare nurses in six New England states. Home healthcare nurse job satisfaction self-report data was collected with the HHNJS survey questionnaire & Retention Survey Questionnaire. Based on a structural equation model, job tenure and job satisfaction were the strongest predictors of nurse retention. Understanding the variables associated with home healthcare nurse retention can help agencies retain nurses in a time of severe nurse shortages and increased patient demand. Predicted nursing shortages and increasing demand have made the retention of experienced, qualified nursing staff essential to assure access to high-quality home healthcare services in the future.

  2. Quality Assurance in the Presence of Variability

    NASA Astrophysics Data System (ADS)

    Lauenroth, Kim; Metzger, Andreas; Pohl, Klaus

    Software Product Line Engineering (SPLE) is a reuse-driven development paradigm that has been applied successfully in information system engineering and other domains. Quality assurance of the reusable artifacts of the product line (e.g. requirements, design, and code artifacts) is essential for successful product line engineering. As those artifacts are reused in several products, a defect in a reusable artifact can affect several products of the product line. A central challenge for quality assurance in product line engineering is how to consider product line variability. Since the reusable artifacts contain variability, quality assurance techniques from single-system engineering cannot directly be applied to those artifacts. Therefore, different strategies and techniques have been developed for quality assurance in the presence of variability. In this chapter, we describe those strategies and discuss in more detail one of those strategies, the so called comprehensive strategy. The comprehensive strategy aims at checking the quality of all possible products of the product line and thus offers the highest benefits, since it is able to uncover defects in all possible products of the product line. However, the central challenge for applying the comprehensive strategy is the complexity that results from the product line variability and the large number of potential products of a product line. In this chapter, we present one concrete technique that we have developed to implement the comprehensive strategy that addresses this challenge. The technique is based on model checking technology and allows for a comprehensive verification of domain artifacts against temporal logic properties.

  3. Quality assurance as an integrated part of the electronic medical record - a prototype applied for colonoscopy.

    PubMed

    Hoff, Geir; Ottestad, Per Marcus; Skafløtten, Stein Roger; Bretthauer, Michael; Moritz, Volker

    2009-01-01

    Electronic medical records (EMRs) have not developed much beyond the days of typewritten journals when it comes to facilitating extraction of data for quality assurance (QA) and improvement of health-care performance. Based on 5 years' experience from the Norwegian Gastronet QA programme, we have developed a highly QA-profiled EMR for colonoscopy. We used a three-tier solution (client, server and database) written in the Java programming language using a number of open-source libraries. QA principles from the Norwegian paper-based Gastronet QA programme formed the basis for development of the ColoReg software. ColoReg is developed primarily for colonoscopy reporting in a screening trial, but may be used in routine clinical work. The QA module in ColoReg is well suited for intervention towards suboptimal performance in both settings. We have developed user-friendly software dominated by clickable boxes and curtain menus reducing free text to a minimum. The software gives warnings when illogical registrations are entered and reasons have to be given for divergence from software recommendations for work-up and surveillance. At any time, defined performance quality parameters are readily accessible in tabular form with the named, logged-in endoscopist being compared with all other anonymized endoscopists in the database. The ColoReg software is developed for use in an international, multicentre trial on colonoscopy screening. It is user-friendly and secures continuous QA of the endoscopist's performance. The principles used are applicable to development of EMRs in general.

  4. Mission Operations Assurance

    NASA Technical Reports Server (NTRS)

    Faris, Grant

    2012-01-01

    Integrate the mission operations assurance function into the flight team providing: (1) value added support in identifying, mitigating, and communicating the project's risks and, (2) being an essential member of the team during the test activities, training exercises and critical flight operations.

  5. UST Financial Assurance Information

    EPA Pesticide Factsheets

    Subtitle I of the Resource Conservation and Recovery Act, as amended by the Hazardous Waste Disposal Act of 1984, brought underground storage tanks (USTs) under federal regulation. As part of that regulation, Congress directed EPA to develop financial responsibility regulations for UST owners and operators. Congress wanted owners and operators of underground storage tanks (USTs) to show that they have the financial resources to clean up a site if a release occurs, correct environmental damage, and compensate third parties for injury to their property or themselves.Owners and operators have several options: obtain insurance coverage from an insurer or a risk retention group; demonstrate self-insurance using a financial test; obtain corporate guarantees, surety bonds, or letters of credit; place the required amount into a trust fund administered by a third party; or rely on coverage provided by a state financial assurance fund.Information in this data asset includes state documentation to support this requirement. Many states have developed financial assurance funds to help owners and operators meet financial responsibility requirements and to help cover the costs of cleanups. State financial assurance fund programs, which supplement or are a substitute for private insurance, have been especially useful for small-to-medium sized petroleum marketers.EPA requires its Regional Offices to conduct annual reviews of state financial assurance funds. Data is provided by s

  6. Quality Assurance for All

    ERIC Educational Resources Information Center

    Cheung, Peter P. T.; Tsui, Cecilia B. S.

    2010-01-01

    For higher education reform, most decision-makers aspire to achieving a higher participation rate and a respectable degree of excellence with diversity at the same time. But very few know exactly how. External quality assurance is a fair basis for differentiation but there can be doubt and resistance in some quarters. Stakeholder interests differ…

  7. Quality Assurance Program Description

    SciTech Connect

    Halford, Vaughn Edward; Ryder, Ann Marie

    2017-07-01

    Effective May 1, 2017, led by a new executive leadership team, Sandia began operating within a new organizational structure. National Technology and Engineering Solutions of Sandia (Sandia’s) Quality Assurance Program (QAP) was established to assign responsibilities and authorities, define workflow policies and requirements, and provide for the performance and assessment of work.

  8. [Integrated quality assurance].

    PubMed

    Bögel, K; Stöhr, K

    1994-07-01

    The definition of terms and connotation of "Quality", "Quality Assurance" and "Integration" lead to an analysis and understanding of inhibiting and fostering factors of the "Health Triad" of people, animals and environment. Although "Quality" is largely or ultimately determined by the consumer, there are considerable differences as this term is applied by (a) the individual consumer, (b) the dynamic producer defending or gaining markets, (c) those engaged in traditional product manufacturing, or (d) governments setting (minimum) requirements for the sake of free trade. "Quality Assurance" offers cooperation of partners all along the food chain from "pasture to table". The managerial process turned into a continuum of responsibility and agreement on processes and product characteristics. This overcomes the disadvantages of strategies stressing distinct defense barriers. In practice this philosophy of a predominant role of defence barriers proved largely partnership destructive, in that it permitted to shift responsibilities for failures and to claim administrative competence according to momentary situations and interests. "Integrated Quality Assurance" means mutual agreement of two or more partners along the food chain (e. g. feed producers, farmers, animal health industry, veterinarians and food processors) on product characteristics and production methods. It involves essential system elements including facilities, materials, manpower, information, transport, management etc. Different principles and procedures of quality assurance have been introduced in practice, including agriculture and food processing. These different approaches are not mutually exclusive but largely of complementary nature.(ABSTRACT TRUNCATED AT 250 WORDS)

  9. [Smart Medicine and Healthcare].

    PubMed

    Lu, Yen-Chiao Angel; Chen, Li-Chin

    2017-08-01

    Innovation and rapid technological development in Smart Medicine or Smart Healthcare impact profoundly on many aspects of healthcare. It is believed that Health Information Technology (HIT) has the potential to improve integration between care providers, reduce administrative costs and burdens, reduce medical errors, and improve care quality and patient outcomes. However, issues such as interoperability, compatibility, and integration are critical to effectively integrating hardware and software in order to fully realize the benefits of HIT. High-end medical devices and equipment, including medical carts / mobile computer carts and wireless physiological and biomedical monitoring devices, should also be integrated into the hospital information system. Furthermore, the Data, Information, Knowledge, and Wisdom Hierarchy (DIKW) has been gaining popularity in the development of Nursing Information Systems (NIS) since 2013. To create a DIKW-based information system, data must first be defined and analyzed and then transformed into meaningful information. Eventually, this information is transformed into an intelligent system. For example, if evidence-based nursing research results / findings are integrated into the NIS to guide clinical practice, patient outcomes, patient safety, and healthcare quality will be greatly enhanced.

  10. Data systems and computer science: Software Engineering Program

    NASA Technical Reports Server (NTRS)

    Zygielbaum, Arthur I.

    1991-01-01

    An external review of the Integrated Technology Plan for the Civil Space Program is presented. This review is specifically concerned with the Software Engineering Program. The goals of the Software Engineering Program are as follows: (1) improve NASA's ability to manage development, operation, and maintenance of complex software systems; (2) decrease NASA's cost and risk in engineering complex software systems; and (3) provide technology to assure safety and reliability of software in mission critical applications.

  11. Quality assurance in digital dental imaging: a systematic review.

    PubMed

    Metsälä, Eija; Henner, Anja; Ekholm, Marja

    2014-07-01

    Doses induced by individual dental examinations are low. However, dental radiography accounts for nearly one third of the total number of radiological examinations in the European Union. Therefore, special attention is needed with regard to radiation protection. In order to lower patient doses, the staff performing dental examinations must have competence in imaging as well as in radiation protection issues. This paper presents a systematic review about the core competencies needed by the healthcare staff in performing digital dental radiological imaging quality assurance. The following databases were searched: Pubmed, Cinahl, Pro Quest and IEEXplore digital library. Also volumes of some dental imaging journals and doctoral theses of the Finnish universities educating dentists were searched. The search was performed using both MeSH terms and keywords using the option 'search all text'. The original keywords were: dental imaging, digital, x-ray, panoramic, quality, assurance, competence, competency, skills, knowledge, radiographer, radiologist technician, dentist, oral hygienist, radiation protection and their Finnish synonyms. Core competencies needed by the healthcare staff performing digital dental radiological imaging quality assurance described in the selected studies were: management of dental imaging equipment, competence in image quality and factors associated with it, dose optimization and quality assurance. In the future there will be higher doses in dental imaging due to increasing use of CBCT and digital imaging. The staff performing dental imaging must have competence in dental imaging quality assurance issues found in this review. They also have to practice ethical radiation safety culture in clinical practice.

  12. Software Program: Software Management Guidebook

    NASA Technical Reports Server (NTRS)

    1996-01-01

    The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.

  13. Proprietary software

    NASA Technical Reports Server (NTRS)

    Marnock, M. J.

    1971-01-01

    The protection of intellectual property by a patent, a copyright, or trade secrets is reviewed. The present and future use of computers and software are discussed, along with the governmental uses of software. The popularity of contractual agreements for sale or lease of computer programs and software services is also summarized.

  14. [Quality assurance in colorectal cancer in Europe AD 2011].

    PubMed

    Mroczkowski, P; Hac, S; Lippert, H; Kube, R

    2013-12-01

    Malignant tumours are the second largest cause of death in Europe. Colorectal cancer takes second place within this group and is responsible for every eighth tumour-related death. Surgical quality assurance requires a prospective observational study, any different type of study is not possible. A complete recording of all treated patients is a prerequisite for quality assurance. Currently, there are quality assurance programmes in Sweden, Norway, Denmark, Great Britain, Spain, Belgium, the Netherlands as well as the multinational study for patients from Germany, Poland and Italy. These projects deliver comprehensive information regarding the treatment of colorectal cancer. However, this information is deeply rooted in the organisation of the health-care system in the given country and is not easily transferable into international settings. Also, an interpretation of the collected data is often possible only within the given health-care system. First, unified initial diagnostics is a prerequisite for quality assurance -  for the local extent and exclusion / confirmation of distant metastases. Until these criteria are unified, any comparison is limited, including a comparison of survival. Second, quality-of-life is not recorded in any of the current projects. Third, the main focus of a quality assurance project must be on therapy-dependent factors. The most sensible method of quality control remains within the connection of preoperative diagnostics (estimate of a best-case scenario), the surgical technique (the actual result) and a standardised pathological examination (evaluation of the actual result). These parameters can be recorded and compared within a quality assurance project regardless of the limitations of the national health-care systems. There is no alternative to a unified diagnostics model and unified histopathological evaluation, a complete picture of treatment quality is also not possible without systematic analysis of the quality of life.

  15. Goal Structuring Notation in a Radiation Hardening Assurance Case for COTS-Based Spacecraft

    NASA Technical Reports Server (NTRS)

    Witulski, A.; Austin, R.; Evans, J.; Mahadevan, N.; Karsai, G.; Sierawski, B.; LaBel, K.; Reed, R.; Schrimpf, R.

    2016-01-01

    A systematic approach is presented to constructing a radiation assurance case using Goal Structuring Notation (GSN) for spacecraft containing COTS parts. The GSN paradigm is applied to an SRAM single-event upset experiment board designed to fly on a CubeSat in January 2017. A custom software language for development of a GSN assurance case is under development at Vanderbilt. Construction of a radiation assurance case without use of hardened parts or extensive radiation testing is discussed.

  16. Addressing software security risk mitigations in the life cycle

    NASA Technical Reports Server (NTRS)

    Gilliam, David; Powell, John; Haugh, Eric; Bishop, Matt

    2003-01-01

    The NASA Office of Safety and Mission Assurance (OSMA) has funded the Jet Propulsion Laboratory (JPL) with a Center Initiative, 'Reducing Software Security Risk through an Integrated Approach' (RSSR), to address this need. The Initiative is a formal approach to addressing software security in the life cycle through the instantiation of a Software Security Assessment Instrument (SSAI) for the development and maintenance life cycles.

  17. Mission assurance increased with regression testing

    NASA Astrophysics Data System (ADS)

    Lang, R.; Spezio, M.

    Knowing what to test is an important attribute in any testing campaign, especially when it has to be right or the mission could be in jeopardy. The New Horizons mission, developed and operated by the John Hopkins University Applied Physics Laboratory, received a planned major upgrade to their Mission Operations and Control (MOC) ground system architecture. Early in the mission planning it was recognized that the ground system platform would require an upgrade to assure continued support of technology used for spacecraft operations. With the planned update to the six year operational ground architecture from Solaris 8 to Solaris 10, it was critical that the new architecture maintain critical operations and control functions. The New Horizons spacecraft is heading to its historic rendezvous with Pluto in July 2015 and then proceeding into the Kuiper Belt. This paper discusses the Independent Software Acceptance Testing (ISAT) Regression test campaign that played a critical role to assure the continued success of the New Horizons mission. The New Horizons ISAT process was designed to assure all the requirements were being met for the ground software functions developed to support the mission objectives. The ISAT team developed a test plan with a series of test case designs. The test objectives were to verify that the software developed from the requirements functioned as expected in the operational environment. As the test cases were developed and executed, a regression test suite was identified at the functional level. This regression test suite would serve as a crucial resource in assuring the operational system continued to function as required with such a large scale change being introduced. Some of the New Horizons ground software changes required modifications to the most critical functions of the operational software. Of particular concern was the new MOC architecture (Solaris 10) is Intel based and little endian, and the legacy architecture (Solaris 8) was SPA

  18. Mission Assurance Modeling and Simulation: A Cyber Security Roadmap

    NASA Technical Reports Server (NTRS)

    Gendron, Gerald; Roberts, David; Poole, Donold; Aquino, Anna

    2012-01-01

    This paper proposes a cyber security modeling and simulation roadmap to enhance mission assurance governance and establish risk reduction processes within constrained budgets. The term mission assurance stems from risk management work by Carnegie Mellon's Software Engineering Institute in the late 19905. By 2010, the Defense Information Systems Agency revised its cyber strategy and established the Program Executive Officer-Mission Assurance. This highlights a shift from simply protecting data to balancing risk and begins a necessary dialogue to establish a cyber security roadmap. The Military Operations Research Society has recommended a cyber community of practice, recognizing there are too few professionals having both cyber and analytic experience. The authors characterize the limited body of knowledge in this symbiotic relationship. This paper identifies operational and research requirements for mission assurance M&S supporting defense and homeland security. M&S techniques are needed for enterprise oversight of cyber investments, test and evaluation, policy, training, and analysis.

  19. Implementing Software Safety in the NASA Environment

    NASA Technical Reports Server (NTRS)

    Wetherholt, Martha S.; Radley, Charles F.

    1994-01-01

    Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of

  20. Improving the Agency's Software Acquisition Capability

    NASA Technical Reports Server (NTRS)

    Hankinson, Allen

    2003-01-01

    External development of software has oftc n led to unsatisfactory results and great frustration for the assurE 7ce community. Contracts frequently omit critical assuranc 4 processes or the right to oversee software development activitie: At a time when NASA depends more and more on software to in plement critical system functions, combination of three factors ex; cerbate this problem: I ) the ever-increasing trend to acquire rather than develop software in-house, 2) the trend toward performance based contracts, and 3) acquisition vehicles that only state softwar 2 requirements while leaving development standards and assur! ince methodologies up to the contractor. We propose to identify specific methods at d tools that NASA projects can use to mitigate the adverse el ects of the three problems. TWO broad classes of methoddt ols will be explored. The first will be those that provide NASA p ojects with insight and oversight into contractors' activities. The st cond will be those that help projects objectively assess, and thus i nprwe, their software acquisition capability. Of particular interest is the Software Engineering Institute's (SEI) Software Acqt isition Capability Maturity Model (SA-CMMO).

  1. Technical Editing as Quality Assurance: Adding Value to Content.

    ERIC Educational Resources Information Center

    Corbin, Michelle; Moell, Pat; Boyd Mike

    2002-01-01

    Reviews typical software testing activities and then compares those activities to technical editing activities. Shows that by providing quality assurance through content editing, technical editors add value to the information development process and help give users the quality content they deserve. Concludes that product information must go…

  2. Support for Quality Assurance in End-User Systems.

    ERIC Educational Resources Information Center

    Klepper, Robert; McKenna, Edward G.

    1989-01-01

    Suggests an approach that organizations can take to provide centralized support services for quality assurance in end-user information systems, based on the experiences of a support group at Citicorp Mortgage, Inc. The functions of the support group include user education, software selection, and assistance in testing, implementation, and support…

  3. A Practical Approach to High Assurance Multilevel Secure Computing Service

    DTIC Science & Technology

    1994-12-01

    arounds such as "air-gaps" and " sneaker -nets" were tolerated. Centralized MLS computing service naturally seemed highly desirable, and it seemed only a...late 1970’s through the early 1990’s, then, several trends were evident: hardware was cheap and getting cheaper, software (at least high assurance

  4. Quality Assurance Model for Digital Adult Education Materials

    ERIC Educational Resources Information Center

    Dimou, Helen; Kameas, Achilles

    2016-01-01

    Purpose: This paper aims to present a model for the quality assurance of digital educational material that is appropriate for adult education. The proposed model adopts the software quality standard ISO/IEC 9126 and takes into account adult learning theories, Bloom's taxonomy of learning objectives and two instructional design models: Kolb's model…

  5. 7 Processes that Enable NASA Software Engineering Technologies: Value-Added Process Engineering

    NASA Technical Reports Server (NTRS)

    Housch, Helen; Godfrey, Sally

    2011-01-01

    The presentation reviews Agency process requirements and the purpose, benefits, and experiences or seven software engineering processes. The processes include: product integration, configuration management, verification, software assurance, measurement and analysis, requirements management, and planning and monitoring.

  6. The quality assurance liaison: Combined technical and quality assurance support

    SciTech Connect

    Bolivar, S.L.; Day, J.L.

    1993-03-01

    This paper describes the role of the quality assurance liaison, the responsibilities of this position, and the evolutionary changes in duties over the last six years. The role of the quality assurance liaison has had a very positive impact on the Los Alamos Yucca Mountain Site Characterization (YW) quality assurance program. Having both technical and quality assurance expertise, the quality assurance liaisons are able to facilitate communications with scientists on quality assurance issues and requirements, thereby generating greater productivity in scientific investigations. The quality assurance liaisons help ensure that the scientific community knows and implements existing requirements, is aware ofmore » new or changing regulations, and is able to conduct scientific work within Project requirements. The influence of the role of the quality assurance liaison can be measured by an overall improvement in attitude of the staff regarding quality assurance requirements and improved job performance, as well as a decrease in deficiencies identified during both internal and external audits and surveillances. This has resulted in a more effective implementation of quality assurance requirements.« less

  7. The quality assurance liaison: Combined technical and quality assurance support

    NASA Astrophysics Data System (ADS)

    Bolivar, S. L.; Day, J. L.

    1993-03-01

    The role of the quality assurance liaison, the responsibilities of this position, and the evolutionary changes in duties over the last six years are described. The role of the quality assurance liaison has had a very positive impact on the Los Alamos Yucca Mountain Site Characterization (YW) quality assurance program. Having both technical and quality assurance expertise, the quality assurance liaisons are able to facilitate communications with scientists on quality assurance issues and requirements, thereby generating greater productivity in scientific investigations. The quality assurance liaisons help ensure that the scientific community knows and implements existing requirements, is aware of new or changing regulations, and is able to conduct scientific work within Project requirements. The influence of the role of the quality assurance liaison can be measured by an overall improvement in attitude of the staff regarding quality assurance requirements and improved job performance, as well as a decrease in deficiencies identified during both internal and external audits and surveillances. This has resulted in a more effective implementation of quality assurance requirements.

  8. Healthcare system simulation using Witness

    NASA Astrophysics Data System (ADS)

    Khakdaman, Masoud; Zeinahvazi, Milad; Zohoori, Bahareh; Nasiri, Fardokht; Yew Wong, Kuan

    2013-02-01

    Simulation techniques have a proven track record in manufacturing industry as well as other areas such as healthcare system improvement. In this study, simulation model of a health center in Malaysia is developed through the application of WITNESS simulation software which has shown its flexibility and capability in manufacturing industry. Modelling procedure is started through process mapping and data collection and continued with model development, verification, validation and experimentation. At the end, final results and possible future improvements are demonstrated.

  9. Software for Analyzing Laminar-to-Turbulent Flow Transitions

    NASA Technical Reports Server (NTRS)

    Chang, Chau-Lyan

    2004-01-01

    Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software. This is achieved by combining two prior programs in an innovative manner

  10. Software safety

    NASA Technical Reports Server (NTRS)

    Leveson, Nancy

    1987-01-01

    Software safety and its relationship to other qualities are discussed. It is shown that standard reliability and fault tolerance techniques will not solve the safety problem for the present. A new attitude requires: looking at what you do NOT want software to do along with what you want it to do; and assuming things will go wrong. New procedures and changes to entire software development process are necessary: special software safety analysis techniques are needed; and design techniques, especially eliminating complexity, can be very helpful.

  11. Software Development Standard Processes (SDSP)

    NASA Technical Reports Server (NTRS)

    Lavin, Milton L.; Wang, James J.; Morillo, Ronald; Mayer, John T.; Jamshidian, Barzia; Shimizu, Kenneth J.; Wilkinson, Belinda M.; Hihn, Jairus M.; Borgen, Rosana B.; Meyer, Kenneth N.; hide

    2011-01-01

    A JPL-created set of standard processes is to be used throughout the lifecycle of software development. These SDSPs cover a range of activities, from management and engineering activities, to assurance and support activities. These processes must be applied to software tasks per a prescribed set of procedures. JPL s Software Quality Improvement Project is currently working at the behest of the JPL Software Process Owner to ensure that all applicable software tasks follow these procedures. The SDSPs are captured as a set of 22 standards in JPL s software process domain. They were developed in-house at JPL by a number of Subject Matter Experts (SMEs) residing primarily within the Engineering and Science Directorate, but also from the Business Operations Directorate and Safety and Mission Success Directorate. These practices include not only currently performed best practices, but also JPL-desired future practices in key thrust areas like software architecting and software reuse analysis. Additionally, these SDSPs conform to many standards and requirements to which JPL projects are beholden.

  12. Integrated Measurement and Analysis Framework for Software Security

    DTIC Science & Technology

    2010-09-01

    com/ Open Web Application Security Project ( OWASP ) Software Assurance Maturity Model (SAMM): http://www.owasp.org/index.php...for software security include the following, taken from the OWASP SAMM, version 1.0 [OpenSAMM 2009]: >90 percent applications and data assets... methodologies and techniques. Measuring Cyber Security and Information Assurance: State-of-the-Art Report (SOAR) [Bar- tol 2009]. This report assesses

  13. MoniQA: a general approach to monitor quality assurance

    NASA Astrophysics Data System (ADS)

    Jacobs, J.; Deprez, T.; Marchal, G.; Bosmans, H.

    2006-03-01

    MoniQA ("Monitor Quality Assurance") is a new, non-commercial, independent quality assurance software application developed in our medical physics team. It is a complete Java TM - based modular environment for the evaluation of radiological viewing devices and it thus fits in the global quality assurance network of our (film less) radiology department. The purpose of the software tool is to guide the medical physicist through an acceptance protocol and the radiologist through a constancy check protocol by presentation of the necessary test patterns and by automated data collection. Data are then sent to a central management system for further analysis. At the moment more than 55 patterns have been implemented, which can be grouped in schemes to implement protocols (i.e. AAPMtg18, DIN and EUREF). Some test patterns are dynamically created and 'drawn' on the viewing device with random parameters as is the case in a recently proposed new pattern for constancy testing. The software is installed on 35 diagnostic stations (70 monitors) in a film less radiology department. Learning time was very limited. A constancy check -with the new pattern that assesses luminance decrease, resolution problems and geometric distortion- takes only 2 minutes and 28 seconds per monitor. The modular approach of the software allows the evaluation of new or emerging test patterns. We will report on the software and its usability: practicality of the constancy check tests in our hospital and on the results from acceptance tests of viewing stations for digital mammography.

  14. Software Reviews.

    ERIC Educational Resources Information Center

    Miller, Anne, Ed.; Radziemski, Cathy, Ed.

    1988-01-01

    Reviews two software packages for the Macintosh series. "Course Builder 2.0," a courseware authoring system, allows the user to create programs which stand alone and may be used independently in the classroom. "World Builder," an artificial intelligence software package, allows creative thinking, problem-solving, and…

  15. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Stephen

    1988-01-01

    Presents reviews of six computer software programs for teaching science. Provides the publisher, grade level, cost, and descriptions of software, including: (1) "Recycling Logic"; (2) "Introduction to Biochemistry"; (3) "Food for Thought"; (4) "Watts in a Home"; (5) "Geology in Action"; and (6)…

  16. Health software: a new CEI Guide for software management in medical environment.

    PubMed

    Giacomozzi, Claudia; Martelli, Francesco

    2016-01-01

    The increasing spread of software components in the healthcare context renders explanatory guides relevant and mandatory to interpret laws and standards, and to support safe management of software products in healthcare. In 2012 a working group has been settled for the above purposes at Italian Electrotechnical Committee (CEI), made of experts from Italian National Institute of Health (ISS), representatives of industry, and representatives of the healthcare organizations. As a first outcome of the group activity, Guide CEI 62-237 was published in February 2015. The Guide incorporates an innovative approach based on the proper contextualization of software products, either medical devices or not, to the specific healthcare scenario, and addresses the risk management of IT systems. The Guide provides operators and manufacturers with an interpretative support with many detailed examples to facilitate the proper contextualization and management of health software, in compliance with related European and international regulations and standards.

  17. Predicting Software Assurance Using Quality and Reliability Measures

    DTIC Science & Technology

    2014-12-01

    errors are not found in unit testing . The rework effort to correct requirement and design problems in later phases can be as high as 300 to 1,000...Literature 31 Appendix B: Quality Cannot Be Tested In 35 Bibliography 38 CMU/SEI-2014-TN-026 | ii CMU/SEI-2014-TN-026 | iii List of Figures...Removal Densities During Development 10 Figure 8: Quality and Security-Focused Workflow 14 Figure 9: Testing Reliability Results for the Largest Project

  18. Prospects for Evidence -Based Software Assurance: Models and Analysis

    DTIC Science & Technology

    2015-09-01

    virtual machine is much lighter than the workstation. The virtual machine doesn’t need to run anti-virus, firewalls, intrusion preven- tion systems...analysis of malicious shellcode. In Proceedings of the 14th international conference on Recent Advances in Intrusion Detection (Berlin, Heidelberg, 2011...correctness of compilation theo- rem below. Together, this implies that derivation of the compilation judgement produces an internal term that does not go

  19. Software Assurance Curriculum Project Volume 2: Undergraduate Course Outlines

    DTIC Science & Technology

    2010-08-01

    acquisition through methods including service-oriented architecture ( SOA ), cloud computing, and virtualization. Systems often aggregate combinations of...presentations, team projects, and exams . Projects and exams should be weighted heavily. Depending on the degree program, this course could be slanted to

  20. Software Quality Assurance and the Fleet Material Support Environment.

    DTIC Science & Technology

    1982-06-01

    D. AMDAHL . . .. ... ......... .. 79 1. Drganizatrin . . . . . . .. o.....80 5t 2. Devel paent Interfaze . . . . . . . . . . 80 3. Operations... interfazes , there is still another built-in device for insu-ing quality products. 77 A Review and Inspection process (RSIe is carried cut by the programmers

  1. Application of Domain Knowledge to Software Quality Assurance

    NASA Technical Reports Server (NTRS)

    Wild, Christian W.

    1997-01-01

    This work focused on capturing, using, and evolving a qualitative decision support structure across the life cycle of a project. The particular application of this study was towards business process reengineering and the representation of the business process in a set of Business Rules (BR). In this work, we defined a decision model which captured the qualitative decision deliberation process. It represented arguments both for and against proposed alternatives to a problem. It was felt that the subjective nature of many critical business policy decisions required a qualitative modeling approach similar to that of Lee and Mylopoulos. While previous work was limited almost exclusively to the decision capture phase, which occurs early in the project life cycle, we investigated the use of such a model during the later stages as well. One of our significant developments was the use of the decision model during the operational phase of a project. By operational phase, we mean the phase in which the system or set of policies which were earlier decided are deployed and put into practice. By making the decision model available to operational decision makers, they would have access to the arguments pro and con for a variety of actions and can thus make a more informed decision which balances the often conflicting criteria by which the value of action is measured. We also developed the concept of a 'monitored decision' in which metrics of performance were identified during the decision making process and used to evaluate the quality of that decision. It is important to monitor those decision which seem at highest risk of not meeting their stated objectives. Operational decisions are also potentially high risk decisions. Finally, we investigated the use of performance metrics for monitored decisions and audit logs of operational decisions in order to feed an evolutionary phase of the the life cycle. During evolution, decisions are revisisted, assumptions verified or refuted, and possible reassessments resulting in new policy are made. In this regard we implemented a machine learning algorithm which automatically defined business rules based on expert assessment of the quality of operational decisions as recorded during deployment.

  2. Agile Software Development in Defense Acquisition: A Mission Assurance Perspective

    DTIC Science & Technology

    2012-03-23

    the actual user and customer 16 @AEROSPACE v^ Acquisition is a Contact Sport ... • Because of different motivation and behavior, there is a...Evaluation Plan ( IOT &EP) prior to Milestone B Clearly, the DAPA panel valued stability and predictability as opposed to agility * There were more...Development IOT &EP Initial Operational Testing & Evaluation Plan IT Information Technology IV&V Independent Verification & Validation JCIDS Joint

  3. Prototype Software Assurance Framework (SAF): Introduction and Overview

    DTIC Science & Technology

    2017-04-05

    Introduction 1 1 Process Management (Category 1) 6 1.1 Process Definition (Area 1.1) 6 1.2 Infrastructure Standards (Area 1.2) 6 1.3 Resources (Area 1.3) 7...5.1 Gap Analysis 20 5.2 Process Improvement 21 5.3 Metrics 23 6 Summary 26 Appendix SAF, v0.2 27 References 35 CMU/SEI-2017-TN-001...release and unlimited distribution. List of Tables Table 1: Example Cybersecurity Practices and Artifacts 4 Table 2: Process Definition Practices

  4. Software Security Assurance: A State-of-Art Report (SAR)

    DTIC Science & Technology

    2007-07-31

    Engineering: Advances and Future Visions, Idea (Group Publishing, 2007). X. Ge, R.F. Paige, F.A.C. Polack , H. Chivers and P.J. Brooke, “Agile Development of...207] For Further Reading Jan Jürjens publications page. Available from: http://www4.in.tum.de/~juerjens/publications.html C. B. Haley, R. C. Laney...SOAR) 26 Context.5 Assumptions and Constraints. Section 7 Resources u Jan Jürjens, Secure Systems Development With UML (Springer, 2004). u Jack

  5. Evidence of Absence software

    USGS Publications Warehouse

    Dalthorp, Daniel; Huso, Manuela M. P.; Dail, David; Kenyon, Jessica

    2014-01-01

    Evidence of Absence software (EoA) is a user-friendly application used for estimating bird and bat fatalities at wind farms and designing search protocols. The software is particularly useful in addressing whether the number of fatalities has exceeded a given threshold and what search parameters are needed to give assurance that thresholds were not exceeded. The software is applicable even when zero carcasses have been found in searches. Depending on the effectiveness of the searches, such an absence of evidence of mortality may or may not be strong evidence that few fatalities occurred. Under a search protocol in which carcasses are detected with nearly 100 percent certainty, finding zero carcasses would be convincing evidence that overall mortality rate was near zero. By contrast, with a less effective search protocol with low probability of detecting a carcass, finding zero carcasses does not rule out the possibility that large numbers of animals were killed but not detected in the searches. EoA uses information about the search process and scavenging rates to estimate detection probabilities to determine a maximum credible number of fatalities, even when zero or few carcasses are observed.

  6. Future Software Sizing Metrics and Estimation Challenges

    DTIC Science & Technology

    2011-07-01

    systems 4. Ultrahigh software system assurance 5. Legacy maintenance and Brownfield development 6. Agile and Lean/ Kanban development. This paper...refined as the design of the maintenance modifications or Brownfield re-engineering is determined. VII. 6. AGILE AND LEAN/ KANBAN DEVELOPMENT The...difficulties of software maintenance estimation can often be mitigated by using lean workflow management techniques such as Kanban [25]. In Kanban

  7. Software Validation via Model Animation

    NASA Technical Reports Server (NTRS)

    Dutle, Aaron M.; Munoz, Cesar A.; Narkawicz, Anthony J.; Butler, Ricky W.

    2015-01-01

    This paper explores a new approach to validating software implementations that have been produced from formally-verified algorithms. Although visual inspection gives some confidence that the implementations faithfully reflect the formal models, it does not provide complete assurance that the software is correct. The proposed approach, which is based on animation of formal specifications, compares the outputs computed by the software implementations on a given suite of input values to the outputs computed by the formal models on the same inputs, and determines if they are equal up to a given tolerance. The approach is illustrated on a prototype air traffic management system that computes simple kinematic trajectories for aircraft. Proofs for the mathematical models of the system's algorithms are carried out in the Prototype Verification System (PVS). The animation tool PVSio is used to evaluate the formal models on a set of randomly generated test cases. Output values computed by PVSio are compared against output values computed by the actual software. This comparison improves the assurance that the translation from formal models to code is faithful and that, for example, floating point errors do not greatly affect correctness and safety properties.

  8. High-Assurance Spiral

    DTIC Science & Technology

    2017-11-01

    Public Release; Distribution Unlimited. PA# 88ABW-2017-5388 Date Cleared: 30 OCT 2017 13. SUPPLEMENTARY NOTES 14. ABSTRACT Cyber-physical systems ...CPS) ranging from critical infrastructures such as power plants, to modern (semi) autonomous vehicles are systems that use software to control...resulting implementations. 15. SUBJECT TERMS Cyber-physical systems , Formal guarantees, Code generation 16. SECURITY CLASSIFICATION OF: 17

  9. Concurrent Information Assurance Architecture

    DTIC Science & Technology

    2002-08-01

    Used for C-IAA collaboration between OversightNets and OverNets, as well as OverNet hierarchy. Project: MSME : Multidimensional Security Management...person A owns bank account X, drove to city Y to meet person B, exchanged item C.” Many companies provide fraud consulting and software, such as

  10. Software Reviews.

    ERIC Educational Resources Information Center

    Miller, Anne, Ed.; Radziemski, Cathy, Ed.

    1988-01-01

    Three pieces of computer software are described and reviewed: HyperCard, to build and use varied applications; Iggy's Gnees, for problem solving with shapes in grades kindergarten-two; and Algebra Shop, for practicing skills and problem solving. (MNS)

  11. Software Reviews.

    ERIC Educational Resources Information Center

    Classroom Computer Learning, 1990

    1990-01-01

    Reviewed are three computer software packages including "Martin Luther King, Jr.: Instant Replay of History,""Weeds to Trees," and "The New Print Shop, School Edition." Discussed are hardware requirements, costs, grade levels, availability, emphasis, strengths, and weaknesses. (CW)

  12. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Stephen, Ed.

    1987-01-01

    Provides a review of four science software programs. Includes topics such as plate tectonics, laboratory experiment simulations, the human body, and light and temperature. Contains information on ordering and reviewers' comments. (ML)

  13. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Stephen, Ed.

    1988-01-01

    Reviews seven instructional software packages covering a variety of topics. Includes: "Science Square-Off"; "The Desert"; "Science Courseware: Physical Science"; "Odell Lake"; "Safety First"; "An Experience in Artificial Intelligence"; and "Master Mapper." (TW)

  14. Software Reviews.

    ERIC Educational Resources Information Center

    Davis, Shelly J., Ed.; Knaupp, Jon, Ed.

    1984-01-01

    Reviewed is computer software on: (1) classification of living things, a tutorial program for grades 5-10; and (2) polynomial practice using tiles, a drill-and-practice program for algebra students. (MNS)

  15. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Eugene T., Ed.

    1988-01-01

    Presents reviews by classroom teachers of software for teaching science. Includes material on the work of geologists, genetics, earth science, classification of living things, astronomy, endangered species, skeleton, drugs, and heartbeat. Provides information on availability and equipment needed. (RT)

  16. Software Reviews.

    ERIC Educational Resources Information Center

    Kimball, Jeffrey P.; And Others

    1987-01-01

    Describes a variety of computer software. The packages reviewed include a variety of simulations, a spread sheet, a printer driver and an alternative operating system for DBM.PCs and compatible programs. (BSR)

  17. Software Reviews.

    ERIC Educational Resources Information Center

    Slatta, Richard W. And Others

    1987-01-01

    Describes a variety of computer software. Subjects reviewed include history simulations and wordprocessing programs. Some of the eleven packages reviewed are Thog, North Utilities, HBJ Writer, Textra, Pro-cite, and Simulation Construction Kit. (BSR)

  18. Software Reviews.

    ERIC Educational Resources Information Center

    Dwyer, Donna; And Others

    1989-01-01

    Reviewed are seven software packages for Apple and IBM computers. Included are: "Toxicology"; "Science Corner: Space Probe"; "Alcohol and Pregnancy"; "Science Tool Kit Plus"; Computer Investigations: Plant Growth"; "Climatrolls"; and "Animal Watch: Whales." (CW)

  19. Software Reviews.

    ERIC Educational Resources Information Center

    McGrath, Diane

    1990-01-01

    Reviews two programs: (1) "The Weather Machine" on understanding weather and weather forecasting and (2) "The Mystery of the Hotel Victoria" on problem solving in mathematics. Presents the descriptions, advantages, and weaknesses of the software. (YP)

  20. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Stephen, Ed.

    1990-01-01

    Reviewed are six computer software packages including "Lunar Greenhouse,""Dyno-Quest,""How Weather Works,""Animal Trackers,""Personal Science Laboratory," and "The Skeletal and Muscular Systems." Availability, functional, and hardware requirements are discussed. (CW)

  1. Improving Individual Acceptance of Health Clouds through Confidentiality Assurance.

    PubMed

    Ermakova, Tatiana; Fabian, Benjamin; Zarnekow, Rüdiger

    2016-10-26

    Cloud computing promises to essentially improve healthcare delivery performance. However, shifting sensitive medical records to third-party cloud providers could create an adoption hurdle because of security and privacy concerns. This study examines the effect of confidentiality assurance in a cloud-computing environment on individuals' willingness to accept the infrastructure for inter-organizational sharing of medical data. We empirically investigate our research question by a survey with over 260 full responses. For the setting with a high confidentiality assurance, we base on a recent multi-cloud architecture which provides very high confidentiality assurance through a secret-sharing mechanism: Health information is cryptographically encoded and distributed in a way that no single and no small group of cloud providers is able to decode it. Our results indicate the importance of confidentiality assurance in individuals' acceptance of health clouds for sensitive medical data. Specifically, this finding holds for a variety of practically relevant circumstances, i.e., in the absence and despite the presence of conventional offline alternatives and along with pseudonymization. On the other hand, we do not find support for the effect of confidentiality assurance in individuals' acceptance of health clouds for non-sensitive medical data. These results could support the process of privacy engineering for health-cloud solutions.

  2. Improving Individual Acceptance of Health Clouds through Confidentiality Assurance

    PubMed Central

    Fabian, Benjamin; Zarnekow, Rüdiger

    2016-01-01

    Summary Background Cloud computing promises to essentially improve healthcare delivery performance. However, shifting sensitive medical records to third-party cloud providers could create an adoption hurdle because of security and privacy concerns. Objectives This study examines the effect of confidentiality assurance in a cloud-computing environment on individuals’ willingness to accept the infrastructure for inter-organizational sharing of medical data. Methods We empirically investigate our research question by a survey with over 260 full responses. For the setting with a high confidentiality assurance, we base on a recent multi-cloud architecture which provides very high confidentiality assurance through a secret-sharing mechanism: Health information is cryptographically encoded and distributed in a way that no single and no small group of cloud providers is able to decode it. Results Our results indicate the importance of confidentiality assurance in individuals’ acceptance of health clouds for sensitive medical data. Specifically, this finding holds for a variety of practically relevant circumstances, i.e., in the absence and despite the presence of conventional offline alternatives and along with pseudonymization. On the other hand, we do not find support for the effect of confidentiality assurance in individuals’ acceptance of health clouds for non-sensitive medical data. These results could support the process of privacy engineering for health-cloud solutions. PMID:27781238

  3. Assured Crew Return Vehicle

    NASA Technical Reports Server (NTRS)

    Stone, D. A.; Craig, J. W.; Drone, B.; Gerlach, R. H.; Williams, R. J.

    1991-01-01

    The developmental status is discussed regarding the 'lifeboat' vehicle to enhance the safety of the crew on the Space Station Freedom (SSF). NASA's Assured Crew Return Vehicle (ACRV) is intended to provide a means for returning the SSF crew to earth at all times. The 'lifeboat' philosophy is the key to managing the development of the ACRV which further depends on matrixed support and total quality management for implementation. The risk of SSF mission scenarios are related to selected ACRV mission requirements, and the system and vehicle designs are related to these precepts. Four possible ACRV configurations are mentioned including the lifting-body, Apollo shape, Discoverer shape, and a new lift-to-drag concept. The SCRAM design concept is discussed in detail with attention to the 'lifeboat' philosophy and requirements for implementation.

  4. Printed Circuit Board Quality Assurance

    NASA Technical Reports Server (NTRS)

    Sood, Bhanu

    2016-01-01

    PCB Assurance Summary: PCB assurance actives are informed by risk in context of the Project. Lessons are being applied across Projects for continuous improvements. Newer component technologies, smaller/high pitch devices: tighter and more demanding PCB designs: Identifying new research areas. New materials, designs, structures and test methods.

  5. Recent Trends in Quality Assurance

    ERIC Educational Resources Information Center

    Amaral, Alberto; Rosa, Maria Joao

    2010-01-01

    In this paper we present a brief description of the evolution of quality assurance in Europe, paying particular attention to its relationship to the rising loss of trust in higher education institutions. We finalise by analysing the role of the European Commission in the setting up of new quality assurance mechanisms that tend to promote…

  6. Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

    NASA Technical Reports Server (NTRS)

    Fitz, Rhonda

    2016-01-01

    Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission

  7. Quality assurance needs for modern image-based radiotherapy: recommendations from 2007 interorganizational symposium on "quality assurance of radiation therapy: challenges of advanced technology".

    PubMed

    Williamson, Jeffrey F; Dunscombe, Peter B; Sharpe, Michael B; Thomadsen, Bruce R; Purdy, James A; Deye, James A

    2008-01-01

    This report summarizes the consensus findings and recommendations emerging from 2007 Symposium, "Quality Assurance of Radiation Therapy: Challenges of Advanced Technology." The Symposium was held in Dallas February 20-22, 2007. The 3-day program, which was sponsored jointly by the American Society for Therapeutic Radiology and Oncology (ASTRO), American Association of Physicists in Medicine (AAPM), and National Cancer Institute (NCI), included >40 invited speakers from the radiation oncology and industrial engineering/human factor communities and attracted nearly 350 attendees, mostly medical physicists. A summary of the major findings follows. The current process of developing consensus recommendations for prescriptive quality assurance (QA) tests remains valid for many of the devices and software systems used in modern radiotherapy (RT), although for some technologies, QA guidance is incomplete or out of date. The current approach to QA does not seem feasible for image-based planning, image-guided therapies, or computer-controlled therapy. In these areas, additional scientific investigation and innovative approaches are needed to manage risk and mitigate errors, including a better balance between mitigating the risk of catastrophic error and maintaining treatment quality, complimenting the current device-centered QA perspective by a more process-centered approach, and broadening community participation in QA guidance formulation and implementation. Industrial engineers and human factor experts can make significant contributions toward advancing a broader, more process-oriented, risk-based formulation of RT QA. Healthcare administrators need to appropriately increase personnel and ancillary equipment resources, as well as capital resources, when new advanced technology RT modalities are implemented. The pace of formalizing clinical physics training must rapidly increase to provide an adequately trained physics workforce for advanced technology RT. The specific

  8. Software engineering

    NASA Technical Reports Server (NTRS)

    Fridge, Ernest M., III; Hiott, Jim; Golej, Jim; Plumb, Allan

    1993-01-01

    Today's software systems generally use obsolete technology, are not integrated properly with other software systems, and are difficult and costly to maintain. The discipline of reverse engineering is becoming prominent as organizations try to move their systems up to more modern and maintainable technology in a cost effective manner. The Johnson Space Center (JSC) created a significant set of tools to develop and maintain FORTRAN and C code during development of the space shuttle. This tool set forms the basis for an integrated environment to reengineer existing code into modern software engineering structures which are then easier and less costly to maintain and which allow a fairly straightforward translation into other target languages. The environment will support these structures and practices even in areas where the language definition and compilers do not enforce good software engineering. The knowledge and data captured using the reverse engineering tools is passed to standard forward engineering tools to redesign or perform major upgrades to software systems in a much more cost effective manner than using older technologies. The latest release of the environment was in Feb. 1992.

  9. Software reengineering

    NASA Technical Reports Server (NTRS)

    Fridge, Ernest M., III

    1991-01-01

    Today's software systems generally use obsolete technology, are not integrated properly with other software systems, and are difficult and costly to maintain. The discipline of reverse engineering is becoming prominent as organizations try to move their systems up to more modern and maintainable technology in a cost effective manner. JSC created a significant set of tools to develop and maintain FORTRAN and C code during development of the Space Shuttle. This tool set forms the basis for an integrated environment to re-engineer existing code into modern software engineering structures which are then easier and less costly to maintain and which allow a fairly straightforward translation into other target languages. The environment will support these structures and practices even in areas where the language definition and compilers do not enforce good software engineering. The knowledge and data captured using the reverse engineering tools is passed to standard forward engineering tools to redesign or perform major upgrades to software systems in a much more cost effective manner than using older technologies. A beta vision of the environment was released in Mar. 1991. The commercial potential for such re-engineering tools is very great. CASE TRENDS magazine reported it to be the primary concern of over four hundred of the top MIS executives.

  10. Report of AAPM TG 135: quality assurance for robotic radiosurgery.

    PubMed

    Dieterich, Sonja; Cavedon, Carlo; Chuang, Cynthia F; Cohen, Alan B; Garrett, Jeffrey A; Lee, Charles L; Lowenstein, Jessica R; d'Souza, Maximian F; Taylor, David D; Wu, Xiaodong; Yu, Cheng

    2011-06-01

    The task group (TG) for quality assurance for robotic radiosurgery was formed by the American Association of Physicists in Medicine's Science Council under the direction of the Radiation Therapy Committee and the Quality Assurance (QA) Subcommittee. The task group (TG-135) had three main charges: (1) To make recommendations on a code of practice for Robotic Radiosurgery QA; (2) To make recommendations on quality assurance and dosimetric verification techniques, especially in regard to real-time respiratory motion tracking software; (3) To make recommendations on issues which require further research and development. This report provides a general functional overview of the only clinically implemented robotic radiosurgery device, the CyberKnife. This report includes sections on device components and their individual component QA recommendations, followed by a section on the QA requirements for integrated systems. Examples of checklists for daily, monthly, annual, and upgrade QA are given as guidance for medical physicists. Areas in which QA procedures are still under development are discussed.

  11. Control Software

    NASA Technical Reports Server (NTRS)

    1997-01-01

    Real-Time Innovations, Inc. (RTI) collaborated with Ames Research Center, the Jet Propulsion Laboratory and Stanford University to leverage NASA research to produce ControlShell software. RTI is the first "graduate" of Ames Research Center's Technology Commercialization Center. The ControlShell system was used extensively on a cooperative project to enhance the capabilities of a Russian-built Marsokhod rover being evaluated for eventual flight to Mars. RTI's ControlShell is complex, real-time command and control software, capable of processing information and controlling mechanical devices. One ControlShell tool is StethoScope. As a real-time data collection and display tool, StethoScope allows a user to see how a program is running without changing its execution. RTI has successfully applied its software savvy in other arenas, such as telecommunications, networking, video editing, semiconductor manufacturing, automobile systems, and medical imaging.

  12. Antiterrorist Software

    NASA Technical Reports Server (NTRS)

    Clark, David A.

    1998-01-01

    In light of the escalation of terrorism, the Department of Defense spearheaded the development of new antiterrorist software for all Government agencies by issuing a Broad Agency Announcement to solicit proposals. This Government-wide competition resulted in a team that includes NASA Lewis Research Center's Computer Services Division, who will develop the graphical user interface (GUI) and test it in their usability lab. The team launched a program entitled Joint Sphere of Security (JSOS), crafted a design architecture (see the following figure), and is testing the interface. This software system has a state-ofthe- art, object-oriented architecture, with a main kernel composed of the Dynamic Information Architecture System (DIAS) developed by Argonne National Laboratory. DIAS will be used as the software "breadboard" for assembling the components of explosions, such as blast and collapse simulations.

  13. 2001 Industry Studies: Healthcare

    DTIC Science & Technology

    2001-01-01

    1 HEALTHCARE ABSTRACT Healthcare is the largest industry in the United States, accounting for approximately $1.4 trillion in sales of goods and...the healthcare industry. In addition to its economic importance, healthcare remains a critical element of national security. The state of public... healthcare industry sets the quality standard for the world, nonetheless there are significant concerns about rising medical costs, the number of un- and

  14. Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

    NASA Technical Reports Server (NTRS)

    Fitz, Rhonda; Whitman, Gerek

    2016-01-01

    Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the

  15. Buying a healthcare information system.

    PubMed

    Clegg, T A

    1998-01-01

    Replacing an antiquated computer system with state of the art equipment and software is a lengthy, at times frustrating, and never an easy decision. At Wesley Woods Center on Aging, Atlanta, an integrated provider of healthcare for the elderly affiliated with Emory University, the process consumed more than two and a half years. This article takes the reader through the entire process, from the initial decision to replace an existing system, through the final purchase and installation. It looks candidly at the problems that were encountered, including turnover among key personnel, difficulties with involving all of the user groups, changes in the technology and coordination with the University. The lessons Wesley Woods learned in its experience can be of benefit to any healthcare facility contemplating an information system change.

  16. [Ballistic quality assurance].

    PubMed

    Cassol, E; Bonnet, J; Porcheron, D; Mazeron, J-J; Peiffert, D; Alapetite, C

    2012-06-01

    This review describes the ballistic quality assurance for stereotactic intracranial irradiation treatments delivered with Gamma Knife® either dedicated or adapted medical linear accelerators. Specific and periodic controls should be performed in order to check the mechanical stability for both irradiation and collimation systems. If this step remains under the responsibility of the medical physicist, it should be done in agreement with the manufacturer's technical support. At this time, there are no recent published guidelines. With technological developments, both frequency and accuracy should be assessed in each institution according to the treatment mode: single versus hypofractionnated dose, circular collimator versus micro-multileaf collimators. In addition, "end-to-end" techniques are mandatory to find the origin of potential discrepancies and to estimate the global ballistic accuracy of the delivered treatment. Indeed, they include frames, non-invasive immobilization devices, localizers, multimodal imaging for delineation and in-room positioning imaging systems. The final precision that could be reasonably achieved is more or less 1mm. Copyright © 2012 Société française de radiothérapie oncologique (SFRO). Published by Elsevier SAS. All rights reserved.

  17. Individualized Healthcare Plans for the School Nurse

    ERIC Educational Resources Information Center

    American School Health Association (NJ3), 2005

    2005-01-01

    This resource sets the standard for school nurses concerning the formulation of individualized healthcare plans designed to fit the unique health needs of students. Eighteen chapters focus on special issues and school nursing concepts. Computer software, which accompanies the manual, assists in the development and creation of individualized…

  18. Software Design Improvements. Part 2; Software Quality and the Design and Inspection Process

    NASA Technical Reports Server (NTRS)

    Lalli, Vincent R.; Packard, Michael H.; Ziemianski, Tom

    1997-01-01

    The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.

  19. Software reengineering

    NASA Technical Reports Server (NTRS)

    Fridge, Ernest M., III

    1991-01-01

    Programs in use today generally have all of the function and information processing capabilities required to do their specified job. However, older programs usually use obsolete technology, are not integrated properly with other programs, and are difficult to maintain. Reengineering is becoming a prominent discipline as organizations try to move their systems to more modern and maintainable technologies. The Johnson Space Center (JSC) Software Technology Branch (STB) is researching and developing a system to support reengineering older FORTRAN programs into more maintainable forms that can also be more readily translated to a modern languages such as FORTRAN 8x, Ada, or C. This activity has led to the development of maintenance strategies for design recovery and reengineering. These strategies include a set of standards, methodologies, and the concepts for a software environment to support design recovery and reengineering. A brief description of the problem being addressed and the approach that is being taken by the STB toward providing an economic solution to the problem is provided. A statement of the maintenance problems, the benefits and drawbacks of three alternative solutions, and a brief history of the STB experience in software reengineering are followed by the STB new FORTRAN standards, methodology, and the concepts for a software environment.

  20. Software Reviews.

    ERIC Educational Resources Information Center

    Wulfson, Stephen, Ed.

    1990-01-01

    Reviewed are seven computer software packages including "Frog Dissection Lab Report,""Backyard Birds,""LEGO TC Logo,""Alcohol--Four Interactive Programs,""Windows on Science--Life Science,""Climate and Weather/Our Town Database," and "Weeds to Trees." Discussed are availability, features, strengths, and weaknesses. (CW)

  1. Software Reviews.

    ERIC Educational Resources Information Center

    Bitter, Gary G., Ed.

    1989-01-01

    Reviews three software packages: (1) "Physics," tutorial, grades 11-12, Macintosh; (2) "Hands On Math: Volume I," interactive math exploration/simulation of manipulatives use, grades K-7, Apple II; and (3) "A.I.: An Experience with Artificial Intelligence," simulation, grades 5-12, Apple II. (MVL)

  2. Software Reviews.

    ERIC Educational Resources Information Center

    Classroom Computer Learning, 1987

    1987-01-01

    Reviews several computer software programs appropriate for educational use. Includes reviews of a graphic environmental operating system, a writers workshop, an exploration of an artificial intelligence program, and a microcomputer based laboratory (MBL) package. Provides information on hardware, grade level, purchasing, and strengths and…

  3. Software Patents.

    ERIC Educational Resources Information Center

    Burke, Edmund B.

    1994-01-01

    Outlines basic patent law information that pertains to computer software programs. Topics addressed include protection in other countries; how to obtain patents; kinds of patents; duration; classes of patentable subject matter, including machines and processes; patentability searches; experimental use prior to obtaining a patent; and patent…

  4. Software Reviews.

    ERIC Educational Resources Information Center

    Classroom Computer Learning, 1990

    1990-01-01

    Reviewed are computer software packages: "Where in Time Is Carmen Sandiego,""The Bio Sci Videodisc," and "Bio Sci Stacks." Included are hardware requirements, costs, emphasis, grade level, and availability. Functions of the packages are discussed including strengths and weaknesses and teaching suggestions. (CW)

  5. Educational Software.

    ERIC Educational Resources Information Center

    Northwest Regional Educational Lab., Portland, OR.

    The third session of IT@EDU98 consisted of five papers on educational software and was chaired by Tran Van Hao (University of Education, Ho Chi Minh City, Vietnam). "Courseware Engineering" (Nguyen Thanh Son, Ngo Ngoc Bao Tran, Quan Thanh Tho, Nguyen Hong Lam) briefly describes the use of courseware. "Machine Discovery Theorems in Geometry: A…

  6. Software Reviews.

    ERIC Educational Resources Information Center

    Smith, Richard L., Ed.

    1988-01-01

    Reviews two software packages, "Solutions Unlimited" and "BASIC Data Base System." Provides a description, summary, strengths and weaknesses, availability and costs. Includes reviews of three structured BASIC packages: "True BASIC (2.0)"; "Turbo BASIC (1.0)"; and "QuickBASIC (3.0)." Explains…

  7. Star Software.

    ERIC Educational Resources Information Center

    Kloza, Brad

    2000-01-01

    Presents a collection of computer software programs designed to spark learning enthusiasm at every grade level and across the curriculum. They include Reader Rabbit's Learn to Read, Spelling Power, Mind Twister Math, Community Construction Kit, Breaking the Code, Encarta Africana 2000, Virtual Serengeti, Operation: Frog (Deluxe), and My First…

  8. Software Reviews.

    ERIC Educational Resources Information Center

    McGrath, Diane, Ed.

    1989-01-01

    Reviewed are two computer software programs for Apple II computers on weather for upper elementary and middle school grades. "Weather" introduces the major factors (temperature, humidity, wind, and air pressure) affecting weather. "How Weather Works" uses simulation and auto-tutorial formats on sun, wind, fronts, clouds, and…

  9. Software Reviews.

    ERIC Educational Resources Information Center

    Mackenzie, Norma N.; And Others

    1988-01-01

    Describes computer software for use with various age groups. Topics include activities involving temperature, simulations, earth science, the circulatory system, human body, reading in science, and ecology. Provides information on equipment needed, availability, package contents, and price. Comments of reviews are presented by classroom teachers.…

  10. Software Reviews.

    ERIC Educational Resources Information Center

    Science and Children, 1989

    1989-01-01

    Reviews of seven software packages are presented including "The Environment I: Habitats and EcoSystems; II Cycles and Interactions"; "Super Sign Maker"; "The Great Knowledge Race: Substance Abuse"; "Exploring Science: Temperature"; "Fast Food Calculator and RD Aide"; "The Human Body:…

  11. Nurses' perceptions of quality assurance.

    PubMed

    Lundqvist, Margareta Jensen; Axelsson, Asa

    2007-01-01

    To describe nurses' perceptions of quality assurance. A qualitative approach using phenomenography was adopted in this study. Data were collected by open and semi-structured interviews from a strategic sample of nurses (N = 10) from a hospital in the south-west of Sweden. The nurses showed 10 different perceptions of the phenomena, which were summarized into four description categories: controlling, development, cooperation and demands. The perceptions described show that nurses can perceive quality assurance both as an asset and as a burden. The expressed perceptions show that nurses use quality assurance as a way of keeping a certain level of caring. It also gives nurses an opportunity for professional growth as well as a possibility for rewards. Working together as a team, even though there are different staff grades, to find joint standpoints, has a positive effect not only on qualitative assurance but also for the patient, as he/she often meets different categories during hospital stay.

  12. Material quality assurance risk assessment.

    DOT National Transportation Integrated Search

    2013-01-01

    Over the past two decades the role of SHA has shifted from quality control (QC) of materials and : placement techniques to quality assurance (QA) and acceptance. The role of the Office of Materials : Technology (OMT) has been shifting towards assuran...

  13. LDUA software custodian`s notebook

    SciTech Connect

    Aftanas, B.L.

    1998-08-20

    This plan describes the activities to be performed and controls to be applied to the process of specifying, obtaining, and qualifying the control and data acquisition software for the Light Duty Utility Arm (LDUA) System. It serves the purpose of a software quality assurance plan, a verification and validation plan, and a configuration management plan. This plan applies to all software that is an integral part of the LDUA control and data acquisition system, that is, software that is installed in the computers that are part of the LDUA system as it is deployed in the field. This plan appliesmore » to the entire development process, including: requirements; design; implementation; and operations and maintenance. This plan does not apply to any software that is not integral with the LDUA system. This plan has-been prepared in accordance with WHC-CM-6-1 Engineering Practices, EP-2.1; WHC-CM-3-10 Software Practices; and WHC-CM-4-2, QR 19.0, Software Quality Assurance Requirements.« less

  14. Primary Healthcare-based Diabetes Registry in Puducherry: Design and Methods

    PubMed Central

    Lakshminarayanan, Subitha; Kar, Sitanshu Sekhar; Gupta, Rajeev; Xavier, Denis; Bhaskar Reddy, S. Vijaya

    2017-01-01

    Background: Diabetes registries monitor the population prevalence and incidence of diabetes, monitor diabetes control program, provide information of quality of care to health service providers, and provide a sampling frame for interventional studies. This study documents the process of establishing a prospective diabetes registry in a primary health-care setting in Puducherry. Methods: This is a facility-based prospective registry conducted in six randomly selected urban health centers in Puducherry, with enrollment of all known patients with diabetes attending chronic disease clinics. Administrative approvals were obtained from Government Health Services. Manuals for training of medical officers, health-care workers, and case report forms were developed. Diabetes registry was prepared using Epi Info software. Results: In the first phase, demographic characteristics, risk factors, complications, coexisting chronic conditions, lifestyle and medical management, and clinical outcomes were recorded. Around 2177 patients with diabetes have been registered in six Primary Health Centres out of a total of 2948 participants seeking care from chronic disease clinic. Registration coverage ranges from 61% to 105% in these centers. Conclusion: This study has documented methodological details, and learning experiences gained while developing a diabetes registry at the primary health care level and the scope for upscaling to a Management Information System for Diabetes and a State-wide Registry. Improvement in patient care through needs assessment and quality assurance in service delivery is an important theme envisioned by this registry. PMID:28553589

  15. Fostering successful scientific software communities

    NASA Astrophysics Data System (ADS)

    Bangerth, W.; Heister, T.; Hwang, L.; Kellogg, L. H.

    2016-12-01

    Developing sustainable open source software packages for the sciences appears at first to be primarily a technical challenge: How can one create stable and robust algorithms, appropriate software designs, sufficient documentation, quality assurance strategies such as continuous integration and test suites, or backward compatibility approaches that yield high-quality software usable not only by the authors, but also the broader community of scientists? However, our experience from almost two decades of leading the development of the deal.II software library (http://www.dealii.org, a widely-used finite element package) and the ASPECT code (http://aspect.dealii.org, used to simulate convection in the Earth's mantle) has taught us that technical aspects are not the most difficult ones in scientific open source software. Rather, it is the social challenge of building and maintaining a community of users and developers interested in answering questions on user forums, contributing code, and jointly finding solutions to common technical and non-technical challenges. These problems are posed in an environment where project leaders typically have no resources to reward the majority of contributors, where very few people are specifically paid for the work they do on the project, and with frequent turnover of contributors as project members rotate into and out of jobs. In particular, much software work is done by graduate students who may become fluent enough in a software only a year or two before they leave academia. We will discuss strategies we have found do and do not work in maintaining and growing communities around the scientific software projects we lead. Specifically, we will discuss the management style necessary to keep contributors engaged, ways to give credit where credit is due, and structuring documentation to decrease reliance on forums and thereby allow user communities to grow without straining those who answer questions.

  16. Calculation Software

    NASA Technical Reports Server (NTRS)

    1994-01-01

    MathSoft Plus 5.0 is a calculation software package for electrical engineers and computer scientists who need advanced math functionality. It incorporates SmartMath, an expert system that determines a strategy for solving difficult mathematical problems. SmartMath was the result of the integration into Mathcad of CLIPS, a NASA-developed shell for creating expert systems. By using CLIPS, MathSoft, Inc. was able to save the time and money involved in writing the original program.

  17. Fully Employing Software Inspections Data

    NASA Technical Reports Server (NTRS)

    Shull, Forrest; Feldmann, Raimund L.; Seaman, Carolyn; Regardie, Myrna; Godfrey, Sally

    2009-01-01

    Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

  18. Thoughts on Internal and External Quality Assurance

    ERIC Educational Resources Information Center

    Zhang, Jianxin

    2012-01-01

    Quality assurance of higher education is made up of two parts: internal quality assurance (IQA) and external quality assurance (EQA). Both belong to a union of the coexistence and balance of yin and yang. But in reality there exists a paradox of "confusion of quality assurance (QA) subject consciousness, singularity of social QA and lack of QA…

  19. Automating linear accelerator quality assurance

    SciTech Connect

    Eckhause, Tobias; Thorwarth, Ryan; Moran, Jean M., E-mail: jmmoran@med.umich.edu

    2015-10-15

    Purpose: The purpose of this study was 2-fold. One purpose was to develop an automated, streamlined quality assurance (QA) program for use by multiple centers. The second purpose was to evaluate machine performance over time for multiple centers using linear accelerator (Linac) log files and electronic portal images. The authors sought to evaluate variations in Linac performance to establish as a reference for other centers. Methods: The authors developed analytical software tools for a QA program using both log files and electronic portal imaging device (EPID) measurements. The first tool is a general analysis tool which can read and visuallymore » represent data in the log file. This tool, which can be used to automatically analyze patient treatment or QA log files, examines the files for Linac deviations which exceed thresholds. The second set of tools consists of a test suite of QA fields, a standard phantom, and software to collect information from the log files on deviations from the expected values. The test suite was designed to focus on the mechanical tests of the Linac to include jaw, MLC, and collimator positions during static, IMRT, and volumetric modulated arc therapy delivery. A consortium of eight institutions delivered the test suite at monthly or weekly intervals on each Linac using a standard phantom. The behavior of various components was analyzed for eight TrueBeam Linacs. Results: For the EPID and trajectory log file analysis, all observed deviations which exceeded established thresholds for Linac behavior resulted in a beam hold off. In the absence of an interlock-triggering event, the maximum observed log file deviations between the expected and actual component positions (such as MLC leaves) varied from less than 1% to 26% of published tolerance thresholds. The maximum and standard deviations of the variations due to gantry sag, collimator angle, jaw position, and MLC positions are presented. Gantry sag among Linacs was 0.336 ± 0.072 mm

  20. Space Station Software Issues

    NASA Technical Reports Server (NTRS)

    Voigt, S. (Editor); Beskenis, S. (Editor)

    1985-01-01

    Issues in the development of software for the Space Station are discussed. Software acquisition and management, software development environment, standards, information system support for software developers, and a future software advisory board are addressed.

  1. Solving the Software Legacy Problem with RISA

    NASA Astrophysics Data System (ADS)

    Ibarra, A.; Gabriel, C.

    2012-09-01

    Nowadays hardware and system infrastructure evolve on time scales much shorter than the typical duration of space astronomy missions. Data processing software capabilities have to evolve to preserve the scientific return during the entire experiment life time. Software preservation is a key issue that has to be tackled before the end of the project to keep the data usable over many years. We present RISA (Remote Interface to Science Analysis) as a solution to decouple data processing software and infrastructure life-cycles, using JAVA applications and web-services wrappers to existing software. This architecture employs embedded SAS in virtual machines assuring a homogeneous job execution environment. We will also present the first studies to reactivate the data processing software of the EXOSAT mission, the first ESA X-ray astronomy mission launched in 1983, using the generic RISA approach.

  2. Communicating with Healthcare Professionals

    MedlinePlus

    ... at follow-up appointments by talking with your healthcare team about your concerns, asking questions and getting ... from the time you spend with all your healthcare providers, not just your doctor. Use the skills ...

  3. Federal Communications Commission (FCC) Transponder Loading Data Conversion Software. User's guide and software maintenance manual, version 1.2

    NASA Technical Reports Server (NTRS)

    Mallasch, Paul G.

    1993-01-01

    This volume contains the complete software system documentation for the Federal Communications Commission (FCC) Transponder Loading Data Conversion Software (FIX-FCC). This software was written to facilitate the formatting and conversion of FCC Transponder Occupancy (Loading) Data before it is loaded into the NASA Geosynchronous Satellite Orbital Statistics Database System (GSOSTATS). The information that FCC supplies NASA is in report form and must be converted into a form readable by the database management software used in the GSOSTATS application. Both the User's Guide and Software Maintenance Manual are contained in this document. This volume of documentation passed an independent quality assurance review and certification by the Product Assurance and Security Office of the Planning Research Corporation (PRC). The manuals were reviewed for format, content, and readability. The Software Management and Assurance Program (SMAP) life cycle and documentation standards were used in the development of this document. Accordingly, these standards were used in the review. Refer to the System/Software Test/Product Assurance Report for the Geosynchronous Satellite Orbital Statistics Database System (GSOSTATS) for additional information.

  4. Fraud Detection in Healthcare

    SciTech Connect

    Chandola, Varun; Schryver, Jack C; Sukumar, Sreenivas R

    2015-01-01

    We discuss the problem of fraud detection in healthcare in this chapter. Given the recent scrutiny of the ineciencies in the US healthcare system, identifying fraud has been on the forefront of the eorts towards reducing the healthcare costs. In this chapter we will focus on understanding the issue of healthcare fraud in detail, and review methods that have been proposed in the literature to combat this issue using data driven approach.

  5. Object-Oriented Software Metrics for Predicting Reusability and Estimating Size

    NASA Technical Reports Server (NTRS)

    Sanderson, D. Peter; Tran, Tuyet-Lan; Sherif, Josef S.; Lee, Susan S.

    1995-01-01

    As object-oriented software development methods come into more widespread use, basic questions of software quality assurance must be reconsidered. We will highlight efforts now underway at NASA's Jet Propulsion Laboratory to both assess the quality of software systems developed using object oriented technology and develop guidelines for future development of such systems. The current focus is on design and code reusability., and system size estimation. A number of metrics are proposed and two software systems measured and analyzed. The preliminary results reported here should be useful to software development and quality assurance personnel working in C++ implementation environment.

  6. Healthcare. Executive Summary

    ERIC Educational Resources Information Center

    Carnevale, Anthony P.; Smith, Nicole; Gulish, Artem; Beach, Bennett H.

    2012-01-01

    This executive summary highlights several findings about healthcare. These are: (1) Healthcare is 18 percent of the U.S. economy, twice as high as in other countries; (2) There are two labor markets in healthcare: high-skill, high-wage professional and technical jobs and low-skill, low-wage support jobs; (3) Demand for postsecondary education in…

  7. Scheduling Software

    NASA Technical Reports Server (NTRS)

    1993-01-01

    Advanced Scheduling Environment is a software product designed and marketed by AVYX, Inc. to provide scheduling solutions for complex manufacturing environments. It can be adapted to specific scheduling and manufacturing processes and has led to substantial cost savings. The system was originally developed for NASA use in scheduling Space Shuttle flights and satellite activities. AVYX, Inc. is an offshoot of a company formed to provide computer-related services to NASA. TREES-plus, the company's initial product became the programming language for the advanced scheduling environment system.

  8. Simulation Software

    NASA Technical Reports Server (NTRS)

    1996-01-01

    Various NASA Small Business Innovation Research grants from Marshall Space Flight Center, Langley Research Center and Ames Research Center were used to develop the 'kernel' of COMCO's modeling and simulation software, the PHLEX finite element code. NASA needed it to model designs of flight vehicles; one of many customized commercial applications is UNISIM, a PHLEX-based code for analyzing underground flows in oil reservoirs for Texaco, Inc. COMCO's products simulate a computational mechanics problem, estimate the solution's error and produce the optimal hp-adapted mesh for the accuracy the user chooses. The system is also used as a research or training tool in universities and in mechanical design in industrial corporations.

  9. Software reliability models for fault-tolerant avionics computers and related topics

    NASA Technical Reports Server (NTRS)

    Miller, Douglas R.

    1987-01-01

    Software reliability research is briefly described. General research topics are reliability growth models, quality of software reliability prediction, the complete monotonicity property of reliability growth, conceptual modelling of software failure behavior, assurance of ultrahigh reliability, and analysis techniques for fault-tolerant systems.

  10. EURECA Software

    NASA Astrophysics Data System (ADS)

    Rohlfs, R.; Bussons, J.; Carrera, F. J.; Ceballos, M.; den Herder, J. W.; de Korte, P.; van der Kuur, J.; Paltani, S.; Rodon, J. R.; Schuurmans, J.

    2008-08-01

    EURECA (EURopEan Calorimeter Array) is a project to develop a fully functional instrument based on transition edge sensors (TES). It shall demonstrate technical readiness for a detector which can be used in the X-ray missions of the next years, like XEUS and EDGE. The produced amount of data can be up to 10 MByte per second, depending on the mode of the instrument. To process and to analyze the data of this EURECA instrument, specific software has to be developed in order to reach the goal of the project: an energy resolution of 1 eV at 1 KeV. On the one hand the software has to be flexible and modular to test several algorithms, on the other hand it should be a straightforward pipeline system to analyze the same data set with different parameters and compare the results. Furthermore display tools to display scientific raw data, housekeeping data and the results of the analysis are required. These display tools will be used for quick look analysis as well as during off-line analysis.

  11. [Quality assurance in tuberculosis laboratories].

    PubMed

    Ozkütük, Aydan

    2009-10-01

    The laboratory has always played a critical role in diagnosis of tuberculosis and monitoring treatment. The basic aim in tuberculosis laboratory is to generate accurate and reliable test results for clinicians. This aim can be achieved by using quality assurance programs. Three main components of quality assurance are, internal quality control, a process by which each laboratory continuously monitors its own performance (guidelines, education and check of staff); external quality control, a process whereby laboratory performance between the other laboratories is assessed by external quality control organization (accuracy and efficiency) and quality improvement (continuous development of quality which involves identification of errors and remedial action). In this article, quality control procedures which are followed in tuberculosis laboratory to ensure the quality assurance, have been reviewed.

  12. Online trust, trustworthiness, or assurance?

    PubMed

    Cheshire, Coye

    2011-01-01

    Every day, individuals around the world retrieve, share, and exchange information on the Internet. We interact online to share personal information, find answers to questions, make financial transactions, play social games, and maintain professional and personal relationships. Sometimes our online interactions take place between two or more humans. In other cases, we rely on computers to manage information on our behalf. In each scenario, risk and uncertainty are essential for determining possible actions and outcomes. This essay highlights common deficiencies in our understanding of key concepts such as trust, trustworthiness, cooperation, and assurance in online environments. Empirical evidence from experimental work in computer-mediated environments underscores the promises and perils of overreliance on security and assurance structures as replacements for interpersonal trust. These conceptual distinctions are critical because the future shape of the Internet will depend on whether we build assurance structures to limit and control ambiguity or allow trust to emerge in the presence of risk and uncertainty.

  13. Software system safety

    NASA Technical Reports Server (NTRS)

    Uber, James G.

    1988-01-01

    Software itself is not hazardous, but since software and hardware share common interfaces there is an opportunity for software to create hazards. Further, these software systems are complex, and proven methods for the design, analysis, and measurement of software safety are not yet available. Some past software failures, future NASA software trends, software engineering methods, and tools and techniques for various software safety analyses are reviewed. Recommendations to NASA are made based on this review.

  14. Strengthening Software Authentication with the ROSE Software Suite

    SciTech Connect

    White, G

    2006-06-15

    Many recent nonproliferation and arms control software projects include a software authentication regime. These include U.S. Government-sponsored projects both in the United States and in the Russian Federation (RF). This trend toward requiring software authentication is only accelerating. Demonstrating assurance that software performs as expected without hidden ''backdoors'' is crucial to a project's success. In this context, ''authentication'' is defined as determining that a software package performs only its intended purpose and performs said purpose correctly and reliably over the planned duration of an agreement. In addition to visual inspections by knowledgeable computer scientists, automated tools are needed to highlightmore » suspicious code constructs, both to aid visual inspection and to guide program development. While many commercial tools are available for portions of the authentication task, they are proprietary and not extensible. An open-source, extensible tool can be customized to the unique needs of each project (projects can have both common and custom rules to detect flaws and security holes). Any such extensible tool has to be based on a complete language compiler. ROSE is precisely such a compiler infrastructure developed within the Department of Energy (DOE) and targeted at the optimization of scientific applications and user-defined libraries within large-scale applications (typically applications of a million lines of code). ROSE is a robust, source-to-source analysis and optimization infrastructure currently addressing large, million-line DOE applications in C and C++ (handling the full C, C99, C++ languages and with current collaborations to support Fortran90). We propose to extend ROSE to address a number of security-specific requirements, and apply it to software authentication for nonproliferation and arms control projects.« less

  15. Anti-malware software and medical devices.

    PubMed

    2010-10-01

    Just as much as healthcare information systems, medical devices need protection against cybersecurity threats. Anti-malware software can help safeguard the devices in your facility-but it has limitations and even risks. Find out what steps you can take to manage anti-malware applications in your devices.

  16. Patient rights and healthcare-associated infection.

    PubMed

    Millar, M

    2011-10-01

    The Universal Declaration of Human Rights was adopted by the United Nations in 1948, and since that time, human rights have become widely recognized and legally enforceable in many countries. Patient rights are now included in healthcare constitutions, such as that of the English National Health Service, and in professional codes of practice. Patient rights have a number of implications for the control of healthcare-associated infections (HCAI), including: (1) justification for infection control over and above economic benefit; (2) focus and emphasis on the individual patient experience; (3) identification of some of the actions taken to control infection as breaches of rights; (4) bridging professional, infection control and public health ethics; (5) a requirement to specify the conditions under which rights can be breached; and (6) grounds for those seeking compensation for HCAI. Assuring patient rights has the potential to improve the patient experience, and in so doing, improve public confidence in healthcare provision and providers. Copyright © 2011 The Healthcare Infection Society. Published by Elsevier Ltd. All rights reserved.

  17. Markov Chains For Testing Redundant Software

    NASA Technical Reports Server (NTRS)

    White, Allan L.; Sjogren, Jon A.

    1990-01-01

    Preliminary design developed for validation experiment that addresses problems unique to assuring extremely high quality of multiple-version programs in process-control software. Approach takes into account inertia of controlled system in sense it takes more than one failure of control program to cause controlled system to fail. Verification procedure consists of two steps: experimentation (numerical simulation) and computation, with Markov model for each step.

  18. Separation Assurance and Collision Avoidance

    NASA Technical Reports Server (NTRS)

    Lauderdale, Todd

    2010-01-01

    Objective SACA-1: Determine the level of safety provided by tactical separation assurance safety monitoring systems for UAS missions. a) Rationale: Continuous mission-risk monitoring can provide equivalent levels of safety for UAS operations possibly reducing the burden on other safety systems. b) Approach: Utilize and adapt algorithms and approaches developed for the NextGen Airspace Systems Program for UAS applications.

  19. Assuring Quality in Education Evaluation.

    ERIC Educational Resources Information Center

    Trochim, William M. K.; Visco, Ronald J.

    1986-01-01

    A number of quality assurance educational evaluation methods are illustrated. Evaluation data obtained from the Providence, Rhode Island, school district are used. The methods are: (1) from auditing, internal control; (2) from accounting, double bookkeeping; and (3) from industrial quality control, acceptance sampling and cumulative percentage…

  20. Assuring Quality in Collaborative Provision.

    ERIC Educational Resources Information Center

    Bocock, Jean; Edwards, Judith

    1998-01-01

    This bulletin is intended to help British further education colleges clarify their rationale for entering into collaborative programs, assess prospective partners, define and implement good practice at all stages of provision, and establish rigorous quality assurance procedures. Following an introduction, Further Education Funding Council…

  1. [Quality assurance in interventional cardiology].

    PubMed

    Gülker, H

    2009-10-01

    Quality assurance in clinical studies aiming at approval of pharmaceutical products is submitted to strict rules, controls and auditing regulations. Comparative instruments to ensure quality in diagnostic and therapeutic procedures are not available in interventional cardiology, likewise in other fields of cardiovascular medicine. Quality assurance simply consists of "quality registers" with basic data not externally controlled. Based on the experiences of clinical studies and their long history of standardization it is assumed that these data may be severely flawed thus being inappropriate to set standards for diagnostic and therapeutic strategies. The precondition for quality assurance are quality data. In invasive coronary angiography and intervention medical indications, the decision making process interventional versus surgical revascularization, technical performance and after - care are essential aspects affecting quality of diagnostics and therapy. Quality data are externally controlled data. To collect quality data an appropriate infrastructure is a necessary precondition which is not existent. For an appropriate infrastructure investments have to be done both to build up as well as to sustain the necessary preconditions. As long as there are no infrastructure and no investments there will be no "quality data". There exist simply registers of data which are not proved to be a basis for significant assurance and enhancement in quality in interventional coronary cardiology. Georg Thieme Verlag KG Stuttgart, New York.

  2. Quality Assurance: One School's Response.

    ERIC Educational Resources Information Center

    Wittemann, K. Joseph

    1990-01-01

    Since 1987, the Virginia Commonwealth University School of Dentistry has established a system of committee responsibilities for quality assurance, involving the committees for clinical affairs, academic performance, safety and therapeutics, and a council composed largely of department chairs. Additional review of procedures and records management…

  3. Teacher Quality Assurance Program Manual.

    ERIC Educational Resources Information Center

    McIntire, Ronald G.; Wong, Martha J.

    The Teacher Quality Assurance Program, an integral part of the Houston, Texas, Plan for Excellence, addresses renewal and professional growth opportunities for current staff. The program is administered by a bi- or tri-dimensional assessment team that may consist of the principal, an instructional supervisor, and the associate and/or deputy…

  4. Counselor Quality Assurance Program Manual.

    ERIC Educational Resources Information Center

    McIntire, Ronald G.; Wong, Martha J.

    The Counselor Quality Assurance Program, part of the Houston, Texas, Plan for Excellence, addresses the renewal and professional growth opportunities for school counselors. The program is administered by a bi- or tri-dimensional assessment team that may consist of the principal, a supervisor or appropriate central office administrator, and the…

  5. Metrology: Measurement Assurance Program Guidelines

    NASA Technical Reports Server (NTRS)

    Eicke, W. G.; Riley, J. P.; Riley, K. J.

    1995-01-01

    The 5300.4 series of NASA Handbooks for Reliability and Quality Assurance Programs have provisions for the establishment and utilization of a documented metrology system to control measurement processes and to provide objective evidence of quality conformance. The intent of these provisions is to assure consistency and conformance to specifications and tolerances of equipment, systems, materials, and processes procured and/or used by NASA, its international partners, contractors, subcontractors, and suppliers. This Measurement Assurance Program (MAP) guideline has the specific objectives to: (1) ensure the quality of measurements made within NASA programs; (2) establish realistic measurement process uncertainties; (3) maintain continuous control over the measurement processes; and (4) ensure measurement compatibility among NASA facilities. The publication addresses MAP methods as applied within and among NASA installations and serves as a guide to: control measurement processes at the local level (one facility); conduct measurement assurance programs in which a number of field installations are joint participants; and conduct measurement integrity (round robin) experiments in which a number of field installations participate to assess the overall quality of particular measurement processes at a point in time.

  6. Online Learning and Quality Assurance

    ERIC Educational Resources Information Center

    Zygouris-Coe, Vicky; Swan, Bonnie; Ireland, Janine

    2009-01-01

    More and more we are seeing the online medium being used to deliver teacher training, and the need for effective evaluation strategies for these programs is crucial. This study investigated the impact of instituting a well-structured quality-assurance process for monitoring a large-scale, statewide online professional development model:…

  7. Quality Assurance 1992-2012

    ERIC Educational Resources Information Center

    Brown, Roger

    2012-01-01

    As the author's contribution to a series marking the Golden Jubilee of the Association of University Administrators, he reflects on changes in quality assurance over the past twenty years and speculates on what the future may hold for quality as the association moves into a new and very different competitive regime. He begins by discussing the…

  8. Employer-Led Quality Assurance

    ERIC Educational Resources Information Center

    Tyszko, Jason A.

    2017-01-01

    Recent criticism of higher education accreditation has prompted calls for reform and sparked interest in piloting alternative quality assurance methods that better address student learning and employment outcomes. Although this debate has brought much needed attention to improving the outcomes of graduates and safeguarding federal investment in…

  9. Redefining and expanding quality assurance.

    PubMed

    Robins, J L

    1992-12-01

    To meet the current standards of excellence necessary for blood establishments, we have learned from industry that a movement toward organization-wide quality assurance/total quality management must be made. Everyone in the organization must accept responsibility for participating in providing the highest quality products and services. Quality must be built into processes and design systems to support these quality processes. Quality assurance has been redefined to include a quality planning function described as the most effective way of designing quality into processes. A formalized quality planning process must be part of quality assurance. Continuous quality improvement has been identified as the strategy every blood establishment must support while striving for error-free processing as the long-term objective. The auditing process has been realigned to support and facilitate this same objective. Implementing organization-wide quality assurance/total quality management is one proven plan for guaranteeing the quality of the 20 million products that are transfused into 4 million patients each year and for moving toward the new order.

  10. Framework for Small-Scale Experiments in Software Engineering: Guidance and Control Software Project: Software Engineering Case Study

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J.

    1998-01-01

    Software is becoming increasingly significant in today's critical avionics systems. To achieve safe, reliable software, government regulatory agencies such as the Federal Aviation Administration (FAA) and the Department of Defense mandate the use of certain software development methods. However, little scientific evidence exists to show a correlation between software development methods and product quality. Given this lack of evidence, a series of experiments has been conducted to understand why and how software fails. The Guidance and Control Software (GCS) project is the latest in this series. The GCS project is a case study of the Requirements and Technical Concepts for Aviation RTCA/DO-178B guidelines, Software Considerations in Airborne Systems and Equipment Certification. All civil transport airframe and equipment vendors are expected to comply with these guidelines in building systems to be certified by the FAA for use in commercial aircraft. For the case study, two implementations of a guidance and control application were developed to comply with the DO-178B guidelines for Level A (critical) software. The development included the requirements, design, coding, verification, configuration management, and quality assurance processes. This paper discusses the details of the GCS project and presents the results of the case study.

  11. Quality assurance of medical ontologies.

    PubMed

    Rogers, J E

    2006-01-01

    To review the literature concerning the quality assurance of medical ontologies. scholar.google.com was searched using the search strings (+ontology +"quality assurance") and (+ontology +"evaluation/evaluating"). Relevant publications were selected by manual review. Other work already familiar to the author, or suggested by other researchers contacted by the author, were included. The papers were analysed for common themes. Four broad properties of an ontology were identified that may be quality-assured: philosophical validity, compliance with meta-ontological commitments, 'content correctness', and fitness for purpose. Each published methodology addressed only a subset of these properties. 'Content' may be divided into domain knowledge content, and metadata describing either the provenance of domain knowledge content, or relationships between it and lexical information (e.g. for display and retrieval). 'Correctness' (whether of domain knowledge content or metadata) may also be further subdivided into truth, completeness, parsimony and internal consistency. Understanding of how to assure the quality of ontologies, or evaluate their fitness for specific purposes, is improving but remains poor. A combination of methodologies is required, but tools to support a comprehensive quality assurance programme remain lacking. Perfect quality of an ontology is not provable and may not be desirable: an ontology compliant with all current philosophical theories, following necessary ontological commitments, and with entirely 'correct' content, may be too complex to be directly usable or useful. The extent to which an ontology's fitness for purpose is predicted or influenced by its other properties remains to be determined. Field studies of ontologies in use, including interrater effects, are required.

  12. 45 CFR 1151.41 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... submit an assurance, on a form specified by the Chairman, that the program or activity will be operated... running with the property assuring nondiscrimination for the period during which the real property is used...

  13. 45 CFR 1151.41 - Assurances required.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... submit an assurance, on a form specified by the Chairman, that the program or activity will be operated... running with the property assuring nondiscrimination for the period during which the real property is used...

  14. 45 CFR 1151.41 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... submit an assurance, on a form specified by the Chairman, that the program or activity will be operated... running with the property assuring nondiscrimination for the period during which the real property is used...

  15. 45 CFR 1151.41 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... submit an assurance, on a form specified by the Chairman, that the program or activity will be operated... running with the property assuring nondiscrimination for the period during which the real property is used...

  16. 45 CFR 1151.41 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... submit an assurance, on a form specified by the Chairman, that the program or activity will be operated... running with the property assuring nondiscrimination for the period during which the real property is used...

  17. Material quality assurance risk assessment : [summary].

    DOT National Transportation Integrated Search

    2013-01-01

    With the shift from quality control (QC) of materials and placement techniques : to quality assurance (QA) and acceptance over the years, the role of the Office : of Materials Technology (OMT) has been shifting towards assurance of : material quality...

  18. Assurance Penalty Level Analysis Final Rule TSD

    EPA Pesticide Factsheets

    This Technical Support Document (TSD) supports EPA’s determination that the final Transport Rule’s assurance provision penalty requirement provides sufficient deterrence against a state exceeding its assurance level.

  19. Implementing Financial Assurance for Mitigation Project Success

    EPA Pesticide Factsheets

    The Institute for Water Resources (IWR) prepared this white paper on financial assurance for mitigation project success to provide a reference resource for Corps district staff involved with establishing and overseeing financial assurances.

  20. Why healthcare providers merge.

    PubMed

    Postma, Jeroen; Roos, Anne-Fleur

    2016-04-01

    In many OECD countries, healthcare sectors have become increasingly concentrated as a result of mergers. However, detailed empirical insight into why healthcare providers merge is lacking. Also, we know little about the influence of national healthcare policies on mergers. We fill this gap in the literature by conducting a survey study on mergers among 848 Dutch healthcare executives, of which 35% responded (resulting in a study sample of 239 executives). A total of 65% of the respondents was involved in at least one merger between 2005 and 2012. During this period, Dutch healthcare providers faced a number of policy changes, including increasing competition, more pressure from purchasers, growing financial risks, de-institutionalisation of long-term care and decentralisation of healthcare services to municipalities. Our empirical study shows that healthcare providers predominantly merge to improve the provision of healthcare services and to strengthen their market position. Also efficiency and financial reasons are important drivers of merger activity in healthcare. We find that motives for merger are related to changes in health policies, in particular to the increasing pressure from competitors, insurers and municipalities.

  1. From Regional Healthcare Information Organizations to a National Healthcare Information Infrastructure

    PubMed Central

    Kaufman, James H; Eiron, Iris; Deen, Glenn; Ford, Dan A; Smith, Eishay; Knoop, Sarah; Nelken, H; Kol, Tomer; Mesika, Yossi; Witting, Karen; Julier, Kevin; Bennett, Craig; Rapp, Bill; Carmeli, Boaz; Cohen, Simona

    2005-01-01

    Recently there has been increased focus on the need to modernize the healthcare information infrastructure in the United States.1–4 The U.S. healthcare industry is by far the largest in the world in both absolute dollars and in percentage of GDP (more than $1.5 trillion, or 15 percent of GDP). It is also fragmented and complex. These difficulties, coupled with an antiquated infrastructure for the collection of and access to medical data, lead to enormous inefficiencies and sources of error. Consumer, regulatory, and governmental pressure drive a growing consensus that the time has come to modernize the U.S. healthcare information infrastructure (HII). While such transformation may be disruptive in the short term, it will, in the future, significantly improve the quality, expediency, efficiency, and successful delivery of healthcare while decreasing costs to patients and payers and improving the overall experiences of consumers and providers. The launch of a national health infrastructure initiative in the United States in May 2004-with the goal of providing an electronic health record for every American within the next decade-will eventually transform the healthcare industry in general, just as information technology (IT) has transformed other industries in the past. The key to this successful outcome will be based on the way we apply IT to healthcare data and the services delivered through IT. This must be accomplished in a way that protects individuals and allows competition but gives caregivers reliable and efficient access to the data required to treat patients and to improve the practice of medical science. This paper describes key IT solutions and technologies that address the challenges of creating a nation-wide healthcare IT infrastructure. Furthermore we discuss the emergence of new electronic healthcare services and the current efforts of IBM Research, Software Group, and Healthcare Life Sciences to realize this new vision for healthcare. PMID:18066378

  2. [Lay agency and healthcare: producing healthcare maps].

    PubMed

    Cecilio, Luiz Carlos de Oliveira; Carapinheiro, Graça; Andreazza, Rosemarie; Souza, Ana Lúcia Medeiros de; Andrade, Maria da Graça Garcia; Santiago, Silvia Maria; Meneses, Consuelo Sampaio; Reis, Denizi Oliveira; Araújo, Eliane Cardoso; Pinto, Nicanor Rodrigues da Silva; Spedo, Sandra Maria

    2014-07-01

    This study aimed to characterize which regulatory logics (other than government regulation) result in healthcare output, using a two-stage qualitative study in two municipalities in the ABCD Paulista region in São Paulo State, Brazil. The first stage included interviews with strategic actors (managers and policymakers) and key health professionals. The second phase collected life histories from 18 individuals with high health-services utilization rates. An analysis of the researchers' involvement in the field allowed a better understanding of the narratives. Four regulatory systems were characterized (governmental, professional, clientelistic, and lay), indicating that regulation is a field in constant dispute, a social production. Users' action produces healthcare maps that reveal the existence of other possible health system arrangements, calling on us to test shared management of healthcare between health teams and users as a promising path to the urgent need to reinvent health.

  3. Improving the Software Development Process Using Testability Research

    NASA Technical Reports Server (NTRS)

    Voas, Jeffrey M.; Miller, Keith W.

    1991-01-01

    Software testability is the the tendency of code to reveal existing faults during random testing. This paper proposes to take software testability predictions into account throughout the development process. These predictions can be made from formal specifications, design documents, and the code itself. The insight provided by software testability is valuable during design, coding, testing, and quality assurance. We further believe that software testability analysis can play a crucial role in quantifying the likelihood that faults are not hiding after testing does not result in any failures for the current version.

  4. V&V Within Reuse-Based Software Engineering

    NASA Technical Reports Server (NTRS)

    Addy, Edward A.

    1996-01-01

    Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.

  5. 29 CFR 32.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... FINANCIAL ASSISTANCE General Provisions § 32.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit an assurance, on a form specified by the...) Duration of obligation. (1) In the case of Federal financial assistance extended in the form of real...

  6. 29 CFR 32.5 - Assurances required.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... FINANCIAL ASSISTANCE General Provisions § 32.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit an assurance, on a form specified by the...) Duration of obligation. (1) In the case of Federal financial assistance extended in the form of real...

  7. 15 CFR 8b.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 15 Commerce and Foreign Trade 1 2010-01-01 2010-01-01 false Assurances required. 8b.5 Section 8b.5 Commerce and Foreign Trade Office of the Secretary of Commerce PROHIBITION OF DISCRIMINATION AGAINST THE... Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies...

  8. 50 CFR 600.240 - Security assurances.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... 50 Wildlife and Fisheries 12 2012-10-01 2012-10-01 false Security assurances. 600.240 Section 600... ADMINISTRATION, DEPARTMENT OF COMMERCE MAGNUSON-STEVENS ACT PROVISIONS Council Membership § 600.240 Security assurances. (a) DOC Office of Security will issue security assurances to Council members following completion...

  9. 50 CFR 600.240 - Security assurances.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 50 Wildlife and Fisheries 10 2011-10-01 2011-10-01 false Security assurances. 600.240 Section 600... ADMINISTRATION, DEPARTMENT OF COMMERCE MAGNUSON-STEVENS ACT PROVISIONS Council Membership § 600.240 Security assurances. (a) DOC Office of Security will issue security assurances to Council members following completion...

  10. 10 CFR 71.37 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 10 Energy 2 2010-01-01 2010-01-01 false Quality assurance. 71.37 Section 71.37 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PACKAGING AND TRANSPORTATION OF RADIOACTIVE MATERIAL Application for Package Approval § 71.37 Quality assurance. (a) The applicant shall describe the quality assurance program (see Subpart H of this part) for the design...

  11. 10 CFR 76.93 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... 10 Energy 2 2013-01-01 2013-01-01 false Quality assurance. 76.93 Section 76.93 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) CERTIFICATION OF GASEOUS DIFFUSION PLANTS Safety § 76.93 Quality assurance. The Corporation shall establish, maintain, and execute a quality assurance program satisfying each of the applicable requirements of ASME NQA-1...

  12. 10 CFR 76.93 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 10 Energy 2 2011-01-01 2011-01-01 false Quality assurance. 76.93 Section 76.93 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) CERTIFICATION OF GASEOUS DIFFUSION PLANTS Safety § 76.93 Quality assurance. The Corporation shall establish, maintain, and execute a quality assurance program satisfying each of the applicable requirements of ASME NQA-1...

  13. 10 CFR 76.93 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 10 Energy 2 2012-01-01 2012-01-01 false Quality assurance. 76.93 Section 76.93 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) CERTIFICATION OF GASEOUS DIFFUSION PLANTS Safety § 76.93 Quality assurance. The Corporation shall establish, maintain, and execute a quality assurance program satisfying each of the applicable requirements of ASME NQA-1...

  14. 10 CFR 71.37 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 10 Energy 2 2012-01-01 2012-01-01 false Quality assurance. 71.37 Section 71.37 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PACKAGING AND TRANSPORTATION OF RADIOACTIVE MATERIAL Application for Package Approval § 71.37 Quality assurance. (a) The applicant shall describe the quality assurance program (see Subpart H of this part) for the design...

  15. 10 CFR 71.37 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... 10 Energy 2 2013-01-01 2013-01-01 false Quality assurance. 71.37 Section 71.37 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PACKAGING AND TRANSPORTATION OF RADIOACTIVE MATERIAL Application for Package Approval § 71.37 Quality assurance. (a) The applicant shall describe the quality assurance program (see Subpart H of this part) for the design...

  16. 10 CFR 71.37 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 10 Energy 2 2011-01-01 2011-01-01 false Quality assurance. 71.37 Section 71.37 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PACKAGING AND TRANSPORTATION OF RADIOACTIVE MATERIAL Application for Package Approval § 71.37 Quality assurance. (a) The applicant shall describe the quality assurance program (see Subpart H of this part) for the design...

  17. 10 CFR 76.93 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 10 Energy 2 2010-01-01 2010-01-01 false Quality assurance. 76.93 Section 76.93 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) CERTIFICATION OF GASEOUS DIFFUSION PLANTS Safety § 76.93 Quality assurance. The Corporation shall establish, maintain, and execute a quality assurance program satisfying each of the applicable requirements of ASME NQA-1...

  18. 10 CFR 71.37 - Quality assurance.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 10 Energy 2 2014-01-01 2014-01-01 false Quality assurance. 71.37 Section 71.37 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) PACKAGING AND TRANSPORTATION OF RADIOACTIVE MATERIAL Application for Package Approval § 71.37 Quality assurance. (a) The applicant shall describe the quality assurance program (see Subpart H of this part) for the design...

  19. 10 CFR 76.93 - Quality assurance.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 10 Energy 2 2014-01-01 2014-01-01 false Quality assurance. 76.93 Section 76.93 Energy NUCLEAR REGULATORY COMMISSION (CONTINUED) CERTIFICATION OF GASEOUS DIFFUSION PLANTS Safety § 76.93 Quality assurance. The Corporation shall establish, maintain, and execute a quality assurance program satisfying each of the applicable requirements of ASME NQA-1...

  20. Office Computer Software: A Comprehensive Review of Software Programs.

    ERIC Educational Resources Information Center

    Secretary, 1992

    1992-01-01

    Describes types of software including system software, application software, spreadsheets, accounting software, graphics packages, desktop publishing software, database, desktop and personal information management software, project and records management software, groupware, and shareware. (JOW)

  1. [Cross-sectoral quality assurance in ambulatory care].

    PubMed

    Albrecht, Martin; Loos, Stefan; Otten, Marcus

    2013-01-01

    Overcoming rigid sectoral segmentation in healthcare has also become a health policy target in quality assurance. With the Act to Enhance Competition in Statutory Health Insurance (GKV-WSG) coming into effect, quality assurance measures are to be designed in a cross-sectoral fashion for in- and outpatient sectors equally. An independent institution is currently mandated to develop specific quality indicators for eleven indications. For three of these operating tests have already been commissioned by the Federal Joint Committee. This article depicts the major results of a feasibility study, including a compliance cost estimate, for the aforementioned indications of cross-sectoral quality assurance (cQA). In conclusion, a number of both practical and conceptual basic challenges are still to be resolved prior to the full implementation of cQA, such as a sufficient specification to activate documentation requirements and an inspection system capable of separating actual quality problems from documentary deficits. So far, a comprehensive cost-utility analysis of cQA has not been provided, in particular with comparison to existing QA systems. In order to optimise cost and utility of cQA an evidence-based approach is required for both the extension of cQA areas and for QA provisions. Copyright © 2013. Published by Elsevier GmbH.

  2. Interactive Visualization of Healthcare Data Using Tableau.

    PubMed

    Ko, Inseok; Chang, Hyejung

    2017-10-01

    Big data analysis is receiving increasing attention in many industries, including healthcare. Visualization plays an important role not only in intuitively showing the results of data analysis but also in the whole process of collecting, cleaning, analyzing, and sharing data. This paper presents a procedure for the interactive visualization and analysis of healthcare data using Tableau as a business intelligence tool. Starting with installation of the Tableau Desktop Personal version 10.3, this paper describes the process of understanding and visualizing healthcare data using an example. The example data of colon cancer patients were obtained from health insurance claims in years 2012 and 2013, provided by the Health Insurance Review and Assessment Service. To explore the visualization of healthcare data using Tableau for beginners, this paper describes the creation of a simple view for the average length of stay of colon cancer patients. Since Tableau provides various visualizations and customizations, the level of analysis can be increased with small multiples, view filtering, mark cards, and Tableau charts. Tableau is a software that can help users explore and understand their data by creating interactive visualizations. The software has the advantages that it can be used in conjunction with almost any database, and it is easy to use by dragging and dropping to create an interactive visualization expressing the desired format.

  3. Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

    NASA Technical Reports Server (NTRS)

    Fitz, Rhonda

    2017-01-01

    As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification Validation (IVV) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASA's Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domaincomponent, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IVV enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this

  4. Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

    NASA Technical Reports Server (NTRS)

    Fitz, Rhonda

    2017-01-01

    As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification & Validation (IV&V) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASAs Office of Safety and Mission Assurance (OSMA) defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domain/component, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IV&V enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing

  5. Assurance specification documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 4

    NASA Technical Reports Server (NTRS)

    Callender, E. David; Steinbacher, Jody

    1989-01-01

    This is the fourth of five volumes on Information System Life-Cycle and Documentation Standards. This volume provides a well organized, easily used standard for assurance documentation for information systems and software, hardware, and operational procedures components, and related processes. The specifications are developed in conjunction with the corresponding management plans specifying the assurance activities to be performed.

  6. Software Model Of Software-Development Process

    NASA Technical Reports Server (NTRS)

    Lin, Chi Y.; Synott, Debra J.; Levary, Reuven R.

    1990-01-01

    Collection of computer programs constitutes software tool for simulation of medium- to large-scale software-development projects. Necessary to include easily identifiable and more-readily quantifiable characteristics like costs, times, and numbers of errors. Mathematical model incorporating these and other factors of dynamics of software-development process implemented in the Software Life Cycle Simulator (SLICS) computer program. Simulates dynamics of software-development process. In combination with input and output expert software systems and knowledge-based management software system, develops information for use in managing large software-development project. Intended to aid managers in planning, managing, and controlling software-development processes by reducing uncertainties in budgets, required personnel, and schedules.

  7. Healthcare. State Report

    ERIC Educational Resources Information Center

    Carnevale, Anthony P.; Smith, Nicole; Gulish, Artem; Beach, Bennett H.

    2012-01-01

    This report projects education requirements linked to forecasted job growth in healthcare by state and the District of Columbia from 2010 through 2020. It complements a larger national report which projects educational demand for healthcare for the same time period. The national report shows that with or without Obamacare, the United States will…

  8. 75 FR 57956 - Draft Revision of the Federalwide Assurance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-09-23

    ...:[sol][sol]www.hhs.gov/ohrp/assurances/assurances_index.html. OHRP will consider comments received... documents available on the OHRP Web site at http:[sol][sol]www.hhs.gov/ohrp/assurances/assurances_index.html...

  9. Assuring Life in Composite Systems

    NASA Technical Reports Server (NTRS)

    Chamis, Christos c.

    2008-01-01

    A computational simulation method is presented to assure life in composite systems by using dynamic buckling of smart composite shells as an example. The combined use of composite mechanics, finite element computer codes, and probabilistic analysis enable the effective assessment of the dynamic buckling load of smart composite shells. A universal plot is generated to estimate the dynamic buckling load of composite shells at various load rates and probabilities. The shell structure is also evaluated with smart fibers embedded in the plies right below the outer plies. The results show that, on the average, the use of smart fibers improved the shell buckling resistance by about 9% at different probabilities and delayed the buckling occurrence time. The probabilistic sensitivities results indicate that uncertainties in the fiber volume ratio and ply thickness have major effects on the buckling load. The uncertainties in the electric field strength and smart material volume fraction have moderate effects and thereby in the assured life of the shell.

  10. Requirement Assurance: A Verification Process

    NASA Technical Reports Server (NTRS)

    Alexander, Michael G.

    2011-01-01

    Requirement Assurance is an act of requirement verification which assures the stakeholder or customer that a product requirement has produced its "as realized product" and has been verified with conclusive evidence. Product requirement verification answers the question, "did the product meet the stated specification, performance, or design documentation?". In order to ensure the system was built correctly, the practicing system engineer must verify each product requirement using verification methods of inspection, analysis, demonstration, or test. The products of these methods are the "verification artifacts" or "closure artifacts" which are the objective evidence needed to prove the product requirements meet the verification success criteria. Institutional direction is given to the System Engineer in NPR 7123.1A NASA Systems Engineering Processes and Requirements with regards to the requirement verification process. In response, the verification methodology offered in this report meets both the institutional process and requirement verification best practices.

  11. Beef Quality Assurance in Feedlots.

    PubMed

    Smith, Robert A; Thomson, Daniel U; Lee, Tiffany L

    2015-07-01

    This article discusses the Beef Quality Assurance (BQA) program, which was created by beef producers and veterinarians. The program has evolved from antibiotic residue avoidance to include animal handling, cattle comfort, food safety, and much more. It provides guidance to producers and veterinarians on best management practices and allows the beef industry to be transparent about the practices used. Veterinarians are key to helping producers implement BQA in their beef operations. Copyright © 2015 Elsevier Inc. All rights reserved.

  12. Mammography quality assurance. Current issues.

    PubMed

    Hendrick, R E

    1993-08-15

    Some of the issues being addressed in mammography quality assurance are 1) that image quality is the most important technical aspect of mammography; 2) that image quality has improved steadily over the past two decades and will continue to improve at most mammography sites in the United States; 3) that the American College of Radiology's Mammography Accreditation Program is the best way to ensure high quality mammogram; 4) that access to high quality mammography is not geographically restricted, with over half the mammography sites in the United States now ACR accredited and another 30% participating in the accreditation process; 5) that regular and effective quality assurance, as described in the ACR Mammography Quality Control Manuals and as required of ACR accredited sites, is the only way to ensure that superior mammography image quality is maintained; and 6) that sites with higher mammography volume have better quality assurance practices and lower failure rates than others within the ACR Mammography Accreditation Program. Two bills passed by the United States Congress, the Medicare Coverage of Screening Mammography (1990) and the Mammography Quality Standards Act (1992), contain mammography quality assurance provisions. As a result of the 1990 Medicare bill, on-site inspections of Medicare screening sites began in the fall of 1992. The Mammography Quality Standards Act is scheduled to go into effect on October 1, 1994. The current challenges to mammography are to improve and maintain high image quality at every mammography site, to improve imaging of the dense breast, to implement patient-tracking and follow-up mechanisms to improve compliance and assess the efficacy of screening, and to ensure that federal mammography quality standards are effectively and appropriately implemented.

  13. Telescience Resource Kit Software Lifecycle

    NASA Technical Reports Server (NTRS)

    Griner, Carolyn S.; Schneider, Michelle

    1998-01-01

    The challenge of a global operations capability led to the Telescience Resource Kit (TReK) project, an in-house software development project of the Mission Operations Laboratory (MOL) at NASA's Marshall Space Flight Center (MSFC). The TReK system is being developed as an inexpensive comprehensive personal computer- (PC-) based ground support system that can be used by payload users from their home sites to interact with their payloads on board the International Space Station (ISS). The TReK project is currently using a combination of the spiral lifecycle model and the incremental lifecycle model. As with any software development project, there are four activities that can be very time consuming: Software design and development, project documentation, testing, and umbrella activities, such as quality assurance and configuration management. In order to produce a quality product, it is critical that each of these activities receive the appropriate amount of attention. For TReK, the challenge was to lay out a lifecycle and project plan that provides full support for these activities, is flexible, provides a way to deal with changing risks, can accommodate unknowns, and can respond to changes in the environment quickly. This paper will provide an overview of the TReK lifecycle, a description of the project's environment, and a general overview of project activities.

  14. Assessment Environment for Complex Systems Software Guide

    NASA Technical Reports Server (NTRS)

    2013-01-01

    This Software Guide (SG) describes the software developed to test the Assessment Environment for Complex Systems (AECS) by the West Virginia High Technology Consortium (WVHTC) Foundation's Mission Systems Group (MSG) for the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD). This software is referred to as the AECS Test Project throughout the remainder of this document. AECS provides a framework for developing, simulating, testing, and analyzing modern avionics systems within an Integrated Modular Avionics (IMA) architecture. The purpose of the AECS Test Project is twofold. First, it provides a means to test the AECS hardware and system developed by MSG. Second, it provides an example project upon which future AECS research may be based. This Software Guide fully describes building, installing, and executing the AECS Test Project as well as its architecture and design. The design of the AECS hardware is described in the AECS Hardware Guide. Instructions on how to configure, build and use the AECS are described in the User's Guide. Sample AECS software, developed by the WVHTC Foundation, is presented in the AECS Software Guide. The AECS Hardware Guide, AECS User's Guide, and AECS Software Guide are authored by MSG. The requirements set forth for AECS are presented in the Statement of Work for the Assessment Environment for Complex Systems authored by NASA Dryden Flight Research Center (DFRC). The intended audience for this document includes software engineers, hardware engineers, project managers, and quality assurance personnel from WVHTC Foundation (the suppliers of the software), NASA (the customer), and future researchers (users of the software). Readers are assumed to have general knowledge in the field of real-time, embedded computer software development.

  15. SYN-OP-SYS™: A Computerized Management Information System for Quality Assurance and Risk Management

    PubMed Central

    Thomas, David J.; Weiner, Jayne; Lippincott, Ronald C.

    1985-01-01

    SYN·OP·SYS™ is a computerized management information system for quality assurance and risk management. Computer software for the efficient collection and analysis of “occurrences” and the clinical data associated with these kinds of patient events is described. The system is evaluated according to certain computer design criteria, and the system's implementation is assessed.

  16. Quality assurance in forensic pathology.

    PubMed

    Ong, Beng Beng; Milne, Nathan

    2009-06-01

    One of the requirements for proper running of a pathology laboratory is implementation of a quality assurance programme. Forensic pathology is not exempted, especially so when cases are increasing in complexity. It is not difficult to introduce a quality assurance programme even in a small forensic centre. Among the steps that can be implemented including introduction of a set of minimal standards in performance of the autopsy, timeliness and report writing, a vigorous peer review process either internally or externally and participation in external quality programmes. Proper documentation of the post-mortem process (photography, slides and blocks and various imaging modalities) is to be encouraged. There should be limits set on workload of pathologists as overburden is known to lower standards. A pleasant work environment is also essential. Personal continuous medical education should be made mandatory. Introduction of a quality assurance programme will not only improve standards but minimise possible negligence. The post-mortem reports will be seen to carry more weight in court.

  17. Assuring eating quality of meat.

    PubMed

    Dalen, G A

    1996-01-01

    The way of assuring quality has changed over the years, from inspection of end product to quality management systems and on-line process control. The latter concepts have had a great impact in many industries during the last decades. But the concept of Total Quality is continuos improvement so it is time to take advantage of the next generation of quality assurance tools: Quality by Design. This is the most powerful instrument in quality assurance today. Quality by design has been used with outstanding results in many industries as the automobile and the electronics industry. Maybe the meat industry will be the next? To succeed, the "eating quality attributes" that are most important to the customer must be brought into focus. The challenge to the meat research scientist is to design products and processes that take care of customer needs despite variation in the raw material and the consumer's rough handling. The Quality Management Standards are helpful in conducting the design and production process, but to focus on the right aspects, there also are need for suitable methods as Quality Function Deployment. Customer needs change and new research changes old 'truths'. This require an organisation, a quality system and a culture which can handle rapid changes and a diversity of customer needs.

  18. Corporate quality assurance programs expanding.

    PubMed

    Walters, M J

    1987-03-01

    The Sisters of Charity Health Care System (SCHCS) of Cincinnati, before expanding its quality assurance (QA) activities, conducted a survey of 29 Catholic multi-institutional systems to learn more about their QA functions. Of those surveyed, nine systems already had a corporate QA program and seven more were considering developing one. The existing programs have four general areas of responsibility: assisting member facilities in complying with Joint Commission on Accreditation of Hospitals standards, coordinating QA activities among facilities, facilitating development of a monitoring system, and providing consultation and education on quality issues. Seven of the nine systems with established QA programs had a single person in charge, generally someone with at least a master's degree and clinical, management, and actual QA experience. They usually were called "directors of quality assurance" and reported to vice-presidents. Their salary ranged from $49,000 to $65,000. Program budgets were an average of $88,809, and average staff size was 2.6 persons. The seven systems that had not yet established a QA program but were considering it had plans similar to existing programs. Based on these trends, SCHCS launched a corporate QA program in July 1986 by hiring a director of quality assurance.

  19. Quality assurance for clinical trials.

    PubMed

    Ibbott, Geoffrey S; Haworth, Annette; Followill, David S

    2013-12-19

    Cooperative groups, of which the Radiation Therapy Oncology Group is one example, conduct national clinical trials that often involve the use of radiation therapy. In preparation for such a trial, the cooperative group prepares a protocol to define the goals of the trial, the rationale for its design, and the details of the treatment procedure to be followed. The Radiological Physics Center (RPC) is one of several quality assurance (QA) offices that is charged with assuring that participating institutions deliver doses that are clinically consistent and comparable. The RPC does this by conducting a variety of independent audits and credentialing processes. The RPC has compiled data showing that credentialing can help institutions comply with the requirements of a cooperative group clinical protocol. Phantom irradiations have been demonstrated to exercise an institution's procedures for planning and delivering advanced external beam techniques (1-3). Similarly, RPC data indicate that a rapid review of patient treatment records or planning procedures can improve compliance with clinical trials (4). The experiences of the RPC are presented as examples of the contributions that a national clinical trials QA center can make to cooperative group trials. These experiences illustrate the critical need for comprehensive QA to assure that clinical trials are successful and cost-effective. The RPC is supported by grants CA 10953 and CA 81647 from the National Cancer Institute, NIH, DHHS.

  20. Medical device software: defining key terms.

    PubMed

    Pashkov, Vitalii; Gutorova, Nataliya; Harkusha, Andrii

    one of the areas of significant growth in medical devices has been the role of software - as an integral component of a medical device, as a standalone device and more recently as applications on mobile devices. The risk related to a malfunction of the standalone software used within healthcare is in itself not a criterion for its qualification or not as a medical device. It is therefore, necessary to clarify some criteria for the qualification of stand-alone software as medical devices Materials and methods: Ukrainian, European Union, United States of America legislation, Guidelines developed by European Commission and Food and Drug Administration's, recommendations represented by international voluntary group and scientific works. This article is based on dialectical, comparative, analytic, synthetic and comprehensive research methods. the legal regulation of software which is used for medical purpose in Ukraine limited to one definition. In European Union and United States of America were developed and applying special guidelines that help developers, manufactures and end users to difference software on types standing on medical purpose criteria. Software becomes more and more incorporated into medical devices. Developers and manufacturers may not have initially appreciated potential risks to patients and users such situation could have dangerous results for patients or users. It is necessary to develop and adopt the legislation that will intend to define the criteria for the qualification of medical device software and the application of the classification criteria to such software, provide some illustrative examples and step by step recommendations to qualify software as medical device.

  1. A monthly quality assurance procedure for 3D surface imaging.

    PubMed

    Wooten, H Omar; Klein, Eric E; Gokhroo, Garima; Santanam, Lakshmi

    2010-12-21

    A procedure for periodic quality assurance of a video surface imaging system is introduced. AlignRT is a video camera-based patient localization system that captures and compares images of a patient's topography to a DICOM-formatted external contour, then calculates shifts required to accurately reposition the patient. This technical note describes the tools and methods implemented in our department to verify correct and accurate operation of the AlignRT hardware and software components. The procedure described is performed monthly and complements a daily calibration of the system.

  2. Behavioral Reference Model for Pervasive Healthcare Systems.

    PubMed

    Tahmasbi, Arezoo; Adabi, Sahar; Rezaee, Ali

    2016-12-01

    The emergence of mobile healthcare systems is an important outcome of application of pervasive computing concepts for medical care purposes. These systems provide the facilities and infrastructure required for automatic and ubiquitous sharing of medical information. Healthcare systems have a dynamic structure and configuration, therefore having an architecture is essential for future development of these systems. The need for increased response rate, problem limited storage, accelerated processing and etc. the tendency toward creating a new generation of healthcare system architecture highlight the need for further focus on cloud-based solutions for transfer data and data processing challenges. Integrity and reliability of healthcare systems are of critical importance, as even the slightest error may put the patients' lives in danger; therefore acquiring a behavioral model for these systems and developing the tools required to model their behaviors are of significant importance. The high-level designs may contain some flaws, therefor the system must be fully examined for different scenarios and conditions. This paper presents a software architecture for development of healthcare systems based on pervasive computing concepts, and then models the behavior of described system. A set of solutions are then proposed to improve the design's qualitative characteristics including, availability, interoperability and performance.

  3. Spacelab software development and integration concepts study report, volume 1

    NASA Technical Reports Server (NTRS)

    Rose, P. L.; Willis, B. G.

    1973-01-01

    The proposed software guidelines to be followed by the European Space Research Organization in the development of software for the Spacelab being developed for use as a payload for the space shuttle are documented. Concepts, techniques, and tools needed to assure the success of a programming project are defined as they relate to operation of the data management subsystem, support of experiments and space applications, use with ground support equipment, and for integration testing.

  4. Healthcare professionals and the ethics of healthcare marketing.

    PubMed

    Hammond, Kevin L; Jurkus, Anthony F

    1993-01-01

    The article explores marketing ethics considerations in the application of marketing to healthcare. While we realize that acceptance of healthcare marketing by all stakeholders is important for successful marketing, we emphasize its level of acceptance by healthcare professionals. The high levels of resistance to advertising and other forms of healthcare marketing by healthcare professionals has been largely based on the grounds that the practices are unethical. The nature of the resistance thus invites this exploration of healthcare marketing (and the marketing concept), marketing ethics, and the acceptance (rejection) by healthcare professionals of healthcare marketing.

  5. Engineering healthcare as a service system.

    PubMed

    Tien, James M; Goldschmidt-Clermont, Pascal J

    2010-01-01

    Engineering has and will continue to have a critical impact on healthcare; the application of technology-based techniques to biological problems can be defined to be technobiology applications. This paper is primarily focused on applying the technobiology approach of systems engineering to the development of a healthcare service system that is both integrated and adaptive. In general, healthcare services are carried out with knowledge-intensive agents or components which work together as providers and consumers to create or co-produce value. Indeed, the engineering design of a healthcare system must recognize the fact that it is actually a complex integration of human-centered activities that is increasingly dependent on information technology and knowledge. Like any service system, healthcare can be considered to be a combination or recombination of three essential components - people (characterized by behaviors, values, knowledge, etc.), processes (characterized by collaboration, customization, etc.) and products (characterized by software, hardware, infrastructures, etc.). Thus, a healthcare system is an integrated and adaptive set of people, processes and products. It is, in essence, a system of systems which objectives are to enhance its efficiency (leading to greater interdependency) and effectiveness (leading to improved health). Integration occurs over the physical, temporal, organizational and functional dimensions, while adaptation occurs over the monitoring, feedback, cybernetic and learning dimensions. In sum, such service systems as healthcare are indeed complex, especially due to the uncertainties associated with the human-centered aspects of these systems. Moreover, the system complexities can only be dealt with methods that enhance system integration and adaptation.

  6. The tidal waves of connected health devices with healthcare applications: consequences on privacy and care management in European healthcare systems.

    PubMed

    Allaert, Francois-André; Mazen, Noël-Jean; Legrand, Louis; Quantin, Catherine

    2017-01-17

    The market for Connected Health Devices (CHD) with healthcare applications is growing fast and should be worth several billion euros in turnover in the coming years. Their development will completely transform the organisation of our healthcare system, profoundly change the way patients are managed and revolutionizes disease prevention. The CHD with healthcare applications is a tidal wave that has societal impact calling into question the privacy of patients' personal and healthcare information and its protection in secure systems. Rather than trying to stop the use of CHD, we must channel the wave by clearly examining the advantages versus the risks and threats to the patients, and find counter-measures for implementation. The main difficulty is channeling the wave in a way that is acceptable to CHD developers who otherwise will bypass the rules, even if they can be sued for it. Therefore, it appears necessary to implement guidelines that can be used by all developers, defining the minimum requirement for assuring the security of patient privacy and healthcare management. In European Healthcare Systems, there is an imperative need for establishing security guidelines that CHD producers could use to ensure compliance, so that patient privacy and healthcare management is safeguarded. The aim would be to implement the guidelines a posteriori rather than a priori control so as not to hamper innovation.

  7. Explaining Synthesized Software

    NASA Technical Reports Server (NTRS)

    VanBaalen, Jeffrey; Robinson, Peter; Lowry, Michael; Pressburger, Thomas; Lau, Sonie (Technical Monitor)

    1998-01-01

    Motivated by NASA's need for high-assurance software, NASA Ames' Amphion project has developed a generic program generation system based on deductive synthesis. Amphion has a number of advantages, such as the ability to develop a new synthesis system simply by writing a declarative domain theory. However, as a practical matter, the validation of the domain theory for such a system is problematic because the link between generated programs and the domain theory is complex. As a result, when generated programs do not behave as expected, it is difficult to isolate the cause, whether it be an incorrect problem specification or an error in the domain theory. This paper describes a tool we are developing that provides formal traceability between specifications and generated code for deductive synthesis systems. It is based on extensive instrumentation of the refutation-based theorem prover used to synthesize programs. It takes augmented proof structures and abstracts them to provide explanations of the relation between a specification, a domain theory, and synthesized code. In generating these explanations, the tool exploits the structure of Amphion domain theories, so the end user is not confronted with the intricacies of raw proof traces. This tool is crucial for the validation of domain theories as well as being important in everyday use of the code synthesis system. It plays an important role in validation because when generated programs exhibit incorrect behavior, it provides the links that can be traced to identify errors in specifications or domain theory. It plays an important role in the everyday use of the synthesis system by explaining to users what parts of a specification or of the domain theory contribute to what pieces of a generated program. Comments are inserted into the synthesized code that document these explanations.

  8. VERIDOS: a new tool for quality assurance for intensity modulated radiotherapy.

    PubMed

    Wiezorek, Tilo; Schwedas, Michael; Scheithauer, Marcel; Salz, Henning; Bellemann, Matthias; Wendt, Thomas G

    2002-12-01

    The use of intensity modulated radiation fields needs an extended quality assurance concept. This consists of a linac related part and a case related part. Case related means the verification of an individual treatment plan, optimized on a CT data set of an individual patient and prepared for the treatment of this patient. This part of the quality assurance work is usually time consuming, delivers only partially quantitative results and is uncomfortable without additional help. It will be shown in this paper how the software VERIDOS will improve the optimization of the case related part of the quality assurance work. The main function of the software is the quantitative comparison of the calculated dose distribution from the treatment planning software with the measured dose distribution of an irradiated phantom. Several additional functions will be explained. Two self-developed phantoms made of RW3 (solid water) and GAFCHROMIC films or Kodak EDR2 films for the measurement of the dose distributions were used. VERIDOS was tested with the treatment planning systems Helay-TMS and Brainscan. VERIDOS is a suitable tool for the import of calculated dose matrices from the treatment planning systems Helax-TMS and Brainscan and of measured dose matrices exported from the dosimetry software Mephysto (PTW). The import from other treatment planning systems and scanning software applications for film dosimetry is generally possible. In such case the import function has to be adapted to the special header of the import matrix. All other functions of this software tool like normalization (automatically, manually), working with corrections (ground substraction, factors), overlay/comparison of dose distributions, difference matrix, cutting function (profiles) and export functions work reliable. VERIDOS improves the optimization of the case related part of the quality assurance work for intensity modulated radiation therapy (IMRT). The diverse functions of the software offer the

  9. Recommended Vaccines for Healthcare Workers

    MedlinePlus

    ... Vaccination Resources for Healthcare Professionals Recommended Vaccines for Healthcare Workers Recommend on Facebook Tweet Share Compartir On ... for More Information Resources for Those Vaccinating HCWs Healthcare workers (HCWs) are at risk for exposure to ...

  10. Software attribute visualization for high integrity software

    SciTech Connect

    Pollock, G.M.

    1998-03-01

    This report documents a prototype tool developed to investigate the use of visualization and virtual reality technologies for improving software surety confidence. The tool is utilized within the execution phase of the software life cycle. It provides a capability to monitor an executing program against prespecified requirements constraints provided in a program written in the requirements specification language SAGE. The resulting Software Attribute Visual Analysis Tool (SAVAnT) also provides a technique to assess the completeness of a software specification.

  11. Turnover among healthcare professionals.

    PubMed

    Wood, Ben D

    2009-01-01

    Turnover among healthcare professionals is a costly consequence. The existing body of knowledge on healthcare professional turnover is correlated with job satisfaction levels. A landmark study differentiated 2 areas of job satisfaction categories: satisfiers and dissatisfiers (intrinsic and extrinsic motivators). The aim of this article is to examine existing research on precursors of turnover, such as burnout behaviors experienced by healthcare professionals, job satisfaction levels, employee organizational commitment, health complications which precede turnover, some current strategies to reduce turnover, and some effects CEO turnover has on employee turnover intentions.

  12. Electronics for better healthcare.

    PubMed

    Wolf, Bernhard; Herzog, Karolin

    2013-06-01

    Microelectronics and microsystem technology have changed our daily lives considerably in the past 50 years. Countless everyday objects contain microelectronic components. In healthcare up to the present, however, it has not been possible to make major alterations in introducing electronics and information technology that would lead to innovative improvements and greater transparency. This paper describes initial steps in diagnostics and oncological therapy including telematic healthcare systems which can, for example, assist patients with cardiovascular diseases and shows, through these areas, how electronics and microsystems technology can contribute to better healthcare.

  13. Software Development Cost: How Much? You Sure? Technical Summary

    NASA Technical Reports Server (NTRS)

    Hihn, Jairus; Menzies, Tim

    2006-01-01

    This slide presentation reports on findings from analyzing a NASA COCOMO 81 dataset with 93 records. The current tool is called COSEEKMO, using a methodology can be applied to any set of cost models and data. The effort was part of a research initiative funded by the NASA Office of Safety and Mission and Assurance (OSMA) aimed at improving software reliability.

  14. Architecture for Business Intelligence in the Healthcare Sector

    NASA Astrophysics Data System (ADS)

    Lee, Sang Young

    2018-03-01

    Healthcare environment is growing to include not only the traditional information systems, but also a business intelligence platform. For executive leaders, consultants, and analysts, there is no longer a need to spend hours in design and develop of typical reports or charts, the entire solution can be completed through using Business Intelligence software. The current paper highlights the advantages of big data analytics and business intelligence in the healthcare industry. In this paper, In this paper we focus our discussion around intelligent techniques and methodologies which are recently used for business intelligence in healthcare.

  15. CORDIET - Healthcare: Extracting knowledge from electronic patient record data.

    PubMed

    Poelmans, Jonas; Van der Mussele, Herman; Verheyden, Gerda; Viaene, Stijn; Dedene, Guido; Kuznetsov, Sergei; Neznanov, Alexei

    2012-01-01

    In this paper we propose the software system CORDIET-Healthcare which we are currently developing in collaboration with the Katholieke Universiteit Leuven, Moscow Higher School of Economics and the GZA-hospital group located in Antwerp. The main aim of this system is to offer healthcare management staff a user-friendly and powerful data analysis environment. Using state of the art techniques from computer science and mathematics we show how CORDIET-Healthcare can be used to gain insight in existing care processes and reveal actionable knowledge which can be used to improve the current way of working.

  16. Controlling Software Piracy.

    ERIC Educational Resources Information Center

    King, Albert S.

    1992-01-01

    Explains what software manufacturers are doing to combat software piracy, recommends how managers should deal with this problem, and provides a role-playing exercise to help students understand the issues in software piracy. (SR)

  17. Report: Scientific Software.

    ERIC Educational Resources Information Center

    Borman, Stuart A.

    1985-01-01

    Discusses various aspects of scientific software, including evaluation and selection of commercial software products; program exchanges, catalogs, and other information sources; major data analysis packages; statistics and chemometrics software; and artificial intelligence. (JN)

  18. Experimental control in software reliability certification

    NASA Technical Reports Server (NTRS)

    Trammell, Carmen J.; Poore, Jesse H.

    1994-01-01

    There is growing interest in software 'certification', i.e., confirmation that software has performed satisfactorily under a defined certification protocol. Regulatory agencies, customers, and prospective reusers all want assurance that a defined product standard has been met. In other industries, products are typically certified under protocols in which random samples of the product are drawn, tests characteristic of operational use are applied, analytical or statistical inferences are made, and products meeting a standard are 'certified' as fit for use. A warranty statement is often issued upon satisfactory completion of a certification protocol. This paper outlines specific engineering practices that must be used to preserve the validity of the statistical certification testing protocol. The assumptions associated with a statistical experiment are given, and their implications for statistical testing of software are described.

  19. Software engineering for ESO's VLT project

    NASA Astrophysics Data System (ADS)

    Filippi, G.

    1994-12-01

    This paper reports on the experience at the European Southern Observatory on the application of software engineering techniques to a 200 man-year control software project for the Very Large Telescope (VLT). This shall provide astronomers, before the end of the century, with one of the most powerful telescopes in the world. From the definition of the general model, described in the software management plan, specific activities have been and will be defined: standards for documents and for code development, design approach using a CASE tool, the process of reviewing both documentation and code, quality assurance, test strategy, etc. The initial choices, the current implementation and the future planned activities are presented and, where feedback is already available, pros and cons are discussed.

  20. Space Flight Software Development Software for Intelligent System Health Management

    NASA Technical Reports Server (NTRS)

    Trevino, Luis C.; Crumbley, Tim

    2004-01-01

    The slide presentation examines the Marshall Space Flight Center Flight Software Branch, including software development projects, mission critical space flight software development, software technical insight, advanced software development technologies, and continuous improvement in the software development processes and methods.

  1. Coproduction of healthcare service

    PubMed Central

    Batalden, Maren; Batalden, Paul; Margolis, Peter; Seid, Michael; Armstrong, Gail; Opipari-Arrigan, Lisa; Hartung, Hans

    2016-01-01

    Efforts to ensure effective participation of patients in healthcare are called by many names—patient centredness, patient engagement, patient experience. Improvement initiatives in this domain often resemble the efforts of manufacturers to engage consumers in designing and marketing products. Services, however, are fundamentally different than products; unlike goods, services are always ‘coproduced’. Failure to recognise this unique character of a service and its implications may limit our success in partnering with patients to improve health care. We trace a partial history of the coproduction concept, present a model of healthcare service coproduction and explore its application as a design principle in three healthcare service delivery innovations. We use the principle to examine the roles, relationships and aims of this interdependent work. We explore the principle's implications and challenges for health professional development, for service delivery system design and for understanding and measuring benefit in healthcare services. PMID:26376674

  2. Cholesterol screening and life assurance.

    PubMed Central

    Neil, H A; Mant, D

    1991-01-01

    OBJECTIVES--To examine how insurance companies assess proposals for life assurance from applicants with raised cholesterol concentrations and to determine the excess mortality rating applied. DESIGN--Survey of 49 companies underwriting term life assurance. SETTING--United Kingdom. SUBJECTS--Four fictional men aged 30 seeking 20 year term policies paying benefit only on death. Two had total cholesterol concentrations of 6.4 and 8.1 mmol/l but no other cardiovascular risk factors; one was overweight, hypertensive, smoked 20 cigarettes daily, and had a total cholesterol concentration of 8.1 mmol/l; and one had possible familial hypercholesterolaemia and a total cholesterol concentration of 10.7 mmol/l after treatment. MAIN OUTCOME MEASURE--Percentage excess mortality rating. RESULTS--All companies used explicit criteria to assess the mortality risk associated with hyperlipidaemias, and 47 companies applied the same criteria to men and women. No excess mortality rating was imposed on an applicant with a total cholesterol concentration of 6.4 mmol/l, but a small excess was applied to an applicant with a concentration of 8.1 mmol/l (median excess 50%, range 0-75%). When multiple cardiovascular risk factors were present the same concentration of 8.1 mmol/l resulted in a substantial excess (median 135%, range 50-200%). A smaller but more variable excess was applied to an applicant with possible familial hypercholesterolaemia (median 75%, range 0-200%). CONCLUSIONS--Despite considerable differences among companies in the excess mortality ratings applied, increases in term life assurance premiums are likely to be restricted to patients with severe hypercholesterolaemia, in particular those with familial hypercholesterolaemia. In the absence of other cardiovascular risk factors milder hypercholesterolaemia is unlikely to result in higher premiums. PMID:2025730

  3. Product Assurance for Spaceflight Hardware

    NASA Technical Reports Server (NTRS)

    Monroe, Mike

    1995-01-01

    This report contains information about the tasks I have completed and the valuable experience I have gained at NASA. The report is divided into two different sections followed by a program summary sheet. The first section describes the two reports I have completed for the Office of Mission Assurance (OMA). I describe the approach and the resources and facilities used to complete each report. The second section describes my experience working in the Receipt Inspection/Quality Assurance Lab (RI/QA). The first report described is a Product Assurance Plan for the Gas Permeable Polymer Materials (GPPM) mission. The purpose of the Product Assurance Plan is to define the various requirements which are to be met through completion of the GPPM mission. The GPPM experiment is a space payload which will be flown in the shuttle's SPACEHAB module. The experiment will use microgravity to enable production of complex polymeric gas permeable materials. The second report described in the first section is a Fracture Analysis for the Mir Environmental Effects Payload (MEEP). The Fracture Analysis report is a summary of the fracture control classifications for all structural elements of the MEEP. The MEEP hardware consists of four experiment carriers, each of which contains an experiment container holding a passive experiment. The MEEP hardware will be attached to the cargo bay of the space shuttle. It will be transferred by Extravehicular Activity and mounted on the Mir space station. The second section of this report describes my experiences in the RVQA lab. I listed the different equipment I used at the lab and their functions. I described the extensive inspection process that must be completed for spaceflight hardware. Included, at the end of this section, are pictures of most of the equipment used in the lab. There is a summary sheet located at the end of this report. It briefly describes the valuable experience I have gained at NASA this summer and what I will be able to take

  4. Radiation Hardness Assurance (RHA) Guideline

    NASA Technical Reports Server (NTRS)

    Campola, Michael J.

    2016-01-01

    Radiation Hardness Assurance (RHA) consists of all activities undertaken to ensure that the electronics and materials of a space system perform to their design specifications after exposure to the mission space environment. The subset of interests for NEPP and the REAG, are EEE parts. It is important to register that all of these undertakings are in a feedback loop and require constant iteration and updating throughout the mission life. More detail can be found in the reference materials on applicable test data for usage on parts.

  5. EPA Quality Assurance Policy Statement

    EPA Pesticide Factsheets

    This document may be of assistance in applying the New Source Review (NSR) air permitting regulations including the Prevention of Significant Deterioration (PSD) requirements. This document is part of the NSR Policy and Guidance Database. Some documents in the database are a scanned or retyped version of a paper photocopy of the original. Although we have taken considerable effort to quality assure the documents, some may contain typographical errors. Contact the office that issued the document if you need a copy of the original.

  6. Explicate '78: Uncovering the Implicit Assurance Case in DO-178C

    NASA Technical Reports Server (NTRS)

    Holloway, C. Michael

    2015-01-01

    For about two decades, compliance with Software Considerations in Airborne Systems and Equipment Certification (DO-178B/ED-12B) has been the primary means for receiving regulatory approval for using software on commercial airplanes. A new edition of the standard, DO-178C/ED-12C, was published in December 2011, and recognized by regulatory bodies in 2013. The purpose remains unchanged: to provide guidance 'for the production of software for airborne systems and equipment that performs its intended function with a level of confidence in safety that complies with airworthiness requirements.' The text of the guidance does not directly explain how its collection of objectives contributes to achieving this purpose; thus, the assurance case for the document is implicit. This paper presents an explicit assurance case developed as part of research jointly sponsored by the Federal Aviation Administration and the National Aeronautics and Space Administration.

  7. Enabling mHealth while assuring compliance: reliable and secure information access in a mobile world.

    PubMed

    Wirth, Axel

    2012-01-01

    An increasingly mobile clinical workforce rapidly adopting consumer devices to access mobile, cloud-based applications, complemented by the wide range of mobile storage devices and other portable electronics, such as digital cameras, MP3 players, can make it difficult to efficiently assure compliance without impacting user productivity. This article reviewed a number of healthcare use cases and introduced comprehensive concepts and possible automated solutions to meet the requirements of a highly complex infrastructure of devices accessing confidential information.

  8. Health information management for research and quality assurance: the Comprehensive Renal Transplant Research Information System.

    PubMed

    Famure, Olusegun; Phan, Nicholas Anh-Tuan; Kim, Sang Joseph

    2014-01-01

    The Kidney Transplant Program at the Toronto General Hospital uses numerous electronic health record platforms housing patient health information that is often not coded in a systematic manner to facilitate quality assurance and research. To address this, the comprehensive renal transplant research information system was conceived by a multidisciplinary healthcare team. Data analysis from comprehensive renal transplant research information system presented at programmatic retreats, scientific meetings, and peer-reviewed manuscripts contributes to quality improvement and knowledge in kidney transplantation.

  9. [Structures and quality assurance of preventive care and health promotion in Germany].

    PubMed

    Kliche, T

    2011-02-01

    In order to identify requirements of quality assurance in this field, a general description of prevention, health promotion and education is outlined, based upon healthcare supply analyses and 158 interviews with experts. Prominent features are, among others, a distinctive heterogeneity and complexity of settings, suppliers, and interventions; supply of coverage is below public health criteria (needs); weak outcome evaluation; competition among suppliers, providers, and political agencies and decision makers; need for intra- and intersectoral coordination; the lack of evidence-based healthcare planning; and hurdles for quality assurance. A structural taxonomy of quality assurance systems is then developed, consisting of three dimensions: validity (quality of information), regularity, and degree of commitment and obligation. In terms of these dimensions, important systems of quality assurance in prevention, health promotion and education in Germany are analyzed. A number of different systems and approaches can be found. However, most of them share questionable validity, regularity, and degree of obligation. Increased commitment on behalf of providers, suppliers, and political institutions and decision makers for the quality of preventive interventions is inevitable in order to raise the performance of prevention and health promotion in Germany to their potential effectiveness.

  10. GSFC Safety and Mission Assurance Organization

    NASA Technical Reports Server (NTRS)

    Kelly, Michael P.

    2010-01-01

    This viewgraph presentation reviews NASA Goddard Space Flight Center's approach to safety and mission assurance. The contents include: 1) NASA GSFC Background; 2) Safety and Mission Assurance Directorate; 3) The Role of SMA-D and the Technical Authority; 4) GSFC Mission assurance Requirements; 5) GSFC Systems Review Office (SRO); 6) GSFC Supply Chain Management Program; and 7) GSFC ISO9001/AS9100 Status Brief.

  11. Quality Assurance: Patient Chart Reviews

    NASA Astrophysics Data System (ADS)

    Oginni, B. M.; Odero, D. O.

    2009-07-01

    Recent developments in radiation therapy have immensely impacted the way the radiation dose is delivered to patients undergoing radiation treatments. However, the fundamental quality assurance (QA) issues underlying the radiation therapy still remain the accuracy of the radiation dose and the radiation safety. One of the major duties of clinical medical physicists in the radiation therapy departments still revolves around ensuring the accuracy of dose delivery to the planning target volume (PTV), the reduction of unintended radiation to normal organs and minimization of the radiation exposure to the medical personnel based on ALARA (as low as reasonably achievable) principle. Many of the errors in radiation therapy can be minimized through a comprehensive program of periodic checks. One of the QA procedures on the patient comes in the form of chart reviews which could be in either electronic or paper-based format. We present the quality assurance procedures that have to be performed on the patient records from the beginning and periodically to the end of the treatment, based on the guidelines from the American Association of Physicists in Medicine (AAPM) and American College of Physicians (ACP).

  12. Non-developmental item computer systems and the malicious software threat

    NASA Technical Reports Server (NTRS)

    Bown, Rodney L.

    1991-01-01

    The following subject areas are covered: a DOD development system - the Army Secure Operating System; non-development commercial computer systems; security, integrity, and assurance of service (SI and A); post delivery SI and A and malicious software; computer system unique attributes; positive feedback to commercial computer systems vendors; and NDI (Non-Development Item) computers and software safety.

  13. Model-Based Assurance Case+ (MBAC+): Tutorial on Modeling Radiation Hardness Assurance Activities

    NASA Technical Reports Server (NTRS)

    Austin, Rebekah; Label, Ken A.; Sampson, Mike J.; Evans, John; Witulski, Art; Sierawski, Brian; Karsai, Gabor; Mahadevan, Nag; Schrimpf, Ron; Reed, Robert A.

    2017-01-01

    This presentation will cover why modeling is useful for radiation hardness assurance cases, and also provide information on Model-Based Assurance Case+ (MBAC+), NASAs Reliability Maintainability Template, and Fault Propagation Modeling.

  14. Software productivity improvement through software engineering technology

    NASA Technical Reports Server (NTRS)

    Mcgarry, F. E.

    1985-01-01

    It has been estimated that NASA expends anywhere from 6 to 10 percent of its annual budget on the acquisition, implementation and maintenance of computer software. Although researchers have produced numerous software engineering approaches over the past 5-10 years; each claiming to be more effective than the other, there is very limited quantitative information verifying the measurable impact htat any of these technologies may have in a production environment. At NASA/GSFC, an extended research effort aimed at identifying and measuring software techniques that favorably impact productivity of software development, has been active over the past 8 years. Specific, measurable, software development technologies have been applied and measured in a production environment. Resulting software development approaches have been shown to be effective in both improving quality as well as productivity in this one environment.

  15. Seven Processes that Enable NASA Software Engineering Technologies

    NASA Technical Reports Server (NTRS)

    Housch, Helen; Godfrey, Sally

    2011-01-01

    This slide presentation reviews seven processes that NASA uses to ensure that software is developed, acquired and maintained as specified in the NPR 7150.2A requirement. The requirement is to ensure that all software be appraised for the Capability Maturity Model Integration (CMMI). The enumerated processes are: (7) Product Integration, (6) Configuration Management, (5) Verification, (4) Software Assurance, (3) Measurement and Analysis, (2) Requirements Management and (1) Planning & Monitoring. Each of these is described and the group(s) that are responsible is described.

  16. Experience with Formal Methods techniques at the Jet Propulsion Laboratory from a quality assurance perspective

    NASA Technical Reports Server (NTRS)

    Kelly, John C.; Covington, Rick

    1993-01-01

    Recent experience with Formal Methods (FM) in the Software Quality Assurance Section at the Jet Propulsion Lab is presented. An integrated Formal Method process is presented to show how related existing requirements analysis and FM techniques complement one another. Example application of FM techniques such as formal specifications and specification animators are presented. The authors suggest that the quality assurance organization is a natural home for the Formal Methods specialist, whose expertise can then be used to best advantage across a range of projects.

  17. Agile Software Development

    ERIC Educational Resources Information Center

    Biju, Soly Mathew

    2008-01-01

    Many software development firms are now adopting the agile software development method. This method involves the customer at every level of software development, thus reducing the impact of change in the requirement at a later stage. In this article, the principles of the agile method for software development are explored and there is a focus on…

  18. Decentralized Software Architecture

    DTIC Science & Technology

    2002-12-01

    recent trends in software architecture towards integrating services across organizational boundaries. This technical report investigates how...historical trends forcing decentralization in software; as well as design, implement, and evaluate a proposed software architectural style called...applied extensively, if indiscriminately, to de- scribe recent trends in software architecture towards inte- grating services across organizational

  19. Integrating a flexible modeling framework (FMF) with the network security assessment instrument to reduce software security risk

    NASA Technical Reports Server (NTRS)

    Gilliam, D. P.; Powell, J. D.

    2002-01-01

    This paper presents a portion of an overall research project on the generation of the network security assessment instrument to aid developers in assessing and assuring the security of software in the development and maintenance lifecycles.

  20. V & V Within Reuse-Based Software Engineering

    NASA Technical Reports Server (NTRS)

    Addy, Edward A.

    1996-01-01

    Verification and validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission critical software. This paper describes the working group's success in identifying V&V tasks that could be performed in the domain engineering and transition levels of reuse-based software engineering. The primary motivation for V&V at the domain level is to provide assurance that the domain requirements are correct and that the domain artifacts correctly implement the domain requirements. A secondary motivation is the possible elimination of redundant V&V activities at the application level. The group also considered the criteria and motivation for performing V&V in domain engineering.

  1. Software Formal Inspections Standard

    NASA Technical Reports Server (NTRS)

    1993-01-01

    This Software Formal Inspections Standard (hereinafter referred to as Standard) is applicable to NASA software. This Standard defines the requirements that shall be fulfilled by the software formal inspections process whenever this process is specified for NASA software. The objective of this Standard is to define the requirements for a process that inspects software products to detect and eliminate defects as early as possible in the software life cycle. The process also provides for the collection and analysis of inspection data to improve the inspection process as well as the quality of the software.

  2. Mobile Usability Testing in Healthcare: Methodological Approaches.

    PubMed

    Borycki, Elizabeth M; Monkman, Helen; Griffith, Janessa; Kushniruk, Andre W

    2015-01-01

    The use of mobile devices and healthcare applications is increasing exponentially worldwide. This has lead to the need for the healthcare industry to develop a better understanding of the impact of the usability of mobile software and hardware upon consumer and health professional adoption and use of these technologies. There are many methodological approaches that can be employed in conducting usability evaluation of mobile technologies. More obtrusive approaches to collecting study data may lead to changes in study participant behaviour, leading to study results that are less consistent with how the technologies will be used in the real-world. Alternatively, less obstrusive methods used in evaluating the usability of mobile software and hardware in-situ and laboratory settings can lead to less detailed information being collected about how an individual interacts with both the software and hardware. In this paper we review and discuss several innovative mobile usability evaluation methods on a contiuum from least to most obtrusive and their effects on the quality of the usability data collected. The strengths and limitations of methods are also discussed.

  3. Professionalism, Profession and Quality Assurance Practitioners in External Quality Assurance Agencies in Higher Education

    ERIC Educational Resources Information Center

    Cheung, Jordan C. M.

    2015-01-01

    This article seeks to spark a dialectic discussion on the establishment of a set of professional competencies for quality assurance practitioners who serve in external quality assurance agencies in higher education. Such a need is identified due to the shortage of relevant and sufficient coverage in the quality assurance literature. To…

  4. Language interpreting as social justice work: perspectives of formal and informal healthcare interpreters.

    PubMed

    Hilfinger Messias, DeAnne K; McDowell, Liz; Estrada, Robin Dawson

    2009-01-01

    The assurance that limited-English-proficient individuals have access to quality healthcare depends on the availability of competent healthcare interpreters. To further understand the complex work of interpreting, we conducted in-depth interviews with 27 formal and informal healthcare interpreters. Participants identified the technical conduit role as the professional standard. Yet they experienced considerable role dissonance and blurring. From their position "in the middle," they witnessed discrimination and bias. Having a social justice perspective encouraged expanding their role to include advocacy and cultural brokering. Implications for nursing include a shared commitment to language access and social justice.

  5. [Quality measurement using administrative data in mandatory quality assurance].

    PubMed

    Heller, Günther; Szecsenyi, Joachim; Willms, Gerald; Broge, Björn

    2014-01-01

    For several years, the use of administrative data in mandatory quality measurement has been requested by several stakeholders in Germany. Main advantages of using administrative data include the reduction of documentary expenditures and the possibility to perform longitudinal quality analyses across different healthcare units. After a short introduction, a brief overview of the current use of administrative data for mandatory quality assurance as well as current developments is given, which will then be further exemplified by decubital ulcer prophylaxis. By using administrative data coding expenditures in this clinical area could be reduced by nine million data fields. At the same time the population analysed was expanded resulting in a more than tenfold increase in potentially quality-relevant events. Finally, perspectives, further developments, possibilities as well as limits of quality measurement with administrative data are discussed. Copyright © 2014. Published by Elsevier GmbH.

  6. Software component quality evaluation

    NASA Technical Reports Server (NTRS)

    Clough, A. J.

    1991-01-01

    The paper describes a software inspection process that can be used to evaluate the quality of software components. Quality criteria, process application, independent testing of the process and proposed associated tool support are covered. Early results indicate that this technique is well suited for assessing software component quality in a standardized fashion. With automated machine assistance to facilitate both the evaluation and selection of software components, such a technique should promote effective reuse of software components.

  7. Guidance and Control Software Project Data - Volume 1: Planning Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

  8. Leadership strategies in healthcare.

    PubMed

    Menaker, Ronald

    2009-01-01

    Healthcare is one of the largest and most important industries in the United States because it affects every individual in the nation. Numerous parties are stakeholders in healthcare, which contributes to the complexity of change efforts. Physicians and administrators play a significant role by providing direct care and influencing other decisions that impact the delivery of patient care. Success in the healthcare industry is influenced by numerous factors, some of which are controllable and others that are not. Understanding leadership and change management will be increasingly important to overcome resistance to change and to improve relationships, the core of leadership in an environment that will become more challenging. In what follows, different approaches to understanding leadership and change management are presented along with other leadership strategies to enhance the effectiveness of leaders. Raising leader awareness regarding transformational leadership behaviors and developing strategies to increase the use of these behaviors may be helpful to enhance organizational performance.

  9. A New Socio-technical Model for Studying Health Information Technology in Complex Adaptive Healthcare Systems

    PubMed Central

    Sittig, Dean F.; Singh, Hardeep

    2011-01-01

    Conceptual models have been developed to address challenges inherent in studying health information technology (HIT). This manuscript introduces an 8-dimensional model specifically designed to address the socio-technical challenges involved in design, development, implementation, use, and evaluation of HIT within complex adaptive healthcare systems. The 8 dimensions are not independent, sequential, or hierarchical, but rather are interdependent and interrelated concepts similar to compositions of other complex adaptive systems. Hardware and software computing infrastructure refers to equipment and software used to power, support, and operate clinical applications and devices. Clinical content refers to textual or numeric data and images that constitute the “language” of clinical applications. The human computer interface includes all aspects of the computer that users can see, touch, or hear as they interact with it. People refers to everyone who interacts in some way with the system, from developer to end-user, including potential patient-users. Workflow and communication are the processes or steps involved in assuring that patient care tasks are carried out effectively. Two additional dimensions of the model are internal organizational features (e.g., policies, procedures, and culture) and external rules and regulations, both of which may facilitate or constrain many aspects of the preceding dimensions. The final dimension is measurement and monitoring, which refers to the process of measuring and evaluating both intended and unintended consequences of HIT implementation and use. We illustrate how our model has been successfully applied in real-world complex adaptive settings to understand and improve HIT applications at various stages of development and implementation. PMID:20959322

  10. Characteristics of healthcare wastes

    SciTech Connect

    Diaz, L.F.; Eggerth, L.L.; Enkhtsetseg, Sh.

    2008-07-01

    A comprehensive understanding of the quantities and characteristics of the material that needs to be managed is one of the most basic steps in the development of a plan for solid waste management. In this case, the material under consideration is the solid waste generated in healthcare facilities, also known as healthcare waste. Unfortunately, limited reliable information is available in the open literature on the quantities and characteristics of the various types of wastes that are generated in healthcare facilities. Thus, sound management of these wastes, particularly in developing countries, often is problematic. This article provides information on the quantitiesmore » and properties of healthcare wastes in various types of facilities located in developing countries, as well as in some industrialized countries. Most of the information has been obtained from the open literature, although some information has been collected by the authors and from reports available to the authors. Only data collected within approximately the last 15 years and using prescribed methodologies are presented. The range of hospital waste generation (both infectious and mixed solid waste fractions) varies from 0.016 to 3.23 kg/bed-day. The relatively wide variation is due to the fact that some of the facilities surveyed in Ulaanbaatar include out-patient services and district health clinics; these facilities essentially provide very basic services and thus the quantities of waste generated are relatively small. On the other hand, the reported amount of infectious (clinical, yellow bag) waste varied from 0.01 to 0.65 kg/bed-day. The characteristics of the components of healthcare wastes, such as the bulk density and the calorific value, have substantial variability. This literature review and the associated attempt at a comparative analysis point to the need for worldwide consensus on the terms and characteristics that describe wastes from healthcare facilities. Such a consensus would

  11. A Reference Model for Software and System Inspections. White Paper

    NASA Technical Reports Server (NTRS)

    He, Lulu; Shull, Forrest

    2009-01-01

    Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level.

  12. 38 CFR 18.405 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... shall submit an assurance on a form specified by the Secretary, that the program or activity will be... extended in the form of real property or structures on the property, the assurance will obligate the... facility. (d) Covenants. (1) Where Federal financial assistance is provided in the form of real property or...

  13. 38 CFR 18.405 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... shall submit an assurance on a form specified by the Secretary, that the program or activity will be... extended in the form of real property or structures on the property, the assurance will obligate the... facility. (d) Covenants. (1) Where Federal financial assistance is provided in the form of real property or...

  14. 38 CFR 18.405 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... shall submit an assurance on a form specified by the Secretary, that the program or activity will be... extended in the form of real property or structures on the property, the assurance will obligate the... facility. (d) Covenants. (1) Where Federal financial assistance is provided in the form of real property or...

  15. 45 CFR 605.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 605.5 Assurances required. (a) Assurances. Recipients of Federal financial assistance to which... purpose for which Federal financial assistance is extended or for another purpose involving the provision...

  16. 22 CFR 217.5 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 217.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall... subsequent applications to the Agency. (b) Duration of obligation. (1) In the case of Federal financial...

  17. 49 CFR 25.115 - Assurance required.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 25.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  18. 34 CFR 106.4 - Assurance required.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... Federal financial assistance extended to provide real property or structures thereon, such assurance shall... NONDISCRIMINATION ON THE BASIS OF SEX IN EDUCATION PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 106.4 Assurance required. (a) General. Every application for Federal financial assistance shall...

  19. 22 CFR 229.115 - Assurance required.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 229.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  20. 15 CFR 8b.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... the real property or structures are used for the purpose for which Federal financial assistance is... Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  1. 34 CFR 110.23 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... NONDISCRIMINATION ON THE BASIS OF AGE IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Duties of ED Recipients § 110.23 Assurances required. (a) Assurances. An applicant for Federal financial assistance to... case of Federal financial assistance extended in the form of real property or to provide real property...

  2. 45 CFR 84.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 84.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  3. 45 CFR 605.5 - Assurances required.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 605.5 Assurances required. (a) Assurances. Recipients of Federal financial assistance to which... Federal financial assistance extended in the form of real property or to provide real property or...

  4. 7 CFR 15a.4 - Assurance required.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... financial assistance extended to provide real property or structures thereon, such assurance shall obligate... FEDERAL FINANCIAL ASSISTANCE Introduction § 15a.4 Assurance required. (a) General. Every application for Federal financial assistance for any education program or activity shall as condition of its approval...

  5. 22 CFR 229.115 - Assurance required.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 229.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  6. 45 CFR 84.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 84.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  7. 22 CFR 142.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... period during which the real property or structures are used for the purposes for which Federal financial... OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 142.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit...

  8. 45 CFR 1203.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... Assurances required. (a) General. (1) An application for Federal financial assistance to which this part... Federal financial assistance to provide a facility shall, as a condition to its approval and the extension of Federal financial assistance pursuant to the application, contain or be accompanied by, assurances...

  9. 22 CFR 146.115 - Assurance required.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 146.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  10. 34 CFR 104.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... NONDISCRIMINATION ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 104.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to.... (1) In the case of Federal financial assistance extended in the form of real property or to provide...

  11. 22 CFR 142.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... period during which the real property or structures are used for the purposes for which Federal financial... OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 142.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit...

  12. 45 CFR 84.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 84.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  13. 7 CFR 15a.4 - Assurance required.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... financial assistance extended to provide real property or structures thereon, such assurance shall obligate... FEDERAL FINANCIAL ASSISTANCE Introduction § 15a.4 Assurance required. (a) General. Every application for Federal financial assistance for any education program or activity shall as condition of its approval...

  14. 22 CFR 142.5 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... period during which the real property or structures are used for the purposes for which Federal financial... OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 142.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit...

  15. 15 CFR 8b.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... the real property or structures are used for the purpose for which Federal financial assistance is... Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  16. 34 CFR 104.5 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... NONDISCRIMINATION ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 104.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to.... (1) In the case of Federal financial assistance extended in the form of real property or to provide...

  17. 15 CFR 8b.5 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... the real property or structures are used for the purpose for which Federal financial assistance is... Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies... subsequent applications to the Department. (b) Duration of obligation. (1) In the case of Federal financial...

  18. 49 CFR 25.115 - Assurance required.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 25.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  19. 7 CFR 15a.4 - Assurance required.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... financial assistance extended to provide real property or structures thereon, such assurance shall obligate... FEDERAL FINANCIAL ASSISTANCE Introduction § 15a.4 Assurance required. (a) General. Every application for Federal financial assistance for any education program or activity shall as condition of its approval...

  20. 45 CFR 605.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 605.5 Assurances required. (a) Assurances. Recipients of Federal financial assistance to which... Federal financial assistance extended in the form of real property or to provide real property or...

  1. 22 CFR 229.115 - Assurance required.

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 229.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  2. 34 CFR 104.5 - Assurances required.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... NONDISCRIMINATION ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 104.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to.... (1) In the case of Federal financial assistance extended in the form of real property or to provide...

  3. 34 CFR 104.5 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... NONDISCRIMINATION ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 104.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to.... (1) In the case of Federal financial assistance extended in the form of real property or to provide...

  4. 34 CFR 110.23 - Assurances required.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... NONDISCRIMINATION ON THE BASIS OF AGE IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Duties of ED Recipients § 110.23 Assurances required. (a) Assurances. An applicant for Federal financial assistance to... case of Federal financial assistance extended in the form of real property or to provide real property...

  5. 34 CFR 106.4 - Assurance required.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... Federal financial assistance extended to provide real property or structures thereon, such assurance shall... NONDISCRIMINATION ON THE BASIS OF SEX IN EDUCATION PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 106.4 Assurance required. (a) General. Every application for Federal financial assistance shall...

  6. 22 CFR 217.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 217.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall... subsequent applications to the Agency. (b) Duration of obligation. (1) In the case of Federal financial...

  7. 22 CFR 146.115 - Assurance required.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 146.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  8. 10 CFR 1042.115 - Assurance required.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 1042.115 Assurance required. (a) General... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  9. 34 CFR 110.23 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... NONDISCRIMINATION ON THE BASIS OF AGE IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Duties of ED Recipients § 110.23 Assurances required. (a) Assurances. An applicant for Federal financial assistance to... case of Federal financial assistance extended in the form of real property or to provide real property...

  10. 22 CFR 146.115 - Assurance required.

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 146.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  11. 10 CFR 1042.115 - Assurance required.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 1042.115 Assurance required. (a) General... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  12. 49 CFR 25.115 - Assurance required.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 25.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  13. 22 CFR 229.115 - Assurance required.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 229.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  14. 34 CFR 106.4 - Assurance required.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... Federal financial assistance extended to provide real property or structures thereon, such assurance shall... NONDISCRIMINATION ON THE BASIS OF SEX IN EDUCATION PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 106.4 Assurance required. (a) General. Every application for Federal financial assistance shall...

  15. 34 CFR 110.23 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... NONDISCRIMINATION ON THE BASIS OF AGE IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Duties of ED Recipients § 110.23 Assurances required. (a) Assurances. An applicant for Federal financial assistance to... case of Federal financial assistance extended in the form of real property or to provide real property...

  16. 10 CFR 1042.115 - Assurance required.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 1042.115 Assurance required. (a) General... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  17. 34 CFR 106.4 - Assurance required.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... Federal financial assistance extended to provide real property or structures thereon, such assurance shall... NONDISCRIMINATION ON THE BASIS OF SEX IN EDUCATION PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 106.4 Assurance required. (a) General. Every application for Federal financial assistance shall...

  18. 34 CFR 104.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... NONDISCRIMINATION ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 104.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to.... (1) In the case of Federal financial assistance extended in the form of real property or to provide...

  19. 45 CFR 605.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 605.5 Assurances required. (a) Assurances. Recipients of Federal financial assistance to which... Federal financial assistance extended in the form of real property or to provide real property or...

  20. 10 CFR 1042.115 - Assurance required.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 1042.115 Assurance required. (a) General... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  1. 45 CFR 605.5 - Assurances required.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... ON THE BASIS OF HANDICAP IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 605.5 Assurances required. (a) Assurances. Recipients of Federal financial assistance to which... Federal financial assistance extended in the form of real property or to provide real property or...

  2. 7 CFR 15b.5 - Assurances required.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... period during which the real property or structures are used for the purpose for which Federal financial... ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 15b.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit an...

  3. 22 CFR 142.5 - Assurances required.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... period during which the real property or structures are used for the purposes for which Federal financial... OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE General Provisions § 142.5 Assurances required. (a) Assurances. An applicant for Federal financial assistance to which this part applies shall submit...

  4. 22 CFR 146.115 - Assurance required.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 146.115 Assurance required. (a... applications for Federal financial assistance or awards of Federal financial assistance contain, be accompanied... assurance. (b) Duration of obligation. (1) In the case of Federal financial assistance extended to provide...

  5. 34 CFR 110.23 - Assurances required.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... NONDISCRIMINATION ON THE BASIS OF AGE IN PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Duties of ED Recipients § 110.23 Assurances required. (a) Assurances. An applicant for Federal financial assistance to... case of Federal financial assistance extended in the form of real property or to provide real property...

  6. 34 CFR 106.4 - Assurance required.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... Federal financial assistance extended to provide real property or structures thereon, such assurance shall... NONDISCRIMINATION ON THE BASIS OF SEX IN EDUCATION PROGRAMS OR ACTIVITIES RECEIVING FEDERAL FINANCIAL ASSISTANCE Introduction § 106.4 Assurance required. (a) General. Every application for Federal financial assistance shall...

  7. Quality Assurance Reconsidered: A Case Study

    ERIC Educational Resources Information Center

    Gynnild, Vidar

    2007-01-01

    This article examines an external evaluation of the quality assurance system at the Norwegian University of Science and Technology (NTNU) conducted by The Norwegian Agency for Quality Assurance in Higher Education (NOKUT). The external audit report along with internal reports provided by the seven faculties of the university served as the major…

  8. 42 CFR 441.464 - State assurances.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... Self-Directed Personal Assistance Services Program § 441.464 State assurances. A State must assure that... financial accountability for funds expended for self-directed services. (1) Safeguards must prevent the... expenditures. (ii) Requiring the financial management entity to flag significant budget variances (over and...

  9. Quality Assurance Program and Brain Drain

    ERIC Educational Resources Information Center

    Lien, Donald

    2008-01-01

    The number of colleges and universities in most developing countries has increased drastically over the past decades. The quality variation of these institutions is an alarming concern. Quality assurance programs are proposed and implemented. This paper evaluates the effects of quality assurance on the demand for college education, study abroad,…

  10. Academic Achievement Standards and Quality Assurance

    ERIC Educational Resources Information Center

    Sadler, D. Royce

    2017-01-01

    Quality assurance processes have been applied to many aspects of higher education, including teaching, learning and assessment. At least in the latter domain, quality assurance needs its fundamental tenets critically scrutinised. A common but inadequate approach has been to identify and promote learning environment changes "likely to…

  11. Exploring Quality Assurance in Sixth Form Colleges

    ERIC Educational Resources Information Center

    Stoten, David William

    2012-01-01

    Purpose: This paper aims to focus on the changing nature of quality assurance systems within the sixth form college sector. Design/methodology/approach: Ten sixth form colleges were surveyed across England and staff from varying levels within college hierarchies questioned about how quality assurance systems were implemented. Research involved…

  12. Teacher Reaction to ICP Quality Assurance Procedures.

    ERIC Educational Resources Information Center

    Leonard, Ann

    An integral part of the Quality Assurance Manual developed by Southwest Regional Laboratory (SWRL) to accompany the Kindergarten Program is the end-of-program assessment of the Instructional Concepts Program (ICP). Following completion of ICP Quality Assurance assessment, four teachers were interviewed in order to gather information pertinent to…

  13. 78 FR 5813 - 2013 Assuring Radiation Protection

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-01-28

    ...] 2013 Assuring Radiation Protection AGENCY: Food and Drug Administration, HHS. ACTION: Notice. SUMMARY... of the Center for Devices and Radiological Health (CDRH) radiation protection program. The goal of the 2013 Assuring Radiation Protection will be to coordinate Federal, State, and Tribal activities to...

  14. 30 CFR 14.8 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Quality assurance. 14.8 Section 14.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR THE APPROVAL OF FLAME-RESISTANT CONVEYOR BELTS General Provisions § 14.8 Quality assurance. Applicants granted a...

  15. Quality Assurance in Chinese Higher Education

    ERIC Educational Resources Information Center

    Li, Yuan

    2010-01-01

    Quality assurance has been integrated into the fabric of higher education in China, with the issue of quality in higher education--how to evaluate it and how to enhance it--now taking centre stage in Chinese higher education. In the past decade, the development of quality assurance in Chinese higher education has covered a broad spectrum of…

  16. Quality Assurance in Sub-Saharan Africa

    ERIC Educational Resources Information Center

    Materu, Peter; Righetti, Petra

    2010-01-01

    This article assesses the status and practice of higher education quality assurance in sub-Saharan Africa, focusing on degree-granting tertiary institutions. A main finding is that structured national-level quality assurance processes in African higher education are a very recent phenomenon and that most countries face major capacity constraints.…

  17. 7 CFR 652.7 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 7 Agriculture 6 2012-01-01 2012-01-01 false Quality assurance. 652.7 Section 652.7 Agriculture Regulations of the Department of Agriculture (Continued) NATURAL RESOURCES CONSERVATION SERVICE, DEPARTMENT OF AGRICULTURE SUPPORT ACTIVITIES TECHNICAL SERVICE PROVIDER ASSISTANCE General Provisions § 652.7 Quality assurance. (a) NRCS will review, in...

  18. 40 CFR 51.363 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 40 Protection of Environment 2 2011-07-01 2011-07-01 false Quality assurance. 51.363 Section 51.363 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR PROGRAMS REQUIREMENTS FOR PREPARATION, ADOPTION, AND SUBMITTAL OF IMPLEMENTATION PLANS Inspection/Maintenance Program Requirements § 51.363 Quality assurance. An ongoing...

  19. 30 CFR 74.9 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 30 Mineral Resources 1 2011-07-01 2011-07-01 false Quality assurance. 74.9 Section 74.9 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR COAL MINE SAFETY AND HEALTH COAL MINE DUST SAMPLING DEVICES Requirements for Continuous Personal Dust Monitors § 74.9 Quality assurance. (a) General requirements. The applicant shall...

  20. 7 CFR 652.7 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 7 Agriculture 6 2011-01-01 2011-01-01 false Quality assurance. 652.7 Section 652.7 Agriculture Regulations of the Department of Agriculture (Continued) NATURAL RESOURCES CONSERVATION SERVICE, DEPARTMENT OF AGRICULTURE SUPPORT ACTIVITIES TECHNICAL SERVICE PROVIDER ASSISTANCE General Provisions § 652.7 Quality assurance. (a) NRCS will review, in...

  1. 30 CFR 15.8 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 30 Mineral Resources 1 2010-07-01 2010-07-01 false Quality assurance. 15.8 Section 15.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR APPROVAL OF EXPLOSIVES AND SHEATHED EXPLOSIVE UNITS General Provisions § 15.8 Quality assurance. (a) Applicants...

  2. 7 CFR 652.7 - Quality assurance.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 7 Agriculture 6 2014-01-01 2014-01-01 false Quality assurance. 652.7 Section 652.7 Agriculture Regulations of the Department of Agriculture (Continued) NATURAL RESOURCES CONSERVATION SERVICE, DEPARTMENT OF AGRICULTURE SUPPORT ACTIVITIES TECHNICAL SERVICE PROVIDER ASSISTANCE General Provisions § 652.7 Quality assurance. (a) NRCS will review, in...

  3. 30 CFR 7.7 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 30 Mineral Resources 1 2010-07-01 2010-07-01 false Quality assurance. 7.7 Section 7.7 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS TESTING BY APPLICANT OR THIRD PARTY General § 7.7 Quality assurance. Applicants granted an approval or an extension of approval...

  4. 40 CFR 51.363 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 40 Protection of Environment 2 2013-07-01 2013-07-01 false Quality assurance. 51.363 Section 51.363 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR PROGRAMS REQUIREMENTS FOR PREPARATION, ADOPTION, AND SUBMITTAL OF IMPLEMENTATION PLANS Inspection/Maintenance Program Requirements § 51.363 Quality assurance. An ongoing...

  5. 30 CFR 15.8 - Quality assurance.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 30 Mineral Resources 1 2014-07-01 2014-07-01 false Quality assurance. 15.8 Section 15.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR APPROVAL OF EXPLOSIVES AND SHEATHED EXPLOSIVE UNITS General Provisions § 15.8 Quality assurance. (a) Applicants...

  6. 30 CFR 14.8 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 30 Mineral Resources 1 2011-07-01 2011-07-01 false Quality assurance. 14.8 Section 14.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR THE APPROVAL OF FLAME-RESISTANT CONVEYOR BELTS General Provisions § 14.8 Quality assurance. Applicants granted a...

  7. 48 CFR 2453.246 - Quality Assurance.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... 48 Federal Acquisition Regulations System 6 2014-10-01 2014-10-01 false Quality Assurance. 2453.246 Section 2453.246 Federal Acquisition Regulations System DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT CLAUSES AND FORMS FORMS Prescription of Forms 2453.246 Quality Assurance...

  8. 30 CFR 15.8 - Quality assurance.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 30 Mineral Resources 1 2011-07-01 2011-07-01 false Quality assurance. 15.8 Section 15.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR APPROVAL OF EXPLOSIVES AND SHEATHED EXPLOSIVE UNITS General Provisions § 15.8 Quality assurance. (a) Applicants...

  9. 40 CFR 51.363 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 40 Protection of Environment 2 2010-07-01 2010-07-01 false Quality assurance. 51.363 Section 51.363 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR PROGRAMS REQUIREMENTS FOR PREPARATION, ADOPTION, AND SUBMITTAL OF IMPLEMENTATION PLANS Inspection/Maintenance Program Requirements § 51.363 Quality assurance. An ongoing...

  10. 30 CFR 74.9 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Quality assurance. 74.9 Section 74.9 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR COAL MINE SAFETY AND HEALTH COAL MINE DUST SAMPLING DEVICES Requirements for Continuous Personal Dust Monitors § 74.9 Quality assurance. (a) General requirements. The applicant shall...

  11. 30 CFR 7.7 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Quality assurance. 7.7 Section 7.7 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS TESTING BY APPLICANT OR THIRD PARTY General § 7.7 Quality assurance. Applicants granted an approval or an extension of approval...

  12. 30 CFR 14.8 - Quality assurance.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 30 Mineral Resources 1 2010-07-01 2010-07-01 false Quality assurance. 14.8 Section 14.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR THE APPROVAL OF FLAME-RESISTANT CONVEYOR BELTS General Provisions § 14.8 Quality assurance. Applicants granted a...

  13. 48 CFR 2453.246 - Quality Assurance.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... 48 Federal Acquisition Regulations System 6 2012-10-01 2012-10-01 false Quality Assurance. 2453.246 Section 2453.246 Federal Acquisition Regulations System DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT CLAUSES AND FORMS FORMS Prescription of Forms 2453.246 Quality Assurance...

  14. 30 CFR 7.7 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Quality assurance. 7.7 Section 7.7 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS TESTING BY APPLICANT OR THIRD PARTY General § 7.7 Quality assurance. Applicants granted an approval or an extension of approval...

  15. 30 CFR 14.8 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Quality assurance. 14.8 Section 14.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR THE APPROVAL OF FLAME-RESISTANT CONVEYOR BELTS General Provisions § 14.8 Quality assurance. Applicants granted a...

  16. 48 CFR 2453.246 - Quality Assurance.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... 48 Federal Acquisition Regulations System 6 2013-10-01 2013-10-01 false Quality Assurance. 2453.246 Section 2453.246 Federal Acquisition Regulations System DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT CLAUSES AND FORMS FORMS Prescription of Forms 2453.246 Quality Assurance...

  17. 30 CFR 15.8 - Quality assurance.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Quality assurance. 15.8 Section 15.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR APPROVAL OF EXPLOSIVES AND SHEATHED EXPLOSIVE UNITS General Provisions § 15.8 Quality assurance. (a) Applicants...

  18. 48 CFR 2453.246 - Quality Assurance.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 48 Federal Acquisition Regulations System 6 2011-10-01 2011-10-01 false Quality Assurance. 2453.246 Section 2453.246 Federal Acquisition Regulations System DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT CLAUSES AND FORMS FORMS Prescription of Forms 2453.246 Quality Assurance...

  19. 30 CFR 15.8 - Quality assurance.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Quality assurance. 15.8 Section 15.8 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION, DEPARTMENT OF LABOR TESTING, EVALUATION, AND APPROVAL OF MINING PRODUCTS REQUIREMENTS FOR APPROVAL OF EXPLOSIVES AND SHEATHED EXPLOSIVE UNITS General Provisions § 15.8 Quality assurance. (a) Applicants...

  20. 40 CFR 51.363 - Quality assurance.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 40 Protection of Environment 2 2014-07-01 2014-07-01 false Quality assurance. 51.363 Section 51.363 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR PROGRAMS REQUIREMENTS FOR PREPARATION, ADOPTION, AND SUBMITTAL OF IMPLEMENTATION PLANS Inspection/Maintenance Program Requirements § 51.363 Quality assurance. An ongoing...