Sample records for information requirements document

  1. 76 FR 39416 - Agency Information Collection Activities: Documentation Requirements for Articles Entered Under...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-07-06

    ... Activities: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions... accordance with the Paperwork Reduction Act: Documentation Requirements for Articles Entered Under Various... techniques or other forms of information. Title: Documentation Requirements for Articles Entered Under...

  2. 7 CFR 1423.6 - Financial information documentation requirements.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... CORPORATION APPROVED WAREHOUSES § 1423.6 Financial information documentation requirements. To be approved under this part, a warehouse operator shall submit a current financial statement at the time of... 7 Agriculture 10 2010-01-01 2010-01-01 false Financial information documentation requirements...

  3. ICESat (GLAS) Science Processing Software Document Series. Volume 3; GLAS Science Software Requirements Document; Ver 2.1

    NASA Technical Reports Server (NTRS)

    Jester, Peggy L.; Lee, Jeffrey; Zukor, Dorothy J. (Technical Monitor)

    2001-01-01

    This document addresses the software requirements of the Geoscience Laser Altimeter System (GLAS) Standard Data Software (SDS) supporting the GLAS instrument on the EOS ICESat Spacecraft. This Software Requirements Document represents the initial collection of the technical engineering information for the GLAS SDS. This information is detailed within the second of four main volumes of the Standard documentation, the Product Specification volume. This document is a "roll-out" from the governing volume outline containing the Concept and Requirements sections.

  4. 20 CFR 669.660 - What planning documents and information are required in the application for MSFW youth grants and...

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... 20 Employees' Benefits 3 2010-04-01 2010-04-01 false What planning documents and information are... PROGRAM UNDER TITLE I OF THE WORKFORCE INVESTMENT ACT The MSFW Youth Program § 669.660 What planning...? The required planning documents and other required information and the submission dates for filing are...

  5. Tank waste remediation system functions and requirements document

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Carpenter, K.E

    1996-10-03

    This is the Tank Waste Remediation System (TWRS) Functions and Requirements Document derived from the TWRS Technical Baseline. The document consists of several text sections that provide the purpose, scope, background information, and an explanation of how this document assists the application of Systems Engineering to the TWRS. The primary functions identified in the TWRS Functions and Requirements Document are identified in Figure 4.1 (Section 4.0) Currently, this document is part of the overall effort to develop the TWRS Functional Requirements Baseline, and contains the functions and requirements needed to properly define the top three TWRS function levels. TWRS Technicalmore » Baseline information (RDD-100 database) included in the appendices of the attached document contain the TWRS functions, requirements, and architecture necessary to define the TWRS Functional Requirements Baseline. Document organization and user directions are provided in the introductory text. This document will continue to be modified during the TWRS life-cycle.« less

  6. 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.

  7. 76 FR 26750 - Agency Information Collection Activities: Documentation Requirements for Articles Entered Under...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-05-09

    ... Activities: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions...: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions. This request... collection: Title: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment...

  8. 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.

  9. 42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 42 Public Health 5 2011-10-01 2011-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

  10. 42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... 42 Public Health 5 2013-10-01 2013-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

  11. 42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... 42 Public Health 5 2012-10-01 2012-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

  12. 42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... 42 Public Health 5 2014-10-01 2014-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

  13. 42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 42 Public Health 5 2010-10-01 2010-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

  14. Microgravity Experiments Safety and Integration Requirements Document Tree

    NASA Technical Reports Server (NTRS)

    Hogan, Jean M.

    1995-01-01

    This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

  15. Live, Model, Learn: Experiencing Information Systems Requirements through Simulation

    ERIC Educational Resources Information Center

    Hartzel, Kathleen S.; Pike, Jacqueline C.

    2015-01-01

    Information system professionals strive to determine requirements by interviewing clients, observing activities at the client's site, and studying existing system documentation. Still this often leads to vague and inaccurate requirements documentation. When teaching the skills needed to determine requirements, it is important to recreate a…

  16. 10 CFR 1045.35 - Training requirements.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    .... (a) RD management officials shall ensure that persons with access to RD and FRD information are trained on the authorities required to classify and declassify RD and FRD information and documents and on... for classifying, declassifying, marking and handling RD and FRD information and documents. (b) The...

  17. 10 CFR 1045.35 - Training requirements.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    .... (a) RD management officials shall ensure that persons with access to RD and FRD information are trained on the authorities required to classify and declassify RD and FRD information and documents and on... for classifying, declassifying, marking and handling RD and FRD information and documents. (b) The...

  18. 10 CFR 1045.35 - Training requirements.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    .... (a) RD management officials shall ensure that persons with access to RD and FRD information are trained on the authorities required to classify and declassify RD and FRD information and documents and on... for classifying, declassifying, marking and handling RD and FRD information and documents. (b) The...

  19. 17 CFR 230.428 - Documents constituting a section 10(a) prospectus for Form S-8 registration statement...

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... employee benefit plan information required by Item 1 of the Form; (ii) The statement of availability of registrant information, employee benefit plan annual reports and other information required by Item 2; and (iii) The documents containing registrant information and employee benefit plan annual reports that are...

  20. Quantitative and qualitative analysis of study-related patient information sheets in randomised neuro-oncology phase III-trials.

    PubMed

    Reinert, Christiane; Kremmler, Lukas; Burock, Susen; Bogdahn, Ulrich; Wick, Wolfgang; Gleiter, Christoph H; Koller, Michael; Hau, Peter

    2014-01-01

    In randomised controlled trials (RCTs), patient informed consent documents are an essential cornerstone of the study flow. However, these documents are often oversized in format and content. Clinical experience suggests that study information sheets are often not used as an aid to decision-making due to their complexity. We analysed nine patient informed consent documents from clinical neuro-oncological phase III-studies running at a German Brain Tumour Centre with the objective to investigate the quality of these documents. Text length, formal layout, readability, application of ethical and legal requirements, scientific evidence and social aspects were used as rating categories. Results were assessed quantitatively by two independents investigators and were depicted using net diagrams. All patient informed consent documents were of insufficient quality in all categories except that ethical and legal requirements were fulfilled. Notably, graduate levels were required to read and understand five of nine consent documents. Quality deficits were consistent between the individual study information texts. Irrespective of formal aspects, a document that is intended to inform and motivate patients to participate in a study needs to be well-structured and understandable. We therefore strongly mandate to re-design patient informed consent documents in a patient-friendly way. Specifically, standardised components with a scientific foundation should be provided that could be retrieved at various times, adapted to the mode of treatment and the patient's knowledge, and could weigh information dependent of the stage of treatment decision. Copyright © 2013 Elsevier Ltd. All rights reserved.

  1. Development of Integrated Programs for Aerospace-Vehicle Design (IPAD)

    NASA Technical Reports Server (NTRS)

    Anderson, O. L.; Calvery, A. L.; Davis, D. A.; Dickmann, L.; Folger, D. H.; Jochem, E. N.; Kitto, C. M.; Vonlimbach, G.

    1977-01-01

    Integrated Programs for Aerospace Vehicle Design (IPAD) system design requirements are given. The information is based on the IPAD User Requirements Document (D6-IPAD-70013-D) and the Integrated Information Processing Requirements Document (D6-IPAD-70012-D). General information about IPAD and a list of the system design requirements that are to be satisfied by the IPAD system are given. The system design requirements definition is to be considered as a baseline definition of the IPAD system design requirements.

  2. 42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 42 Public Health 5 2011-10-01 2011-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

  3. 42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... 42 Public Health 5 2012-10-01 2012-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

  4. 42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... 42 Public Health 5 2014-10-01 2014-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

  5. 42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... 42 Public Health 5 2013-10-01 2013-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

  6. 3 CFR - Freedom of Information Act

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 3 The President 1 2010-01-01 2010-01-01 false Freedom of Information Act Presidential Documents Other Presidential Documents Memorandum of January 21, 2009 Freedom of Information Act Memorandum for the Heads of Executive Departments and Agencies A democracy requires accountability, and accountability requires transparency. As Justice Louis...

  7. 42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 42 Public Health 5 2010-10-01 2010-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

  8. 20 CFR 669.570 - What information is required to document a requested waiver?

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ..., DEPARTMENT OF LABOR NATIONAL FARMWORKER JOBS PROGRAM UNDER TITLE I OF THE WORKFORCE INVESTMENT ACT Performance Accountability, Planning and Waiver Provision § 669.570 What information is required to document a...

  9. 76 FR 76430 - Agency Information Collection Activities: Documents Required Aboard Private Aircraft

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-12-07

    ... certificate of registration, which is also called a ``pink slip'' and is a duplicate copy of the Aircraft... Activities: Documents Required Aboard Private Aircraft AGENCY: U.S. Customs and Border Protection, Department... Required Aboard Private Aircraft. This is a proposed extension of an information collection that was...

  10. 76 FR 33305 - Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-06-08

    ... Identifier: CMS-10379] Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB); Correction AGENCY: Centers for Medicare & Medicaid Services (CMS), HHS. ACTION: Correction of notice. SUMMARY: This document corrects the information provided for [Document Identifier: CMS...

  11. Hanford tanks initiative (HTI) configuration management desk instruction

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Schaus, P.S., Fluor Daniel Hanford

    The purpose of the document is to provide working level directions for submitting requirements, making changes to the requirements database, and entering Project documentation into the HTI Project information and document management system.

  12. 50 CFR 23.25 - What additional information is required on a non-Party CITES document?

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ....25 What additional information is required on a non-Party CITES document? (a) Purpose. Under Article... Certification (1) Export (i) For Appendix-I and -II specimens, the Scientific Authority has advised that the...

  13. Facilitating access to information in large documents with an intelligent hypertext system

    NASA Technical Reports Server (NTRS)

    Mathe, Nathalie

    1993-01-01

    Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation) and tested it on the Space Station Freedom requirement documents. The CID system enables integration of various technical documents in a hypertext framework and includes an intelligent context-sensitive indexing and retrieval mechanism. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time.

  14. Requirements Specification Document

    DOT National Transportation Integrated Search

    1996-04-26

    The System Definition Document identifies the top level processes, data flows, : and system controls for the Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center (C-TIC). This Requirements Specification establishes the requirements...

  15. 78 FR 13368 - Agency Information Collection Activities: Application for Employment Authorization, Form I-765...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-02-27

    ... of total applicants who require English translations of their supporting documents. The percentage of supporting documents for each individual applicant that require translation into English. The time required to find, hire or otherwise obtain translations of supporting documents for immigration benefit...

  16. 39 CFR 3007.2 - Scope.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... information, documents, and things in its possession or control, or any information, documents, and things... under title 39 of the U.S. Code. Information, documents, and things the Postal Service may be required to provide, include, but are not limited to, paper hard copy and electronically stored data and...

  17. 78 FR 40758 - Agency Information Collection Activities: Application for Temporary Protected Status, Form I-821...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-07-08

    ... applicants who require English translations of their supporting documents. The percentage of supporting documents for each individual applicant that require translation into English. The time required to find, hire, or otherwise obtain translations of supporting documents for immigration benefit requests. The...

  18. Information system life-cycle and documentation standards, volume 1

    NASA Technical Reports Server (NTRS)

    Callender, E. David; Steinbacher, Jody

    1989-01-01

    The Software Management and Assurance Program (SMAP) Information System Life-Cycle and Documentation Standards Document describes the Version 4 standard information system life-cycle in terms of processes, products, and reviews. The description of the products includes detailed documentation standards. The standards in this document set can be applied to the life-cycle, i.e., to each phase in the system's development, and to the documentation of all NASA information systems. This provides consistency across the agency as well as visibility into the completeness of the information recorded. An information system is software-intensive, but consists of any combination of software, hardware, and operational procedures required to process, store, or transmit data. This document defines a standard life-cycle model and content for associated documentation.

  19. Tank waste remediation system privatization infrastructure program requirements and document management process guide

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    ROOT, R.W.

    1999-05-18

    This guide provides the Tank Waste Remediation System Privatization Infrastructure Program management with processes and requirements to appropriately control information and documents in accordance with the Tank Waste Remediation System Configuration Management Plan (Vann 1998b). This includes documents and information created by the program, as well as non-program generated materials submitted to the project. It provides appropriate approval/control, distribution and filing systems.

  20. 77 FR 52035 - Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-28

    ... Identifier: CMS-10003] Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB); Correction AGENCY: Centers for Medicare & Medicaid Services (CMS), HHS. ACTION: Correction of notice. SUMMARY: This document corrects a technical error in the notice [Document Identifier: CMS...

  1. 36 CFR 801.7 - Information requirements.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 36 Parks, Forests, and Public Property 3 2014-07-01 2014-07-01 false Information requirements. 801... HISTORIC PRESERVATION REQUIREMENTS OF THE URBAN DEVELOPMENT ACTION GRANT PROGRAM § 801.7 Information requirements. (a) Information To Be Retained by Applicants Determining No Effect. (1) Recommended Documentation...

  2. Software Requirements for the Move to Unix

    NASA Astrophysics Data System (ADS)

    Rees, Paul

    This document provides information concerning the software requirements of each STARLINK site to move entirely to UNIX. It provides a list of proposed UNIX migration deadlines for all sites and lists of software requirements, both STARLINK and non-STARLINK software, which must be met before the existing VMS hardware can be switched off. The information presented in this document is used for the planning of software porting and distribution activities and also for setting realistic migration deadlines for STARLINK sites. The information on software requirements has been provided by STARLINK Site Managers.

  3. Functions and requirements document for interim store solidified high-level and transuranic waste

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Smith-Fewell, M.A., Westinghouse Hanford

    1996-05-17

    The functions, requirements, interfaces, and architectures contained within the Functions and Requirements (F{ampersand}R) Document are based on the information currently contained within the TWRS Functions and Requirements database. The database also documents the set of technically defensible functions and requirements associated with the solidified waste interim storage mission.The F{ampersand}R Document provides a snapshot in time of the technical baseline for the project. The F{ampersand}R document is the product of functional analysis, requirements allocation and architectural structure definition. The technical baseline described in this document is traceable to the TWRS function 4.2.4.1, Interim Store Solidified Waste, and its related requirements, architecture,more » and interfaces.« less

  4. 17 CFR 4.31 - Required delivery of Disclosure Document to prospective clients.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... Disclosure Document to prospective clients. 4.31 Section 4.31 Commodity and Securities Exchanges COMMODITY... Advisors § 4.31 Required delivery of Disclosure Document to prospective clients. (a) Each commodity trading... prospective client a Disclosure Document containing the information set forth in §§ 4.34 and 4.35 for the...

  5. Weather Requirements and Procedures for Step 1: High Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS) Flight Operations in the National Air Space (NAS)

    NASA Technical Reports Server (NTRS)

    2007-01-01

    This cover sheet is for version 2 of the weather requirements document along with Appendix A. The purpose of the requirements document was to identify and to list the weather functional requirements needed to achieve the Access 5 vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS) for Step 1." A discussion of the Federal Aviation Administration (FAA) references and related policies, procedures, and standards is provided as basis for the recommendations supported within this document. Additional procedures and reference documentation related to weather functional requirements is also provided for background. The functional requirements and related information are to be proposed to the FAA and various standards organizations for consideration and approval. The appendix was designed to show that sources of flight weather information are readily available to UAS pilots conducting missions in the NAS. All weather information for this presentation was obtained from the public internet.

  6. Initial SVS Integrated Technology Evaluation Flight Test Requirements and Hardware Architecture

    NASA Technical Reports Server (NTRS)

    Harrison, Stella V.; Kramer, Lynda J.; Bailey, Randall E.; Jones, Denise R.; Young, Steven D.; Harrah, Steven D.; Arthur, Jarvis J.; Parrish, Russell V.

    2003-01-01

    This document presents the flight test requirements for the Initial Synthetic Vision Systems Integrated Technology Evaluation flight Test to be flown aboard NASA Langley's ARIES aircraft and the final hardware architecture implemented to meet these requirements. Part I of this document contains the hardware, software, simulator, and flight operations requirements for this light test as they were defined in August 2002. The contents of this section are the actual requirements document that was signed for this flight test. Part II of this document contains information pertaining to the hardware architecture that was realized to meet these requirements as presented to and approved by a Critical Design Review Panel prior to installation on the B-757 Airborne Research Integrated Experiments Systems (ARIES) airplane. This information includes a description of the equipment, block diagrams of the architecture, layouts of the workstations, and pictures of the actual installations.

  7. Assessment of Beddown Alternatives for the F-35

    DTIC Science & Technology

    2013-01-01

    For More Information Visit RAND at www.rand.org Explore the RAND Corporation View document details Support RAND Purchase this document Browse Reports...copyright law. Permission is required from RAND to reproduce, or reuse in another form, any of our research documents for commercial use. For information ...HOMELAND SECURITY Report Documentation Page Form ApprovedOMB No. 0704-0188 Public reporting burden for the collection of information is estimated to

  8. Electronic availability of microgravity experiments safety and integration requirements documents

    NASA Technical Reports Server (NTRS)

    Hogan, Jean M.

    1995-01-01

    This follow-on to NASA Contractor Report 195447, Microgravity Experiments Safety and Integration Requirements Document Tree, provides the details for accessing the systems that contain the official, electronic versions of the documents initially researched in NASA Contractor Report 195447. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center (PDC), as well as for all developers of space experiments. The PDC has acquired the hardware, software, ID's, and passwords necessary to access most of these systems and is now able to provide customers with current document information as well as immediate delivery of available documents in either electronic or hard copy format.

  9. Functional requirements document for NASA/MSFC Earth Science and Applications Division: Data and information system (ESAD-DIS). Interoperability, 1992

    NASA Technical Reports Server (NTRS)

    Stephens, J. Briscoe; Grider, Gary W.

    1992-01-01

    These Earth Science and Applications Division-Data and Information System (ESAD-DIS) interoperability requirements are designed to quantify the Earth Science and Application Division's hardware and software requirements in terms of communications between personal and visualization workstation, and mainframe computers. The electronic mail requirements and local area network (LAN) requirements are addressed. These interoperability requirements are top-level requirements framed around defining the existing ESAD-DIS interoperability and projecting known near-term requirements for both operational support and for management planning. Detailed requirements will be submitted on a case-by-case basis. This document is also intended as an overview of ESAD-DIs interoperability for new-comers and management not familiar with these activities. It is intended as background documentation to support requests for resources and support requirements.

  10. TWRS configuration management requirement source document

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    The TWRS Configuration Management (CM) Requirement Source document prescribes CM as a basic product life-cycle function by which work and activities are conducted or accomplished. This document serves as the requirements basis for the TWRS CM program. The objective of the TWRS CM program is to establish consistency among requirements, physical/functional configuration, information, and documentation for TWRS and TWRS products, and to maintain this consistency throughout the life-cycle of TWRS and the product, particularly as changes are being made.

  11. Information System Life-Cycle And Documentation Standards (SMAP DIDS)

    NASA Technical Reports Server (NTRS)

    1990-01-01

    Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

  12. The Effects of Tasks on Integrating Information from Multiple Documents

    ERIC Educational Resources Information Center

    Cerdan, Raquel; Vidal-Abarca, Eduardo

    2008-01-01

    The authors examine 2 issues: (a) how students integrate information from multiple scientific documents to describe and explain a physical phenomenon that represents a subset of the information in the documents; and (b) the role of 2 sorts of tasks to achieve this type of integration, either writing an essay on a question requiring integration…

  13. 45 CFR 164.316 - Policies and procedures and documentation requirements.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... Electronic Protected Health Information § 164.316 Policies and procedures and documentation requirements. A... reasonable and appropriate policies and procedures to comply with the standards, implementation... 45 Public Welfare 1 2010-10-01 2010-10-01 false Policies and procedures and documentation...

  14. 45 CFR 164.316 - Policies and procedures and documentation requirements.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... Electronic Protected Health Information § 164.316 Policies and procedures and documentation requirements. A... reasonable and appropriate policies and procedures to comply with the standards, implementation... 45 Public Welfare 1 2011-10-01 2011-10-01 false Policies and procedures and documentation...

  15. Interface Control Specification

    DOT National Transportation Integrated Search

    1996-06-12

    The Requirements Specification Document (#9933.04) identifies the overall system level requirements of the Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center (C-TIC). This document provides details about the data and control flow...

  16. 7 CFR 735.402 - Providers of other electronic documents.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 7 Agriculture 7 2011-01-01 2011-01-01 false Providers of other electronic documents. 735.402... Electronic Providers § 735.402 Providers of other electronic documents. (a) To establish a USWA-authorized...) Records; (6) Conflict of interest requirements; (7) USDA common electronic information requirements; (8...

  17. 7 CFR 735.402 - Providers of other electronic documents.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 7 Agriculture 7 2012-01-01 2012-01-01 false Providers of other electronic documents. 735.402... Electronic Providers § 735.402 Providers of other electronic documents. (a) To establish a USWA-authorized...) Records; (6) Conflict of interest requirements; (7) USDA common electronic information requirements; (8...

  18. 10 CFR 1045.35 - Training requirements.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 10 Energy 4 2010-01-01 2010-01-01 false Training requirements. 1045.35 Section 1045.35 Energy... of Documents Containing Restricted Data and Formerly Restricted Data § 1045.35 Training requirements... trained on the authorities required to classify and declassify RD and FRD information and documents and on...

  19. 10 CFR 1045.35 - Training requirements.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 10 Energy 4 2011-01-01 2011-01-01 false Training requirements. 1045.35 Section 1045.35 Energy... of Documents Containing Restricted Data and Formerly Restricted Data § 1045.35 Training requirements... trained on the authorities required to classify and declassify RD and FRD information and documents and on...

  20. Gary-Chicago-Milwaukee corridor : corridor transportation information center : system glossary

    DOT National Transportation Integrated Search

    1995-10-30

    The following definitions, abbreviations and acronyms are generated from the : System Definition Document (Document #9931.GCM), the Interface Control : Specification (Document #9932.GCM), and the Requirements Specification (Document : #9933.GCM). The...

  1. 15 CFR 30.10 - Retention of export information and the authority to require production of documents.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 15 Commerce and Foreign Trade 1 2010-01-01 2010-01-01 false Retention of export information and the authority to require production of documents. 30.10 Section 30.10 Commerce and Foreign Trade Regulations Relating to Commerce and Foreign Trade BUREAU OF THE CENSUS, DEPARTMENT OF COMMERCE FOREIGN TRADE...

  2. Mask Analysis Program (MAP) reference manual

    NASA Technical Reports Server (NTRS)

    Mitchell, C. L.

    1976-01-01

    A document intended to serve as a User's Manual and a Programmer's Manual for the Mask Analysis Program is presented. The first portion of the document is devoted to the user. It contains all of the information required to execute MAP. The remainder of the document describes the details of MAP software logic. Although the information in this portion is not required to run the program, it is recommended that every user review it to gain an appreciation for the program functions.

  3. Automated documentation generator for advanced protein crystal growth

    NASA Technical Reports Server (NTRS)

    Maddux, Gary A.; Provancha, Anna; Chattam, David

    1994-01-01

    To achieve an environment less dependent on the flow of paper, automated techniques of data storage and retrieval must be utilized. This software system, 'Automated Payload Experiment Tool,' seeks to provide a knowledge-based, hypertext environment for the development of NASA documentation. Once developed, the final system should be able to guide a Principal Investigator through the documentation process in a more timely and efficient manner, while supplying more accurate information to the NASA payload developer. The current system is designed for the development of the Science Requirements Document (SRD), the Experiment Requirements Document (ERD), the Project Plan, and the Safety Requirements Document.

  4. Information Model for Reusability in Clinical Trial Documentation

    ERIC Educational Resources Information Center

    Bahl, Bhanu

    2013-01-01

    In clinical research, New Drug Application (NDA) to health agencies requires generation of a large number of documents throughout the clinical development life cycle, many of which are also submitted to public databases and external partners. Current processes to assemble the information, author, review and approve the clinical research documents,…

  5. EMC Test Report Electrodynamic Dust Shield

    NASA Technical Reports Server (NTRS)

    Carmody, Lynne M.; Boyette, Carl B.

    2014-01-01

    This report documents the Electromagnetic Interference E M I evaluation performed on the Electrodynamic Dust Shield (EDS) which is part of the MISSE-X System under the Electrostatics and Surface Physics Laboratory at Kennedy Space Center. Measurements are performed to document the emissions environment associated with the EDS units. The purpose of this report is to collect all information needed to reproduce the testing performed on the Electrodynamic Dust Shield units, document data gathered during testing, and present the results. This document presents information unique to the measurements performed on the Bioculture Express Rack payload; using test methods prepared to meet SSP 30238 requirements. It includes the information necessary to satisfy the needs of the customer per work order number 1037104. The information presented herein should only be used to meet the requirements for which it was prepared.

  6. Reference Model for an Open Archival Information System

    NASA Technical Reports Server (NTRS)

    1997-01-01

    This document is a technical report for use in developing a consensus on what is required to operate a permanent, or indefinite long-term, archive of digital information. It may be useful as a starting point for a similar document addressing the indefinite long-term preservation of non-digital information. This report establishes a common framework of terms and concepts which comprise an Open Archival Information System (OAIS). It allows existing and future archives to be more meaningfully compared and contrasted. It provides a basis for further standardization of within an archival context and it should promote greater vendor awareness of, and support of , archival requirements. Through the process of normal evolution, it is expected that expansion, deletion, or modification to this document may occur. This report is therefore subject to CCSDS document management and change control procedures.

  7. 2007 Wholesale Power Rate Case Initial Proposal : Wholesale Power Rate Development Study.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    United States. Bonneville Power Administration.

    The Wholesale Power Rate Development Study (WPRDS) calculates BPA proposed rates based on information either developed in the WPRDS or supplied by the other studies that comprise the BPA rate proposal. All of these studies, and accompanying documentation, provide the details of computations and assumptions. In general, information about loads and resources is provided by the Load Resource Study (LRS), WP-07-E-BPA-01, and the LRS Documentation, WP-07-E-BPA-01A. Revenue requirements information, as well as the Planned Net Revenues for Risk (PNNR), is provided in the Revenue Requirement Study, WP-07-E-BPA-02, and its accompanying Revenue Requirement Study Documentation, WP-07-E-BPA-02A and WP-07-E-BPA-02B. The Market Pricemore » Forecast Study (MPFS), WP-07-E-BPA-03, and the MPFS Documentation, WP-07-E-BPA-03A, provide the WPRDS with information regarding seasonal and diurnal differentiation of energy rates, as well information regarding monthly market prices for Demand Rates. In addition, this study provides information for the pricing of unbundled power products. The Risk Analysis Study, WP-07-E-BPA-04, and the Risk Analysis Study Documentation, WP-07-E-BPA-04A, provide short-term balancing purchases as well as secondary energy sales and revenue. The Section 7(b)(2) Rate Test Study, WP-07-E-BPA-06, and the Section 7(b)(2) Rate Test Study Documentation, WP-07-E-BPA-06A, implement Section 7(b)(2) of the Northwest Power Act to ensure that BPA preference customers firm power rates applied to their general requirements are no higher than rates calculated using specific assumptions in the Northwest Power Act.« less

  8. 32 CFR 187.6 - Information requirements.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 32 National Defense 1 2011-07-01 2011-07-01 false Information requirements. 187.6 Section 187.6... ABROAD OF MAJOR DEPARTMENT OF DEFENSE ACTIONS § 187.6 Information requirements. The documents to be... but should include sufficient information on which a determination can be made whether the proposed...

  9. 32 CFR 187.6 - Information requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 32 National Defense 1 2010-07-01 2010-07-01 false Information requirements. 187.6 Section 187.6... ABROAD OF MAJOR DEPARTMENT OF DEFENSE ACTIONS § 187.6 Information requirements. The documents to be... but should include sufficient information on which a determination can be made whether the proposed...

  10. 78 FR 72903 - Collection of Information Under Review by Office of Management and Budget

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-04

    ... will address them accordingly. Viewing Comments and Documents To view comments, as well as documents.... This information is required to control vessel traffic, develop contingency plans and enforce...

  11. An Object-Based Requirements Modeling Method.

    ERIC Educational Resources Information Center

    Cordes, David W.; Carver, Doris L.

    1992-01-01

    Discusses system modeling and specification as it relates to object-based information systems development and software development. An automated system model based on the objects in the initial requirements document is described, the requirements document translator is explained, and a sample application of the technique is provided. (12…

  12. GCS programmer's manual

    NASA Technical Reports Server (NTRS)

    Lowman, Douglas S.; Withers, B. Edward; Shagnea, Anita M.; Dent, Leslie A.; Hayhurst, Kelly J.

    1990-01-01

    A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

  13. Functional Requirements for an Electronic Work Package System

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Oxstrand, Johanna H.

    This document provides a set of high level functional requirements for a generic electronic work package (eWP) system. The requirements have been identified by the U.S. nuclear industry as a part of the Nuclear Electronic Work Packages - Enterprise Requirements (NEWPER) initiative. The functional requirements are mainly applied to eWP system supporting Basic and Moderate types of smart documents, i.e., documents that have fields for recording input such as text, dates, numbers, and equipment status, and documents which incorporate additional functionalities such as form field data “type“ validation (e.g. date, text, number, and signature) of data entered and/or self-populate basicmore » document information (usually from existing host application meta data) on the form when the user first opens it. All the requirements are categorized by the roles; Planner, Supervisor, Craft, Work Package Approval Reviewer, Operations, Scheduling/Work Control, and Supporting Functions. The categories Statistics, Records, Information Technology are also included used to group the requirements. All requirements are presented in Section 2 through Section 11. Examples of more detailed requirements are provided for the majority of high level requirements. These examples are meant as an inspiration to be used as each utility goes through the process of identifying their specific requirements. The report’s table of contents provides a summary of the high level requirements.« less

  14. 46 CFR 503.59 - Safeguarding classified information.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... classification. (b) Whenever classified material is removed from a storage facility, such material shall not be... classification of the information; and (2) The prospective recipient requires access to the information in order... documents that have been destroyed. (k) An inventory of all documents classified higher than confidential...

  15. 46 CFR 503.59 - Safeguarding classified information.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... classification. (b) Whenever classified material is removed from a storage facility, such material shall not be... classification of the information; and (2) The prospective recipient requires access to the information in order... documents that have been destroyed. (k) An inventory of all documents classified higher than confidential...

  16. 46 CFR 503.59 - Safeguarding classified information.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... classification. (b) Whenever classified material is removed from a storage facility, such material shall not be... classification of the information; and (2) The prospective recipient requires access to the information in order... documents that have been destroyed. (k) An inventory of all documents classified higher than confidential...

  17. 76 FR 17032 - Forbearance Petition Filing Requirements

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-03-28

    ... Petition Filing Requirements AGENCY: Federal Communications Commission. ACTION: Final rule; confirmation of... Budget (OMB) had approved the associated information collection requirements. OMB approved those information collection requirements on April 5, 2010, under OMB Control Number 3060-1138. This document...

  18. NASA Docking System (NDS) Users Guide: International Space Station Program. Type 4

    NASA Technical Reports Server (NTRS)

    Tabakman, Alexander

    2010-01-01

    The NASA Docking System (NDS) Users Guide provides an overview of the basic information needed to integrate the NDS onto a Host Vehicle (HV). This Users Guide is intended to provide a vehicle developer with a fundamental understanding of the NDS technical and operations information to support their program and engineering integration planning. The Users Guide identifies the NDS Specification, Interface Definition or Requirement Documents that contain the complete technical details and requirements that a vehicle developer must use to design, develop and verify their systems will interface with NDS. This Guide is an initial reference and must not be used as a design document. In the event of conflict between this Users Guide and other applicable interface definition or requirements documents; the applicable document will take precedence. This Users Guide is organized in three main sections. Chapter 1 provides an overview of the NDS and CDA hardware and the operations concepts for the NDS. Chapter 2 provides information for Host Vehicle Program integration with the NDS Project Office. Chapter 2 describes the NDS Project organization, integration and verification processes, user responsibilities, and specification and interface requirement documents. Chapter 3 provides a summary of basic technical information for the NDS design. Chapter 3 includes NDS hardware component descriptions, physical size and weight characteristics, and summary of the capabilities and constraints for the various NDS sub-systems.

  19. Information retrieval for a document writing assistance program

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Corral, M.L.; Simon, A.; Julien, C.

    This paper presents an Information Retrieval mechanism to facilitate the writing of technical documents in the space domain. To address the need for document exchange between partners in a given project, documents are standardized. The writing of a new document requires the re-use of existing documents or parts thereof. These parts can be identified by {open_quotes}tagging{close_quotes} the logical structure of documents and restored by means of a purpose-built Information Retrieval System (I.R.S.). The I.R.S. implemented in our writing assistance tool uses natural language queries and is based on a statistical linguistic approach which is enhanced by the use of documentmore » structure module.« less

  20. 22 CFR 203.4 - U.S. PVO initial documentation requirements.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... VOLUNTARY ORGANIZATIONS (PVOs) § 203.4 U.S. PVO initial documentation requirements. (a) So that USAID can... an independent certified public accountant (CPA); an Office of Management and Budget (OMB) Circular A... other information as USAID may reasonably require to determine whether the organization meets the...

  1. 22 CFR 203.4 - U.S. PVO initial documentation requirements.

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... VOLUNTARY ORGANIZATIONS (PVOs) § 203.4 U.S. PVO initial documentation requirements. (a) So that USAID can... an independent certified public accountant (CPA); an Office of Management and Budget (OMB) Circular A... other information as USAID may reasonably require to determine whether the organization meets the...

  2. 22 CFR 203.4 - U.S. PVO initial documentation requirements.

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... VOLUNTARY ORGANIZATIONS (PVOs) § 203.4 U.S. PVO initial documentation requirements. (a) So that USAID can... an independent certified public accountant (CPA); an Office of Management and Budget (OMB) Circular A... other information as USAID may reasonably require to determine whether the organization meets the...

  3. 22 CFR 203.4 - U.S. PVO initial documentation requirements.

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ... VOLUNTARY ORGANIZATIONS (PVOs) § 203.4 U.S. PVO initial documentation requirements. (a) So that USAID can... an independent certified public accountant (CPA); an Office of Management and Budget (OMB) Circular A... other information as USAID may reasonably require to determine whether the organization meets the...

  4. An updated look at document security: from initiation to storage or shredder.

    PubMed

    McConnell, Charles R

    2014-01-01

    In these days of close attention to security of information handled electronically, there is often a tendency to overlook the security of hard-copy documents. Document security can involve many areas of business, but the health care department manager's concerns are primarily for patient records and employee documentation. Document security is closely related to growing concerns for individual privacy; guidelines are furnished for protecting employee privacy by separating retention practices for business information from personal information. Sensitive documentation requires rules and procedures for processing, retaining, accessing, storing, and eventually destroying. Also, documents that are missing or incomplete at times present unique problems for the organization. The department manager is provided with some simple rules for safeguarding employee and patient documentation.

  5. Description of the AILS Alerting Algorithm

    NASA Technical Reports Server (NTRS)

    Samanant, Paul; Jackson, Mike

    2000-01-01

    This document provides a complete description of the Airborne Information for Lateral Spacing (AILS) alerting algorithms. The purpose of AILS is to provide separation assurance between aircraft during simultaneous approaches to closely spaced parallel runways. AILS will allow independent approaches to be flown in such situations where dependent approaches were previously required (typically under Instrument Meteorological Conditions (IMC)). This is achieved by providing multiple levels of alerting for pairs of aircraft that are in parallel approach situations. This document#s scope is comprehensive and covers everything from general overviews, definitions, and concepts down to algorithmic elements and equations. The entire algorithm is presented in complete and detailed pseudo-code format. This can be used by software programmers to program AILS into a software language. Additional supporting information is provided in the form of coordinate frame definitions, data requirements, calling requirements as well as all necessary pre-processing and post-processing requirements. This is important and required information for the implementation of AILS into an analysis, a simulation, or a real-time system.

  6. 30 CFR 210.154 - What documents or other information must I submit for Federal oil valuation purposes?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... and Reports-Oil, Gas, and Geothermal Resources § 210.154 What documents or other information must I submit for Federal oil valuation purposes? (a) General. The MMS may require you to submit documents or... submit for Federal oil valuation purposes? 210.154 Section 210.154 Mineral Resources MINERALS MANAGEMENT...

  7. 76 FR 37704 - Federal Acquisition Regulation; Documenting Contractor Performance

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-06-28

    ... Federal Acquisition Regulation; Documenting Contractor Performance AGENCY: Department of Defense (DoD..., and to require all past performance information be entered into the Contractor Performance Assessment... Contractor Performance Information. These changes provide Governmentwide standardized evaluation factors and...

  8. DOE Office of Scientific and Technical Information (OSTI.GOV)

    None, None

    This document provides information on energy consumption in Federal buildings, operations, and vehicles and equipment, and documents activities conducted by Federal agencies to meet the statutory requirements.

  9. 32 CFR 187.6 - Information requirements.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 32 National Defense 1 2013-07-01 2013-07-01 false Information requirements. 187.6 Section 187.6 National Defense Department of Defense OFFICE OF THE SECRETARY OF DEFENSE ENVIRONMENT ENVIRONMENTAL EFFECTS ABROAD OF MAJOR DEPARTMENT OF DEFENSE ACTIONS § 187.6 Information requirements. The documents to be...

  10. Implementing the EuroFIR Document and Data Repositories as accessible resources of food composition information.

    PubMed

    Unwin, Ian; Jansen-van der Vliet, Martine; Westenbrink, Susanne; Presser, Karl; Infanger, Esther; Porubska, Janka; Roe, Mark; Finglas, Paul

    2016-02-15

    The EuroFIR Document and Data Repositories are being developed as accessible collections of source documents, including grey literature, and the food composition data reported in them. These Repositories will contain source information available to food composition database compilers when selecting their nutritional data. The Document Repository was implemented as searchable bibliographic records in the Europe PubMed Central database, which links to the documents online. The Data Repository will contain original data from source documents in the Document Repository. Testing confirmed the FoodCASE food database management system as a suitable tool for the input, documentation and quality assessment of Data Repository information. Data management requirements for the input and documentation of reported analytical results were established, including record identification and method documentation specifications. Document access and data preparation using the Repositories will provide information resources for compilers, eliminating duplicated work and supporting unambiguous referencing of data contributing to their compiled data. Copyright © 2014 Elsevier Ltd. All rights reserved.

  11. An Exploratory Survey of Information Requirements for Instrument Approach Charts

    DOT National Transportation Integrated Search

    1995-03-01

    This report documents a user centered survey and interview effort conducted to analyze the information content of : current Instrument Approach Plates (IAP). In the pilot opinion survey of approach chart information requirements, : respondents indica...

  12. Solid waste information and tracking system client-server conversion project management plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    May, D.L.

    1998-04-15

    This Project Management Plan is the lead planning document governing the proposed conversion of the Solid Waste Information and Tracking System (SWITS) to a client-server architecture. This plan presents the content specified by American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE) standards for software development, with additional information categories deemed to be necessary to describe the conversion fully. This plan is a living document that will be reviewed on a periodic basis and revised when necessary to reflect changes in baseline design concepts and schedules. This PMP describes the background, planning and management of the SWITS conversion.more » It does not constitute a statement of product requirements. Requirements and specification documentation needed for the SWITS conversion will be released as supporting documents.« less

  13. 10 CFR 1707.203 - Filing requirements for demands or requests for documents or testimony.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 10 Energy 4 2014-01-01 2014-01-01 false Filing requirements for demands or requests for documents or testimony. 1707.203 Section 1707.203 Energy DEFENSE NUCLEAR FACILITIES SAFETY BOARD TESTIMONY BY...) The Defense Nuclear Facilities Safety Board reserves the right to require additional information to...

  14. 10 CFR 1707.203 - Filing requirements for demands or requests for documents or testimony.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... 10 Energy 4 2013-01-01 2013-01-01 false Filing requirements for demands or requests for documents or testimony. 1707.203 Section 1707.203 Energy DEFENSE NUCLEAR FACILITIES SAFETY BOARD TESTIMONY BY...) The Defense Nuclear Facilities Safety Board reserves the right to require additional information to...

  15. 10 CFR 1707.203 - Filing requirements for demands or requests for documents or testimony.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 10 Energy 4 2010-01-01 2010-01-01 false Filing requirements for demands or requests for documents or testimony. 1707.203 Section 1707.203 Energy DEFENSE NUCLEAR FACILITIES SAFETY BOARD TESTIMONY BY...) The Defense Nuclear Facilities Safety Board reserves the right to require additional information to...

  16. 10 CFR 1707.203 - Filing requirements for demands or requests for documents or testimony.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 10 Energy 4 2012-01-01 2012-01-01 false Filing requirements for demands or requests for documents or testimony. 1707.203 Section 1707.203 Energy DEFENSE NUCLEAR FACILITIES SAFETY BOARD TESTIMONY BY...) The Defense Nuclear Facilities Safety Board reserves the right to require additional information to...

  17. 36 CFR 1238.12 - What documentation is required for microfilmed records?

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... microforms capture all information contained on the source documents and that they can be used for the... retrieval and use. Agencies must: (a) Arrange, describe, and index the filmed records to permit retrieval of... titling target or header. For fiche, place the titling information in the first frame if the information...

  18. 36 CFR § 1238.12 - What documentation is required for microfilmed records?

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... microforms capture all information contained on the source documents and that they can be used for the... retrieval and use. Agencies must: (a) Arrange, describe, and index the filmed records to permit retrieval of... titling target or header. For fiche, place the titling information in the first frame if the information...

  19. 36 CFR 1238.12 - What documentation is required for microfilmed records?

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... microforms capture all information contained on the source documents and that they can be used for the... retrieval and use. Agencies must: (a) Arrange, describe, and index the filmed records to permit retrieval of... titling target or header. For fiche, place the titling information in the first frame if the information...

  20. 36 CFR 1238.12 - What documentation is required for microfilmed records?

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... microforms capture all information contained on the source documents and that they can be used for the... retrieval and use. Agencies must: (a) Arrange, describe, and index the filmed records to permit retrieval of... titling target or header. For fiche, place the titling information in the first frame if the information...

  1. 36 CFR 1238.12 - What documentation is required for microfilmed records?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... microforms capture all information contained on the source documents and that they can be used for the... retrieval and use. Agencies must: (a) Arrange, describe, and index the filmed records to permit retrieval of... titling target or header. For fiche, place the titling information in the first frame if the information...

  2. User Problems Associated with the Services of Federal and Quasi-Federal Technical Information Producing Agencies.

    ERIC Educational Resources Information Center

    Los Angeles Regional Technical Information Users Council, CA.

    Nine reports of the Los Angeles Regional Technical Information Users Council, which identify and discuss user problem areas and recommend solutions, comprise this document. The topics of the reports are: (1) Air Force Technical Objective Document Release Program (AFTOD); (2) Army Qualitative Requirements Information Program (QDRI); (3)…

  3. Requirements for color technology

    NASA Astrophysics Data System (ADS)

    Campbell, Ronald B., Jr.

    1993-06-01

    The requirements for color technology in the general office are reviewed. The two most salient factors driving the requirements for color are the information explosion and the virtually negligible growth in white collar productivity in the recent past. Accordingly, the business requirement upon color technology is that it be utilized in an effective and efficient manner to increase office productivity. Recent research on productivity and growth has moved beyond the classical two factor productivity model of labor and capital to explicitly include knowledge as a third and vital factor. Documents are agents of knowledge in the general office. Documents articulate, express, disseminate, and communicate knowledge. The central question addressed here is how can color, in conjunction with other techniques such as graphics and document design, improve the growth of knowledge? The central thesis is that the effective use of color to convert information into knowledge is one of the most powerful ways to increase office productivity. Material on the value of color is reviewed. This material is related to the role of documents. Document services are the way in which users access and utilize color technology. The requirements for color technology are then defined against the services taxonomy.

  4. Requirement of scientific documentation for the development of Naturopathy.

    PubMed

    Rastogi, Rajiv

    2006-01-01

    Past few decades have witnessed explosion of knowledge in almost every field. This has resulted not only in the advancement of the subjects in particular but also have influenced the growth of various allied subjects. The present paper explains about the advancement of science through efforts made in specific areas and also through discoveries in different allied fields having an indirect influence upon the subject in proper. In Naturopathy this seems that though nothing particular is added to the basic thoughts or fundamental principles of the subject yet the entire treatment understanding is revolutionised under the influence of scientific discoveries of past few decades. Advent of information technology has further added to the boom of knowledge and many times this seems impossible to utilize these informations for the good of human being because these are not logically arranged in our minds. In the above background, the author tries to define documentation stating that we have today ocean of information and knowledge about various things- living or dead, plants, animals or human beings; the geographical conditions or changing weather and environment. What required to be done is to extract the relevant knowledge and information required to enrich the subject. The author compares documentation with churning of milk to extract butter. Documentation, in fact, is churning of ocean of information to extract the specific, most appropriate, relevant and defined information and knowledge related to the particular subject . The paper besides discussing the definition of documentation, highlights the areas of Naturopathy requiring an urgent necessity to make proper documentations. Paper also discusses the present status of Naturopathy in India, proposes short-term and long-term goals to be achieved and plans the strategies for achieving them. The most important aspect of the paper is due understanding of the limitations of Naturopathy but a constant effort to improve the same with the growth made in various discipline of science so far.

  5. 40 CFR 26.1117 - Documentation of informed consent.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... 40 Protection of Environment 1 2011-07-01 2011-07-01 false Documentation of informed consent. 26.1117 Section 26.1117 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY GENERAL PROTECTION OF HUMAN SUBJECTS Basic Ethical Requirements for Third-Party Human Research for Pesticides Involving...

  6. 40 CFR 26.1117 - Documentation of informed consent.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... 40 Protection of Environment 1 2013-07-01 2013-07-01 false Documentation of informed consent. 26.1117 Section 26.1117 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY GENERAL PROTECTION OF HUMAN SUBJECTS Basic Ethical Requirements for Third-Party Human Research for Pesticides Involving...

  7. 40 CFR 26.1117 - Documentation of informed consent.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... 40 Protection of Environment 1 2012-07-01 2012-07-01 false Documentation of informed consent. 26.1117 Section 26.1117 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY GENERAL PROTECTION OF HUMAN SUBJECTS Basic Ethical Requirements for Third-Party Human Research for Pesticides Involving...

  8. 40 CFR 26.1117 - Documentation of informed consent.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 40 Protection of Environment 1 2010-07-01 2010-07-01 false Documentation of informed consent. 26.1117 Section 26.1117 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY GENERAL PROTECTION OF HUMAN SUBJECTS Basic Ethical Requirements for Third-Party Human Research for Pesticides Involving...

  9. 40 CFR 26.1117 - Documentation of informed consent.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 40 Protection of Environment 1 2014-07-01 2014-07-01 false Documentation of informed consent. 26.1117 Section 26.1117 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY GENERAL PROTECTION OF HUMAN SUBJECTS Basic Ethical Requirements for Third-Party Human Research for Pesticides Involving...

  10. Concept document of the repository-based software engineering program: A constructive appraisal

    NASA Technical Reports Server (NTRS)

    1992-01-01

    A constructive appraisal of the Concept Document of the Repository-Based Software Engineering Program is provided. The Concept Document is designed to provide an overview of the Repository-Based Software Engineering (RBSE) Program. The Document should be brief and provide the context for reading subsequent requirements and product specifications. That is, all requirements to be developed should be traceable to the Concept Document. Applied Expertise's analysis of the Document was directed toward assuring that: (1) the Executive Summary provides a clear, concise, and comprehensive overview of the Concept (rewrite as necessary); (2) the sections of the Document make best use of the NASA 'Data Item Description' for concept documents; (3) the information contained in the Document provides a foundation for subsequent requirements; and (4) the document adequately: identifies the problem being addressed; articulates RBSE's specific role; specifies the unique aspects of the program; and identifies the nature and extent of the program's users.

  11. 78 FR 22554 - Document to Support Submission of an Electronic Common Technical Document-Specifications for File...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-16

    ... documents at either http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements...Vaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm . Dated: April 10, 2013. Leslie Kux...

  12. Resolving the problem of compliance with the ever increasing and changing regulations

    NASA Astrophysics Data System (ADS)

    Leigh, Harley

    1992-01-01

    The most common problem identified at several U.S. Department of Energy (DOE) sites is regulatory compliance. Simply, the project viability depends on identifying regulatory requirements at the beginning of a specific project to avoid possible delays and cost overruns. The Radioisotope Power Systems Facility (RPSF) is using the Regulatory Compliance System (RCS) to deal with the problem that well over 1000 regulatory documents had to be reviewed for possible compliance requirements applicable to the facility. This overwhelming number of possible documents is not atypical of all DOE facilities thus far reviewed using the RCS system. The RCS was developed to provide control and tracking of all the regulatory and institutional requirements on a given project. WASTREN, Inc., developed the RCS through various DOE contracts and continues to enhance and update the system for existing and new contracts. The RCS provides the information to allow the technical expert to assimilate and manage accurate resource information, compile the necessary checklists, and document that the project or facility fulfills all of the appropriate regulatory requirements. The RCS provides on-line information, including status throughout the project life, thereby allowing more intelligent and proactive decision making. Also, consistency and traceability are provided for regulatory compliance documentation.

  13. 40 CFR 265.1090 - Recordkeeping requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... applicable to the facility. Except for air emission control equipment design documentation and information... the operating record for a minimum of 3 years. Air emission control equipment design documentation... explain: How use of the required air emission controls on the tanks would affect the tank design features...

  14. 40 CFR 264.1089 - Recordkeeping requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... facility. Except for air emission control equipment design documentation and information required by... record for a minimum of 3 years. Air emission control equipment design documentation shall be maintained... the owner or operator stating that the control device is designed to operate at the performance level...

  15. 40 CFR 265.1090 - Recordkeeping requirements.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... applicable to the facility. Except for air emission control equipment design documentation and information... the operating record for a minimum of 3 years. Air emission control equipment design documentation... explain: How use of the required air emission controls on the tanks would affect the tank design features...

  16. 40 CFR 264.1089 - Recordkeeping requirements.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... facility. Except for air emission control equipment design documentation and information required by... record for a minimum of 3 years. Air emission control equipment design documentation shall be maintained... the owner or operator stating that the control device is designed to operate at the performance level...

  17. 40 CFR 264.1089 - Recordkeeping requirements.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... facility. Except for air emission control equipment design documentation and information required by... record for a minimum of 3 years. Air emission control equipment design documentation shall be maintained... the owner or operator stating that the control device is designed to operate at the performance level...

  18. 40 CFR 265.1090 - Recordkeeping requirements.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... applicable to the facility. Except for air emission control equipment design documentation and information... the operating record for a minimum of 3 years. Air emission control equipment design documentation... explain: How use of the required air emission controls on the tanks would affect the tank design features...

  19. A hypertext system that learns from user feedback

    NASA Technical Reports Server (NTRS)

    Mathe, Nathalie

    1994-01-01

    Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation). Besides providing an hypertext interface for browsing large documents, the CID system automatically acquires and reuses the context in which previous searches were appropriate. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. Thus, the user continually augments and refines the intelligence of the retrieval system. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time. We successfully tested the CID system with users of the Space Station Freedom requirements documents. We are currently extending CID to other application domains (Space Shuttle operations documents, airplane maintenance manuals, and on-line training). We are also exploring the potential commercialization of this technique.

  20. 11 CFR 9033.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... supporting documentation and other information that the Commission may request. (5) The candidate and the... other information that the Commission may request. If the candidate or the candidate's authorized...) that meet the requirements of 11 CFR 9033.12(b). Upon request, documentation explaining the computer...

  1. 11 CFR 9033.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... supporting documentation and other information that the Commission may request. (5) The candidate and the... other information that the Commission may request. If the candidate or the candidate's authorized...) that meet the requirements of 11 CFR 9033.12(b). Upon request, documentation explaining the computer...

  2. The Johnson Space Center Management Information Systems (JSCMIS). 1: Requirements Definition and Design Specifications for Versions 2.1 and 2.1.1. 2: Documented Test Scenario Environments. 3: Security Design and Specifications

    NASA Technical Reports Server (NTRS)

    1986-01-01

    The Johnson Space Center Management Information System (JSCMIS) is an interface to computer data bases at NASA Johnson which allows an authorized user to browse and retrieve information from a variety of sources with minimum effort. This issue gives requirements definition and design specifications for versions 2.1 and 2.1.1, along with documented test scenario environments, and security object design and specifications.

  3. Live Virtual Constructive (LVC): Interface Control Document (ICD) for the LVC Gateway. [Flight Test 3

    NASA Technical Reports Server (NTRS)

    Jovic, Srba

    2015-01-01

    This Interface Control Document (ICD) documents and tracks the necessary information required for the Live Virtual and Constructive (LVC) systems components as well as protocols for communicating with them in order to achieve all research objectives captured by the experiment requirements. The purpose of this ICD is to clearly communicate all inputs and outputs from the subsystem components.

  4. Solid waste information and tracking system server conversion project management plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    MAY, D.L.

    1999-04-12

    The Project Management Plan governing the conversion of Solid Waste Information and Tracking System (SWITS) to a client-server architecture. The Solid Waste Information and Tracking System Project Management Plan (PMP) describes the background, planning and management of the SWITS conversion. Requirements and specification documentation needed for the SWITS conversion will be released as supporting documents.

  5. Space Telecommunications Radio System (STRS) Application Repository Design and Analysis

    NASA Technical Reports Server (NTRS)

    Handler, Louis M.

    2013-01-01

    The Space Telecommunications Radio System (STRS) Application Repository Design and Analysis document describes the STRS application repository for software-defined radio (SDR) applications intended to be compliant to the STRS Architecture Standard. The document provides information about the submission of artifacts to the STRS application repository, to provide information to the potential users of that information, and for the systems engineer to understand the requirements, concepts, and approach to the STRS application repository. The STRS application repository is intended to capture knowledge, documents, and other artifacts for each waveform application or other application outside of its project so that when the project ends, the knowledge is retained. The document describes the transmission of technology from mission to mission capturing lessons learned that are used for continuous improvement across projects and supporting NASA Procedural Requirements (NPRs) for performing software engineering projects and NASAs release process.

  6. Analysis of a risk prevention document using dependability techniques: a first step towards an effectiveness model

    NASA Astrophysics Data System (ADS)

    Ferrer, Laetitia; Curt, Corinne; Tacnet, Jean-Marc

    2018-04-01

    Major hazard prevention is a main challenge given that it is specifically based on information communicated to the public. In France, preventive information is notably provided by way of local regulatory documents. Unfortunately, the law requires only few specifications concerning their content; therefore one can question the impact on the general population relative to the way the document is concretely created. Ergo, the purpose of our work is to propose an analytical methodology to evaluate preventive risk communication document effectiveness. The methodology is based on dependability approaches and is applied in this paper to the Document d'Information Communal sur les Risques Majeurs (DICRIM; in English, Municipal Information Document on Major Risks). DICRIM has to be made by mayors and addressed to the public to provide information on major hazards affecting their municipalities. An analysis of law compliance of the document is carried out thanks to the identification of regulatory detection elements. These are applied to a database of 30 DICRIMs. This analysis leads to a discussion on points such as usefulness of the missing elements. External and internal function analysis permits the identification of the form and content requirements and service and technical functions of the document and its components (here its sections). Their results are used to carry out an FMEA (failure modes and effects analysis), which allows us to define the failure and to identify detection elements. This permits the evaluation of the effectiveness of form and content of each components of the document. The outputs are validated by experts from the different fields investigated. Those results are obtained to build, in future works, a decision support model for the municipality (or specialised consulting firms) in charge of drawing up documents.

  7. Invisibly Sanitizable Digital Signature Scheme

    NASA Astrophysics Data System (ADS)

    Miyazaki, Kunihiko; Hanaoka, Goichiro; Imai, Hideki

    A digital signature does not allow any alteration of the document to which it is attached. Appropriate alteration of some signed documents, however, should be allowed because there are security requirements other than the integrity of the document. In the disclosure of official information, for example, sensitive information such as personal information or national secrets is masked when an official document is sanitized so that its nonsensitive information can be disclosed when it is requested by a citizen. If this disclosure is done digitally by using the current digital signature schemes, the citizen cannot verify the disclosed information because it has been altered to prevent the leakage of sensitive information. The confidentiality of official information is thus incompatible with the integrity of that information, and this is called the digital document sanitizing problem. Conventional solutions such as content extraction signatures and digitally signed document sanitizing schemes with disclosure condition control can either let the sanitizer assign disclosure conditions or hide the number of sanitized portions. The digitally signed document sanitizing scheme we propose here is based on the aggregate signature derived from bilinear maps and can do both. Moreover, the proposed scheme can sanitize a signed document invisibly, that is, no one can distinguish whether the signed document has been sanitized or not.

  8. 32 CFR 202.11 - Documenting RAB activities.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 32 National Defense 2 2010-07-01 2010-07-01 false Documenting RAB activities. 202.11 Section 202.11 National Defense Department of Defense (Continued) OFFICE OF THE SECRETARY OF DEFENSE (CONTINUED) MISCELLANEOUS RESTORATION ADVISORY BOARDS Operating Requirements § 202.11 Documenting RAB activities. (a) The installation shall document information...

  9. 48 CFR 1837.203-70 - Providing contractors access to sensitive information.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... NATIONAL AERONAUTICS AND SPACE ADMINISTRATION SPECIAL CATEGORIES OF CONTRACTING SERVICE CONTRACTING... contract, as a compliance document. (e) If the service provider will be operating an information technology... 1852.204-76, Security Requirements for Unclassified Information Technology Resources, which requires...

  10. 48 CFR 1837.203-70 - Providing contractors access to sensitive information.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... NATIONAL AERONAUTICS AND SPACE ADMINISTRATION SPECIAL CATEGORIES OF CONTRACTING SERVICE CONTRACTING... contract, as a compliance document. (e) If the service provider will be operating an information technology... 1852.204-76, Security Requirements for Unclassified Information Technology Resources, which requires...

  11. 48 CFR 1837.203-70 - Providing contractors access to sensitive information.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... NATIONAL AERONAUTICS AND SPACE ADMINISTRATION SPECIAL CATEGORIES OF CONTRACTING SERVICE CONTRACTING... contract, as a compliance document. (e) If the service provider will be operating an information technology... 1852.204-76, Security Requirements for Unclassified Information Technology Resources, which requires...

  12. Utilizing the Structure and Content Information for XML Document Clustering

    NASA Astrophysics Data System (ADS)

    Tran, Tien; Kutty, Sangeetha; Nayak, Richi

    This paper reports on the experiments and results of a clustering approach used in the INEX 2008 document mining challenge. The clustering approach utilizes both the structure and content information of the Wikipedia XML document collection. A latent semantic kernel (LSK) is used to measure the semantic similarity between XML documents based on their content features. The construction of a latent semantic kernel involves the computing of singular vector decomposition (SVD). On a large feature space matrix, the computation of SVD is very expensive in terms of time and memory requirements. Thus in this clustering approach, the dimension of the document space of a term-document matrix is reduced before performing SVD. The document space reduction is based on the common structural information of the Wikipedia XML document collection. The proposed clustering approach has shown to be effective on the Wikipedia collection in the INEX 2008 document mining challenge.

  13. Emergency Response Capability Baseline Needs Assessment Compliance Assessment

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Sharry, John A.

    2013-09-16

    This document is the second of a two-part analysis of Emergency Response Capabilities of Lawrence Livermore National Laboratory. The first part, 2013 Baseline Needs Assessment Requirements Document established the minimum performance criteria necessary to meet mandatory requirements. This second part analyses the performance of Lawrence Livermore Laboratory Emergency Management Department to the contents of the Requirements Document. The document was prepared based on an extensive review of information contained in the 2009 BNA, the 2012 BNA document, a review of Emergency Planning Hazards Assessments, a review of building construction, occupancy, fire protection features, dispatch records, LLNL alarm system records, firemore » department training records, and fire department policies and procedures.« less

  14. MARC ES: a computer program for estimating medical information storage requirements.

    PubMed

    Konoske, P J; Dobbins, R W; Gauker, E D

    1998-01-01

    During combat, documentation of medical treatment information is critical for maintaining continuity of patient care. However, knowledge of prior status and treatment of patients is limited to the information noted on a paper field medical card. The Multi-technology Automated Reader Card (MARC), a smart card, has been identified as a potential storage mechanism for casualty medical information. Focusing on data capture and storage technology, this effort developed a Windows program, MARC ES, to estimate storage requirements for the MARC. The program calculates storage requirements for a variety of scenarios using medical documentation requirements, casualty rates, and casualty flows and provides the user with a tool to estimate the space required to store medical data at each echelon of care for selected operational theaters. The program can also be used to identify the point at which data must be uploaded from the MARC if size constraints are imposed. Furthermore, this model can be readily extended to other systems that store or transmit medical information.

  15. 75 FR 82134 - Agency Information Collection Activities: Requests for Comments; Clearance of Renewed Approval of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-12-29

    ... Aviation Regulation. The pilot training requires a logbook endorsement and documentation of a training...) that established a standardized pilot training program. The collection of information is necessary to document participation, completion, and compliance with the pilot training program. Respondents...

  16. 78 FR 67204 - Agency Information Collection Activities: Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-11-08

    ... action to submit an information collection request to the Office of Management and Budget (OMB) and... Verification System (LVS) has been developed, providing an electronic method for fulfilling this requirement... publicly available documents, including the draft supporting statement, at the NRC's Public Document Room...

  17. 77 FR 66663 - Agency Information Collection Activities: Proposed Information Collection; Submission for OMB Review

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-11-06

    ... titled, ``Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions... review and clearance. Company-Run Annual Stress Test Reporting Template and Documentation for Covered... savings associations, to conduct annual stress tests \\2\\ and requires the primary financial regulatory...

  18. Mixture design procedure for flexible base.

    DOT National Transportation Integrated Search

    2013-04-01

    This document provides information on mixture design requirements for a flexible base course. Sections : design requirements, job mix formula, contractor's responsibility, and engineer's responsibility. Tables : material requirements; requirements fo...

  19. 32 CFR 750.27 - Information and supporting documentation.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... documentation. Depending on the type of claim, claimants may be required to submit information, as follows: (1) Death. (i) An authenticated death certificate or other competent evidence showing cause of death, date... decedent to each survivor at time of death; (v) Decedent's general physical and mental condition before...

  20. 32 CFR 750.27 - Information and supporting documentation.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... documentation. Depending on the type of claim, claimants may be required to submit information, as follows: (1) Death. (i) An authenticated death certificate or other competent evidence showing cause of death, date... decedent to each survivor at time of death; (v) Decedent's general physical and mental condition before...

  1. 32 CFR 750.27 - Information and supporting documentation.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... documentation. Depending on the type of claim, claimants may be required to submit information, as follows: (1) Death. (i) An authenticated death certificate or other competent evidence showing cause of death, date... decedent to each survivor at time of death; (v) Decedent's general physical and mental condition before...

  2. 32 CFR 750.27 - Information and supporting documentation.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... documentation. Depending on the type of claim, claimants may be required to submit information, as follows: (1) Death. (i) An authenticated death certificate or other competent evidence showing cause of death, date... decedent to each survivor at time of death; (v) Decedent's general physical and mental condition before...

  3. Implicature, Pragmatics, and Documentation: A Comparative Study

    ERIC Educational Resources Information Center

    Wright, David

    2008-01-01

    This study investigates the link between the linguistic principles of implicature and pragmatics and software documentation. When implicatures are created in conversation or text, the listener or reader is required to fill in missing information not overtly stated. This information is usually filled in on the basis of previous knowledge or…

  4. NASA Space Safety Standards and Procedures for Human Rating Requirements

    NASA Technical Reports Server (NTRS)

    Shivers, C. Herbert

    2009-01-01

    The National Aeronautics and Space Administration of the United States of America (NASA) has arguably led this planet in space exploration and certainly has been one of two major leaders in those endeavors. NASA governance is institutionalized and managed in a series documents arranged in a hierarchy and flowing down to the work levels. A document tree of NASA s documentation in its totality would likely overwhelm and not be very informative. Taken in segments related to the various business topics and focusing in those segments, however, provides a logical and understandable relationship and flow of requirements and processes. That is the nature of this chapter, a selection of NASA documentation pertaining to space exploration and a description of how those documents together form the plan by which NASA business for space exploration is conducted. Information presented herein is taken from NASA publications and is available publicly and no information herein is protected by copyright or security regulations. While NASA documents are the source of information presented herein, any and all views expressed herein and any misrepresentations of NASA data that may occur herein are those of the author and should not be considered NASA official positions or statements, nor should NASA endorsement of anything presented in this work be assumed.

  5. Automated search and retrieval of information from imaged documents using optical correlation techniques

    NASA Astrophysics Data System (ADS)

    Stalcup, Bruce W.; Dennis, Phillip W.; Dydyk, Robert B.

    1999-10-01

    Litton PRC and Litton Data Systems Division are developing a system, the Imaged Document Optical Correlation and Conversion System (IDOCCS), to provide a total solution to the problem of managing and retrieving textual and graphic information from imaged document archives. At the heart of IDOCCS, optical correlation technology provides the search and retrieval of information from imaged documents. IDOCCS can be used to rapidly search for key words or phrases within the imaged document archives. In addition, IDOCCS can automatically compare an input document with the archived database to determine if it is a duplicate, thereby reducing the overall resources required to maintain and access the document database. Embedded graphics on imaged pages can also be exploited; e.g., imaged documents containing an agency's seal or logo can be singled out. In this paper, we present a description of IDOCCS as well as preliminary performance results and theoretical projections.

  6. Towards a Methodology for Identifying Program Constraints During Requirements Analysis

    NASA Technical Reports Server (NTRS)

    Romo, Lilly; Gates, Ann Q.; Della-Piana, Connie Kubo

    1997-01-01

    Requirements analysis is the activity that involves determining the needs of the customer, identifying the services that the software system should provide and understanding the constraints on the solution. The result of this activity is a natural language document, typically referred to as the requirements definition document. Some of the problems that exist in defining requirements in large scale software projects includes synthesizing knowledge from various domain experts and communicating this information across multiple levels of personnel. One approach that addresses part of this problem is called context monitoring and involves identifying the properties of and relationships between objects that the system will manipulate. This paper examines several software development methodologies, discusses the support that each provide for eliciting such information from experts and specifying the information, and suggests refinements to these methodologies.

  7. Generating Hierarchical Document Indices from Common Denominators in Large Document Collections.

    ERIC Educational Resources Information Center

    O'Kane, Kevin C.

    1996-01-01

    Describes an algorithm for computer generation of hierarchical indexes for document collections. The resulting index, when presented with a graphical interface, provides users with a view of a document collection that permits general browsing and informal search activities via an access method that requires no keyboard entry or prior knowledge of…

  8. 78 FR 63461 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Foreign...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-10-24

    ... Certificate, as prescribed in 225.1101(1), requires an offeror to identify, in its proposal, supplies that are... in 225.1101(4), requires the contractor to provide information on shipping documents and customs... of origin. DFARS 252.225-7020, Trade Agreements Certificate, as prescribed in 225.1101(5), requires...

  9. NASA Publications Guide for Authors. Revised

    NASA Technical Reports Server (NTRS)

    2005-01-01

    This document presents guidelines for use by NASA authors for preparing and publishing their scientific and technical information (STI). Section 1 gives an overview. Section 2 describes each type of report in the NASA STI Report Series and other forms of publications. It also discusses dissemination and safeguarding of STI. Section 3 gives technical, data quality, and dissemination reviews, including the mandatory review via NASA Form 1676, NASA Scientific and Technical Information (STI) Document Availability Authorization (DAA). It also describes handling unlimited and limited/restricted STI. Section 4 provides recommended standards for document format, composition, and organization and element of a typical report. Section 5 presents miscellaneous preparation recommendations. Section 6 discusses two required forms, Standard Form 298 and NF-1676. The guide cites additional sources of information of standards, guidelines, and review and approval requirements.

  10. 77 FR 49485 - Agency Information Collection Activities: Proposed Information Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-16

    ... requirement for national banks and Federal savings associations titled, ``Company-Run Annual Stress Test... proposed information collection: Title: Company-Run Annual Stress Test Reporting Template and Documentation... stress tests \\2\\ and requires the primary financial regulatory agency \\3\\ of those financial companies to...

  11. Resolving the problem of compliance with the ever increasing and changing regulations

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Leigh, H.

    1991-06-01

    The most common problem identified at several US Department of Energy (DOE) sites is regulatory compliance. Simply, the project viability depends on identifying regulatory requirements at the beginning of a specific project to avoid possible delays and cost overruns. The Radioisotope Power Systems Facility (RFSP) is using the Regulatory Compliance System (RCS) to deal with the problem that well over 1000 regulatory documents had to be reviewed for possible compliance requirements applicable to the facility. This overwhelming number of possible documents is not atypical of all DOE facilities thus far reviewed using the RCS system. The RCS was developed tomore » provide a control and tracking of all the regulatory and institutional requirements on a given project. WASTREN, Inc., developed the RCS through various DOE contracts and continues to enhance and update the system for existing and new contracts. The RCS provides the information to allow the technical expert to assimilate and manage accurate resource information, compile the checklists, and document that the project or facility fulfills all of the appropriate regulatory requirements. The RCS provides on-line information, including status throughput the project life, thereby allowing more intelligent and proactive decision making. Also, consistency and traceability are provided for regulatory compliance documentation. 1 ref., 1 fig.« less

  12. System Definition Document

    DOT National Transportation Integrated Search

    1996-06-12

    The Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center : (C-TIC) System Definition Document describes the C-TIC concept and defines the : high level processes and dataflows. The Requirements Specification together : with the Inte...

  13. 27 CFR 24.110 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents..., DEPARTMENT OF THE TREASURY LIQUORS WINE Establishment and Operations Application § 24.110 Organizational documents. The supporting information required by paragraph (c) of § 24.109, includes, as applicable, copies...

  14. 32 CFR 2001.24 - Additional requirements.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ...,” “Secret,” and “Confidential” shall not be used to identify classified national security information. (b) Transmittal documents. A transmittal document shall indicate on its face the highest classification level of... Removed or Upon Removal of Attachments, This Document is (Classification Level) (c) Foreign government...

  15. Advanced Marketing/Coop Course Outline.

    ERIC Educational Resources Information Center

    Dixon, Bobby

    This document contains the information required to present a 1-year school course that is the capstone class of a 2-year marketing major and is designed for high school students wishing to develop the skills required for entry into the marketing industry. The document begins with a rationale, brief course description, list of course objectives,…

  16. The Professional Development Requirements of Workplace English Language and Literacy Programme Practitioners: Support Document

    ERIC Educational Resources Information Center

    Berghella, Tina; Molenaar, John; Wyse, Linda

    2006-01-01

    This support document was produced by the authors based on their research for the report, "The Professional Development Requirements of Workplace English Language and Literacy Programme Practitioners," [ED495200] and is an added resource for further information. The original report examines the extent and nature of professional development…

  17. Automated payload experiment tool feasibility study

    NASA Technical Reports Server (NTRS)

    Maddux, Gary A.; Clark, James; Delugach, Harry; Hammons, Charles; Logan, Julie; Provancha, Anna

    1991-01-01

    To achieve an environment less dependent on the flow of paper, automated techniques of data storage and retrieval must be utilized. The prototype under development seeks to demonstrate the ability of a knowledge-based, hypertext computer system. This prototype is concerned with the logical links between two primary NASA support documents, the Science Requirements Document (SRD) and the Engineering Requirements Document (ERD). Once developed, the final system should have the ability to guide a principal investigator through the documentation process in a more timely and efficient manner, while supplying more accurate information to the NASA payload developer.

  18. Requirements, Verification, and Compliance (RVC) Database Tool

    NASA Technical Reports Server (NTRS)

    Rainwater, Neil E., II; McDuffee, Patrick B.; Thomas, L. Dale

    2001-01-01

    This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

  19. 43 CFR 4.612 - What documentation of fees and expenses must I provide?

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 43 Public Lands: Interior 1 2010-10-01 2010-10-01 false What documentation of fees and expenses... Proceedings Information Required from Applicants § 4.612 What documentation of fees and expenses must I provide? (a) Your application must be accompanied by full documentation of the fees and expenses for which...

  20. Validating competence: a new credential for clinical documentation improvement practitioners.

    PubMed

    Ryan, Jessica; Patena, Karen; Judd, Wallace; Niederpruem, Mike

    2013-01-01

    As the health information management (HIM) profession continues to expand and become more specialized, there is an ever-increasing need to identify emerging HIM workforce roles that require a codified level of proficiency and professional standards. The Commission on Certification for Health Informatics and Information Management (CCHIIM) explored one such role-clinical documentation improvement (CDI) practitioner-to define the tasks and responsibilities of the job as well as the knowledge required to perform them effectively. Subject-matter experts (SMEs) defined the CDI specialty by following best practices for job analysis methodology. A random sample of 4,923 CDI-related professionals was surveyed regarding the tasks and knowledge required for the job. The survey data were used to create a weighted blueprint of the six major domains that make up the CDI practitioner role, which later formed the foundation for the clinical documentation improvement practitioner (CDIP) credential. As a result, healthcare organizations can be assured that their certified documentation improvement practitioners have demonstrated excellence in clinical care, treatment, coding guidelines, and reimbursement methodologies.

  1. 27 CFR 25.66 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... Organizational documents. The supporting information required by paragraph (a)(4) of § 25.62 includes, as... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents. 25.66 Section 25.66 Alcohol, Tobacco Products and Firearms ALCOHOL AND TOBACCO TAX AND TRADE BUREAU...

  2. 27 CFR 19.167 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ....167 Organizational documents. The supporting information required by paragraph (c) of § 19.152, and... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents. 19.167 Section 19.167 Alcohol, Tobacco Products and Firearms ALCOHOL AND TOBACCO TAX AND TRADE BUREAU...

  3. 27 CFR 19.916 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... Organizational documents. The supporting information required by paragraph (a)(5) of § 19.915, includes, as... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents. 19.916 Section 19.916 Alcohol, Tobacco Products and Firearms ALCOHOL AND TOBACCO TAX AND TRADE BUREAU...

  4. 27 CFR 18.25 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... § 18.25 Organizational documents. The supporting information required by paragraph (d) of § 18.24... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents. 18.25 Section 18.25 Alcohol, Tobacco Products and Firearms ALCOHOL AND TOBACCO TAX AND TRADE BUREAU...

  5. Tags Extarction from Spatial Documents in Search Engines

    NASA Astrophysics Data System (ADS)

    Borhaninejad, S.; Hakimpour, F.; Hamzei, E.

    2015-12-01

    Nowadays the selective access to information on the Web is provided by search engines, but in the cases which the data includes spatial information the search task becomes more complex and search engines require special capabilities. The purpose of this study is to extract the information which lies in spatial documents. To that end, we implement and evaluate information extraction from GML documents and a retrieval method in an integrated approach. Our proposed system consists of three components: crawler, database and user interface. In crawler component, GML documents are discovered and their text is parsed for information extraction; storage. The database component is responsible for indexing of information which is collected by crawlers. Finally the user interface component provides the interaction between system and user. We have implemented this system as a pilot system on an Application Server as a simulation of Web. Our system as a spatial search engine provided searching capability throughout the GML documents and thus an important step to improve the efficiency of search engines has been taken.

  6. Informed consent document improvement does not increase patients' comprehension in biomedical research

    PubMed Central

    Paris, Adeline; Brandt, Christian; Cornu, Catherine; Maison, Patrick; Thalamas, Claire; Cracowski, Jean-Luc

    2010-01-01

    AIMS International guidelines on ethics in biomedical research require that the informed consent of all enrolled participants is obtained. A written document describing the research, the informed consent (IC) document, must be given to all participants by the investigator. Most IC documents are long, containing much information. The aim of the present study was to determine whether the modification of the IC document by a working group or systematic improvement in its lexicosyntactic readability can improve comprehension of the written information given to patients participating in biomedical research. METHODS One hundred and fifty-nine patients were randomized to read one of the three versions of the IC document: unchanged document, document modified using systematic improvement of lexicosyntactic readability and document modified by a working group. RESULTS Neither the improvement in the lexicosyntactic readability, nor the intervention of the working group significantly improved the score of objective comprehension for the subjects included in this study: it was 66.6 (95% confidence interval 64.0, 69.2) for the control group, 68.8 (66.2, 71.4) for the group with the document improved for lexicosyntactic readability and 69.2 (66.0, 72.4) for the group who read the document improved by the working group (P= 0.38). CONCLUSIONS We failed to show that improving IC document comprehension through a lexicosyntactic approach or by a working group leads to better comprehension. PMID:20233193

  7. 77 FR 54617 - Agency Information Collection Activities: Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-09-05

    .... 4. Who is required or asked to report: Individuals, companies, or organizations requesting document... NRC Headquarters' Public Document Room. Copies of the form are utilized by the reproduction contractor...

  8. 16 CFR 803.3 - Statement of reasons for noncompliance.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... made to obtain such information and documents, including the names of persons who searched for required... and all facts relied on in support thereof, including the identity of each document, its author...

  9. 16 CFR 803.3 - Statement of reasons for noncompliance.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... made to obtain such information and documents, including the names of persons who searched for required... and all facts relied on in support thereof, including the identity of each document, its author...

  10. Electrical Bonding: A Survey of Requirement, Methods, and Specifications

    NASA Technical Reports Server (NTRS)

    Evans, R. W.

    1998-01-01

    This document provides information helpful to engineers imposing electrical bonding requirements, reviewing waiver requests, or modifying specifications on various space programs. Electrical bonding specifications and some of the processes used in the United States have been reviewed. This document discusses the specifications, the types of bonds, the intent of each, and the basic requirements where possible. Additional topics discussed are resistance versus impedance, bond straps, corrosion, finishes, and special applications.

  11. Ethics Review Committee approval and informed consent: an analysis of biomedical publications originating from Sri Lanka

    PubMed Central

    Sumathipala, Athula; Siribaddana, Sisira; Hewege, Suwin; Lekamwattage, Manura; Athukorale, Manjula; Siriwardhana, Chesmal; Murray, Joanna; Prince, Martin

    2008-01-01

    Background International guidelines on research have focused on protecting research participants. Ethical Research Committee (ERC) approval and informed consent are the cornerstones. Externally sponsored research requires approval through ethical review in both the host and the sponsoring country. This study aimed to determine to what extent ERC approval and informed consent procedures are documented in locally and internationally published human subject research carried out in Sri Lanka. Methods We obtained ERC approval in Sri Lanka and the United Kingdom. Theses from 1985 to 2005 available at the Postgraduate Institute of Medicine (PGIM) library affiliated to the University of Colombo were scrutinised using checklists agreed in consultation with senior research collaborators. A Medline search was carried out with MeSH major and minor heading 'Sri Lanka' as the search term for international publications originating in Sri Lanka during 1999 to 2004. All research publications from CMJ during 1999 to 2005 were also scrutinized. Results Of 291 theses, 34% documented ERC approvals and 61% documented obtaining consent. From the international journal survey, 250 publications originated from Sri Lanka of which only 79 full text original research publications could be accessed electronically. Of these 38% documented ERC approval and 39% documented obtaining consent. In the Ceylon Medical Journal 36% documented ERC approval and 37% documented obtaining consent. Conclusion Only one third of the publications scrutinized recorded ERC approval and procurement of informed consent. However, there is a positive trend in documenting these ethical requirements in local postgraduate research and in the local medical journal. PMID:18267015

  12. 12 CFR 1705.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 12 Banks and Banking 7 2010-01-01 2010-01-01 false Documentation of fees and expenses. 1705.12 Section 1705.12 Banks and Banking OFFICE OF FEDERAL HOUSING ENTERPRISE OVERSIGHT, DEPARTMENT OF HOUSING... ACT Information Required from Applicants § 1705.12 Documentation of fees and expenses. (a) The...

  13. 6 CFR 5.45 - Procedure when testimony or production of documents is sought; general.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 6 Domestic Security 1 2010-01-01 2010-01-01 false Procedure when testimony or production of... Procedure when testimony or production of documents is sought; general. (a) If official information is... requiring oral testimony, and identification of potentially relevant documents. (c) The appropriate...

  14. 5 CFR 1216.203 - Filing requirements for litigants seeking documents or testimony.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... documents or testimony. 1216.203 Section 1216.203 Administrative Personnel MERIT SYSTEMS PROTECTION BOARD... OFFICIAL RECORDS IN LEGAL PROCEEDINGS Demands or Requests for Testimony and Production of Documents § 1216... written request must contain the following information: (1) The caption of the legal proceeding, docket...

  15. 27 CFR 22.45 - Organizational documents.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... Permit, Form 5150.22 § 22.45 Organizational documents. The supporting information required by § 22.42(a... 27 Alcohol, Tobacco Products and Firearms 1 2010-04-01 2010-04-01 false Organizational documents. 22.45 Section 22.45 Alcohol, Tobacco Products and Firearms ALCOHOL AND TOBACCO TAX AND TRADE BUREAU...

  16. 78 FR 56898 - Emergency Clearance: Public Information Collection Requirements Submitted to the Office of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-09-16

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Medicare and Medicaid Services [Document Identifier: CMS-10371] Emergency Clearance: Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB) AGENCY: Center for Medicare and Medicaid Services, HHS. In compliance with the requirement of section 3506(c)(2)...

  17. Educating anesthesia residents to obtain and document informed consent for epidural labor analgesia: does simulation play a role?

    PubMed

    Antoniou, A; Marmai, K; Qasem, F; Cherry, R; Jones, P M; Singh, S

    2018-05-01

    Informed consent is required before placing an epidural. At our hospital, teaching of residents about this is done informally at the bedside. This study aimed to assess the ability of anesthesia residents to acquire and retain knowledge required when seeking informed consent for epidural labor analgesia. It assessed how well this knowledge was translated to clinical ability, by assessing the verbal consent process during an interaction with a standardized patient. Twenty anesthesia residents were randomized to a 'didactic group' or a 'simulation group'. Each resident was presented with a written scenario and asked to document the informed consent process, as they normally would do (pre-test). The didactic group then had a presentation about informed consent, while the simulation group members interviewed a simulated patient, the scenarios focusing on different aspects of consent. All residents then read a scenario and documented their informed consent process (post-test). Six weeks later all residents interviewed a standardized patient in labor and documented the consent from this interaction (six-week test). There was no significant difference in the baseline performance of the two groups. Both groups showed significant improvement in their written consent documentation at the immediate time point, the improvement in the didactic group being greater. The didactic group performed better at both the immediate time point and the six-week time point. In this small study, a didactic teaching method proved better than simulation-based teaching in helping residents to gain knowledge needed to obtain informed consent for epidural labor analgesia. Copyright © 2017 Elsevier Ltd. All rights reserved.

  18. 75 FR 80296 - Extension of Filing Accommodation for Static Pool Information in Filings With Respect to Asset...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-12-22

    ... Systems in 1993 for document exchange. PDF captures formatting information from a variety of desktop publishing applications, making it possible to send formatted documents and have them appear on the recipient... Administrative Procedure Act generally requires that an agency publish an adopted rule in the Federal Register 30...

  19. Emergency Operation Center

    NASA Technical Reports Server (NTRS)

    Chinea, Anoushka Z.

    1995-01-01

    The Emergency Operation Center (EOC) is a site from which NASA LaRC Emergency Preparedness Officials exercise control and direction in an emergency. Research was conducted in order to determine what makes an effective EOC. Specifically information concerning the various types of equipment and communication capability that an efficient EOC should contain (i.e., computers, software, telephone systems, radio systems, etc.) was documented. With this information a requirements document was written stating a brief description of the equipment and required quantity to be used in an EOC and then compared to current capabilities at the NASA Langley Research Center.

  20. 77 FR 40790 - Flightcrew Member Duty and Rest Requirements; OMB Approval of Information Collection

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-07-11

    ... concerning this document, contact Dale E. Roberts, Air Transportation Division (AFS-200), Flight Standards... (202) 267- 5749; email: dale[email protected] . For legal questions concerning this document, contact...

  1. Annual report to Congress on Federal Government Energy Management and Conservation Programs Fiscal Year 1999

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    None, None

    2001-05-01

    This document provides information on energy consumption in Federal buildings, operations, and vehicles and equipment, and documents activities conducted by Federal agencies to meet the statutory requirements.

  2. 76 FR 66311 - Draft Documents To Support Submission of an Electronic Common Technical Document; Availability

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-10-26

    .../DevelopmentApprovalProcess/FormsSubmissionRequirements/ElectronicSubmissions/ucm253101.htm , http://www.fda.gov/BiologicsBloodVaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm , or http...

  3. A Compositional Relevance Model for Adaptive Information Retrieval

    NASA Technical Reports Server (NTRS)

    Mathe, Nathalie; Chen, James; Lu, Henry, Jr. (Technical Monitor)

    1994-01-01

    There is a growing need for rapid and effective access to information in large electronic documentation systems. Access can be facilitated if information relevant in the current problem solving context can be automatically supplied to the user. This includes information relevant to particular user profiles, tasks being performed, and problems being solved. However most of this knowledge on contextual relevance is not found within the contents of documents, and current hypermedia tools do not provide any easy mechanism to let users add this knowledge to their documents. We propose a compositional relevance network to automatically acquire the context in which previous information was found relevant. The model records information on the relevance of references based on user feedback for specific queries and contexts. It also generalizes such information to derive relevant references for similar queries and contexts. This model lets users filter information by context of relevance, build personalized views of documents over time, and share their views with other users. It also applies to any type of multimedia information. Compared to other approaches, it is less costly and doesn't require any a priori statistical computation, nor an extended training period. It is currently being implemented into the Computer Integrated Documentation system which enables integration of various technical documents in a hypertext framework.

  4. MODIS information, data and control system (MIDACS) level 2 functional requirements

    NASA Technical Reports Server (NTRS)

    Han, D.; Salomonson, V.; Ormsby, J.; Sharts, B.; Folta, D.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.

    1988-01-01

    The MODIS Information, Data and Control System (MIDACS) Level 2 Functional Requirements Document establishes the functional requirements for MIDACS and provides a basis for the mutual understanding between the users and the designers of the EosDIS, including the requirements, operating environment, external interfaces, and development plan. In defining the requirements and scope of the system, this document describes how MIDACS will operate as an element of the EOS within the EosDIS environment. This version of the Level 2 Requirements Document follows an earlier release of a preliminary draft version. The sections on functional and performance requirements do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. Indeed, the team members have not yet been selected and the team has not yet been formed; however, it has been possible to identify many relevant requirements based on the present concept of EosDIS and through interviews and meetings with key members of the scientific community. These requirements have been grouped by functional component of the data system, and by function within each component. These requirements have been merged with the complete set of Level 1 and Level 2 context diagrams, data flow diagrams, and data dictionary.

  5. Failures in communication through documents and documentation across the perioperative pathway.

    PubMed

    Braaf, Sandra; Riley, Robin; Manias, Elizabeth

    2015-07-01

    To explore how communication failures occur in documents and documentations across the perioperative pathway in nurses' interactions with other nurses, surgeons and anaesthetists. Documents and documentation are used to communicate vital patient and procedural information among nurses, and in nurses' interactions with surgeons and anaesthetists, across the perioperative pathway. Previous research indicates that communication failure regularly occurs in the perioperative setting. A qualitative study was undertaken. The study was conducted over three hospitals in Melbourne, Australia. One hundred and twenty-five healthcare professionals from the disciplines of surgery, anaesthesia and nursing participated in the study. Data collection commenced in January 2010 and concluded in October 2010. Data were generated through 350 hours of observation, two focus groups and 20 semi-structured interviews. A detailed thematic analysis was undertaken. Communication failure occurred owing to a reliance on documents and documentation to transfer information at patient transition points, poor quality documents and documentation, and problematic access to information. Institutional ruling practices of professional practice, efficiency and productivity, and fiscal constraint dominated the coordination of nurses', surgeons' and anaesthetists' communication through documents and documentation. These governing practices configured communication to be incongruous with reliably meeting safety and quality objectives. Communication failure occurred because important information was sometimes buried in documents, insufficient, inaccurate, out-of-date or not verbally reinforced. Furthermore, busy nurses were not always able to access information they required in a timely manner. Patient safety was affected, which led to delays in treatment and at times inadequate care. Organisational support needs to be provided to nurses, surgeons and anaesthetists so they have sufficient time to complete, locate, and read documents and documentation. Infrastructure supporting communication technologies should be implemented to enable the rapid retrieval, entry, and dispersion of information. © 2015 John Wiley & Sons Ltd.

  6. Using resources for scientific-driven pharmacovigilance: from many product safety documents to one product safety master file.

    PubMed

    Furlan, Giovanni

    2012-08-01

    Current regulations require a description of the overall safety profile or the specific risks of a drug in multiple documents such as the Periodic and Development Safety Update Reports, Risk Management Plans (RMPs) and Signal Detection Reports. In a resource-constrained world, the need for preparing multiple documents reporting the same information results in shifting the focus from a thorough scientific and medical evaluation of the available data to maintaining compliance with regulatory timelines. Since the aim of drug safety is to understand and characterize product issues to take adequate risk minimization measures rather than to comply with bureaucratic requirements, there is the need to avoid redundancy. In order to identify core drug safety activities that need to be undertaken to protect patient safety and reduce the number of documents reporting the results of these activities, the author has reviewed the main topics included in the drug safety guidelines and templates. The topics and sources that need to be taken into account in the main regulatory documents have been found to greatly overlap and, in the future, as a result of the new Periodic Safety Update Report structure and requirements, in the author's opinion this overlap is likely to further increase. Many of the identified inter-document differences seemed to be substantially formal. The Development Safety Update Report, for example, requires separate presentation of the safety issues emerging from different sources followed by an overall evaluation of each safety issue. The RMP, instead, requires a detailed description of the safety issues without separate presentation of the evidence derived from each source. To some extent, however, the individual documents require an in-depth analysis of different aspects; the RMP, for example, requires an epidemiological description of the indication for which the drug is used and its risks. At the time of writing this article, this is not specifically required by other documents. The author has identified signal detection (intended not only as adverse event disproportionate reporting, but including non-clinical, laboratory, clinical analysis data and literature screening) and characterization as the basis for the preparation of all drug safety documents, which can be viewed as different ways of presenting the results of this activity. Therefore, the author proposes to merge all the aggregate reports required by current regulations into a single document - the Drug Safety Master File. This report should contain all the available information, from any source, regarding the potential and identified risks of a drug. It should be a living document updated and submitted to regulatory authorities on an ongoing basis.

  7. Technical requirements for bioassay support services

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Hickman, D.P.; Anderson, A.L.

    1991-05-01

    This document provides the technical basis for the Chem-Nuclear Geotech (Geotech) bioassay program. It includes information and details that can be used as a model in providing technical contents and requirements for bioassay laboratory support, either internally or in solicitations by Geotech to obtain subcontractor laboratory support. It provides a detailed summary and description of the types of bioassay samples to be expected in support of Geotech remedial projects for the US Department of Energy and the bioassay services and analytical requirements necessary to process such samples, including required limits of sensitivity. General responsibilities of the bioassay laboratory are alsomore » addressed, including quality assurance. Peripheral information of importance to the program is included in the appendices of this document. 7 tabs.« less

  8. Sample RFP for Architectural Services, 2000.

    ERIC Educational Resources Information Center

    Arizona State School Facilities Board, Phoenix.

    This document presents a sample request for proposal that Arizona school districts can use when requesting architectural services, from the general request requirements to response information and signature sheet. General proposal requirements cover such areas as information on special terms and conditions, the scope of architectural services…

  9. Modern Corneal Eye-Banking Using a Software-Based IT Management Solution.

    PubMed

    Kern, C; Kortuem, K; Wertheimer, C; Nilmayer, O; Dirisamer, M; Priglinger, S; Mayer, W J

    2018-01-01

    Increasing government legislation and regulations in manufacturing have led to additional documentation regarding the pharmaceutical product requirements of corneal grafts in the European Union. The aim of this project was to develop a software within a hospital information system (HIS) to support the documentation process, to improve the management of the patient waiting list and to increase informational flow between the clinic and eye bank. After an analysis of the current documentation process, a new workflow and software were implemented in our electronic health record (EHR) system. The software takes over most of the documentation and reduces the time required for record keeping. It guarantees real-time tracing of all steps during human corneal tissue processing from the start of production until allocation during surgery and includes follow-up within the HIS. Moreover, listing of the patient for surgery as well as waiting list management takes place in the same system. The new software for corneal eye banking supports the whole process chain by taking over both most of the required documentation and the management of the transplant waiting list. It may provide a standardized IT-based solution for German eye banks working within the same HIS.

  10. Toxicology profiles of chemical and radiological contaminants at Hanford

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Harper, B.L.; Strenge, D.L.; Stenner, R.D.

    1995-07-01

    This document summarizes toxicology information required under Section 3.3 (Toxicity Assessment) of HSRAM, and can also be used to develop the short toxicology profiles required in site assessments (described in HSRAM, Section 3.3.5). Toxicology information is used in the dose-response step of the risk assessment process. The dose-response assessment describes the quantitative relationship between the amount of exposure to a substance and the extent of toxic injury or disease. Data are derived from animal studies or, less frequently, from studies in exposed human populations. The risks of a substance cannot be ascertained with any degree of confidence unless dose-response relationsmore » are quantified. This document summarizes dose-response information available from the US Environmental Protection Agency (EPA). The contaminants selected for inclusion in this document represent most of the contaminants found at Hanford (both radiological and chemical), based on sampling and analysis performed during site investigations, and historical information on waste disposal practices at the Hanford Site.« less

  11. Gender Differences in Reading Performance on Documents across Countries.

    ERIC Educational Resources Information Center

    Rosen, Monica

    2001-01-01

    Notes how females are known to excel over males in most reading tasks, but not consistently so in tasks that require processing information from maps, tables, charts and diagrams, so called "Documents." Describes and analyzes gender differences on Document tasks, and investigates if and how the pattern of differences varies over countries. (SG)

  12. A WET TALE: TOXICITY OF COMPLEX EFFLUENTS

    EPA Science Inventory

    This course covers standards, regulations, policy, guidance and technical aspects of implementing the whole effluent toxicity program. The curriculum incorporates rationale and information on WET test requirements from USEPA documents, such as the Technical Support Document for W...

  13. 78 FR 51729 - Emergency Clearance: Public Information Collection Requirements Submitted to the Office of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-21

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Medicare and Medicaid Services [Document Identifier: CMS-10496 Emergency Clearance: Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB) AGENCY: Center for Medicare and Medicaid Services. In compliance with the requirement of section 3506(c)(2)(A) of...

  14. The California Central Coast Research Partnership: Building Relationships, Partnerships, and Paradigms for University-Industry Research Collaboration

    DTIC Science & Technology

    2011-03-28

    particular topic of interest. Paper -based documents require the availability of a physical instance of a document, involving the transport of documents...repository of documents via the World Wide Web and search engines offer support in locating documents that are likely to contain relevant information. The... Web , with news agencies, newspapers, various organizations, and individuals as sources. Clearly the analysis, interpretation, and integration of

  15. WIDA Assessment and Accommodations for English Language Learners with Disabilities. 2014-2015 Test Administration

    ERIC Educational Resources Information Center

    Indiana Department of Education, 2015

    2015-01-01

    On a case-by-case basis where appropriate documentation exists, students with disabilities may require accommodations in order to access the W-APT and/or ACCESS for English Language Learners (ELLs). The information in this document replaces accommodations information in the appendices of the W-APT and ACCESS for ELLs test administration manuals…

  16. 42 CFR 68a.13 - Under what circumstances can the service or payment obligation be canceled, waived, or suspended?

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... be canceled upon the death of the participant. (b) The Secretary may waive or suspend any service or... considered impossible if the Secretary determines, on the basis of such information and documentation as may... good conscience, the Secretary, on the basis of such information and documentation as may be required...

  17. Data Quality Objectives for Regulatory Requirements for Dangerous Waste Sampling and Analysis

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    MULKEY, C.H.

    1999-07-02

    This document describes sampling and analytical requirements needed to meet state and federal regulations for dangerous waste (DW). The River Protection Project (RPP) is assigned to the task of storage and interim treatment of hazardous waste. Any final treatment or disposal operations, as well as requirements under the land disposal restrictions (LDRs), fall in the jurisdiction of another Hanford organization and are not part of this scope. The requirements for this Data Quality Objective (DQO) Process were developed using the RPP Data Quality Objective Procedure (Banning 1996), which is based on the U.S. Environmental Protection Agency's (EPA) Guidance for themore » Data Quality Objectives Process (EPA 1994). Hereafter, this document is referred to as the DW DQO. Federal and state laws and regulations pertaining to waste contain requirements that are dependent upon the composition of the waste stream. These regulatory drivers require that pertinent information be obtained. For many requirements, documented process knowledge of a waste composition can be used instead of analytical data to characterize or designate a waste. When process knowledge alone is used to characterize a waste, it is a best management practice to validate the information with analytical measurements.« less

  18. Joint Refugee Information Clearing Office (JRICO)

    DTIC Science & Technology

    1976-03-02

    A. JRICO Documentation 42 B. DA Documentation 62 C. DOD Documentation 75 D. IATF Documentation 83 E. Operating Procedures 103 F. Data...Indochina ( IATF ) and maintain access to the IATF computer data files on refugees, as well as coordinating with OSD, refugee resettlement centers...providing facilities and administrative support as requir- ed and negotiating with IATF for on-line computer access to the refugee records in the

  19. Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study. Volume 3: Interface control documents. Part 2: AMPS payload to spacelab ICD

    NASA Technical Reports Server (NTRS)

    1976-01-01

    The AMPS to Spacelab Interface Control Document which is to be used as a guide for format and information content in generating specific AMPS Mission ICDs is presented. This document is meant to supplement the Spacelab Payload Accommodations Handbook in that it only defines interfaces which are not discussed in the handbook to the level required for design purposes. The AMPS Top Level Requirements Tree, illustrates this ICD by a shaded area and its relationship to the other AMPS technical documents. Other interface documents shown are the Level II, AMPS to Space Shuttle Vehicle ICD and the Level III, AMPS to Instruments ICD.

  20. Ethics in the publication of studies on human visceral leishmaniasis in Brazilian periodicals.

    PubMed

    Malafaia, Guilherme; Rodrigues, Aline Sueli de Lima; Talvani, André

    2011-02-01

    To analyze ethical aspects of Brazilian articles on human visceral leishmaniasis, published after Resolution CNS 196/1996, and to analyze the policy on Brazilian periodicals on research ethics. An explanatory study with a bibliographical and documental nature was conducted. Selection of publications on research involving human beings since 1996 was performed in the SciELO Brazil database. Gaps associated with editorial policies on medical periodicals, based on information obtained from the "Instructions to authors" section of each periodical, were analyzed. While there were no articles on the compliance with ethical aspects in the first four-year period (from 1997 to 2000), 75% fulfilled at least one of the ethical requirements evaluated in the first year (2009) of a subsequent four-year period (from 2009 to 2012). A total of six out of 11 periodicals indicated that the information about ethical aspects should be mentioned in the body of the article. There were three periodicals that required a letter or document, informing about compliance with these aspects and signed by the author(s), to be sent; two that requested a copy of the document used to obtain the free and informed consent; one that clarified the need of a copy to authorize the approval by the Committee on Ethics in Research; and four in which no requirements of ethical aspects were found. There was an improvement in the description of compliance with ethical aspects found in articles. Standardization of ethical requirements for human research in Brazilian periodicals is suggested. This could promote compliance with the presuppositions of documents regulating human research.

  1. 32 CFR 235.7 - Information requirements.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... 32 National Defense 2 2014-07-01 2014-07-01 false Information requirements. 235.7 Section 235.7 National Defense Department of Defense (Continued) OFFICE OF THE SECRETARY OF DEFENSE (CONTINUED... Chair of the Board shall submit to the PDUSD(P&R) an annual report documenting the activities, decisions...

  2. 78 FR 78970 - Emergency Clearance: Public Information Collection Requirements Submitted to the Office of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-27

    ... Identifier: CMS-10510] Emergency Clearance: Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB); Correction AGENCY: Centers for Medicare & Medicaid Services (CMS..., Federal Register notice (document identifier: CMS-10510) entitled ``Basic Health Program Report for Health...

  3. 78 FR 47335 - 60-Day Notice of Proposed Information Collection: Public Housing Contracting With Resident-Owned...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-05

    ... with State law; Certification that shows the business is owned by residents, disclosure documents that... Information Collection: Public Housing Contracting With Resident-Owned Business--Application Requirements... Contracting with Resident- Owned Businesses/Application Requirements. OMB Approval Number: 2577-0161...

  4. 78 FR 65697 - 30-Day Notice of Proposed Information Collection: Public Housing, Contracting With Resident-Owned...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-11-01

    ... State law; Certification that shows the business is owned by residents, disclosure documents that... Information Collection: Public Housing, Contracting With Resident-Owned Businesses--Application Requirements..., Contracting with Resident-Owned Businesses-Application Requirements. OMB Approval Number: 2577-0161. Type of...

  5. 19 CFR 141.61 - Completion of entry and entry summary documentation.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... on CBP Form 7501. (e) Statistical information—(1) Information required on entry summary or withdrawal... a separate statistical reporting number, the applicable information required by the General Statistical Notes, Harmonized Tariff Schedule of the United States (HTSUS), must be shown on the entry summary...

  6. Oak Ridge Environmental Information System (OREIS) functional system design document

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Birchfield, T.E.; Brown, M.O.; Coleman, P.R.

    1994-03-01

    The OREIS Functional System Design document provides a detailed functional description of the Oak Ridge Environmental Information System (OREIS). It expands the system requirements defined in the OREIS Phase 1-System Definition Document (ES/ER/TM-34). Documentation of OREIS development is based on the Automated Data Processing System Development Methodology, a Martin Marietta Energy Systems, Inc., procedure written to assist in developing scientific and technical computer systems. This document focuses on the development of the functional design of the user interface, which includes the integration of commercial applications software. The data model and data dictionary are summarized briefly; however, the Data Management Planmore » for OREIS (ES/ER/TM-39), a companion document to the Functional System Design document, provides the complete data dictionary and detailed descriptions of the requirements for the data base structure. The OREIS system will provide the following functions, which are executed from a Menu Manager: (1) preferences, (2) view manager, (3) macro manager, (4) data analysis (assisted analysis and unassisted analysis), and (5) spatial analysis/map generation (assisted ARC/INFO and unassisted ARC/INFO). Additional functionality includes interprocess communications, which handle background operations of OREIS.« less

  7. 78 FR 77484 - Agency Information Collection Activities: Documents Required Aboard Private Aircraft

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-23

    ... of information (a total capital/startup costs and operations and maintenance costs). The comments... to extend the expiration date of this information collection with no change to the burden hours. Type...

  8. Validating Competence: A New Credential for Clinical Documentation Improvement Practitioners

    PubMed Central

    Ryan, Jessica; Patena, Karen; Judd, Wallace; Niederpruem, Mike

    2013-01-01

    As the health information management (HIM) profession continues to expand and become more specialized, there is an ever-increasing need to identify emerging HIM workforce roles that require a codified level of proficiency and professional standards. The Commission on Certification for Health Informatics and Information Management (CCHIIM) explored one such role—clinical documentation improvement (CDI) practitioner—to define the tasks and responsibilities of the job as well as the knowledge required to perform them effectively. Subject-matter experts (SMEs) defined the CDI specialty by following best practices for job analysis methodology. A random sample of 4,923 CDI-related professionals was surveyed regarding the tasks and knowledge required for the job. The survey data were used to create a weighted blueprint of the six major domains that make up the CDI practitioner role, which later formed the foundation for the clinical documentation improvement practitioner (CDIP) credential. As a result, healthcare organizations can be assured that their certified documentation improvement practitioners have demonstrated excellence in clinical care, treatment, coding guidelines, and reimbursement methodologies. PMID:23843769

  9. 7 CFR 3022.9 - Documents required.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... AGRICULTURE RESEARCH INSTITUTIONS CONDUCTING USDA-FUNDED EXTRAMURAL RESEARCH; RESEARCH MISCONDUCT § 3022.9... the following documents related to an allegation of research misconduct at the research institution... used to gather and evaluate information pertinent to the alleged misconduct during inquiry and...

  10. Association of Medical Directors of Information Systems consensus on inpatient electronic health record documentation.

    PubMed

    Shoolin, J; Ozeran, L; Hamann, C; Bria, W

    2013-01-01

    In 2013, electronic documentation of clinical care stands at a crossroads. The benefits of creating digital notes are at risk of being overwhelmed by the inclusion of easily importable detail. Providers are the primary authors of encounters with patients. We must document clearly our understanding of patients and our communication with them and our colleagues. We want to document efficiently to meet without exceeding documentation guidelines. We copy and paste documentation, because it not only simplifies the documentation process generally, but also supports meeting coding and regulatory requirements specifically. Since the primary goal of our profession is to spend as much time as possible listening to, understanding and helping patients, clinicians need information technology to make electronic documentation easier, not harder. At the same time, there should be reasonable restrictions on the use of copy and paste to limit the growing challenge of 'note bloat'. We must find the right balance between ease of use and thoughtless documentation. The guiding principles in this document may be used to launch an interdisciplinary dialogue that promotes useful and necessary documentation that best facilitates efficient information capture and effective display.

  11. 78 FR 23545 - Proposed Extension of Approval of Information Collection; Comment Request: Third Party Conformity...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-19

    ... evaluate whether third party conformity assessment bodies meet the requirements to test for compliance to... background documents or comments received, go to http://www.regulations.gov . FOR FURTHER INFORMATION CONTACT...: A. Background The Consumer Product Safety Improvement Act of 2008 (CPSIA) requires third party...

  12. Experiment Document for 01-E077 Microgravity Investigation of Crew Reactions in 0-G (MICRO-G)

    NASA Technical Reports Server (NTRS)

    Newman, Dava J.

    2003-01-01

    The Experiment Document (ED) serves the following purposes: a) It provides a vehicle for Principal Investigators (PIS) to formally specify the requirements for performing their experiments. b) It provides a technical Statement of Work (SOW). c) It provides experiment investigators and hardware developers with a convenient source of information about Human Life Sciences (HLS) requirements for the development and/or integration of flight experiment projects. d) It is the primary source of experiment specifications for the HLS Research Program Office (RPO). Inputs from this document will be placed into a controlled database that will be used to generate other documents.

  13. Aerial Refueling Clearance Initiation Request

    DTIC Science & Technology

    2016-07-14

    and receiver agencies. The AR Clearance Initiation Request document recognizes the requirement for definitive aerial refueling agreements between...and contractual tanker support requests from one organization or nation to another. The AR Clearance Initiation Request document is not intended to...proprietary, sensitive, classified or otherwise restricted information. ARSAG documents, as prepared, are not DOD, MOD or NATO standards, but provide

  14. 8 CFR 264.1 - Registration and fingerprinting.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... Security, providing fingerprints, photographs, or submitting supplemental information or documentation. (ii... may be required and each change of material fact is a registration that is required under sections 262...

  15. 8 CFR 264.1 - Registration and fingerprinting.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... Security, providing fingerprints, photographs, or submitting supplemental information or documentation. (ii... may be required and each change of material fact is a registration that is required under sections 262...

  16. 29 CFR 2200.200 - Purpose.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... answers are not required. (2) Pleadings generally are not required. Early discussions among the parties and the Administrative Law Judge are required to narrow and define the disputes between the parties. (3) The Secretary is required to provide the employer with certain informational documents early in...

  17. 29 CFR 2200.200 - Purpose.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... answers are not required. (2) Pleadings generally are not required. Early discussions among the parties and the Administrative Law Judge are required to narrow and define the disputes between the parties. (3) The Secretary is required to provide the employer with certain informational documents early in...

  18. 29 CFR 2200.200 - Purpose.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... answers are not required. (2) Pleadings generally are not required. Early discussions among the parties and the Administrative Law Judge are required to narrow and define the disputes between the parties. (3) The Secretary is required to provide the employer with certain informational documents early in...

  19. 29 CFR 2200.200 - Purpose.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... answers are not required. (2) Pleadings generally are not required. Early discussions among the parties and the Administrative Law Judge are required to narrow and define the disputes between the parties. (3) The Secretary is required to provide the employer with certain informational documents early in...

  20. 29 CFR 2200.200 - Purpose.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... answers are not required. (2) Pleadings generally are not required. Early discussions among the parties and the Administrative Law Judge are required to narrow and define the disputes between the parties. (3) The Secretary is required to provide the employer with certain informational documents early in...

  1. San Francisco urban partnership agreement, national evaluation : telecommuting/TDM data test plan.

    DOT National Transportation Integrated Search

    2002-04-01

    The Standards Requirements Document (SRD) collects information from the other National ITS Architecture program documents and reorganizes it in a manner intended to support the development of critical ITS standards. The key results in the SRD a...

  2. Robust Requirements Tracing via Internet Search Technology: Improving an IV and V Technique. Phase 2

    NASA Technical Reports Server (NTRS)

    Hayes, Jane; Dekhtyar, Alex

    2004-01-01

    There are three major objectives to this phase of the work. (1) Improvement of Information Retrieval (IR) methods for Independent Verification and Validation (IV&V) requirements tracing. Information Retrieval methods are typically developed for very large (order of millions - tens of millions and more documents) document collections and therefore, most successfully used methods somewhat sacrifice precision and recall in order to achieve efficiency. At the same time typical IR systems treat all user queries as independent of each other and assume that relevance of documents to queries is subjective for each user. The IV&V requirements tracing problem has a much smaller data set to operate on, even for large software development projects; the set of queries is predetermined by the high-level specification document and individual requirements considered as query input to IR methods are not necessarily independent from each other. Namely, knowledge about the links for one requirement may be helpful in determining the links of another requirement. Finally, while the final decision on the exact form of the traceability matrix still belongs to the IV&V analyst, his/her decisions are much less arbitrary than those of an Internet search engine user. All this suggests that the information available to us in the framework of the IV&V tracing problem can be successfully leveraged to enhance standard IR techniques, which in turn would lead to increased recall and precision. We developed several new methods during Phase II; (2) IV&V requirements tracing IR toolkit. Based on the methods developed in Phase I and their improvements developed in Phase II, we built a toolkit of IR methods for IV&V requirements tracing. The toolkit has been integrated, at the data level, with SAIC's SuperTracePlus (STP) tool; (3) Toolkit testing. We tested the methods included in the IV&V requirements tracing IR toolkit on a number of projects.

  3. Step 1:Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Collision Avoidance

    NASA Technical Reports Server (NTRS)

    2007-01-01

    This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

  4. Emergency Response Capability Baseline Needs Assessment - Compliance Assessment

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Sharry, John A.

    This document was prepared by John A. Sharry, LLNL Fire Marshal and Division Leader for Fire Protection and was reviewed by LLNL Emergency Management Department Head, James Colson. This document is the second of a two-part analysis on Emergency Response Capabilities of Lawrence Livermore National Laboratory. The first part, 2016 Baseline Needs Assessment Requirements Document established the minimum performance criteria necessary to meet mandatory requirements. This second part analyses the performance of Lawrence Livermore Laboratory Emergency Management Department to the contents of the Requirements Document. The document was prepared based on an extensive review of information contained in the 2016more » BNA, a review of Emergency Planning Hazards Assessments, a review of building construction, occupancy, fire protection features, dispatch records, LLNL alarm system records, fire department training records, and fire department policies and procedures. The 2013 BNA was approved by NNSA’s Livermore Field Office on January 22, 2014.« less

  5. How Analysts Cognitively “Connect the Dots”

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bradel, Lauren; Self, Jessica S.; Endert, Alexander

    2013-06-04

    As analysts attempt to make sense of a collection of documents, such as intelligence analysis reports, they may wish to “connect the dots” between pieces of information that may initially seem unrelated. This process of synthesizing information between information requires users to make connections between pairs of documents, creating a conceptual story. We conducted a user study to analyze the process by which users connect pairs of documents and how they spatially arrange information. Users created conceptual stories that connected the dots using organizational strategies that ranged in complexity. We propose taxonomies for cognitive connections and physical structures used whenmore » trying to “connect the dots” between two documents. We compared the user-created stories with a data-mining algorithm that constructs chains of documents using co-occurrence metrics. Using the insight gained into the storytelling process, we offer design considerations for the existing data mining algorithm and corresponding tools to combine the power of data mining and the complex cognitive processing of analysts.« less

  6. ICAM (Conceptual Design for Computer-Integrated Manufacturing. Volume 2. Part 6. Task B - Establishment of the Factory of the Future Conceptual Framework Conceptual Framework Document, (MMR)

    DTIC Science & Technology

    1984-06-29

    effort that requires hard copy documentation. As a result, there are generally numerous delays in providing current quality information. In the FoF...process have had fixed controls or were based on " hard -coded" information. A template, for example, is hard -coded information defining the shape of a...represents soft-coded control information. (Although manual handling of punch tapes still possess some of the limitations of " hard -coded" controls

  7. 8 CFR 264.1 - Registration and finger-printing.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... Security, providing fingerprints, photographs, or submitting supplemental information or documentation. (ii... may be required and each change of material fact is a registration that is required under sections 262...

  8. Imaged document information location and extraction using an optical correlator

    NASA Astrophysics Data System (ADS)

    Stalcup, Bruce W.; Dennis, Phillip W.; Dydyk, Robert B.

    1999-12-01

    Today, the paper document is fast becoming a thing of the past. With the rapid development of fast, inexpensive computing and storage devices, many government and private organizations are archiving their documents in electronic form (e.g., personnel records, medical records, patents, etc.). Many of these organizations are converting their paper archives to electronic images, which are then stored in a computer database. Because of this, there is a need to efficiently organize this data into comprehensive and accessible information resources and provide for rapid access to the information contained within these imaged documents. To meet this need, Litton PRC and Litton Data Systems Division are developing a system, the Imaged Document Optical Correlation and Conversion System (IDOCCS), to provide a total solution to the problem of managing and retrieving textual and graphic information from imaged document archives. At the heart of IDOCCS, optical correlation technology provide a means for the search and retrieval of information from imaged documents. IDOCCS can be used to rapidly search for key words or phrases within the imaged document archives and has the potential to determine the types of languages contained within a document. In addition, IDOCCS can automatically compare an input document with the archived database to determine if it is a duplicate, thereby reducing the overall resources required to maintain and access the document database. Embedded graphics on imaged pages can also be exploited, e.g., imaged documents containing an agency's seal or logo can be singled out. In this paper, we present a description of IDOCCS as well as preliminary performance results and theoretical projections.

  9. A nursing-specific model of EPR documentation: organizational and professional requirements.

    PubMed

    von Krogh, Gunn; Nåden, Dagfinn

    2008-01-01

    To present the Norwegian documentation KPO model (quality assurance, problem solving, and caring). To present the requirements and multiple electronic patient record (EPR) functions the model is designed to address. The model's professional substance, a conceptual framework for nursing practice is developed by examining, reorganizing, and completing existing frameworks. The model's methodology, an information management system, is developed using an expert group. Both model elements were clinically tested over a period of 1 year. The model is designed for nursing documentation in step with statutory, organizational, and professional requirements. Complete documentation is arranged for by incorporating the Nursing Minimum Data Set. A systematic and comprehensive documentation is arranged for by establishing categories as provided in the model's framework domains. Consistent documentation is arranged for by incorporating NANDA-I Nursing Diagnoses, Nursing Intervention Classification, and Nursing Outcome Classification. The model can be used as a tool in cooperation with vendors to ensure the interests of the nursing profession is met when developing EPR solutions in healthcare. The model can provide clinicians with a framework for documentation in step with legal and organizational requirements and at the same time retain the ability to record all aspects of clinical nursing.

  10. A need to simplify informed consent documents in cancer clinical trials. A position paper of the ARCAD Group

    PubMed Central

    Bleiberg, H.; Decoster, G.; de Gramont, A.; Rougier, P.; Sobrero, A.; Benson, A.; Chibaudel, B.; Douillard, J. Y.; Eng, C.; Fuchs, C.; Fujii, M.; Labianca, R.; Larsen, A. K.; Mitchell, E.; Schmoll, H. J.; Sprumont, D.; Zalcberg, J.

    2017-01-01

    Background In respect of the principle of autonomy and the right of self-determination, obtaining an informed consent of potential participants before their inclusion in a study is a fundamental ethical obligation. The variations in national laws, regulations, and cultures contribute to complex informed consent documents for patients participating in clinical trials. Currently, only few ethics committees seem willing to address the complexity and the length of these documents and to request investigators and sponsors to revise them in a way to make them understandable for potential participants. The purpose of this work is to focus on the written information in the informed consent documentation for drug development clinical trials and suggests (i) to distinguish between necessary and not essential information, (ii) to define the optimal format allowing the best legibility of those documents. Methods The Aide et Recherche en Cancérologie Digestive (ARCAD) Group, an international scientific committee involving oncologists from all over the world, addressed these issues and developed and uniformly accepted a simplified informed consent documentation for future clinical research. Results A simplified form of informed consent with the leading part of 1200–1800 words containing all of the key information necessary to meet ethical and regulatory requirements and ‘relevant supportive information appendix’ of 2000–3000 words is provided. Conclusions This position paper, on the basis of the ARCAD Group experts discussions, proposes our informed consent model and the rationale for its content. PMID:28453700

  11. ASTP experiment support data processing

    NASA Technical Reports Server (NTRS)

    Osburn, R. K.; Barnett, E. L.; Moore, H. L.; Moore, J. B.; Ball, J. R.

    1975-01-01

    Activities associated with the generation of ASTP experiment support data in the areas of spacecraft ephemeris and orientation and instrument pointing and field-of-view are documented. It is intended that this document represent a cradle-to-grave chronicle of these activities. To satisfy this intent while facilitating the ready dissemination of information, the document is being published twice. The first publication, scheduled for release prior to ASTP liftoff, includes all preflight phases of the experiment support activity in addition to those appendixes that do not pertain to any mission-specific data. The second publication will provide any required updates to the original documentation and will add all mission-specific data, including documentation of all postflight data processing activities and data archiving information.

  12. Long-term pavement performance compliance with Department of Transportation information dissemination quality guidelines

    DOT National Transportation Integrated Search

    2008-11-01

    This document provides information on the compliance of the LTPP program with the guidelines the Department of Transportation (DOT) issued Information Dissemination Quality Guidelines (IDQG). These guidelines were developed in response to requirement...

  13. Forest Products Industry Permitting Information

    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.

  14. BACT Information for Coal-Fired Power Plants

    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.

  15. 10 CFR 1045.40 - Marking requirements.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... DEPARTMENT OF ENERGY (GENERAL PROVISIONS) NUCLEAR CLASSIFICATION AND DECLASSIFICATION Generation and Review... holder that it contains RD or FRD information, the level of classification assigned, and the additional... classification level of the document, the following notices shall appear on the front of the document, as...

  16. 10 CFR 1045.40 - Marking requirements.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... DEPARTMENT OF ENERGY (GENERAL PROVISIONS) NUCLEAR CLASSIFICATION AND DECLASSIFICATION Generation and Review... holder that it contains RD or FRD information, the level of classification assigned, and the additional... classification level of the document, the following notices shall appear on the front of the document, as...

  17. 77 FR 76435 - Connect America Fund

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-12-28

    ... excluding Phase I fiber from Phase II support is that the Bureau would not likely receive information... carriers should be restricted in building fiber, what information carriers should be required to provide... additional information on the rulemaking process, see the SUPPLEMENTARY INFORMATION section of this document...

  18. The valuation of nursing begins with identifying value drivers.

    PubMed

    Rutherford, Marcella M

    2010-03-01

    Adequate investment in a profession links to its ability to define and document its value. This requires identifying those elements or value drivers that demonstrate its worth. To completely identify nursing's value drivers requires meshing the economic, technical, and caring aspects of its profession. Nursing's valuation includes assessing nursing's tangible and intangible assets and documenting these assets. This information communicates nursing's worth and ensures adequate economic investment in its services.

  19. 76 FR 7145 - Notice of Public Information Collection Requirements Submitted to OMB for Review

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-02-09

    ... involved parties due to their familiarity with the certification process and salary costs and benefits... documents other than rules #0;or proposed rules that are applicable to the public. Notices of hearings #0... Public Information Collection Requirements Submitted to OMB for Review SUMMARY: This Federal Register...

  20. 48 CFR 752.7005 - Submission requirements for development experience documents.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ..., technologies, management, research, results and experience as outlined in the Agency's ADS Chapter 540, section... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor... descriptive information: (A) Name and version of the application software used to create the file, e.g., Word...

  1. 48 CFR 752.7005 - Submission requirements for development experience documents.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ..., technologies, management, research, results and experience as outlined in the Agency's ADS Chapter 540, section... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor... descriptive information: (A) Name and version of the application software used to create the file, e.g., Word...

  2. 48 CFR 752.7005 - Submission requirements for development experience documents.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ..., technologies, management, research, results and experience as outlined in the Agency's ADS Chapter 540, section... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor... descriptive information: (A) Name and version of the application software used to create the file, e.g., Word...

  3. 48 CFR 752.7005 - Submission requirements for development experience documents.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ..., technologies, management, research, results and experience as outlined in the Agency's ADS Chapter 540, section... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor... descriptive information: (A) Name and version of the application software used to create the file, e.g., Word...

  4. 48 CFR 752.7005 - Submission requirements for development experience documents.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ..., technologies, management, research, results and experience as outlined in the Agency's ADS Chapter 540, section... paragraph (b)(1)(i) of this clause. (2) Format. (i) Descriptive information is required for all Contractor... descriptive information: (A) Name and version of the application software used to create the file, e.g., Word...

  5. 76 FR 51123 - Agency Information Collection Activities; Submission for OMB Review and Approval; Joint Comment...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-08-17

    ... clearly the definition of capital used in any aspect of its internal capital adequacy assessment process (ICAAP) and document any changes in the internal definition of capital. Section 41 requires banks to... regulatory or accounting). The agencies' burden estimates for these information collection requirements are...

  6. 78 FR 77469 - Emergency Clearance: Public Information Collection Requirements Submitted to the Office of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-23

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Medicare & Medicaid Services [Document Identifier: CMS-10510] Emergency Clearance: Public Information Collection Requirements Submitted to the Office of Management and Budget (OMB) AGENCY: Centers for Medicare & Medicaid Services, HHS. In compliance with section 3506(c)(2)(A) of the Paperwork...

  7. 26 CFR 1.6050W-2 - Electronic furnishing of information statements for payments made in settlement of payment card...

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ... statements required by section 6050W(f) electronically on a website instead of in a paper format. The letter... website, downloading the consent document, completing the consent document, and e-mailing the completed consent back to F. The consent document posted on the website uses the same electronic format that F uses...

  8. 26 CFR 1.6050W-2 - Electronic furnishing of information statements for payments made in settlement of payment card...

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ... statements required by section 6050W(f) electronically on a website instead of in a paper format. The letter... website, downloading the consent document, completing the consent document, and e-mailing the completed consent back to F. The consent document posted on the website uses the same electronic format that F uses...

  9. 26 CFR 1.6050W-2 - Electronic furnishing of information statements for payments made in settlement of payment card...

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... statements required by section 6050W(f) electronically on a website instead of in a paper format. The letter... website, downloading the consent document, completing the consent document, and e-mailing the completed consent back to F. The consent document posted on the website uses the same electronic format that F uses...

  10. 77 FR 63803 - Federal Acquisition Regulation; Information Collection; Pollution Prevention and Right-to-Know...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-10-17

    ...; Information Collection; Pollution Prevention and Right-to-Know Information (FAR 52.223-5) AGENCY: Department... previously approved information collection requirement concerning pollution prevention and right-to-know..., Pollution Prevention and Right-to-Know Information'' on your attached document. Fax: 202-501-4067. Mail...

  11. BRD usability requirements

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Deshpande, Alina

    2015-03-12

    This document describes the usability requirements for the Biosurveillance resource directory (BRD); that is, who will be using the tool and what tasks they will be using it for. It does not include information on technical implementation (e.g., whether specific information is contained in the database or pulled on demand from other sources). It also avoids specific design ideas (such as widget descriptions) unless they are necessary to illustrate a requirement.

  12. 75 FR 45147 - Notice of Submission of Proposed Information Collection to OMB Management Certifications and...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-08-02

    ...The proposed information collection requirement described below has been submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal. Owners of insured and assisted multifamily housing projects are required to submit documentation for HUD's review and approval of new management agents.

  13. An approach for software-driven and standard-based support of cross-enterprise tumor boards.

    PubMed

    Mangesius, Patrick; Fischer, Bernd; Schabetsberger, Thomas

    2015-01-01

    For tumor boards, the networking of different medical disciplines' expertise continues to gain importance. However, interdisciplinary tumor boards spread across several institutions are rarely supported by information technology tools today. The aim of this paper is to point out an approach for a tumor board management system prototype. For analyzing the requirements, an incremental process was used. The requirements were surveyed using Informal Conversational Interview and documented with Use Case Diagrams defined by the Unified Modeling Language (UML). Analyses of current EHR standards were conducted to evaluate technical requirements. Functional and technical requirements of clinical conference applications were evaluated and documented. In several steps, workflows were derived and application mockups were created. Although there is a vast amount of common understanding concerning how clinical conferences should be conducted and how their workflows should be structured, these are hardly standardized, neither on a functional nor on a technical level. This results in drawbacks for participants and patients. Using modern EHR technologies based on profiles such as IHE Cross Enterprise document sharing (XDS), these deficits could be overcome.

  14. Interim rules for amending ERISA disclosure requirements for group health plans; approval of information collection requirements--DoL. Interim rules; approval of information collection requirements.

    PubMed

    1997-07-07

    On April 8, 1997, the Department of Labor published interim final rules governing disclosure requirements for private sector group health plans (62 FR 16979). The rules implemented changes to made to certain provisions of the Employee Retirement Income Security Act of 1974 (ERISA), enacted as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and the Newborns' and Mothers' Health Protection Act of 1996 (NMHPA). In the April 8 publication, the Department submitted its revision of the currently approved collection regarding Summary Plan Description requirements under ERISA to the Office of Management and Budget (OMB) for emergency review under the Paperwork Reduction Act of 1965 (PRA 95). This document amends the April 8 Federal Register document to properly display the OMB control number, 1210-0039.

  15. Engineering Safety- and Security-Related Requirements for Software-Intensive Systems

    DTIC Science & Technology

    2010-04-27

    Requirements Negative (shall not) Requirements Hardware Requirements equ remen s System / Documentation Requirements eve oper Requirements Operational ...Validation Actual / Proposed Defensibility C li Operational Vulnerability Analysis VulnerabilityVulnerability Safety Vulnerability performs System ...including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson

  16. Re-evaluating ethical concerns in planned emergency research involving critically ill patients: an interpretation of the guidance document from the United States Food and Drug Administration.

    PubMed

    Smischney, Nathan J; Onigkeit, James A; Hinds, Richard F; Nicholson, Wayne T

    2015-01-01

    U.S. federal regulations require that certain ethical elements be followed to protect human research subjects. The location and clinical circumstances of a proposed research study can differ substantially and can have significant implications for these ethical considerations. Both the location and clinical circumstances are particularly relevant for research in intensive care units (ICUs), where patients are often unable to provide informed consent to participate in a proposed research intervention. Our goal is to elaborate on the updated 2013 U.S. Food and Drug Administration (FDA) guidance document regarding an exemption from the requirement of obtaining informed consent from patients or their surrogates and to address certain elements within that document, thereby assisting clinicians in developing a framework for emergency research in accordance with the regulatory bodies at their own institutions and in the United States. Review of the 2011 and updated FDA guidance document on exemption from informed consent. The current process of obtaining informed consent within ICUs needs to be revisited, especially for research in which timely informed consent is not likely. In particular, the process of obtaining informed consent may not be appropriate or even ethical for critically ill patients in extremis who require an intervention for which there is no current acceptable standard of care and clinical equipoise exists. We provide clinicians with a viewpoint that further elaborates on the FDA guidance document. The viewpoints provided herein are those of the authors and are therefore inherently limited by the personal views of a selected few. Other clinicians or researchers may not interpret the FDA guidelines in a similar manner. Moreover, the discussion of a guideline document is a limitation in and of itself. The guidelines set forth by the FDA are precisely that-guidelines. Therefore, they may not be followed as outlined in the guidance document within one's own institution. Our goal is that, by elaborating on the guidelines for planned research involving human subjects in the ICU, institutional regulatory bodies may gain a better understanding in drafting their own document when faced with a clinician or a researcher who wishes to conduct planned research in an ICU. We believe that the interpretations provided will allow clinicians to safely undertake planned research in ICUs without endangering the main tenets of ethical research involving human participants. This research is needed for the advancement of care in the critically ill. Copyright 2015 The Journal of Clinical Ethics. All rights reserved.

  17. 75 FR 51985 - Notice of Proposed Information Collection Requests

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-08-24

    ... collection requirements and provide the requested data in the desired format. The Director, Information..., Regulatory Information Management Services, Office of Management, publishes this notice containing proposed... Review: Revision. Title of Collection: Student Aid Internet Gateway (SAIG) Enrollment Documents. OMB...

  18. 5 CFR 2606.203 - Granting access.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... Access to Records and Accounting of Disclosures § 2606.203 Granting access. (a) The methods for allowing... documentation will be required for the disclosure to the data subject of information required to be made...

  19. Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 2: Concept document

    NASA Technical Reports Server (NTRS)

    1989-01-01

    The Simulation Computer System (SCS) concept document describes and establishes requirements for the functional performance of the SCS system, including interface, logistic, and qualification requirements. The SCS is the computational communications and display segment of the Marshall Space Flight Center (MSFC) Payload Training Complex (PTC). The PTC is the MSFC facility that will train onboard and ground operations personnel to operate the payloads and experiments on board the international Space Station Freedom. The requirements to be satisfied by the system implementation are identified here. The SCS concept document defines the requirements to be satisfied through the implementation of the system capability. The information provides the operational basis for defining the requirements to be allocated to the system components and enables the system organization to assess whether or not the completed system complies with the requirements of the system.

  20. Sustained Assessment Metadata as a Pathway to Trustworthiness of Climate Science Information

    NASA Astrophysics Data System (ADS)

    Champion, S. M.; Kunkel, K.

    2017-12-01

    The Sustained Assessment process has produced a suite of climate change reports: The Third National Climate Assessment (NCA3), Regional Surface Climate Conditions in CMIP3 and CMIP5 for the United States: Differences, Similarities, and Implications for the U.S. National Climate Assessment, Impacts of Climate Change on Human Health in the United States: A Scientific Assessment, The State Climate Summaries, as well as the anticipated Climate Science Special Report and Fourth National Climate Assessment. Not only are these groundbreaking reports of climate change science, they are also the first suite of climate science reports to provide access to complex metadata directly connected to the report figures and graphics products. While the basic metadata documentation requirement is federally mandated through a series of federal guidelines as a part of the Information Quality Act, Sustained Assessment products are also deemed Highly Influential Scientific Assessments, which further requires demonstration of the transparency and reproducibility of the content. To meet these requirements, the Technical Support Unit (TSU) for the Sustained Assessment embarked on building a system for not only collecting and documenting metadata to the required standards, but one that also provides consumers unprecedented access to the underlying data and methods. As our process and documentation have evolved, the value of both continue to grow in parallel with the consumer expectation of quality, accessible climate science information. This presentation will detail the how the TSU accomplishes the mandated requirements with their metadata collection and documentation process, as well as the technical solution designed to demonstrate compliance while also providing access to the content for the general public. We will also illustrate how our accessibility platforms guide consumers through the Assessment science at a level of transparency that builds trust and confidence in the report content.

  1. User documentation for the FHWA Carpool Matching Program (second edition)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    1975-01-01

    This document provides persons interested in computerized carpool/buspool matching programs a complete description of the user documentation for the FHWA Carpool Matching Program. The FHWA program is written in American National Standard COBOL and thus should be readily transferable to environments other than the IBM 360/65 (OS) under which it has been developed and tested. The program has a compiled time core requirement of 110K and a maximum execution time core requirement of 110K. While considerable effort has been made to test the program in several applications and to achieve accuracy and completeness in the program and supporting documentation, themore » FHWA cannot guarantee the proper operation of this program by any user nor can it assume liability for any damage, loss, or inconvenience resulting from the operation of this program or the results obtained thereby. This present version of the carpool matching program represents the latest version of the first generation of an ongoing multi-phase process of improvements and refinements. The ultimate goal is an effective carpool and transit information system that will produce individualized information covering not only carpooling opportunities, but also transit routing, scheduling, and other identifying information for the commuter. (MCW)« less

  2. Sandia National Laboratories/New Mexico Environmental Information Document - Volume 1

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    BAYLISS, LINDA S.; GUERRERO, JOSEPH V.; JOHNS, WILLIAM H.

    This Sandia National Laboratories/New Mexico Environmental Information Document (EID) compiles information on the existing environment, or environmental baseline, for SNUNM. Much of the information is drawn from existing reports and databases supplemented by new research and data. The SNL/NM EID, together with the Sandia National Laboratories/New Mexico Facilities and Safety Information Document, provide a basis for assessing the environment, safety, and health aspects of operating selected facilities at SNL/NM. The environmental baseline provides a record of the existing physical, biological, and socioeconomic environment at SNL/NLM prior to being altered (beneficially or adversely) by proposed programs or projects. More specifically, themore » EID provides information on the following topics: Geology; Land Use; Hydrology and Water Resources; Air Quality and Meteorology; Ecology; Noise and Vibration; Cultural Resources; Visual Resources; Socioeconomic and Community Services; Transportation; Material Management; Waste Management; and Regulatory Requirements.« less

  3. SP-100 Program: space reactor system and subsystem investigations

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Harty, R.B.

    1983-09-30

    For a space reactor power system, a comprehensive safety program will be required to assure that no undue risk is present. This report summarizes the nuclear safety review/approval process that will be required for a space reactor system. The documentation requirements are presented along with a summary of the required contents of key documents. Finally, the aerospace safety program conducted for the SNAP-10A reactor system is summarized. The results of this program are presented to show the type of program that can be expected and to provide information that could be usable in future programs.

  4. SP-100 program: Space reactor system and subsystem investigations

    NASA Astrophysics Data System (ADS)

    Harty, R. B.

    1983-09-01

    For a space reactor power system, a comprehensive safety program will be required to assure that no undue risk is present. The nuclear safety review/approval process that is required for a space reactor system is summarized. The documentation requirements are presented along with a summary of the required contents of key documents. Finally, the aerospace safety program conducted for the SNAP-10A reactor system is summarized. The results of this program are presented to show the type of program that is expected and to provide information that could be usable in future programs.

  5. 10 CFR 603.420 - Disclosure of information.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... types that are exempt: (i) Proposals, proposal abstracts, and supporting documents; and (ii) Business plans and technical information submitted on a confidential basis. (c) If proposers desire to protect business plans and technical information for five years from FOIA disclosure requirements, they must mark...

  6. 14 CFR 14.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... 14 Aeronautics and Space 1 2012-01-01 2012-01-01 false Documentation of fees and expenses. 14.12 Section 14.12 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PROCEDURAL RULES RULES IMPLEMENTING THE EQUAL ACCESS TO JUSTICE ACT OF 1980 Information Required From...

  7. 14 CFR 14.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... 14 Aeronautics and Space 1 2013-01-01 2013-01-01 false Documentation of fees and expenses. 14.12 Section 14.12 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PROCEDURAL RULES RULES IMPLEMENTING THE EQUAL ACCESS TO JUSTICE ACT OF 1980 Information Required From...

  8. 14 CFR 14.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... 14 Aeronautics and Space 1 2014-01-01 2014-01-01 false Documentation of fees and expenses. 14.12 Section 14.12 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PROCEDURAL RULES RULES IMPLEMENTING THE EQUAL ACCESS TO JUSTICE ACT OF 1980 Information Required From...

  9. 14 CFR 14.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... 14 Aeronautics and Space 1 2011-01-01 2011-01-01 false Documentation of fees and expenses. 14.12 Section 14.12 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PROCEDURAL RULES RULES IMPLEMENTING THE EQUAL ACCESS TO JUSTICE ACT OF 1980 Information Required From...

  10. 14 CFR 14.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 14 Aeronautics and Space 1 2010-01-01 2010-01-01 false Documentation of fees and expenses. 14.12 Section 14.12 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PROCEDURAL RULES RULES IMPLEMENTING THE EQUAL ACCESS TO JUSTICE ACT OF 1980 Information Required From...

  11. 19 CFR 212.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... 19 Customs Duties 3 2010-04-01 2010-04-01 false Documentation of fees and expenses. 212.12 Section 212.12 Customs Duties UNITED STATES INTERNATIONAL TRADE COMMISSION INVESTIGATIONS OF UNFAIR PRACTICES IN IMPORT TRADE IMPLEMENTATION OF THE EQUAL ACCESS TO JUSTICE ACT Information Required From...

  12. A need to simplify informed consent documents in cancer clinical trials. A position paper of the ARCAD Group.

    PubMed

    Bleiberg, H; Decoster, G; de Gramont, A; Rougier, P; Sobrero, A; Benson, A; Chibaudel, B; Douillard, J Y; Eng, C; Fuchs, C; Fujii, M; Labianca, R; Larsen, A K; Mitchell, E; Schmoll, H J; Sprumont, D; Zalcberg, J

    2017-05-01

    In respect of the principle of autonomy and the right of self-determination, obtaining an informed consent of potential participants before their inclusion in a study is a fundamental ethical obligation. The variations in national laws, regulations, and cultures contribute to complex informed consent documents for patients participating in clinical trials. Currently, only few ethics committees seem willing to address the complexity and the length of these documents and to request investigators and sponsors to revise them in a way to make them understandable for potential participants. The purpose of this work is to focus on the written information in the informed consent documentation for drug development clinical trials and suggests (i) to distinguish between necessary and not essential information, (ii) to define the optimal format allowing the best legibility of those documents. The Aide et Recherche en Cancérologie Digestive (ARCAD) Group, an international scientific committee involving oncologists from all over the world, addressed these issues and developed and uniformly accepted a simplified informed consent documentation for future clinical research. A simplified form of informed consent with the leading part of 1200-1800 words containing all of the key information necessary to meet ethical and regulatory requirements and 'relevant supportive information appendix' of 2000-3000 words is provided. This position paper, on the basis of the ARCAD Group experts discussions, proposes our informed consent model and the rationale for its content. © The Author 2017. Published by Oxford University Press on behalf of the European Society for Medical Oncology.

  13. Software Management Environment (SME) installation guide

    NASA Technical Reports Server (NTRS)

    Kistler, David; Jeletic, Kellyann

    1992-01-01

    This document contains installation information for the Software Management Environment (SME), developed for the Systems Development Branch (Code 552) of the Flight Dynamics Division of Goddard Space Flight Center (GSFC). The SME provides an integrated set of management tools that can be used by software development managers in their day-to-day management and planning activities. This document provides a list of hardware and software requirements as well as detailed installation instructions and trouble-shooting information.

  14. IMIS: Integrated Maintenance Information System. A maintenance information delivery concept

    NASA Technical Reports Server (NTRS)

    Vonholle, Joseph C.

    1987-01-01

    The Integrated Maintenance Information System (IMIS) will optimize the use of available manpower, enhance technical performance, improve training, and reduce the support equipment and documentation needed for deployment. It will serve as the technician's single, integrated source of all the technical information required to perform modern aircraft maintenance.

  15. Integration of clinical research documentation in electronic health records.

    PubMed

    Broach, Debra

    2015-04-01

    Clinical trials of investigational drugs and devices are often conducted within healthcare facilities concurrently with clinical care. With implementation of electronic health records, new communication methods are required to notify nonresearch clinicians of research participation. This article reviews clinical research source documentation, the electronic health record and the medical record, areas in which the research record and electronic health record overlap, and implications for the research nurse coordinator in documentation of the care of the patient/subject. Incorporation of clinical research documentation in the electronic health record will lead to a more complete patient/subject medical record in compliance with both research and medical records regulations. A literature search provided little information about the inclusion of clinical research documentation within the electronic health record. Although regulations and guidelines define both source documentation and the medical record, integration of research documentation in the electronic health record is not clearly defined. At minimum, the signed informed consent(s), investigational drug or device usage, and research team contact information should be documented within the electronic health record. Institutional policies should define a standardized process for this integration in the absence federal guidance. Nurses coordinating clinical trials are in an ideal position to define this integration.

  16. Towards fraud-proof ID documents using multiple data hiding technologies and biometrics

    NASA Astrophysics Data System (ADS)

    Picard, Justin; Vielhauer, Claus; Thorwirth, Niels

    2004-06-01

    Identity documents, such as ID cards, passports, and driver's licenses, contain textual information, a portrait of the legitimate holder, and eventually some other biometric characteristics such as a fingerprint or handwritten signature. As prices for digital imaging technologies fall, making them more widely available, we have seen an exponential increase in the ease and the number of counterfeiters that can effectively forge documents. Today, with only limited knowledge of technology and a small amount of money, a counterfeiter can effortlessly replace a photo or modify identity information on a legitimate document to the extent that it is very diffcult to differentiate from the original. This paper proposes a virtually fraud-proof ID document based on a combination of three different data hiding technologies: digital watermarking, 2-D bar codes, and Copy Detection Pattern, plus additional biometric protection. As will be shown, that combination of data hiding technologies protects the document against any forgery, in principle without any requirement for other security features. To prevent a genuine document to be used by an illegitimate user,biometric information is also covertly stored in the ID document, to be used for identification at the detector.

  17. Computer program documentation user information for the RSO-tape print program (RSOPRNT)

    NASA Technical Reports Server (NTRS)

    Gibbs, P. M. (Principal Investigator)

    1980-01-01

    A user's guide for the RSOPRNT, a TRASYS Master Restart Output Tape (RSO) reader is presented. Background information and sample runstreams, as well as, references, input requirements and options, are included.

  18. Procedure: Ensuring EPA Public Content in the EPA Web Environment

    EPA Pesticide Factsheets

    This document outlines the procedures for ensuring access to EPA information by hosting EPA data and information on the epa.gov server. Additionally, it provides the procedures for obtaining waivers of this requirement.

  19. 75 FR 38168 - Federal Motor Vehicle Theft Prevention Standard; Final Listing of 2011 Light Duty Truck Lines...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-07-01

    ...The National Highway Traffic Safety Administration (NHTSA) published a document in the Federal Register of June 21, 2010, announcing NHTSA's determination that there were no new model year (MY) 2011 light-duty truck lines subject to the requirements of the Federal motor vehicle theft prevention standard. The final rule also identified those vehicle lines that had been granted an exemption from the parts- marking requirements for the 2011 model year and those vehicle lines the agency removed because certain vehicle lines had been discontinued more than 5 years ago. This document corrects certain information published in the SUPPLEMENTARY INFORMATION section and Appendix A-I listing of the final rule. All previous information associated with the published notice remains the same.

  20. 77 FR 59455 - Internal Revenue Service

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-09-27

    ...-37 describes documentation and information a taxpayer that uses the fair market value method of... information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance... on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of...

  1. 10 CFR 1045.40 - Marking requirements.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    .... (a) RD classifiers shall ensure that each RD and FRD document is clearly marked to convey to the holder that it contains RD or FRD information, the level of classification assigned, and the additional... sanctions. (2) If the document contains FRD but does not contain RD: FORMERLY RESTRICTED DATA Unauthorized...

  2. 10 CFR 1045.40 - Marking requirements.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    .... (a) RD classifiers shall ensure that each RD and FRD document is clearly marked to convey to the holder that it contains RD or FRD information, the level of classification assigned, and the additional... sanctions. (2) If the document contains FRD but does not contain RD: FORMERLY RESTRICTED DATA Unauthorized...

  3. 10 CFR 1045.40 - Marking requirements.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    .... (a) RD classifiers shall ensure that each RD and FRD document is clearly marked to convey to the holder that it contains RD or FRD information, the level of classification assigned, and the additional... sanctions. (2) If the document contains FRD but does not contain RD: FORMERLY RESTRICTED DATA Unauthorized...

  4. Aerospace Technology Careers: The Opportunity To Soar. Information Summaries.

    ERIC Educational Resources Information Center

    National Aeronautics and Space Administration, Washington, DC.

    This document provides guidelines for the preparation of careers in aerospace, whether with the National Aeronautics and Space Administration (NASA) or private industry. The document discusses the following topics: (1) Preparing for an Aerospace Career; (2) Careers in Aerospace; (3) Employment Requirements; and (4) How To Apply. (ZWH)

  5. 41 CFR 102-118.565 - What documentation is required when filing an administrative claim?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 41 Public Contracts and Property Management 3 2010-07-01 2010-07-01 false What documentation is... Management Federal Property Management Regulations System (Continued) FEDERAL MANAGEMENT REGULATION..., reports and information available to GSA and/or to the agency involved and the written and documentary...

  6. 30 CFR 250.490 - Hydrogen sulfide.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... mitigate damage to property and the environment caused by H2S. You must follow the requirements of this... documentation do I need? For each individual working on the platform, either: (i) You must have documentation of... respirator; practice in donning and adjusting the assigned respirator; information on the safe briefing areas...

  7. 29 CFR 11.11 - Development of environmental analyses and documents.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... development indicates that preparation of an environmental impact statement will be required, the agency shall begin preparation of such a document by initiating the scoping process in accordance with 40 CFR 1501.7. However, if the information is not clearly indicative of the need for preparation of an environmental...

  8. Latent Dirichlet Allocation (LDA) Model and kNN Algorithm to Classify Research Project Selection

    NASA Astrophysics Data System (ADS)

    Safi’ie, M. A.; Utami, E.; Fatta, H. A.

    2018-03-01

    Universitas Sebelas Maret has a teaching staff more than 1500 people, and one of its tasks is to carry out research. In the other side, the funding support for research and service is limited, so there is need to be evaluated to determine the Research proposal submission and devotion on society (P2M). At the selection stage, research proposal documents are collected as unstructured data and the data stored is very large. To extract information contained in the documents therein required text mining technology. This technology applied to gain knowledge to the documents by automating the information extraction. In this articles we use Latent Dirichlet Allocation (LDA) to the documents as a model in feature extraction process, to get terms that represent its documents. Hereafter we use k-Nearest Neighbour (kNN) algorithm to classify the documents based on its terms.

  9. Word Spotting for Indic Documents to Facilitate Retrieval

    NASA Astrophysics Data System (ADS)

    Bhardwaj, Anurag; Setlur, Srirangaraj; Govindaraju, Venu

    With advances in the field of digitization of printed documents and several mass digitization projects underway, information retrieval and document search have emerged as key research areas. However, most of the current work in these areas is limited to English and a few oriental languages. The lack of efficient solutions for Indic scripts has hampered information extraction from a large body of documents of cultural and historical importance. This chapter presents two relevant topics in this area. First, we describe the use of a script-specific keyword spotting for Devanagari documents that makes use of domain knowledge of the script. Second, we address the needs of a digital library to provide access to a collection of documents from multiple scripts. This requires intelligent solutions which scale across different scripts. We present a script-independent keyword spotting approach for this purpose. Experimental results illustrate the efficacy of our methods.

  10. Integrated information systems for electronic chemotherapy medication administration.

    PubMed

    Levy, Mia A; Giuse, Dario A; Eck, Carol; Holder, Gwen; Lippard, Giles; Cartwright, Julia; Rudge, Nancy K

    2011-07-01

    Chemotherapy administration is a highly complex and distributed task in both the inpatient and outpatient infusion center settings. The American Society of Clinical Oncology and the Oncology Nursing Society (ASCO/ONS) have developed standards that specify procedures and documentation requirements for safe chemotherapy administration. Yet paper-based approaches to medication administration have several disadvantages and do not provide any decision support for patient safety checks. Electronic medication administration that includes bar coding technology may provide additional safety checks, enable consistent documentation structure, and have additional downstream benefits. We describe the specialized configuration of clinical informatics systems for electronic chemotherapy medication administration. The system integrates the patient registration system, the inpatient order entry system, the pharmacy information system, the nursing documentation system, and the electronic health record. We describe the process of deploying this infrastructure in the adult and pediatric inpatient oncology, hematology, and bone marrow transplant wards at Vanderbilt University Medical Center. We have successfully adapted the system for the oncology-specific documentation requirements detailed in the ASCO/ONS guidelines for chemotherapy administration. However, several limitations remain with regard to recording the day of treatment and dose number. Overall, the configured systems facilitate compliance with the ASCO/ONS guidelines and improve the consistency of documentation and multidisciplinary team communication. Our success has prompted us to deploy this infrastructure in our outpatient chemotherapy infusion centers, a process that is currently underway and that will require a few unique considerations.

  11. 46 CFR 177.202 - Plans and information required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... materials; (iv) Type and size of generators and prime movers; (v) Type and size of generator cables, bus-tie... 7102, Washington, DC 20593-7102. Three copies of all documents are required to be submitted for Marine...

  12. Environmental Protection Agency EIT Procurement Checklist for Section 508 Instructions

    EPA Pesticide Factsheets

    Includes examples of items that are considered electronic information technology (EIT), and some that are not, explanations of each exemption and requirement, and how to provide required documentation to justify exemption or undue burden.

  13. Multisource data fusion for documenting archaeological sites

    NASA Astrophysics Data System (ADS)

    Knyaz, Vladimir; Chibunichev, Alexander; Zhuravlev, Denis

    2017-10-01

    The quality of archaeological sites documenting is of great importance for cultural heritage preserving and investigating. The progress in developing new techniques and systems for data acquisition and processing creates an excellent basis for achieving a new quality of archaeological sites documenting and visualization. archaeological data has some specific features which have to be taken into account when acquiring, processing and managing. First of all, it is a needed to gather as full as possible information about findings providing no loss of information and no damage to artifacts. Remote sensing technologies are the most adequate and powerful means which satisfy this requirement. An approach to archaeological data acquiring and fusion based on remote sensing is proposed. It combines a set of photogrammetric techniques for obtaining geometrical and visual information at different scales and detailing and a pipeline for archaeological data documenting, structuring, fusion, and analysis. The proposed approach is applied for documenting of Bosporus archaeological expedition of Russian State Historical Museum.

  14. Method and apparatus for filtering visual documents

    NASA Technical Reports Server (NTRS)

    Rorvig, Mark E. (Inventor); Shelton, Robert O. (Inventor)

    1993-01-01

    A method and apparatus for producing an abstract or condensed version of a visual document is presented. The frames comprising the visual document are first sampled to reduce the number of frames required for processing. The frames are then subjected to a structural decomposition process that reduces all information in each frame to a set of values. These values are in turn normalized and further combined to produce only one information content value per frame. The information content values of these frames are then compared to a selected distribution cutoff point. This effectively selects those values at the tails of a normal distribution, thus filtering key frames from their surrounding frames. The value for each frame is then compared with the value from the previous frame, and the respective frame is finally stored only if the values are significantly different. The method filters or compresses a visual document with a reduction in digital storage on the ratio of up to 700 to 1 or more, depending on the content of the visual document being filtered.

  15. 75 FR 52543 - Notice of Proposed Information Collection for Public Comment; Requirements for Designating...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-08-26

    ... designation before they designate projects for elderly families only, non-elderly disabled families only, or elderly and disabled families. In this plan, PHAs must document why the designation is needed, information...

  16. 76 FR 60853 - Agency Information Collection Activities: Documents Required Aboard Private Aircraft

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-09-30

    ... respondents or record keepers from the collection of information (a total of capital/startup costs and.... Estimated Number of Respondents: 120,000. Estimated Number of Annual Responses: 120,000. Estimated Time per...

  17. Tank waste remediation system configuration management plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    The configuration management program for the Tank Waste Remediation System (TWRS) Project Mission supports management of the project baseline by providing the mechanisms to identify, document, and control the functional and physical characteristics of the products. This document is one of the tools used to develop and control the mission and work. It is an integrated approach for control of technical, cost, schedule, and administrative information necessary to manage the configurations for the TWRS Project Mission. Configuration management focuses on five principal activities: configuration management system management, configuration identification, configuration status accounting, change control, and configuration management assessments. TWRS Projectmore » personnel must execute work in a controlled fashion. Work must be performed by verbatim use of authorized and released technical information and documentation. Application of configuration management will be consistently applied across all TWRS Project activities and assessed accordingly. The Project Hanford Management Contract (PHMC) configuration management requirements are prescribed in HNF-MP-013, Configuration Management Plan (FDH 1997a). This TWRS Configuration Management Plan (CMP) implements those requirements and supersedes the Tank Waste Remediation System Configuration Management Program Plan described in Vann, 1996. HNF-SD-WM-CM-014, Tank Waste Remediation System Configuration Management Implementation Plan (Vann, 1997) will be revised to implement the requirements of this plan. This plan provides the responsibilities, actions and tools necessary to implement the requirements as defined in the above referenced documents.« less

  18. Analyzing Document Retrievability in Patent Retrieval Settings

    NASA Astrophysics Data System (ADS)

    Bashir, Shariq; Rauber, Andreas

    Most information retrieval settings, such as web search, are typically precision-oriented, i.e. they focus on retrieving a small number of highly relevant documents. However, in specific domains, such as patent retrieval or law, recall becomes more relevant than precision: in these cases the goal is to find all relevant documents, requiring algorithms to be tuned more towards recall at the cost of precision. This raises important questions with respect to retrievability and search engine bias: depending on how the similarity between a query and documents is measured, certain documents may be more or less retrievable in certain systems, up to some documents not being retrievable at all within common threshold settings. Biases may be oriented towards popularity of documents (increasing weight of references), towards length of documents, favour the use of rare or common words; rely on structural information such as metadata or headings, etc. Existing accessibility measurement techniques are limited as they measure retrievability with respect to all possible queries. In this paper, we improve accessibility measurement by considering sets of relevant and irrelevant queries for each document. This simulates how recall oriented users create their queries when searching for relevant information. We evaluate retrievability scores using a corpus of patents from US Patent and Trademark Office.

  19. Informed Consent: Does Anyone Really Understand What Is Contained In The Medical Record?

    PubMed

    Fenton, S H; Manion, F; Hsieh, K; Harris, M

    2015-01-01

    Despite efforts to provide standard definitions of terms such as "medical record", "computer-based patient record", "electronic medical record" and "electronic health record", the terms are still used interchangeably. Initiatives like data and information governance, research biorepositories, and learning health systems require availability and reuse of data, as well as common understandings of the scope for specific purposes. Lacking widely shared definitions, utilization of the afore-mentioned terms in research informed consent documents calls to question whether all participants in the research process - patients, information technology and regulatory staff, and the investigative team - fully understand what data and information they are asking to obtain and agreeing to share. This descriptive study explored the terminology used in research informed consent documents when describing patient data and information, asking the question "Does the use of the term "medical record" in the context of a research informed consent document accurately represent the scope of the data involved?" Informed consent document templates found on 17 Institutional Review Board (IRB) websites with Clinical and Translational Science Awards (CTSA) were searched for terms that appeared to be describing the data resources to be accessed. The National Library of Medicine's (NLM) Terminology Services was searched for definitions provided by key standards groups that deposit terminologies with the NLM. The results suggest research consent documents are using outdated terms to describe patient information, health care terminology systems need to consider the context of research for use cases, and that there is significant work to be done to assure the HIPAA Omnibus Rule is applied to contemporary activities such as biorepositories and learning health systems. "Medical record", a term used extensively in research informed consent documents, is ambiguous and does not serve us well in the context of contemporary information management and governance.

  20. Directory of Energy Information Administration model abstracts

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    1987-08-11

    This report contains brief statements from the model managers about each model's title, acronym, purpose, and status, followed by more detailed information on characteristics, uses, and requirements. Sources for additional information are identified. All models ''active'' through March 1987 are included. The main body of this directory is an alphabetical list of all active EIA models. Appendix A identifies major EIA modeling systems and the models within these systems, and Appendix B identifies active EIA models by type (basic, auxiliary, and developing). A basic model is one designated by the EIA Administrator as being sufficiently important to require sustained supportmore » and public scrutiny. An auxiliary model is one designated by the EIA Administrator as being used only occasionally in analyses, and therefore requires minimal levels of documentation. A developing model is one designated by the EIA Administrator as being under development and yet of sufficient interest to require a basic level of documentation at a future date. EIA also leases models developed by proprietary software vendors. Documentation for these ''proprietary'' models is the responsibility of the companies from which they are leased. EIA has recently leased models from Chase Econometrics, Inc., Data Resources, Inc. (DRI), the Oak Ridge National Laboratory (ORNL), and Wharton Econometric Forecasting Associates (WEFA). Leased models are not abstracted here. The directory is intended for the use of energy and energy-policy analysts in the public and private sectors.« less

  1. 78 FR 16825 - Approval of Air Quality Implementation Plans; Navajo Nation; Regional Haze Requirements for...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-03-19

    ... Quality Implementation Plans; Navajo Nation; Regional Haze Requirements for Navajo Generating Station... source-specific federal implementation plan (FIP) requiring the Navajo Generating Station (NGS), located... . SUPPLEMENTARY INFORMATION: Throughout this document, ``we'', ``us'', and ``our'' refer to EPA. Table of Contents...

  2. 24 CFR 982.158 - Program accounts and records.

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ... by HUD, including requirements governing computerized or electronic forms of record-keeping. The PHA... furnish to HUD accounts and other records, reports, documents and information, as required by HUD. For provisions on electronic transmission of required family data, see 24 CFR part 908. (c) HUD and the...

  3. 24 CFR 982.158 - Program accounts and records.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... by HUD, including requirements governing computerized or electronic forms of record-keeping. The PHA... furnish to HUD accounts and other records, reports, documents and information, as required by HUD. For provisions on electronic transmission of required family data, see 24 CFR part 908. (c) HUD and the...

  4. An exponentiation method for XML element retrieval.

    PubMed

    Wichaiwong, Tanakorn

    2014-01-01

    XML document is now widely used for modelling and storing structured documents. The structure is very rich and carries important information about contents and their relationships, for example, e-Commerce. XML data-centric collections require query terms allowing users to specify constraints on the document structure; mapping structure queries and assigning the weight are significant for the set of possibly relevant documents with respect to structural conditions. In this paper, we present an extension to the MEXIR search system that supports the combination of structural and content queries in the form of content-and-structure queries, which we call the Exponentiation function. It has been shown the structural information improve the effectiveness of the search system up to 52.60% over the baseline BM25 at MAP.

  5. Documentation requirements for Applications Systems Verification and Transfer projects (ASVTs)

    NASA Technical Reports Server (NTRS)

    Suchy, J. T.

    1977-01-01

    NASA's Application Systems Verification and Transfer Projects (ASVTs) are deliberate efforts to facilitate the transfer of applications of NASA-developed space technology to users such as federal agencies, state and local governments, regional planning groups, public service institutions, and private industry. This study focused on the role of documentation in facilitating technology transfer both to primary users identified during project planning and to others with similar information needs. It was understood that documentation can be used effectively when it is combined with informal (primarily verbal) communication within each user community and with other formal techniques such as organized demonstrations and training programs. Documentation examples from eight ASVT projects and one potential project were examined to give scope to the investigation.

  6. Design study of RL10 derivatives. Volume 3, part 1: Preliminary interface control document. [development of baseline engines for space tug vehicles

    NASA Technical Reports Server (NTRS)

    Adams, A.

    1973-01-01

    The Interface Control Document contains engine information necessary for installation of the baseline RL10 Derivative engines in the Space Tug vehicle. The ICD presents a description of the baseline engines and their operating characteristics, mass and load characteristics, and environmental criteria. The document defines the engine/vehicle mechanical, electrical, fluid and pneumatic interface requirements.

  7. Development of integrated programs for Aerospace-vehicle Design (IPAD): Product program management systems

    NASA Technical Reports Server (NTRS)

    Isenberg, J. M.; Southall, J. W.

    1979-01-01

    The Integrated Programs for Aerospace Vehicle Design (IPAD) is a computing system to support company-wide design information processing. This document presents a brief description of the management system used to direct and control a product-oriented program. This document, together with the reference design process (CR 2981) and the manufacture interactions with the design process (CR 2982), comprises the reference information that forms the basis for specifying IPAD system requirements.

  8. 75 FR 72858 - Agency Information Collection Activities; Revision of a Currently-Approved Information Collection...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-11-26

    ... Safety Assistance Programs (MCSAP).'' The information required consists of grant application preparation, quarterly reports and electronic data documenting the results of driver/vehicle inspections performed by the... Time per Response: Grant application preparation: 79.5 hours each; quarterly report preparation: 8...

  9. 50 CFR 23.52 - What are the requirements for replacing a lost, damaged, stolen, or accidentally destroyed CITES...

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... information you need to provide (more than one circumstance may apply to you): If Then (i) The shipment has.... When applying for a U.S. replacement document, you must provide sufficient information for us to find... issued for a shipment that has already occurred does not require validation. (f) Validation. For an...

  10. 12 CFR 611.1216 - Public availability of documents related to the termination.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

  11. 12 CFR 611.1216 - Public availability of documents related to the termination.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

  12. 12 CFR 611.1216 - Public availability of documents related to the termination.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

  13. 12 CFR 611.1216 - Public availability of documents related to the termination.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

  14. 17 CFR 240.14c-4 - Presentation of information in information statement.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... documents, such as type size and font, by presenting all required information in a format readily... printed information statements shall be in roman type at least as large and as legible as 10-point modern type except that to the extent necessary for convenient presentation, financial statements and other...

  15. 78 FR 54790 - Revisions to Operational Requirements for the Use of Enhanced Flight Vision Systems (EFVS) and to...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-09-06

    ....gov . SUPPLEMENTARY INFORMATION: See the ``Additional Information'' section for information on how to comment on this proposal and how the FAA will handle comments received. The ``Additional Information..., environmental, energy, or federalism impacts that might result from adopting the proposals in this document. The...

  16. The Electronic Documentation Project in the NASA mission control center environment

    NASA Technical Reports Server (NTRS)

    Wang, Lui; Leigh, Albert

    1994-01-01

    NASA's space programs like many other technical programs of its magnitude is supported by a large volume of technical documents. These documents are not only diverse but also abundant. Management, maintenance, and retrieval of these documents is a challenging problem by itself; but, relating and cross-referencing this wealth of information when it is all on a medium of paper is an even greater challenge. The Electronic Documentation Project (EDP) is to provide an electronic system capable of developing, distributing and controlling changes for crew/ground controller procedures and related documents. There are two primary motives for the solution. The first motive is to reduce the cost of maintaining the current paper based method of operations by replacing paper documents with electronic information storage and retrieval. And, the other is to improve the efficiency and provide enhanced flexibility in document usage. Initially, the current paper based system will be faithfully reproduced in an electronic format to be used in the document viewing system. In addition, this metaphor will have hypertext extensions. Hypertext features support basic functions such as full text searches, key word searches, data retrieval, and traversal between nodes of information as well as speeding up the data access rate. They enable related but separate documents to have relationships, and allow the user to explore information naturally through non-linear link traversals. The basic operational requirements of the document viewing system are to: provide an electronic corollary to the current method of paper based document usage; supplement and ultimately replace paper-based documents; maintain focused toward control center operations such as Flight Data File, Flight Rules and Console Handbook viewing; and be available NASA wide.

  17. XML and its impact on content and structure in electronic health care documents.

    PubMed Central

    Sokolowski, R.; Dudeck, J.

    1999-01-01

    Worldwide information networks have the requirement that electronic documents must be easily accessible, portable, flexible and system-independent. With the development of XML (eXtensible Markup Language), the future of electronic documents, health care informatics and the Web itself are about to change. The intent of the recently formed ASTM E31.25 subcommittee, "XML DTDs for Health Care", is to develop standard electronic document representations of paper-based health care documents and forms. A goal of the subcommittee is to work together to enhance existing levels of interoperability among the various XML/SGML standardization efforts, products and systems in health care. The ASTM E31.25 subcommittee uses common practices and software standards to develop the implementation recommendations for XML documents in health care. The implementation recommendations are being developed to standardize the many different structures of documents. These recommendations are in the form of a set of standard DTDs, or document type definitions that match the electronic document requirements in the health care industry. This paper discusses recent efforts of the ASTM E31.25 subcommittee. PMID:10566338

  18. 5 CFR 1216.203 - Filing requirements for litigants seeking documents or testimony.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... outweighs any need to maintain the confidentiality of the information and outweighs the burden on the MSPB... travel, and for attendance in the legal proceeding. (c) The MSPB reserves the right to require additional...

  19. 75 FR 458 - Agency Information Collection Activities: Submission for the Office of Management and Budget (OMB...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-01-05

    ... required: Frequently. 6. Who will be required or asked to report: Individuals or companies requesting... NRC Headquarters' Public Document Room. Copies of the form are utilized by the reproduction contractor...

  20. Semantic Similarity between Web Documents Using Ontology

    NASA Astrophysics Data System (ADS)

    Chahal, Poonam; Singh Tomer, Manjeet; Kumar, Suresh

    2018-06-01

    The World Wide Web is the source of information available in the structure of interlinked web pages. However, the procedure of extracting significant information with the assistance of search engine is incredibly critical. This is for the reason that web information is written mainly by using natural language, and further available to individual human. Several efforts have been made in semantic similarity computation between documents using words, concepts and concepts relationship but still the outcome available are not as per the user requirements. This paper proposes a novel technique for computation of semantic similarity between documents that not only takes concepts available in documents but also relationships that are available between the concepts. In our approach documents are being processed by making ontology of the documents using base ontology and a dictionary containing concepts records. Each such record is made up of the probable words which represents a given concept. Finally, document ontology's are compared to find their semantic similarity by taking the relationships among concepts. Relevant concepts and relations between the concepts have been explored by capturing author and user intention. The proposed semantic analysis technique provides improved results as compared to the existing techniques.

  1. Semantic Similarity between Web Documents Using Ontology

    NASA Astrophysics Data System (ADS)

    Chahal, Poonam; Singh Tomer, Manjeet; Kumar, Suresh

    2018-03-01

    The World Wide Web is the source of information available in the structure of interlinked web pages. However, the procedure of extracting significant information with the assistance of search engine is incredibly critical. This is for the reason that web information is written mainly by using natural language, and further available to individual human. Several efforts have been made in semantic similarity computation between documents using words, concepts and concepts relationship but still the outcome available are not as per the user requirements. This paper proposes a novel technique for computation of semantic similarity between documents that not only takes concepts available in documents but also relationships that are available between the concepts. In our approach documents are being processed by making ontology of the documents using base ontology and a dictionary containing concepts records. Each such record is made up of the probable words which represents a given concept. Finally, document ontology's are compared to find their semantic similarity by taking the relationships among concepts. Relevant concepts and relations between the concepts have been explored by capturing author and user intention. The proposed semantic analysis technique provides improved results as compared to the existing techniques.

  2. Reporting of feasibility factors in publications on integrated treatment programs for women with substance abuse issues and their children: a systematic review and analysis.

    PubMed

    Henderson, Joanna; Milligan, Karen; Niccols, Alison; Thabane, Lehana; Sword, Wendy; Smith, Ainsley; Rosenkranz, Susan

    2012-12-07

    Implementation of evidence-based practices in real-world settings is a complex process impacted by many factors, including intervention, dissemination, service provider, and organizational characteristics. Efforts to improve knowledge translation have resulted in greater attention to these factors. Researcher attention to the applicability of findings to applied settings also has increased. Much less attention, however, has been paid to intervention feasibility, an issue important to applied settings. In a systematic review of 121 documents regarding integrated treatment programs for women with substance abuse issues and their children, we examined the presence of feasibility-related information. Specifically, we analysed study descriptions for information regarding feasibility factors in six domains (intervention, practitioner, client, service delivery, organizational, and service system). On average, fewer than half of the 25 feasibility details assessed were included in the documents. Most documents included some information describing the participating clients, the services offered as part of the intervention, the location of services, and the expected length of stay or number of sessions. Only approximately half of the documents included specific information about the treatment model. Few documents indicated whether the intervention was manualized or whether the intervention was preceded by a standardized screening or assessment process. Very few provided information about the core intervention features versus the features open to local adaptation, or the staff experience or training required to deliver the intervention. As has been found in reviews of intervention studies in other fields, our findings revealed that most documents provide some client and intervention information, but few documents provided sufficient information to fully evaluate feasibility. We consider possible explanations for the paucity of feasibility information and provide suggestions for better reporting to promote diffusion of evidence-based practices.

  3. 2014 Proposed Revision to 2008 Ozone National Ambient Air Quality Standards (NAAQS) Supporting Documents

    EPA Pesticide Factsheets

    Find information on the 2014 proposed ozone NAAQS revision, and find tools for background ozone, maps of nonattainment areas, an overview of the proposal, and information on designations, monitoring and permitting requirements

  4. 78 FR 65663 - Agency Information Collection Activities; Proposed Collection; Comment Request; Food Labeling...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-11-01

    ... elements required by Sec. 101.9(j)(18). Section 101.10 requires that restaurants provide nutrition... or regulatory officials upon request. Section 101.13(q)(5) requires that restaurants document and... their products. Some of the regulations affect food retailers, such as supermarkets and restaurants. We...

  5. Bayesian Inference for NASA Probabilistic Risk and Reliability Analysis

    NASA Technical Reports Server (NTRS)

    Dezfuli, Homayoon; Kelly, Dana; Smith, Curtis; Vedros, Kurt; Galyean, William

    2009-01-01

    This document, Bayesian Inference for NASA Probabilistic Risk and Reliability Analysis, is intended to provide guidelines for the collection and evaluation of risk and reliability-related data. It is aimed at scientists and engineers familiar with risk and reliability methods and provides a hands-on approach to the investigation and application of a variety of risk and reliability data assessment methods, tools, and techniques. This document provides both: A broad perspective on data analysis collection and evaluation issues. A narrow focus on the methods to implement a comprehensive information repository. The topics addressed herein cover the fundamentals of how data and information are to be used in risk and reliability analysis models and their potential role in decision making. Understanding these topics is essential to attaining a risk informed decision making environment that is being sought by NASA requirements and procedures such as 8000.4 (Agency Risk Management Procedural Requirements), NPR 8705.05 (Probabilistic Risk Assessment Procedures for NASA Programs and Projects), and the System Safety requirements of NPR 8715.3 (NASA General Safety Program Requirements).

  6. Information Extraction for System-Software Safety Analysis: Calendar Year 2008 Year-End Report

    NASA Technical Reports Server (NTRS)

    Malin, Jane T.

    2009-01-01

    This annual report describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.

  7. 78 FR 23330 - Reports, Forms and Record Keeping Requirements, Agency Information Collection Activity Under OMB...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-18

    ... of this document and cite OMB Clearance No. 2127-0609, ``Criminal Penalty Safe Harbor Provision... Penalty Safe Harbor Provision.'' SUPPLEMENTARY INFORMATION: Under the Paperwork Reduction Act of 1995... change, of a currently approved collection of information: Criminal Penalty Safe Harbor Provision Type of...

  8. The NASA Program Management Tool: A New Vision in Business Intelligence

    NASA Technical Reports Server (NTRS)

    Maluf, David A.; Swanson, Keith; Putz, Peter; Bell, David G.; Gawdiak, Yuri

    2006-01-01

    This paper describes a novel approach to business intelligence and program management for large technology enterprises like the U.S. National Aeronautics and Space Administration (NASA). Two key distinctions of the approach are that 1) standard business documents are the user interface, and 2) a "schema-less" XML database enables flexible integration of technology information for use by both humans and machines in a highly dynamic environment. The implementation utilizes patent-pending NASA software called the NASA Program Management Tool (PMT) and its underlying "schema-less" XML database called Netmark. Initial benefits of PMT include elimination of discrepancies between business documents that use the same information and "paperwork reduction" for program and project management in the form of reducing the effort required to understand standard reporting requirements and to comply with those reporting requirements. We project that the underlying approach to business intelligence will enable significant benefits in the timeliness, integrity and depth of business information available to decision makers on all organizational levels.

  9. 12 CFR 625.12 - Documentation of fees and expenses.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... 12 Banks and Banking 6 2010-01-01 2010-01-01 false Documentation of fees and expenses. 625.12 Section 625.12 Banks and Banking FARM CREDIT ADMINISTRATION FARM CREDIT SYSTEM APPLICATION FOR AWARD OF FEES AND OTHER EXPENSES UNDER THE EQUAL ACCESS TO JUSTICE ACT Applicant Information Required § 625.12...

  10. 76 FR 61937 - Practice and Procedure: Rules of General Application, Safeguards, Antidumping and Countervailing...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-10-06

    ... System Web site at https://edis.usitc.gov . Failure to comply with the requirements of this chapter and... Electronic Document Information System (EDIS) already accepts electronic filing of certain documents, and..., regardless of whether the electronic docketing system is operational. The ITC TLA makes a similar comment...

  11. 40 CFR 8.5 - Submission of environmental documents.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... environmental documentation meets the requirements of Article 8 and Annex I of the Protocol and the provisions... Article 8 and Annex I of the Protocol and the provisions of this part, the operator will have no further... and with the concurrence of the National Science Foundation, will inform the operator that EPA finds...

  12. 40 CFR 8.5 - Submission of environmental documents.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... environmental documentation meets the requirements of Article 8 and Annex I of the Protocol and the provisions... Article 8 and Annex I of the Protocol and the provisions of this part, the operator will have no further... and with the concurrence of the National Science Foundation, will inform the operator that EPA finds...

  13. 40 CFR 8.5 - Submission of environmental documents.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... environmental documentation meets the requirements of Article 8 and Annex I of the Protocol and the provisions... Article 8 and Annex I of the Protocol and the provisions of this part, the operator will have no further... and with the concurrence of the National Science Foundation, will inform the operator that EPA finds...

  14. 40 CFR 8.5 - Submission of environmental documents.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... environmental documentation meets the requirements of Article 8 and Annex I of the Protocol and the provisions... Article 8 and Annex I of the Protocol and the provisions of this part, the operator will have no further... and with the concurrence of the National Science Foundation, will inform the operator that EPA finds...

  15. 40 CFR 8.5 - Submission of environmental documents.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... environmental documentation meets the requirements of Article 8 and Annex I of the Protocol and the provisions... Article 8 and Annex I of the Protocol and the provisions of this part, the operator will have no further... and with the concurrence of the National Science Foundation, will inform the operator that EPA finds...

  16. 49 CFR 1104.6 - Timely filing required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... offers next day delivery to Washington, DC. If the e-filing option is chosen (for those pleadings and documents that are appropriate for e-filing, as determined by reference to the information on the Board's Web site), then the e-filed pleading or document is timely filed if the e-filing process is completed...

  17. Challenges in reusing transactional data for daily documentation in neonatal intensive care.

    PubMed

    Kim, G R; Lawson, E E; Lehmann, C U

    2008-11-06

    The reuse of transactional data for clinical documentation requires navigation of computational, institutional and adaptive barriers. We describe organizational and technical issues in developing and deploying a daily progress note tool in a tertiary neonatal intensive care unit that reuses and aggregates data from a commercial integrated clinical information system.

  18. Minimum Qualifications for Faculty and Administrators in California Community Colleges. [Fifth Edition

    ERIC Educational Resources Information Center

    California Community Colleges, Sacramento. Office of the Chancellor.

    This document is the fifth edition of Minimum Qualifications for Faculty and Administrators in California Community Colleges and it updates information presented in the last edition. The document is divided into the following sections: disciplines requiring a Mater's degree, disciplines in which a Master's degree is not generally expected for…

  19. 77 FR 46763 - Documents to Support Submission of an Electronic Common Technical Document; Availability

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-06

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration [Docket No. FDA-2011-N-0724... not prepared at present to accept submissions utilizing this new version because eCTD software vendors need time to update their software to accommodate this information and because its use will require...

  20. 8 CFR 204.1 - General information about immediate relative and family-sponsored petitions.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... question. When an interview is required, all original documents must be presented for examination at the interview. (3) Foreign language documents must be accompanied by an English translation which has been... Service. If questions arise concerning the filing of the petition which cannot be resolved through a check...

  1. 8 CFR 204.1 - General information about immediate relative and family-sponsored petitions.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... question. When an interview is required, all original documents must be presented for examination at the interview. (3) Foreign language documents must be accompanied by an English translation which has been... Service. If questions arise concerning the filing of the petition which cannot be resolved through a check...

  2. Automated Detection of Privacy Sensitive Conditions in C-CDAs: Security Labeling Services at the Department of Veterans Affairs

    PubMed Central

    Bouhaddou, Omar; Davis, Mike; Donahue, Margaret; Mallia, Anthony; Griffin, Stephania; Teal, Jennifer; Nebeker, Jonathan

    2016-01-01

    Care coordination across healthcare organizations depends upon health information exchange. Various policies and laws govern permissible exchange, particularly when the information includes privacy sensitive conditions. The Department of Veterans Affairs (VA) privacy policy has required either blanket consent or manual sensitivity review prior to exchanging any health information. The VA experience has been an expensive, administratively demanding burden on staffand Veterans alike, particularly for patients without privacy sensitive conditions. Until recently, automatic sensitivity determination has not been feasible. This paper proposes a policy-driven algorithmic approach (Security Labeling Service or SLS) to health information exchange that automatically detects the presence or absence of specific privacy sensitive conditions and then, to only require a Veteran signed consent for release when actually present. The SLS was applied successfully to a sample of real patient Consolidated-Clinical Document Architecture(C-CDA) documents. The SLS identified standard terminology codes by both parsing structured entries and analyzing textual information using Natural Language Processing (NLP). PMID:28269828

  3. Automated Detection of Privacy Sensitive Conditions in C-CDAs: Security Labeling Services at the Department of Veterans Affairs.

    PubMed

    Bouhaddou, Omar; Davis, Mike; Donahue, Margaret; Mallia, Anthony; Griffin, Stephania; Teal, Jennifer; Nebeker, Jonathan

    2016-01-01

    Care coordination across healthcare organizations depends upon health information exchange. Various policies and laws govern permissible exchange, particularly when the information includes privacy sensitive conditions. The Department of Veterans Affairs (VA) privacy policy has required either blanket consent or manual sensitivity review prior to exchanging any health information. The VA experience has been an expensive, administratively demanding burden on staffand Veterans alike, particularly for patients without privacy sensitive conditions. Until recently, automatic sensitivity determination has not been feasible. This paper proposes a policy-driven algorithmic approach (Security Labeling Service or SLS) to health information exchange that automatically detects the presence or absence of specific privacy sensitive conditions and then, to only require a Veteran signed consent for release when actually present. The SLS was applied successfully to a sample of real patient Consolidated-Clinical Document Architecture(C-CDA) documents. The SLS identified standard terminology codes by both parsing structured entries and analyzing textual information using Natural Language Processing (NLP).

  4. Standard formatted data units-control authority operations

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The purpose of this document is to illustrate a Control Authority's (CA) possible operation. The document is an interpretation and expansion of the concept found in the CA Procedures Recommendation. The CA is described in terms of the functions it performs for the management and control of data descriptions (metadata). Functions pertaining to the organization of Member Agency Control Authority Offices (MACAOs) (e.g., creating and disbanding) are not discussed. The document also provides an illustrative operational view of a CA through scenarios describing interaction between those roles involved in collecting, controlling, and accessing registered metadata. The roles interacting with the CA are identified by their actions in requesting and responding to requests for metadata, and by the type of information exchanged. The scenarios and examples presented in this document are illustrative only. They represent possible interactions supported by either a manual or automated system. These scenarios identify requirements for an automated system. These requirements are expressed by identifying the information to be exchanged and the services that may be provided by a CA for that exchange.

  5. Unique strategies for technical information management at Johnson Space Center

    NASA Technical Reports Server (NTRS)

    Krishen, Vijay

    1994-01-01

    In addition to the current NASA manned programs, the maturation of Space Station and the introduction of the Space Exploration programs are anticipated to add substantially to the number and variety of data and documentation at NASA Johnson Space Center (JSC). This growth in the next decade has been estimated at five to ten fold compared to the current numbers. There will be an increased requirement for the tracking and currency of space program data and documents with National pressures to realize economic benefits from the research and technological developments of space programs. From a global perspective the demand for NASA's technical data and documentation is anticipated to increase at local, national, and international levels. The primary users will be government, industry, and academia. In our present national strategy, NASA's research and technology will assume a great role in the revitalization of the economy and gaining international competitiveness. Thus, greater demand will be placed on NASA's data and documentation resources. In this paper the strategies and procedures developed by DDMS, Inc., to accommodate the present and future information utilization needs are presented. The DDMS, Inc., strategies and procedures rely on understanding user requirements, library management issues, and technological applications for acquiring, searching, storing, and retrieving specific information accurately and quickly. The proposed approach responds to changing customer requirements and product deliveries. The unique features of the proposed strategy include: (1) To establish customer driven data and documentation management through an innovative and unique methods to identify needs and requirements. (2) To implement a structured process which responds to user needs, aimed at minimizing costs and maximizing services, resulting in increased productivity. (3) To provide a process of standardization of services and procedures. This standardization is the central theme of the strategic approach. It will allow Division level Data and Documentation Libraries (DDL's) to function independently and optimize efficiency at the Directorate level. This process also facilitates interconnectivity between Division level DDL's and makes them transparent to the users. (4) To implement the process of 'cost savings', and at the same time the objective is to gain substantial improvement in the organization, categorization, and preservation of JSC-generated data and documentation, and (5) To find, locate, retrace, restore, and preserve the Center-generated crucial scientific and technical information that has been and is being provided by the engineers and scientists of JSC. This is important to the preservation of 'lessons learned'. Preliminary estimates of the possible cost savings which will result from the implementation of this process will also be discussed in this paper.

  6. Directory of Energy Information Administration model abstracts 1988

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    1988-01-01

    This directory contains descriptions about each basic and auxiliary model, including the title, acronym, purpose, and type, followed by more detailed information on characteristics, uses, and requirements. For developing models, limited information is provided. Sources for additional information are identified. Included in this directory are 44 EIA models active as of February 1, 1988; 16 of which operate on personal computers. Models that run on personal computers are identified by ''PC'' as part of the acronyms. The main body of this directory is an alphabetical listing of all basic and auxiliary EIA models. Appendix A identifies major EIA modeling systemsmore » and the models within these systems, and Appendix B identifies EIA models by type (basic or auxiliary). Appendix C lists developing models and contact persons for those models. A basic model is one designated by the EIA Administrator as being sufficiently important to require sustained support and public scrutiny. An auxiliary model is one designated by the EIA Administrator as being used only occasionally in analyses, and therefore requires minimal levels of documentation. A developing model is one designated by the EIA Administrator as being under development and yet of sufficient interest to require a basic level of documentation at a future date. EIA also leases models developed by proprietary software vendors. Documentation for these ''proprietary'' models is the responsibility of the companies from which they are leased. EIA has recently leased models from Chase Econometrics, Inc., Data Resources, Inc. (DRI), the Oak Ridge National Laboratory (ORNL), and Wharton Econometric Forecasting Associates (WEFA). Leased models are not abstracted here.« less

  7. Requirements report for SSTO vertical take-off/horizontal landing vehicle

    NASA Technical Reports Server (NTRS)

    Greenberg, H. S.

    1994-01-01

    This document describes the detailed design requirements and design criteria to support Structures/TPS Technology development for SSTO winged vehicle configurations that use vertical take-off and horizontal landing and deliver 25,000 lb payloads to a 220 nm circular orbit at an inclination of 51.6 degrees or 40,000 lb payloads to a 150 nm circular orbit at a 28.5 degree of inclination. This document will be updated on a timely basis as informatIon becomes available throughout the project.

  8. Requirements report for SSTO vertical take-off/horizontal landing vehicle

    NASA Astrophysics Data System (ADS)

    Greenberg, H. S.

    1994-07-01

    This document describes the detailed design requirements and design criteria to support Structures/TPS Technology development for SSTO winged vehicle configurations that use vertical take-off and horizontal landing and deliver 25,000 lb payloads to a 220 nm circular orbit at an inclination of 51.6 degrees or 40,000 lb payloads to a 150 nm circular orbit at a 28.5 degree of inclination. This document will be updated on a timely basis as informatIon becomes available throughout the project.

  9. Supplemental design requirements document, Multifunction Waste Tank Facility, Project W-236A. Revision 1

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Groth, B.D.

    The Multi-Function Waste Tank Facility (MWTF) consists of four, nominal 1 million gallon, underground double-shell tanks, located in the 200-East area, and two tanks of the same capacity in the 200-West area. MWTF will provide environmentally safe storage capacity for wastes generated during remediation/retrieval activities of existing waste storage tanks. This document delineates in detail the information to be used for effective implementation of the Functional Design Criteria requirements.

  10. W-320 Department of Health documentation

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bailey, J.W.

    1998-08-07

    The purpose of this document is to gather information required to show that Project W-320 is in compliance with Washington State Department of Health requirements as specified in Radioactive Air Emissions Notice of Construction Project W-320, Tank 241-C-106 Sluicing, DOE/RL-95-45. Specifically, that W-320 is in compliance with ASME N509-1989 (Nuclear Power Plant Air-Cleaning Units and Components) and ASME N5 10-1989 (Testing of Nuclear Air Treatment Systems) for the 296-C-006 exhaust system.

  11. Capabilities and applications of the Program to Optimize Simulated Trajectories (POST). Program summary document

    NASA Technical Reports Server (NTRS)

    Brauer, G. L.; Cornick, D. E.; Stevenson, R.

    1977-01-01

    The capabilities and applications of the three-degree-of-freedom (3DOF) version and the six-degree-of-freedom (6DOF) version of the Program to Optimize Simulated Trajectories (POST) are summarized. The document supplements the detailed program manuals by providing additional information that motivates and clarifies basic capabilities, input procedures, applications and computer requirements of these programs. The information will enable prospective users to evaluate the programs, and to determine if they are applicable to their problems. Enough information is given to enable managerial personnel to evaluate the capabilities of the programs and describes the POST structure, formulation, input and output procedures, sample cases, and computer requirements. The report also provides answers to basic questions concerning planet and vehicle modeling, simulation accuracy, optimization capabilities, and general input rules. Several sample cases are presented.

  12. Requirements Specification Language (RSL) and supporting tools

    NASA Technical Reports Server (NTRS)

    Frincke, Deborah; Wolber, Dave; Fisher, Gene; Cohen, Gerald C.

    1992-01-01

    This document describes a general purpose Requirement Specification Language (RSL). RSL is a hybrid of features found in several popular requirement specification languages. The purpose of RSL is to describe precisely the external structure of a system comprised of hardware, software, and human processing elements. To overcome the deficiencies of informal specification languages, RSL includes facilities for mathematical specification. Two RSL interface tools are described. The Browser view contains a complete document with all details of the objects and operations. The Dataflow view is a specialized, operation-centered depiction of a specification that shows how specified operations relate in terms of inputs and outputs.

  13. Expanding the Use of Time/Frequency Difference of Arrival Geolocation in the Department of Defense

    DTIC Science & Technology

    2012-01-01

    next decade. Military acquisition and research , development, test , and evaluation will likely be the hardest hit by spending cuts (Eaglen and Nguyen...Unauthorized posting of RAND electronic documents to a non-RAND website is prohibited. RAND electronic documents are protected under copyright law...Permission is required from RAND to reproduce, or reuse in another form, any of our research documents for commercial use. For information on reprint

  14. Sampling criteria in multicollection searching.

    NASA Astrophysics Data System (ADS)

    Gilio, A.; Scozzafava, R.; Marchetti, P. G.

    In the first stage of the document retrieval process, no information concerning relevance of a particular document is available. On the other hand, computer implementation requires that the analysis be made only for a sample of retrieved documents. This paper addresses the significance and suitability of two different sampling criteria for a multicollection online search facility. The inevitability of resorting to a logarithmic criterion in order to achieve a "spread of representativeness" from the multicollection is demonstrated.

  15. Hanford Site National Environmental Policy Act (NEPA) Characterization Report, Revision 17

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Neitzel, Duane A.; Bunn, Amoret L.; Cannon, Sandra D.

    2005-09-30

    This document describes the U.S. Department of Energy’s (DOE) Hanford Site environment. It is updated each year and is intended to provide a consistent description of the Hanford Site environment for the many environmental documents being prepared by DOE contractors concerning the National Environmental Policy Act (NEPA). No statements about significance or environmental consequences are provided. This year’s report is the seventeenth revision of the original document published in 1988 and is (until replaced by the eighteenth revision) the only version that is relevant for use in the preparation of Hanford NEPA, State Environmental Policy Act (SEPA), and Comprehensive Environmentalmore » Response, Compensation, and Liability Act (CERCLA) documents. The two chapters included in this document (Chapters 4 and 6) are numbered to correspond to the chapters where such information is typically presented in environmental impact statements (EISs) and other Hanford Site NEPA or CERCLA documentation. Chapter 4.0 (Affected Environment) describes Hanford Site climate and meteorology; air quality; geology; hydrology; ecology; cultural, archaeological, and historical resources; socioeconomics; noise; and occupational health and safety. Sources for extensive tabular data related to these topics are provided in the chapter. Most subjects are divided into a general description of the characteristics of the Hanford Site, followed by site-specific information, where available, of the 100, 200, 300, and other areas. This division allows the reader to go directly to those sections of particular interest. When specific information on each of these separate areas is not complete or available, the general Hanford Site description should be used. Chapter 6.0 (Statutory and Regulatory Requirements) describes federal and state laws and regulations, DOE directives and permits, and presidential executive orders that are applicable to the NEPA documents prepared for Hanford Site activities. Information in Chapter 6 of this document can be adapted and supplemented with specific information for a chapter covering statutory and regulatory requirements in an environmental assessment or environmental impact statement. When preparing environmental assessments and EISs, authors should also be cognizant of the document titled Recommendations for the Preparation of Environmental Assessments and Environmental Impact Statements published by the DOE Office of NEPA Oversight (DOE 2004). Additional guidance on preparing DOE NEPA documents can be found at http://tis.eh.doe.gov/nepa/guidance.html. Any interested individual seeking baseline data on the Hanford Site and its past activities may also use the information contained in this document to evaluate projected activities and their impacts. For this 2005 revision, the following sections of the document were reviewed by the authors and updated with the best available information through May 2005: Climate and Meteorology Air Quality Geology – Seismicity section only Hydrology – Flow charts for the Columbia and Yakima rivers only Ecology – Threatened and Endangered Species subsection only Socioeconomics Occupational Safety All of Chapter 6.« less

  16. Generalized Information Architecture for Managing Requirements in IBM?s Rational DOORS(r) Application.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Aragon, Kathryn M.; Eaton, Shelley M.; McCornack, Marjorie Turner

    When a requirements engineering effort fails to meet expectations, often times the requirements management tool is blamed. Working with numerous project teams at Sandia National Laboratories over the last fifteen years has shown us that the tool is rarely the culprit; usually it is the lack of a viable information architecture with well- designed processes to support requirements engineering. This document illustrates design concepts with rationale, as well as a proven information architecture to structure and manage information in support of requirements engineering activities for any size or type of project. This generalized information architecture is specific to IBM's Rationalmore » DOORS (Dynamic Object Oriented Requirements System) software application, which is the requirements management tool in Sandia's CEE (Common Engineering Environment). This generalized information architecture can be used as presented or as a foundation for designing a tailored information architecture for project-specific needs. It may also be tailored for another software tool. Version 1.0 4 November 201« less

  17. Deep Borehole Field Test Requirements and Controlled Assumptions.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Hardin, Ernest

    2015-07-01

    This document presents design requirements and controlled assumptions intended for use in the engineering development and testing of: 1) prototype packages for radioactive waste disposal in deep boreholes; 2) a waste package surface handling system; and 3) a subsurface system for emplacing and retrieving packages in deep boreholes. Engineering development and testing is being performed as part of the Deep Borehole Field Test (DBFT; SNL 2014a). This document presents parallel sets of requirements for a waste disposal system and for the DBFT, showing the close relationship. In addition to design, it will also inform planning for drilling, construction, and scientificmore » characterization activities for the DBFT. The information presented here follows typical preparations for engineering design. It includes functional and operating requirements for handling and emplacement/retrieval equipment, waste package design and emplacement requirements, borehole construction requirements, sealing requirements, and performance criteria. Assumptions are included where they could impact engineering design. Design solutions are avoided in the requirements discussion. Deep Borehole Field Test Requirements and Controlled Assumptions July 21, 2015 iv ACKNOWLEDGEMENTS This set of requirements and assumptions has benefited greatly from reviews by Gordon Appel, Geoff Freeze, Kris Kuhlman, Bob MacKinnon, Steve Pye, David Sassani, Dave Sevougian, and Jiann Su.« less

  18. Using building information modeling to track and assess the structural condition of bridges.

    DOT National Transportation Integrated Search

    2016-08-01

    National Bridge Inspection Standards do not require documenting damage locations during an inspection, but bridge evaluation provisions highlight the importance of it. When determining a safe load-carrying capacity of a bridge, damage location inform...

  19. Implementing Information Assurance - Beyond Process

    DTIC Science & Technology

    2009-01-01

    disabled or properly configured. Tools and scripts are available to expedite the configuration process on some platforms, For example, approved Windows...in the System Security Plan (SSP) or Information Security Plan (lSP). Any PPSs not required for operation by the system must be disabled , This...Services must be disabled , Implementing an 1M capability within the boundary carries many policy and documentation requirements. Usemame and passwords

  20. Detailed requirements document for Stowage List and Hardware Tracking System (SLAHTS). [computer based information management system in support of space shuttle orbiter stowage configuration

    NASA Technical Reports Server (NTRS)

    Keltner, D. J.

    1975-01-01

    The stowage list and hardware tracking system, a computer based information management system, used in support of the space shuttle orbiter stowage configuration and the Johnson Space Center hardware tracking is described. The input, processing, and output requirements that serve as a baseline for system development are defined.

  1. ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

    NASA Technical Reports Server (NTRS)

    Wilber, George F.

    2017-01-01

    This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

  2. Software Documentation for the Bartlesville Public Schools: Part One. The Bartlesville System Total Guidance Information Support System.

    ERIC Educational Resources Information Center

    Roberts, Tommy L.; And Others

    The Total Guidance Information Support System (TGISS), is an information storage and retrieval system for counselors. The total TGISS, including hardware and software, extends the counselor's capabilities by providing ready access to student information under secure conditions. The hardware required includes: (1) IBM 360/50 central processing…

  3. An Exponentiation Method for XML Element Retrieval

    PubMed Central

    2014-01-01

    XML document is now widely used for modelling and storing structured documents. The structure is very rich and carries important information about contents and their relationships, for example, e-Commerce. XML data-centric collections require query terms allowing users to specify constraints on the document structure; mapping structure queries and assigning the weight are significant for the set of possibly relevant documents with respect to structural conditions. In this paper, we present an extension to the MEXIR search system that supports the combination of structural and content queries in the form of content-and-structure queries, which we call the Exponentiation function. It has been shown the structural information improve the effectiveness of the search system up to 52.60% over the baseline BM25 at MAP. PMID:24696643

  4. Mental Status Documentation: Information Quality and Data Processes

    PubMed Central

    Weir, Charlene; Gibson, Bryan; Taft, Teresa; Slager, Stacey; Lewis, Lacey; Staggers, Nancy

    2016-01-01

    Delirium is a fluctuating disturbance of cognition and/or consciousness associated with poor outcomes. Caring for patients with delirium requires integration of disparate information across clinicians, settings and time. The goal of this project was to characterize the information processes involved in nurses’ assessment, documentation, decisionmaking and communication regarding patients’ mental status in the inpatient setting. VA nurse managers of medical wards (n=18) were systematically selected across the US. A semi-structured telephone interview focused on current assessment, documentation, and communication processes, as well as clinical and administrative decision-making was conducted, audio-recorded and transcribed. A thematic analytic approach was used. Five themes emerged: 1) Fuzzy Concepts, 2) Grey Data, 3) Process Variability 4) Context is Critical and 5) Goal Conflict. This project describes the vague and variable information processes related to delirium and mental status that undermine effective risk, prevention, identification, communication and mitigation of harm. PMID:28269919

  5. Mental Status Documentation: Information Quality and Data Processes.

    PubMed

    Weir, Charlene; Gibson, Bryan; Taft, Teresa; Slager, Stacey; Lewis, Lacey; Staggers, Nancy

    2016-01-01

    Delirium is a fluctuating disturbance of cognition and/or consciousness associated with poor outcomes. Caring for patients with delirium requires integration of disparate information across clinicians, settings and time. The goal of this project was to characterize the information processes involved in nurses' assessment, documentation, decisionmaking and communication regarding patients' mental status in the inpatient setting. VA nurse managers of medical wards (n=18) were systematically selected across the US. A semi-structured telephone interview focused on current assessment, documentation, and communication processes, as well as clinical and administrative decision-making was conducted, audio-recorded and transcribed. A thematic analytic approach was used. Five themes emerged: 1) Fuzzy Concepts, 2) Grey Data, 3) Process Variability 4) Context is Critical and 5) Goal Conflict. This project describes the vague and variable information processes related to delirium and mental status that undermine effective risk, prevention, identification, communication and mitigation of harm.

  6. Integrated Information Systems for Electronic Chemotherapy Medication Administration

    PubMed Central

    Levy, Mia A.; Giuse, Dario A.; Eck, Carol; Holder, Gwen; Lippard, Giles; Cartwright, Julia; Rudge, Nancy K.

    2011-01-01

    Introduction: Chemotherapy administration is a highly complex and distributed task in both the inpatient and outpatient infusion center settings. The American Society of Clinical Oncology and the Oncology Nursing Society (ASCO/ONS) have developed standards that specify procedures and documentation requirements for safe chemotherapy administration. Yet paper-based approaches to medication administration have several disadvantages and do not provide any decision support for patient safety checks. Electronic medication administration that includes bar coding technology may provide additional safety checks, enable consistent documentation structure, and have additional downstream benefits. Methods: We describe the specialized configuration of clinical informatics systems for electronic chemotherapy medication administration. The system integrates the patient registration system, the inpatient order entry system, the pharmacy information system, the nursing documentation system, and the electronic health record. Results: We describe the process of deploying this infrastructure in the adult and pediatric inpatient oncology, hematology, and bone marrow transplant wards at Vanderbilt University Medical Center. We have successfully adapted the system for the oncology-specific documentation requirements detailed in the ASCO/ONS guidelines for chemotherapy administration. However, several limitations remain with regard to recording the day of treatment and dose number. Conclusion: Overall, the configured systems facilitate compliance with the ASCO/ONS guidelines and improve the consistency of documentation and multidisciplinary team communication. Our success has prompted us to deploy this infrastructure in our outpatient chemotherapy infusion centers, a process that is currently underway and that will require a few unique considerations. PMID:22043185

  7. Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

    NASA Technical Reports Server (NTRS)

    2005-01-01

    This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

  8. Spaceflight Human System Standards

    NASA Technical Reports Server (NTRS)

    Holubec, Keith; Tillman, Barry; Connolly, Jan

    2009-01-01

    NASA created a new approach for human system integration and human performance standards. NASA created two documents a standard and a reference handbook. The standard is titled NASA Space Flight Human-System Standard (SFHSS) and consists of two-volumes: Volume 1- Crew Health This volume covers standards needed to support astronaut health (medical care, nutrition, sleep, exercise, etc.) Volume 2 Human Factors, Habitability and Environmental Health This volume covers the standards for system design that will maintain astronaut performance (ie., environmental factors, design of facilities, layout of workstations, and lighting requirements). It includes classic human factors requirements. The new standards document is written in terms so that it is applicable to a broad range of present and future NASA systems. The document states that all new programs prepare system-specific requirements that will meet the general standards. For example, the new standard does not specify a design should accommodate specific percentiles of a defined population. Rather, NASA-STD-3001, Volume 2 states that all programs shall prepare program-specific requirements that define the user population and their size ranges. The design shall then accommodate the full size range of those users. The companion reference handbook, Human Integration Design Handbook (HIDH), was developed to capture the design consideration information from NASA-STD-3000, and adds spaceflight lessons learned, gaps in knowledge, example solutions, and suggests research to further mature specific disciplines. The HIDH serves two major purposes: HIDH is the reference document for writing human factors requirements for specific systems. HIDH contains design guidance information that helps insure that designers create systems which safely and effectively accommodate the capabilities and limitations of space flight crews.

  9. 40 CFR 141.74 - Analytical and monitoring requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... 40 Protection of Environment 22 2010-07-01 2010-07-01 false Analytical and monitoring requirements. 141.74 Section 141.74 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER... listed below. Information regarding obtaining these documents can be obtained from the Safe Drinking...

  10. 18 CFR 35.37 - Market power analysis required.

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ... the proceeding will be able to review any of the data, information, analysis or other documentation... 18 Conservation of Power and Water Resources 1 2012-04-01 2012-04-01 false Market power analysis... power analysis required. (a) (1) In addition to other requirements in subparts A and B, a Seller must...

  11. 18 CFR 35.37 - Market power analysis required.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... the proceeding will be able to review any of the data, information, analysis or other documentation... 18 Conservation of Power and Water Resources 1 2011-04-01 2011-04-01 false Market power analysis... power analysis required. (a) (1) In addition to other requirements in subparts A and B, a Seller must...

  12. 11 CFR 9003.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2014 CFR

    2014-01-01

    ... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

  13. 11 CFR 9003.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

  14. 11 CFR 9003.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

  15. 11 CFR 9003.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

  16. 11 CFR 9003.1 - Candidate and committee agreements.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

  17. YAdumper: extracting and translating large information volumes from relational databases to structured flat files.

    PubMed

    Fernández, José M; Valencia, Alfonso

    2004-10-12

    Downloading the information stored in relational databases into XML and other flat formats is a common task in bioinformatics. This periodical dumping of information requires considerable CPU time, disk and memory resources. YAdumper has been developed as a purpose-specific tool to deal with the integral structured information download of relational databases. YAdumper is a Java application that organizes database extraction following an XML template based on an external Document Type Declaration. Compared with other non-native alternatives, YAdumper substantially reduces memory requirements and considerably improves writing performance.

  18. Shuttle Ground Operations Efficiencies/Technologies Study (SGOE/T). Volume 5: Technical Information Sheets (TIS)

    NASA Technical Reports Server (NTRS)

    Scholz, A. L.; Hart, M. T.; Lowry, D. J.

    1987-01-01

    The Technology Information Sheet was assembled in database format during Phase I. This document was designed to provide a repository for information pertaining to 144 Operations and Maintenance Instructions (OMI) controlled operations in the Orbiter Processing Facility (OPF), Vehicle Assembly Building (VAB), and PAD. It provides a way to accumulate information about required crew sizes, operations task time duration (serial and/or parallel), special Ground Support Equipment (GSE). required, and identification of a potential application of existing technology or the need for the development of a new technolgoy item.

  19. 40 CFR 265.1064 - Recordkeeping requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... waste management units in one recordkeeping system if the system identifies each record by each...) Design documentation and monitoring, operating, and inspection information for each closed-vent system...) An up-to-date analysis and the supporting information and data used to determine whether or not...

  20. How to become a competent medical writer?

    PubMed

    Sharma, Suhasini

    2010-01-01

    Medical writing involves writing scientific documents of different types which include regulatory and research-related documents, disease or drug-related educational and promotional literature, publication articles like journal manuscripts and abstracts, content for healthcare websites, health-related magazines or news articles. The scientific information in these documents needs to be presented to suit the level of understanding of the target audience, namely, patients or general public, physicians or the regulators. Medical writers require an understanding of the medical concepts and terminology, knowledge of relevant guidelines as regards the structure and contents of specific documents, and good writing skills. They also need to be familiar with searching medical literature, understanding and presenting research data, the document review process, and editing and publishing requirements. Many resources are now available for medical writers to get the required training in the science and art of medical writing, and upgrade their knowledge and skills on an ongoing basis. The demand for medical writing is growing steadily in pharmaceutical and healthcare communication market. Medical writers can work independently or be employed as full time professionals. Life sciences graduates can consider medical writing as a valuable career option.

  1. Advanced information processing system: Input/output network management software

    NASA Technical Reports Server (NTRS)

    Nagle, Gail; Alger, Linda; Kemp, Alexander

    1988-01-01

    The purpose of this document is to provide the software requirements and specifications for the Input/Output Network Management Services for the Advanced Information Processing System. This introduction and overview section is provided to briefly outline the overall architecture and software requirements of the AIPS system before discussing the details of the design requirements and specifications of the AIPS I/O Network Management software. A brief overview of the AIPS architecture followed by a more detailed description of the network architecture.

  2. 50 CFR 23.53 - What are the requirements for obtaining a retrospective CITES document?

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... section have been met. (5) The issuing Management Authority must provide all of the following information... sufficient information for us to find that your activity meets all of the following criteria: (1) The... a technical error that was not prompted by information provided by the applicant when issuing the...

  3. 22 CFR 42.68 - Informal evaluation of family members if principal applicant precedes them.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ...: DOCUMENTATION OF IMMIGRANTS UNDER THE IMMIGRATION AND NATIONALITY ACT, AS AMENDED Application for Immigrant... an immigrant visa, the principal applicant shall be informed and required to acknowledge receipt of... alien will be issued an immigrant visa in the future. The principal applicant shall be so informed and...

  4. Public Goods and Public Interests: Scholarly Communication and Government Documents in Research Libraries

    ERIC Educational Resources Information Center

    Potvin, Sarah; Sare, Laura

    2016-01-01

    Federal mandates requiring that publicly funded research be made openly accessible recast scholarly information as public information and provide an impetus to join the efforts of scholarly communication and government information programs in United States research libraries. Most major research libraries are long-standing participants in the…

  5. Information Brokers: Case Studies of Successful Ventures.

    ERIC Educational Resources Information Center

    Holland Johnson, Alice Jane

    This guide is intended for librarians planning to start an information brokerage, whether as an entrepreneur or as a member of a document delivery group in a library. The guide identifies specific skills and relevant characteristics required to establish a successful information brokerage firm and describes a model to assist readers in the process…

  6. Hubble Space Telescope cycle 5 call for proposals

    NASA Technical Reports Server (NTRS)

    Bond, Howard E. (Editor)

    1994-01-01

    This document invites and supports participation by the international astronomical community in the HST General Observer and Archival Research programs. These documents contain the basic procedural and technical information required for HST proposal preparation and submission, including applicable deadlines. The telescope and its instruments were built under the auspices of the NASA and the European Space Agency.

  7. Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study. Volume 3: Interface control documents. Part 3: AMPS payload to instruments ICD

    NASA Technical Reports Server (NTRS)

    1976-01-01

    General physical, functional, and operational interface control requirements for instruments on the first AMPS payload are presented. Interface specifications are included to satisfy ground handling, prelaunch, launch, stowage, operation, and landing activities. Applicable supporting documentation to implement the information is also given.

  8. Documentation for Emissions of Greenhouse Gases in the United States 2008

    EIA Publications

    2011-01-01

    The Energy Policy Act of 1992 required the U.S. Energy Information Administration (EIA) to prepare an inventory of aggregate U.S. national emissions of greenhouse gases for the period 1987-1990, with annual updates thereafter. This report documents the methodology for the seventeenth annual inventory, covering national emissions over the period 1990-2008.

  9. Automated Text Markup for Information Retrieval from an Electronic Textbook of Infectious Disease

    PubMed Central

    Berrios, Daniel C.; Kehler, Andrew; Kim, David K.; Yu, Victor L.; Fagan, Lawrence M.

    1998-01-01

    The information needs of practicing clinicians frequently require textbook or journal searches. Making these sources available in electronic form improves the speed of these searches, but precision (i.e., the fraction of relevant to total documents retrieved) remains low. Improving the traditional keyword search by transforming search terms into canonical concepts does not improve search precision greatly. Kim et al. have designed and built a prototype system (MYCIN II) for computer-based information retrieval from a forthcoming electronic textbook of infectious disease. The system requires manual indexing by experts in the form of complex text markup. However, this mark-up process is time consuming (about 3 person-hours to generate, review, and transcribe the index for each of 218 chapters). We have designed and implemented a system to semiautomate the markup process. The system, information extraction for semiautomated indexing of documents (ISAID), uses query models and existing information-extraction tools to provide support for any user, including the author of the source material, to mark up tertiary information sources quickly and accurately.

  10. Relevance of health level 7 clinical document architecture and integrating the healthcare enterprise cross-enterprise document sharing profile for managing chronic wounds in a telemedicine context.

    PubMed

    Finet, Philippe; Gibaud, Bernard; Dameron, Olivier; Le Bouquin Jeannès, Régine

    2016-03-01

    The number of patients with complications associated with chronic diseases increases with the ageing population. In particular, complex chronic wounds raise the re-admission rate in hospitals. In this context, the implementation of a telemedicine application in Basse-Normandie, France, contributes to reduce hospital stays and transport. This application requires a new collaboration among general practitioners, private duty nurses and the hospital staff. However, the main constraint mentioned by the users of this system is the lack of interoperability between the information system of this application and various partners' information systems. To improve medical data exchanges, the authors propose a new implementation based on the introduction of interoperable clinical documents and a digital document repository for managing the sharing of the documents between the telemedicine application users. They then show that this technical solution is suitable for any telemedicine application and any document sharing system in a healthcare facility or network.

  11. Hanford Site National Environmental Policy Act (NEPA) Characterization

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Duncan, Joanne P.; Burk, Kenneth W.; Chamness, Mickie A.

    2007-09-27

    This document describes the U.S. Department of Energy’s (DOE) Hanford Site environment. It is intended to provide a consistent description of the Hanford Site for the many environmental documents being prepared by DOE contractors concerning the National Environmental Policy Act (NEPA). No statements regarding significance or environmental consequences are provided. This year’s report is the eighteen revision of the original document published in 1988 and is (until replaced by the nineteenth revision) the only version that is relevant for use in the preparation of Hanford NEPA, State Environmental Policy Act (SEPA), and Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA)more » documents. Two chapters are included in this document (Chapters 4 and 6), numbered to correspond to chapters typically presented in environmental impact statements (EISs) and other Hanford Site NEPA or CERCLA documentation. Chapter 4.0 (Affected Environment) describes Hanford Site climate and meteorology; air quality; geology; hydrology; ecology; cultural, archaeological, and historical resources; socioeconomics; noise; and occupational health and safety. Sources for extensive tabular data related to these topics are provided in the chapter. When possible, subjects are divided into a general description of the characteristics of the Hanford Site, followed by site-specific information, where available, for the 100, 200, 300 and other areas. This division allows the reader to go directly to those sections of particular interest. When specific information on each of these separate areas is not complete or available, the general Hanford Site description should be used. Chapter 6.0 (Statutory and Regulatory Requirements) describes federal and state laws and regulations, DOE directives and permits, and presidential executive orders that are applicable to NEPA documents prepared for Hanford Site activities. Information in Chapter 6 can be adapted and supplemented with specific information covering statutory and regulatory requirements for use in an environmental assessment or environmental impact statement. When preparing environmental assessments and EISs, authors should consult Recommendations for the Preparation of Environmental Assessments and Environmental Impact Statements published by the DOE Office of NEPA Oversight (DOE 2004). Additional direction and guidance on the preparation of DOE NEPA documents can be found at http://tis.eh.doe.gov/nepa/guidance.html. Individuals seeking baseline data on the Hanford Site and its past activities may also use the information contained in this document to evaluate projected activities and their impacts. Pacific Northwest National Laboratory (PNNL) staff prepared individual sections of this document, with input from other Hanford Site contractors with the best available information through May 2007. More detailed data are available from reference sources cited or from the authors. For this 2007 revision, the following sections of the document were reviewed by the authors and updated with the best available information through May 2005: Climate and Meteorology Air Quality Geology – Seismicity section only Hydrology – Flow charts for the Columbia and Yakima rivers only Ecology – Threatened and Endangered Species subsection only Socioeconomics Occupational Safety All of Chapter 6.« less

  12. Documentation of Nursing Practice Using a Computerized Medical Information System

    PubMed Central

    Romano, Carol

    1981-01-01

    This paper discusses a definition of the content of the computerized nursing data base developed by the Nursing Department for the Clinical Center Medical Information System at the National Institutes of Health in Bethesda, Maryland. The author describes the theoretical framework for the content and presents a model to describe the organization of the nursing data components in relation to the process of nursing care delivery. Nursing documentation requirements of Nurse Practice Acts, American Nurses Association Standards of Practice and the Joint Commission on Accreditation of Hospitals are also addressed as they relate to this data base. The advantages and disadvantages of such an approach to computerized documentation are discussed.

  13. 42 CFR 441.353 - Supporting documentation required.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... that are maintained by the agency and by providers of services to support financial accountability, information regarding how the State meets the requirement for financial accountability, and an explanation of... 1915(d) home and community-based waiver services. If the State has an approved Medicaid Management...

  14. NETMARK

    NASA Technical Reports Server (NTRS)

    Maluf, David A.; Koga, Dennis (Technical Monitor)

    2002-01-01

    This presentation discuss NASA's proposed NETMARK knowledge management tool which aims 'to control and interoperate with every block in a document, email, spreadsheet, power point, database, etc. across the lifecycle'. Topics covered include: system software requirements and hardware requirements, seamless information systems, computer architecture issues, and potential benefits to NETMARK users.

  15. Questions & Answers for the New Chemicals Program under the Toxic Substances Control Act (TSCA)

    EPA Pesticide Factsheets

    This Questions & Answers document for the New Chemicals Program is intended only to explain the requirements of TSCA section 5 and selected EPA regulations implementing section 5, and to provide useful information to persons subject to these requirements.

  16. 49 CFR 525.6 - Requirements for petition.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... ADMINISTRATION, DEPARTMENT OF TRANSPORTATION EXEMPTIONS FROM AVERAGE FUEL ECONOMY STANDARDS § 525.6 Requirements... arguments of the petitioner supporting the exemption and alternative average fuel economy standard requested... analyses used to develop that information and data. No documents may be incorporated by reference in a...

  17. Applying a sociolinguistic model to the analysis of informed consent documents.

    PubMed

    Granero-Molina, José; Fernández-Sola, Cayetano; Aguilera-Manrique, Gabriel

    2009-11-01

    Information on the risks and benefits related to surgical procedures is essential for patients in order to obtain their informed consent. Some disciplines, such as sociolinguistics, offer insights that are helpful for patient-professional communication in both written and oral consent. Communication difficulties become more acute when patients make decisions through an informed consent document because they may sign this with a lack of understanding and information, and consequently feel deprived of their freedom to make their choice about different treatments or surgery. This article discusses findings from documentary analysis using the sociolinguistic SPEAKING model, which was applied to the general and specific informed consent documents required for laparoscopic surgery of the bile duct at Torrecárdenas Hospital, Almería, Spain. The objective of this procedure was to identify flaws when information was provided, together with its readability, its voluntary basis, and patients' consent. The results suggest potential linguistic communication difficulties, different languages being used, cultural clashes, asymmetry of communication between professionals and patients, assignment of rights on the part of patients, and overprotection of professionals and institutions.

  18. 76 FR 49805 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-08-11

    ... request for extension of the previously approved collection of information discussed below. Regulation S-T... submission of documents on the Electronic Data Gathering, Analysis and Retrieval (``EDGAR'') system... any information collection requirements. An agency may not conduct or sponsor, and a person is not...

  19. Remote sensing for mined area reclamation: Application inventory

    NASA Technical Reports Server (NTRS)

    1971-01-01

    Applications of aerial remote sensing to coal mined area reclamation are documented, and information concerning available data banks for coal producing areas in the east and midwest is given. A summary of mined area information requirements to which remote sensing methods might contribute is included.

  20. 76 FR 28812 - Agency Information Collection Activities; Submission for OMB Review; Comment Request; Hoist...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-05-18

    ... for OMB Review; Comment Request; Hoist Operators' Physical Fitness ACTION: Notice. SUMMARY: The... information collection request (ICR) titled, ``Hoist Operators' Physical Fitness,'' to the Office of...' fitness by a qualified, licensed physician that includes documentation and recordkeeping requirements. The...

  1. Automation for System Safety Analysis

    NASA Technical Reports Server (NTRS)

    Malin, Jane T.; Fleming, Land; Throop, David; Thronesbery, Carroll; Flores, Joshua; Bennett, Ted; Wennberg, Paul

    2009-01-01

    This presentation describes work to integrate a set of tools to support early model-based analysis of failures and hazards due to system-software interactions. The tools perform and assist analysts in the following tasks: 1) extract model parts from text for architecture and safety/hazard models; 2) combine the parts with library information to develop the models for visualization and analysis; 3) perform graph analysis and simulation to identify and evaluate possible paths from hazard sources to vulnerable entities and functions, in nominal and anomalous system-software configurations and scenarios; and 4) identify resulting candidate scenarios for software integration testing. There has been significant technical progress in model extraction from Orion program text sources, architecture model derivation (components and connections) and documentation of extraction sources. Models have been derived from Internal Interface Requirements Documents (IIRDs) and FMEA documents. Linguistic text processing is used to extract model parts and relationships, and the Aerospace Ontology also aids automated model development from the extracted information. Visualizations of these models assist analysts in requirements overview and in checking consistency and completeness.

  2. Document fraud deterrent strategies: four case studies

    NASA Astrophysics Data System (ADS)

    Mercer, John W.

    1998-04-01

    This paper discusses the approaches taken to deter fraud committed against four documents: the machine-readable passport; the machine-readable visa; the Consular Report of Birth Abroad; and the Border Crossing Card. General approaches are discussed first, with an emphasis on the reasons for the document, the conditions of its use and the information systems required for it to function. A cost model of counterfeit deterrence is introduced. Specific approaches to each of the four documents are then discussed, in light of the issuance circumstances and criteria, the intent of the issuing authority, the applicable international standards and the level of protection and fraud resistance appropriate for the document.

  3. The TMIS life-cycle process document, revision A

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The Technical and Management Information System (TMIS) Life-Cycle Process Document describes the processes that shall be followed in the definition, design, development, test, deployment, and operation of all TMIS products and data base applications. This document is a roll out of TMIS Standards Document (SSP 30546). The purpose of this document is to define the life cycle methodology that the developers of all products and data base applications and any subsequent modifications shall follow. Included in this methodology are descriptions of the tasks, deliverables, reviews, and approvals that are required before a product or data base application is accepted in the TMIS environment.

  4. Interpreting and Reporting Radiological Water-Quality Data

    USGS Publications Warehouse

    McCurdy, David E.; Garbarino, John R.; Mullin, Ann H.

    2008-01-01

    This document provides information to U.S. Geological Survey (USGS) Water Science Centers on interpreting and reporting radiological results for samples of environmental matrices, most notably water. The information provided is intended to be broadly useful throughout the United States, but it is recommended that scientists who work at sites containing radioactive hazardous wastes need to consult additional sources for more detailed information. The document is largely based on recognized national standards and guidance documents for radioanalytical sample processing, most notably the Multi-Agency Radiological Laboratory Analytical Protocols Manual (MARLAP), and on documents published by the U.S. Environmental Protection Agency and the American National Standards Institute. It does not include discussion of standard USGS practices including field quality-control sample analysis, interpretive report policies, and related issues, all of which shall always be included in any effort by the Water Science Centers. The use of 'shall' in this report signifies a policy requirement of the USGS Office of Water Quality.

  5. Challenges and methodology for indexing the computerized patient record.

    PubMed

    Ehrler, Frédéric; Ruch, Patrick; Geissbuhler, Antoine; Lovis, Christian

    2007-01-01

    Patient records contain most crucial documents for managing the treatments and healthcare of patients in the hospital. Retrieving information from these records in an easy, quick and safe way helps care providers to save time and find important facts about their patient's health. This paper presents the scalability issues induced by the indexing and the retrieval of the information contained in the patient records. For this study, EasyIR, an information retrieval tool performing full text queries and retrieving the related documents has been used. An evaluation of the performance reveals that the indexing process suffers from overhead consequence of the particular structure of the patient records. Most IR tools are designed to manage very large numbers of documents in a single index whereas in our hypothesis, one index per record, which usually implies few documents, has been imposed. As the number of modifications and creations of patient records are significant in a day, using a specialized and efficient indexation tool is required.

  6. Photogrammetry for Archaeology: Collecting Pieces Together

    NASA Astrophysics Data System (ADS)

    Chibunichev, A. G.; Knyaz, V. A.; Zhuravlev, D. V.; Kurkov, V. M.

    2018-05-01

    The complexity of retrieving and understanding the archaeological data requires to apply different techniques, tools and sensors for information gathering, processing and documenting. Archaeological research now has the interdisciplinary nature involving technologies based on different physical principles for retrieving information about archaeological findings. The important part of archaeological data is visual and spatial information which allows reconstructing the appearance of the findings and relation between them. Photogrammetry has a great potential for accurate acquiring of spatial and visual data of different scale and resolution allowing to create archaeological documents of new type and quality. The aim of the presented study is to develop an approach for creating new forms of archaeological documents, a pipeline for their producing and collecting in one holistic model, describing an archaeological site. A set of techniques is developed for acquiring and integration of spatial and visual data of different level of details. The application of the developed techniques is demonstrated for documenting of Bosporus archaeological expedition of Russian State Historical Museum.

  7. Informed consent: Part II.

    PubMed

    Murphy, E K

    1988-05-01

    Although the legal responsibility to inform and obtain the patient's consent lies with the surgeon, the agency may have a duty to ensure that the patient's consent has been obtained. Agency liability is limited to those cases in which the agency knew (or should have known) that informed consent was not obtained. It is still unclear whether agencies have an affirmative duty to ensure that consent has been obtained. If this duty does exist, it appears that a policy requiring documentation in the medical record of the patient's consent meets this requirement. It is clear that whatever the extent of the agency's duty, it does not include the duty to give the patient information or assess his or her level of understanding. Court opinions discourage anyone but the physician from doing so. A nurse's legal responsibility is limited to following agency policy. Courts have not recognized any independent nurse duty beyond that which accrues to them as employees of the agency. Perioperative nurses often provide the final checkpoint that consent has been obtained and documented before the procedure begins. This unique position raises additional legal concerns if the agency's policy is not followed or if the premedicated patient arrives without proper consent documentation in the record. Perioperative nursing concerns will be discussed next month in Part III.

  8. 12 CFR 1022.3 - Definitions.

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... fingerprint, voice print, retina or iris image, or other unique physical representation; (3) Unique electronic... reporting agency to require additional documentation or information, such as a notarized affidavit. (j...

  9. 12 CFR 1022.3 - Definitions.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ... fingerprint, voice print, retina or iris image, or other unique physical representation; (3) Unique electronic... reporting agency to require additional documentation or information, such as a notarized affidavit. (j...

  10. Stationary Refrigeration

    EPA Pesticide Factsheets

    Resources for HVACR contractors, technicians, equipment owners and other regulated industry to check rules and requirements for managing refrigerant emissions, information on how to become a certified technician, and compliance assistance documents.

  11. Information Pre-Processing using Domain Meta-Ontology and Rule Learning System

    NASA Astrophysics Data System (ADS)

    Ranganathan, Girish R.; Biletskiy, Yevgen

    Around the globe, extraordinary amounts of documents are being created by Enterprises and by users outside these Enterprises. The documents created in the Enterprises constitute the main focus of the present chapter. These documents are used to perform numerous amounts of machine processing. While using thesedocuments for machine processing, lack of semantics of the information in these documents may cause misinterpretation of the information, thereby inhibiting the productiveness of computer assisted analytical work. Hence, it would be profitable to the Enterprises if they use well defined domain ontologies which will serve as rich source(s) of semantics for the information in the documents. These domain ontologies can be created manually, semi-automatically or fully automatically. The focus of this chapter is to propose an intermediate solution which will enable relatively easy creation of these domain ontologies. The process of extracting and capturing domain ontologies from these voluminous documents requires extensive involvement of domain experts and application of methods of ontology learning that are substantially labor intensive; therefore, some intermediate solutions which would assist in capturing domain ontologies must be developed. This chapter proposes a solution in this direction which involves building a meta-ontology that will serve as an intermediate information source for the main domain ontology. This chapter proposes a solution in this direction which involves building a meta-ontology as a rapid approach in conceptualizing a domain of interest from huge amount of source documents. This meta-ontology can be populated by ontological concepts, attributes and relations from documents, and then refined in order to form better domain ontology either through automatic ontology learning methods or some other relevant ontology building approach.

  12. Digitization of medical documents: an X-Windows application for fast scanning.

    PubMed

    Muñoz, A; Salvador, C H; Gonzalez, M A; Dueñas, A

    1992-01-01

    This paper deals with digitization, using a commercial scanner, of medical documents as still images for introduction into a computer-based Information System. Document management involves storing, editing and transmission. This task has usually been approached from the perspective of the difficulties posed by radiologic images because of their indisputable qualitative and quantitative significance. However, healthcare activities require the management of many other types of documents and involve the requirements of numerous users. One key to document management will be the availability of a digitizer to deal with the greatest possible number of different types of documents. This paper describes the relevant aspects of documents and the technical specifications that digitizers must fulfill. The concept of document type is introduced as the ideal set of digitizing parameters for a given document. The use of document type parameters can drastically reduce the time the user spends in scanning sessions. Presentation is made of an application based on Unix, X-Windows and OSF/Motif, with a GPIB interface, implemented around the document type concept. Finally, the results of the evaluation of the application are presented, focusing on the user interface, as well as on the viewing of color images in an X-Windows environment and the use of lossy algorithms in the compression of medical images.

  13. Completeness of patient records in community pharmacies post-discharge after in-patient medication reconciliation: a before-after study.

    PubMed

    Karapinar-Çarkıt, Fatma; van Breukelen, Ben R L; Borgsteede, Sander D; Janssen, Marjo J A; Egberts, Antoine C G; van den Bemt, Patricia M L A

    2014-08-01

    Transfer of discharge medication related information to community pharmacies could improve continuity of care. This requires for community pharmacies to accurately update their patient records when new information is transferred. An instruction manual that specifies how to document information regarding medication changes and clinical information (i.e. allergies/contraindications) could support community pharmacies. To explore the effect of instruction manuals sent to community pharmacies on completeness of their patient records. A before-after study was performed (July 2009-August 2010) in the St Lucas Andreas Hospital, a general teaching hospital in Amsterdam, The Netherlands. Patients discharged from the cardiology and respiratory ward were included consecutively. The intervention consisted of a training session for community pharmacies regarding documentation problems and faxing an instruction manual to community pharmacies specifying how to document discharge information in their information system. Usual care consisted of faxing a discharge medication overview to community pharmacies without additional instructions. Two weeks after discharge the medication records of community pharmacies were collected by fax. These were compared with the initial discharge overviews regarding completeness of medication changes (i.e. explicit explanation that medication had been changed) and clinical information documentation. MAIN OUTCOME MEASURE OUTCOMES: were the number and percentage of completely documented medication changes (either needing to be dispensed or not) and clinical information items. The sample size was calculated at 107 patients per measurement period. Multivariable logistic regression was used for analysis. Two hundred and eighteen patients (112 before-106 after) were included. Completeness of medication changes documentation increased marginally after the intervention (46.6 vs 56.3 %, adjusted Odds Ratio 1.4 [95 % confidence interval 1.07-1.83]). Documentation increased when medication was actually dispensed by the community pharmacy. No significant improvements were seen for allergy and contraindication documentation. The intervention is insufficient to increase the completeness of documentation by community pharmacies as marginal improvements were achieved. Future studies should evaluate whether electronic infrastructures may help in achieving updated medication records to improve continuity of pharmaceutical care.

  14. Guidelines and standard procedures for studies of ground-water quality; selection and installation of wells, and supporting documentation

    USGS Publications Warehouse

    Lapham, W.W.; Wilde, F.D.; Koterba, M.T.

    1997-01-01

    This is the first of a two-part report to document guidelines and standard procedures of the U.S. Geological Survey for the acquisition of data in ground-water-quality studies. This report provides guidelines and procedures for the selection and installation of wells for water-quality studies/*, and the required or recommended supporting documentation of these activities. Topics include (1) documentation needed for well files, field folders, and electronic files; (2) criteria and information needed for the selection of water-supply and observation wells, including site inventory and data collection during field reconnaissance; and (3) criteria and preparation for installation of monitoring wells, including the effects of equipment and materials on the chemistry of ground-water samples, a summary of drilling and coring methods, and information concerning well completion, development, and disposition.

  15. Space station systems: A bibliography with indexes (supplement 7)

    NASA Technical Reports Server (NTRS)

    1988-01-01

    This bibliography lists 1,158 reports, articles, and other documents introduced into the NASA scientific and technical information system between January 1, 1988 and June 30, 1988. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

  16. Space station systems: A bibliography with indexes (supplement 10)

    NASA Technical Reports Server (NTRS)

    1990-01-01

    This bibliography lists 1,422 reports, articles, and other documents introduced into the NASA scientific and technical information system between July 1, 1989 and December 31, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

  17. Space Station Systems: a Bibliography with Indexes (Supplement 8)

    NASA Technical Reports Server (NTRS)

    1988-01-01

    This bibliography lists 950 reports, articles, and other documents introduced into the NASA scientific and technical information system between July 1, 1989 and December 31, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

  18. Space station systems: A bibliography with indexes (supplement 9)

    NASA Technical Reports Server (NTRS)

    1989-01-01

    This bibliography lists 1,313 reports, articles, and other documents introduced into the NASA scientific and technical information system between January 1, 1989 and June 30, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

  19. Method for Examination and Documentation of Basic Information and Metadata from Published Reports Relevant to the Study of Stormwater Runoff Quality

    USGS Publications Warehouse

    Dionne, Shannon G.; Granato, Gregory E.; Tana, Cameron K.

    1999-01-01

    A readily accessible archive of information that is valid, current, and technically defensible is needed to make informed highway-planning, design, and management decisions. The National Highway Runoff Water-Quality Data and Methodology Synthesis (NDAMS) is a cataloging and assessment of the documentation of information relevant to highway-runoff water quality available in published reports. The report review process is based on the NDAMS review sheet, which was designed by the USGS with input from the FHWA, State transportation agencies, and the regulatory community. The report-review process is designed to determine the technical merit of the existing literature in terms of current requirements for data documentation, data quality, quality assurance and quality control (QA/QC), and technical issues that may affect the use of historical data. To facilitate the review process, the NDAMS review sheet is divided into 12 sections: (1) administrative review information, (2) investigation and report information, (3) temporal information, (4) location information (5) water-quality-monitoring information, (6) sample-handling methods, (7) constituent information, (8) sampling focus and matrix, (9) flow monitoring methods, (10) field QA/QC, (11) laboratory, and (12) uncertainty/error analysis. This report describes the NDAMS report reviews and metadata documentation methods and provides an overview of the approach and of the quality-assurance and quality-control program used to implement the review process. Detailed information, including a glossary of relevant terms, a copy of the report-review sheets, and reportreview instructions are completely documented in a series of three appendixes included with this report. Therefore the reviews are repeatable and the methods can be used by transportation research organizations to catalog new reports as they are published.

  20. GMSEC Interface Specification Document 2016 March

    NASA Technical Reports Server (NTRS)

    Handy, Matthew

    2016-01-01

    The GMSEC Interface Specification Document contains the standard set of defined messages. Each GMSEC standard message contains a GMSEC Information Bus Header section and a Message Contents section. Each message section identifies required fields, optional fields, data type and recommended use of the fields. Additionally, this document includes the message subjects associated with the standard messages. The system design of the operations center should ensure the components that are selected use both the API and the defined standard messages in order to achieve full interoperability from component to component.

  1. 17 CFR 4.34 - General disclosures required.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... trading advisor who participates in making trading or operational decisions for the trading advisor or... required. Except as otherwise provided herein, a Disclosure Document must include the following information... MAY BE LIQUIDATED AT A LOSS, AND YOU WILL BE LIABLE FOR ANY RESULTING DEFICIT IN YOUR ACCOUNT. UNDER...

  2. 78 FR 66365 - Proposed Information Collection Activity; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-11-05

    ... for Needy Families (TANF) program, it imposed a new data requirement that States prepare and submit data verification procedures and replaced other data requirements with new versions including: the TANF Data Report, the SSP-MOE Data Report, the Caseload Reduction Documentation Process, and the Reasonable...

  3. Directory of Energy Information Administration Model Abstracts

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    1986-07-16

    This directory partially fulfills the requirements of Section 8c, of the documentation order, which states in part that: The Office of Statistical Standards will annually publish an EIA document based on the collected abstracts and the appendices. This report contains brief statements about each model's title, acronym, purpose, and status, followed by more detailed information on characteristics, uses, and requirements. Sources for additional information are identified. All models active through March 1985 are included. The main body of this directory is an alphabetical list of all active EIA models. Appendix A identifies major EIA modeling systems and the models withinmore » these systems, and Appendix B identifies active EIA models by type (basic, auxiliary, and developing). EIA also leases models developed by proprietary software vendors. Documentation for these proprietary models is the responsibility of the companies from which they are leased. EIA has recently leased models from Chase Econometrics, Inc., Data Resources, Inc. (DRI), the Oak Ridge National Laboratory (ORNL), and Wharton Econometric Forecasting Associates (WEFA). Leased models are not abstracted here. The directory is intended for the use of energy and energy-policy analysts in the public and private sectors.« less

  4. 7 CFR Exhibit C to Subpart C of... - Checklist of Visual Exhibits and Documentation for RRH, RCH, and LH Proposals

    Code of Federal Regulations, 2013 CFR

    2013-01-01

    ... the required information will be sufficient. C. Property Survey Map. A current survey map of the... specimen trees. If a current survey does not exist, the most accurate document which is available will be... suitable drainage and landscaping plans later in the planning process. E. Market survey. A market survey...

  5. U-10Mo Sample Preparation and Examination using Optical and Scanning Electron Microscopy

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Prabhakaran, Ramprashad; Joshi, Vineet V.; Rhodes, Mark A.

    2016-10-01

    The purpose of this document is to provide guidelines to prepare specimens of uranium alloyed with 10 weight percent molybdenum (U-10Mo) for optical metallography and scanning electron microscopy. This document also provides instructions to set up an optical microscope and a scanning electron microscope to analyze U-10Mo specimens and to obtain the required information.

  6. U-10Mo Sample Preparation and Examination using Optical and Scanning Electron Microscopy

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Prabhakaran, Ramprashad; Joshi, Vineet V.; Rhodes, Mark A.

    2016-03-30

    The purpose of this document is to provide guidelines to prepare specimens of uranium alloyed with 10 weight percent molybdenum (U-10Mo) for optical metallography and scanning electron microscopy. This document also provides instructions to set up an optical microscope and a scanning electron microscope to analyze U-10Mo specimens and to obtain the required information.

  7. Template protocol for clinical trials investigating vaccines—Focus on safety elements☆

    PubMed Central

    Bonhoeffer, Jan; Imoukhuede, Egeruan B.; Aldrovandi, Grace; Bachtiar, Novilia S.; Chan, Eng-Soon; Chang, Soju; Chen, Robert T.; Fernandopulle, Rohini; Goldenthal, Karen L.; Heffelfinger, James D.; Hossain, Shah; Jevaji, Indira; Khamesipour, Ali; Kochhar, Sonali; Makhene, Mamodikoe; Malkin, Elissa; Nalin, David; Prevots, Rebecca; Ramasamy, Ranjan; Sellers, Sarah; Vekemans, Johan; Walker, Kenneth B.; Wilson, Pam; Wong, Virginia; Zaman, Khalequz; Heininger, Ulrich

    2015-01-01

    This document is intended as a guide to the protocol development for trials of prophylactic vaccines. The template may serve phases I–IV clinical trials protocol development to include safety relevant information as required by the regulatory authorities and as deemed useful by the investigators. This document may also be helpful for future site strengthening efforts. PMID:23499603

  8. Zenith-100 Microcomputer Network for Air Command and Staff College.

    DTIC Science & Technology

    1987-04-01

    34 AD-A182 495 ZENI T-ipo ml CROCOMFUT E NET WOR( FOR AIR COMAND AND h SAFF CoLLG (U) AIl COMMAND ANDCSTAFF COLL MAX(WELL AFS "CAL W L GALWAY El AL...processing of documents by eliminating the time required to physically move the documents from one office to the next. Reproduction Savings. Information

  9. 17 CFR 240.14a-5 - Presentation of information in proxy statement.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... to printed documents, such as type size and font, by presenting all required information in a format... information. (d)(1) All printed proxy statements shall be in roman type at least as large and as legible as 10-point modern type, except that to the extent necessary for convenient presentation financial statements...

  10. Land use and land cover digital data

    USGS Publications Warehouse

    Fegeas, Robin G.; Claire, Robert W.; Guptill, Stephen C.; Anderson, K. Eric; Hallam, Cheryl A.

    1983-01-01

    The discipline of cartography is undergoing a number of profound changesthat center on the emerging influence ofdigital manipulation and analysis ofdata for the preparation of cartographic materials and for use in geographic information systems. Operational requirements have led to the development by the USGS National Mapping Division of several documents that establish in-house digital cartographic standards. In an effort to fulfill lead agency requirements for promulgation of Federal standards in the earth sciences, the documents have been edited and assembled with explanatory text into a USGS Circular. This Circular describes some of the pertinent issues relative to digital cartographic data standards, documents the digital cartographic data standards currently in use within the USGS, and details the efforts of the USGS related to the definition of national digital cartographic data standards. It consists of several chapters; the first is a general overview, and each succeeding chapter is made up from documents that establish in-house standards for one of the various types of digital cartographic data currently produced. This chapter 895-E, describes the Geographic Information Retrieval and Analysis System that is used in conjunction with the USGS land use and land cover classification system to encode, edit, manipuate, and analyze land use and land cover digital data.

  11. 77 FR 34123 - Information Collection Available for Public Comments and Recommendations

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-06-08

    ... from that office. SUPPLEMENTARY INFORMATION: Title of Collection: Monthly Report of Ocean Shipments... responsibilities under Public Resolution 17, to ensure compliance of ocean shipping requirements operating under.... An electronic version of this document is available on the World Wide Web at http://regulations.gov...

  12. 77 FR 4561 - Agency Information Collection Request; 60-Day Public Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-01-30

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES [Document Identifier: OS-0990-0335] Agency Information... Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed... OMB-approved program assessment requirements. The lack of general awareness and understanding about...

  13. 75 FR 76750 - BOEMRE Information Collection Activity: 1010-0183, Information Requirements for Exploration Plans...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-12-09

    ... DEPARTMENT OF THE INTERIOR Bureau of Ocean Energy Management, Regulation and Enforcement [Docket... for Exploration Plans, Development and Production Plans, and Development Operations Coordination Documents on the OCS NTL, Renewal of a Collection; Submitted for Office of Management and Budget (OMB...

  14. 40 CFR 82.178 - Information required to be submitted.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... chemicals. The submitter must also provide supporting documentation or references. (6) Global warming impacts. Data on the total global warming potential of the substitute, including information on the GWP index and the indirect contributions to global warming caused by the production or use of the substitute...

  15. 40 CFR 82.178 - Information required to be submitted.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... chemicals. The submitter must also provide supporting documentation or references. (6) Global warming impacts. Data on the total global warming potential of the substitute, including information on the GWP index and the indirect contributions to global warming caused by the production or use of the substitute...

  16. 32 CFR 2001.24 - Additional requirements.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... Foreign Nuclear Information (TFNI). (1) As permitted under 42 U.S.C. 2162(e), the Department of Energy.... (d) Working papers. A working paper is defined as documents or materials, regardless of the media... retention. Working papers containing classified information shall be dated when created, marked with the...

  17. 32 CFR 2001.24 - Additional requirements.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... Foreign Nuclear Information (TFNI). (1) As permitted under 42 U.S.C. 2162(e), the Department of Energy.... (d) Working papers. A working paper is defined as documents or materials, regardless of the media... retention. Working papers containing classified information shall be dated when created, marked with the...

  18. 32 CFR 2001.24 - Additional requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... Foreign Nuclear Information (TFNI). (1) As permitted under 42 U.S.C. 2162(e), the Department of Energy.... (d) Working papers. A working paper is defined as documents or materials, regardless of the media... retention. Working papers containing classified information shall be dated when created, marked with the...

  19. 32 CFR 2001.24 - Additional requirements.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... Foreign Nuclear Information (TFNI). (1) As permitted under 42 U.S.C. 2162(e), the Department of Energy.... (d) Working papers. A working paper is defined as documents or materials, regardless of the media... retention. Working papers containing classified information shall be dated when created, marked with the...

  20. The Bartlesville System; TGISS Software Documentation.

    ERIC Educational Resources Information Center

    Roberts, Tommy L.; And Others

    TGISS (Total Guidance Information Support System) is an information storage and retrieval system specifically designed to meet the needs and requirements of a counselor in the Bartlesville Public School environment. The system, which is a combination of man/machine capabilities, includes the hardware and software necessary to extend the…

  1. Reporting of feasibility factors in publications on integrated treatment programs for women with substance abuse issues and their children: a systematic review and analysis

    PubMed Central

    2012-01-01

    Background Implementation of evidence-based practices in real-world settings is a complex process impacted by many factors, including intervention, dissemination, service provider, and organizational characteristics. Efforts to improve knowledge translation have resulted in greater attention to these factors. Researcher attention to the applicability of findings to applied settings also has increased. Much less attention, however, has been paid to intervention feasibility, an issue important to applied settings. Methods In a systematic review of 121documents regarding integrated treatment programs for women with substance abuse issues and their children, we examined the presence of feasibility-related information. Specifically, we analysed study descriptions for information regarding feasibility factors in six domains (intervention, practitioner, client, service delivery, organizational, and service system). Results On average, fewer than half of the 25 feasibility details assessed were included in the documents. Most documents included some information describing the participating clients, the services offered as part of the intervention, the location of services, and the expected length of stay or number of sessions. Only approximately half of the documents included specific information about the treatment model. Few documents indicated whether the intervention was manualized or whether the intervention was preceded by a standardized screening or assessment process. Very few provided information about the core intervention features versus the features open to local adaptation, or the staff experience or training required to deliver the intervention. Conclusions As has been found in reviews of intervention studies in other fields, our findings revealed that most documents provide some client and intervention information, but few documents provided sufficient information to fully evaluate feasibility. We consider possible explanations for the paucity of feasibility information and provide suggestions for better reporting to promote diffusion of evidence-based practices. PMID:23217025

  2. Schema for the LANL infrasound analysis tool, infrapy

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Dannemann, Fransiska Kate; Marcillo, Omar Eduardo

    2017-04-14

    The purpose of this document is to define the schema used for the operation of the infrasound analysis tool, infrapy. The tables described by this document extend the CSS3.0 or KB core schema to include information required for the operation of infrapy. This document is divided into three sections, the first being this introduction. Section two defines eight new, infrasonic data processing-specific database tables. Both internal (ORACLE) and external formats for the attributes are defined, along with a short description of each attribute. Section three of the document shows the relationships between the different tables by using entity-relationship diagrams.

  3. Development of vendor evaluation criteria and post-implementation considerations for MSFC center-wide executive information system

    NASA Technical Reports Server (NTRS)

    Moynihan, Gary P.

    1992-01-01

    In June 1991, the MITRE Corporation submitted a series of recommendations as part of a Marshall Space Flight Center (MSFC) Management Information System Requirements Study, initiated by the Information Systems Office (ISO). A major recommendation of the study was to develop an Executive Information System (EIS) for MSFC executives. ISO was directed, by center management, to proceed with the development of a Center-Wide Executive Information System. Existing EIS prototypes, developed by the Space Shuttle Projects Office and the Payload Projects Office, were reviewed. These existing MSFC prototypes were considered not to encompass the required functionality needed on a center-wide basis. A follow-up study by MITRE provided top-level system requirements. These were later incorporated into a final requirements specification document by Boeing Computer Support Services.

  4. The CMIP5 Model Documentation Questionnaire: Development of a Metadata Retrieval System for the METAFOR Common Information Model

    NASA Astrophysics Data System (ADS)

    Pascoe, Charlotte; Lawrence, Bryan; Moine, Marie-Pierre; Ford, Rupert; Devine, Gerry

    2010-05-01

    The EU METAFOR Project (http://metaforclimate.eu) has created a web-based model documentation questionnaire to collect metadata from the modelling groups that are running simulations in support of the Coupled Model Intercomparison Project - 5 (CMIP5). The CMIP5 model documentation questionnaire will retrieve information about the details of the models used, how the simulations were carried out, how the simulations conformed to the CMIP5 experiment requirements and details of the hardware used to perform the simulations. The metadata collected by the CMIP5 questionnaire will allow CMIP5 data to be compared in a scientifically meaningful way. This paper describes the life-cycle of the CMIP5 questionnaire development which starts with relatively unstructured input from domain specialists and ends with formal XML documents that comply with the METAFOR Common Information Model (CIM). Each development step is associated with a specific tool. (1) Mind maps are used to capture information requirements from domain experts and build a controlled vocabulary, (2) a python parser processes the XML files generated by the mind maps, (3) Django (python) is used to generate the dynamic structure and content of the web based questionnaire from processed xml and the METAFOR CIM, (4) Python parsers ensure that information entered into the CMIP5 questionnaire is output as CIM compliant xml, (5) CIM compliant output allows automatic information capture tools to harvest questionnaire content into databases such as the Earth System Grid (ESG) metadata catalogue. This paper will focus on how Django (python) and XML input files are used to generate the structure and content of the CMIP5 questionnaire. It will also address how the choice of development tools listed above provided a framework that enabled working scientists (who we would never ordinarily get to interact with UML and XML) to be part the iterative development process and ensure that the CMIP5 model documentation questionnaire reflects what scientists want to know about the models. Keywords: metadata, CMIP5, automatic information capture, tool development

  5. Battlefield Management System: Data Requirements to Support Passage of Company Level Tactical Information.

    DTIC Science & Technology

    1987-03-01

    intelligent way, assemble those documents and data in usable formats, examine the communications tapes available for this project, and to develop a sampling...Lifetime Learning Publications, Belmont. CA. 1982. Rowe. Neil C.. Artifcial Intelligence , Draft Copv, Class Notes for Winter Quarter. CS 33 10, \\aval...AT2 122 BATTLEFIELD MANAGEMENT SYSTEM DATA REQUIRENTS TO 1/2 SUPPORT PASSAGE OF COMPANY LEVEL TACTICAL INFORMATION (U) NVALE POSTGRADUATE SCHOOL

  6. Technical guide on documentation requirements for open market contract acquisitions of information resources

    NASA Technical Reports Server (NTRS)

    Shaw, Asa L., Jr.; Kivett, William R.; Taylor, James Y.

    1990-01-01

    A guide is presented to assist requestors in formulating and submitting the required Complete Package for Information Resources (IR) acquisitions. Advance discussions with cognizant procurement personnel are strongly recommended for complex IR requirements or for those requestors new to the acquisition process. Open Market means the requirement either is not available on GSA Schedule Contract or exceeds the $300,000 threshold and/or the quantity Maximum Order Limitation of the GSA Schedule Contract. Only open market contract acquisitions (i.e., in excess of the $25,000 small purchase threshold), are addressed.

  7. Human Systems Integration: Requirements and Functional Decomposition

    NASA Technical Reports Server (NTRS)

    Berson, Barry; Gershzohn, Gary; Boltz, Laura; Wolf, Russ; Schultz, Mike

    2005-01-01

    This deliverable was intended as an input to the Access 5 Policy and Simulation Integrated Product Teams. This document contains high-level pilot functionality for operations in the National Airspace System above FL430. Based on the derived pilot functions the associated pilot information and control requirements are given.

  8. 50 CFR 23.25 - What additional information is required on a non-Party CITES document?

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... IN ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Prohibitions, Exemptions, and Requirements § 23... export will not be detrimental to the survival of the species.(ii) The Management Authority is satisfied... purposes that are not detrimental to the survival of the species. ...

  9. 50 CFR 23.25 - What additional information is required on a non-Party CITES document?

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... IN ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Prohibitions, Exemptions, and Requirements § 23... export will not be detrimental to the survival of the species.(ii) The Management Authority is satisfied... purposes that are not detrimental to the survival of the species. ...

  10. 50 CFR 23.25 - What additional information is required on a non-Party CITES document?

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... IN ENDANGERED SPECIES OF WILD FAUNA AND FLORA (CITES) Prohibitions, Exemptions, and Requirements § 23... export will not be detrimental to the survival of the species.(ii) The Management Authority is satisfied... purposes that are not detrimental to the survival of the species. ...

  11. High School Graduation Minimum Competency Requirements. Final Technical Report.

    ERIC Educational Resources Information Center

    Austin Independent School District, TX. Office of Research and Evaluation.

    This technical report details the testing results and analyses supporting the evaluation findings related to the Austin (Texas) Independent School District (AISD) minimum competency graduation requirements. The graduation competency status of all AISD students in grades 8 to 12 are documented. The report provides additional information on the data…

  12. Air Force Institute of Technology, Civil Engineering School: Environmental Protection Course.

    ERIC Educational Resources Information Center

    Air Force Inst. of Tech., Wright-Patterson AFB, OH. School of Engineering.

    This document contains information assembled by the Civil Engineering School to meet the initial requirements of NEPA 1969 and Executive Orders which required the Air Force to implement an effective environmental protection program. This course presents the various aspects of Air Force environmental protection problems which military personnel…

  13. 10 CFR 2.704 - Discovery-required disclosures.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... at the NRC Web site, http://www.nrc.gov, and/or the NRC Public Document Room, a sufficient disclosure... based on the information then reasonably available to it. A party is not excused from making its... disclosures when required under paragraph (e) of this section. (c) Pretrial disclosures. (1) In addition to...

  14. 75 FR 25266 - Centers for Medicare & Medicaid Services; Agency Information Collection Activities: Submission...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-05-07

    ... (Recovery Act) amended section 1902(a)(73) of the Act to require that certain States utilize a process for... DEPARTMENT OF HEALTH AND HUMAN SERVICES [Document Identifier: CMS-10293] Centers for Medicare & Medicaid Services; Agency Information Collection Activities: Submission for OMB Review; Comment Request...

  15. 78 FR 51272 - Agency Information Collection Activities: Revision of an Approved Information Collection; Comment...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-20

    ... requirement for national banks and Federal savings associations titled, ``Company-Run Annual Stress Test...://www.occ.treas.gov/tools-forms/forms/bank-operations/stress-test-reporting.html ). SUPPLEMENTARY...: Title: Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions with...

  16. 78 FR 76548 - New Standards To Enhance Package Visibility

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-18

    ... electronic documentation including piece-level address or ZIP+4[supreg] Code information. Included in these new requirements is a per-piece price adjustment for mailpieces not complying with the IMpb standards... relies on the availability of piece-level information provided through the use of IMpb. [[Page 76549...

  17. 77 FR 55216 - Agency Information Collection Activities: Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-09-07

    ..., due to technical difficulties, the documents associated with the information collection request were not made available to the public until August 14, 2012. Because of the technical difficulties, CMS is... Social Security Act (SSA) requires Medicare health plans to provide enrollees with a written notice in...

  18. Space Geodesy Project Information and Configuration Management Procedure

    NASA Technical Reports Server (NTRS)

    Merkowitz, Stephen M.

    2016-01-01

    This plan defines the Space Geodesy Project (SGP) policies, procedures, and requirements for Information and Configuration Management (CM). This procedure describes a process that is intended to ensure that all proposed and approved technical and programmatic baselines and changes to the SGP hardware, software, support systems, and equipment are documented.

  19. 76 FR 64942 - Agency Information Collection Activities; Proposed Collection; Comment Request; General...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-10-19

    ... public comments, access the index listing of the contents of the docket, and to access those documents in..., mechanical, or other technological collection techniques or other forms of information technology, e.g..., and Indian tribal governments. Title: General Administrative Requirements for Assistance Programs. ICR...

  20. 75 FR 6185 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Rights in...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-02-08

    ...; Defense Federal Acquisition Regulation Supplement; Rights in Technical Data and Computer Software (OMB... 227.72, Rights in Computer Software and Computer Software Documentation, and related provisions and... rights in technical data and computer software. DoD needs this information to implement 10 U.S.C. 2320...

  1. 76 FR 9695 - Proposed Christmas Tree Promotion, Research, and Information Order; Extension of Comment Period...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-02-22

    ... DEPARTMENT OF AGRICULTURE Agricultural Marketing Service 7 CFR Part 1214 [Document No. AMS-FV-10... of Comment Period on Proposed Establishment of a Program AGENCY: Agricultural Marketing Service, USDA... for the new Christmas tree information collection requirements by the Office of Management and Budget...

  2. 26 CFR 1.1247-5 - Information and recordkeeping requirements.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... section 1247, a foreign investment company shall keep the records and comply with the information... maintain and preserve such permanent books of account, records, and other documents as are sufficient to... domestic corporation. Generally, if the books and records of the company are maintained in the manner...

  3. 75 FR 1060 - Agency Information Collection Activities: Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-01-08

    ... DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Medicare & Medicaid Services [Document Identifier: CMS-906] Agency Information Collection Activities: Proposed Collection; Comment Request AGENCY: Centers for Medicare & Medicaid Services, HHS. In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995,...

  4. 76 FR 27629 - Endangered and Threatened Wildlife and Plants; Listing of the Altamaha Spinymussel and...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-05-12

    .... Information for this analysis was gathered from the Small Business Administration, stakeholders, and the... designation, and the amended required determinations provided in this document. We will consider information... in threat outweighs the benefit of designation such that the designation of critical habitat is not...

  5. 75 FR 44058 - Office of Postsecondary Education; Overview Information; Promoting Postbaccalaureate...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-07-27

    ... one of the exceptions to the electronic submission requirement and submit, no later than two weeks... these exceptions. Further information regarding calculation of the date that is two weeks [[Page 44060... upload large documents to e-Application; and No later than two weeks before the application deadline date...

  6. Discharge documentation of patients discharged to subacute facilities: a three-year quality improvement process across an integrated health care system.

    PubMed

    Gandara, Esteban; Ungar, Jonathan; Lee, Jason; Chan-Macrae, Myrna; O'Malley, Terrence; Schnipper, Jeffrey L

    2010-06-01

    Effective communication among physicians during hospital discharge is critical to patient care. Partners Healthcare (Boston) has been engaged in a multi-year process to measure and improve the quality of documentation of all patients discharged from its five acute care hospitals to subacute facilities. Partners first engaged stakeholders to develop a consensus set of 12 required data elements for all discharges to subacute facilities. A measurement process was established and later refined. Quality improvement interventions were then initiated to address measured deficiencies and included education of physicians and nurses, improvements in information technology, creation of or improvements in discharge documentation templates, training of hospitalists to serve as role models, feedback to physicians and their service chiefs regarding reviewed cases, and case manager review of documentation before discharge. To measure improvement in quality as a result of these efforts, rates of simultaneous inclusion of all 12 applicable data elements ("defect-free rate") were analyzed over time. Some 3,101 discharge documentation packets of patients discharged to subacute facilities from January 1, 2006, through September 2008 were retrospectively studied. During the 11 monitored quarters, the defect-free rate increased from 65% to 96% (p < .001 for trend). The largest improvements were seen in documentation of preadmission medication lists, allergies, follow-up, and warfarin information. Institution of rigorous measurement, feedback, and multidisciplinary, multimodal quality improvement processes improved the inclusion of data elements in discharge documentation required for safe hospital discharge across a large integrated health care system.

  7. Informed consent for genetic research.

    PubMed

    Hamvas, Aaron; Madden, Katherine K; Nogee, Lawrence M; Trusgnich, Michelle A; Wegner, Daniel J; Heins, Hillary B; Cole, F Sessions

    2004-06-01

    Rapid technological advances in genetic research and public concern about genetic discrimination have led to anticipatory safeguards in the informed consent process in the absence of legal examples of proven discrimination. Despite federal and state regulations to restrict access to personal health information, including genetic information, institutional review boards have required the addition of language to informed consent documents that warns about the risks of discrimination with participation in genetic research. To determine the reasons that families refused consent for their infant's participation in a study evaluating a genetic cause of respiratory distress syndrome. Survey conducted between February 1, 2002, and March 31, 2003. Academic, tertiary free-standing children's hospital. A convenience sample of 465 families were approached for consent. The 135 families who refused consent were surveyed. Reasons for refusal. Of the nonconsenting families, 79% spontaneously and specifically identified institutionally required language in our consent form concerning the risk of denial of access to health insurance and employment as the primary reason for refusal; 97% indicated that their fears resulted directly from language in our consent form. Only 20% of families who refused consent cited inadequate time to consider the study. The institutionally required description of risk of genetic discrimination due solely to participation in genetic research was the primary reason for refusal to consent in this cohort. Information about federally and institutionally mandated protections for confidentiality of participants in genetic research should be included in the informed consent document to balance the description of hypothetical risks and more accurately inform subjects.

  8. A Feature-Reinforcement-Based Approach for Supporting Poly-Lingual Category Integration

    NASA Astrophysics Data System (ADS)

    Wei, Chih-Ping; Chen, Chao-Chi; Cheng, Tsang-Hsiang; Yang, Christopher C.

    Document-category integration (or category integration for short) is fundamental to many e-commerce applications, including information integration along supply chains and information aggregation by intermediaries. Because of the trend of globalization, the requirement for category integration has been extended from monolingual to poly-lingual settings. Poly-lingual category integration (PLCI) aims to integrate two document catalogs, each of which consists of documents written in a mix of languages. Several category integration techniques have been proposed in the literature, but these techniques focus only on monolingual category integration rather than PLCI. In this study, we propose a feature-reinforcement-based PLCI (namely, FR-PLCI) technique that takes into account the master documents of all languages when integrating source documents (in the source catalog) written in a specific language into the master catalog. Using the monolingual category integration (MnCI) technique as a performance benchmark, our empirical evaluation results show that our proposed FR-PLCI technique achieves better integration accuracy than MnCI does in both English and Chinese category integration tasks.

  9. NASA information resources management handbook

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This National Aeronautics and Space Administration (NASA) Handbook (NHB) implements recent changes to Federal laws and regulations involving the acquisition, management, and use of Federal Information Processing (FIP) resources. This document defines NASA's Information Resources Management (IRM) practices and procedures and is applicable to all NASA personnel. The dynamic nature of the IRM environment requires that the controlling management practices and procedures for an Agency at the leading edge of technology, such as NASA, must be periodically updated to reflect the changes in this environment. This revision has been undertaken to accommodate changes in the technology and the impact of new laws and regulations dealing with IRM. The contents of this document will be subject to a complete review annually to determine its continued applicability to the acquisition, management, and use of FIP resources by NASA. Updates to this document will be accomplished by page changes. This revision cancels NHB 2410.1D, dated April 1985.

  10. A survey of nursing documentation, terminologies and standards in European countries

    PubMed Central

    Thoroddsen, Asta; Ehrenberg, Anna; Sermeus, Walter; Saranto, Kaija

    2012-01-01

    A survey was carried out to describe the current state of art in the use of nursing documentation, terminologies, standards and education. Key informants in European countries were targeted by the Association for Common European Nursing Diagnoses, Interventions and Outcomes (ACENDIO). Replies were received from key informants in 20 European countries. Results show that the nursing process was most often used to structure nursing documentation. Many standardized nursing terminologies were used in Europe with NANDA, NIC, NOC and ICF most frequently used. In 70% of the countries minimum requirements were available for electronic health records (EHR), but nursing not addressed specifically. Standards in use for nursing terminologies and information systems were lacking. The results should be a major concern to the nursing community in Europe. As a European platform, ACENDIO can play a role in enhancing standardization activities, and should develop its role accordingly. PMID:24199130

  11. Clustering XML Documents Using Frequent Subtrees

    NASA Astrophysics Data System (ADS)

    Kutty, Sangeetha; Tran, Tien; Nayak, Richi; Li, Yuefeng

    This paper presents an experimental study conducted over the INEX 2008 Document Mining Challenge corpus using both the structure and the content of XML documents for clustering them. The concise common substructures known as the closed frequent subtrees are generated using the structural information of the XML documents. The closed frequent subtrees are then used to extract the constrained content from the documents. A matrix containing the term distribution of the documents in the dataset is developed using the extracted constrained content. The k-way clustering algorithm is applied to the matrix to obtain the required clusters. In spite of the large number of documents in the INEX 2008 Wikipedia dataset, the proposed frequent subtree-based clustering approach was successful in clustering the documents. This approach significantly reduces the dimensionality of the terms used for clustering without much loss in accuracy.

  12. The paper crisis: from hospitals to medical practices.

    PubMed

    Park, Gregory; Neaveill, Rodney S

    2009-01-01

    Hospitals, not unlike physician practices, are faced with an increasing burden of managing piles of hard copy documents including insurance forms, requests for information, and advance directives. Healthcare organizations are moving to transform paper-based forms and documents into digitized files in order to save time and money and to have those documents available at a moment's notice. The cost of these document management/imaging systems can be easily justified with the significant savings of resources realized from the implementation of these systems. This article illustrates the enormity of the "paper problem" in healthcare and outlines just a few of the required processes that could be improved with the use of automated document management/imaging systems.

  13. 17 CFR 240.14d-100 - Schedule TO. Tender offer statement under section 14(d)(1) or 13(e)(1) of the Securities Exchange...

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... text of disclosure requirements in the schedule or any document published, sent or given to security holders. Indicate clearly the coverage of the requirements without referring to the text of the items. F... holders. If pro forma financial information is required by this instruction, the historical financial...

  14. State Requirements for Teacher Evaluation Policies Promoted by Race to the Top. NCEE Evaluation Brief. NCEE 2014-4016

    ERIC Educational Resources Information Center

    Hallgren, Kristin; James-Burdumy, Susanne; Perez-Johnson, Irma

    2014-01-01

    This brief describes the extent to which states required teacher evaluation policies aligned with the Race to the Top (RTT) initiative as of spring 2012. Although teacher evaluation policies appear to be rapidly evolving, documenting policy requirements in the early years of RTT implementation can help inform policymakers about the pace of policy…

  15. RH-TRU Waste Inventory Characterization by AK and Proposed WIPP RH-TRU Waste Characterization Objectives

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Most, W. A.; Kehrman, R.; Gist, C.

    2002-02-26

    The U.S. Department of Energy (DOE)-Carlsbad Field Office (CBFO) has developed draft documentation to present the proposed Waste Isolation Pilot Plant (WIPP) remote-handled (RH-) transuranic (TRU) waste characterization program to its regulators, the U.S. Environmental Protection Agency and the New Mexico Environment Department. Compliance with Title 40, Code of Federal Regulations, Parts 191 and 194; the WIPP Land Withdrawal Act (PL 102-579); and the WIPP Hazardous Waste Facility Permit, as well as the Certificates of Compliance for the 72-B and 10-160B Casks, requires that specific waste parameter limits be imposed on DOE sites disposing of TRU waste at WIPP. Themore » DOE-CBFO must control the sites' compliance with the limits by specifying allowable characterization methods. As with the established WIPP contact handled TRU waste characterization program, the DOE-CBFO has proposed a Remote-Handled TRU Waste Acceptance Criteria (RH-WAC) document consolidating the requirements from various regulatory drivers and proposed allowable characterization methods. These criteria are consistent with the recommendation of a recent National Academy Sciences/National Research Council to develop an RH-TRU waste characterization approach that removes current self imposed requirements that lack a legal or safety basis. As proposed in the draft RH-WAC and other preliminary documents, the DOE-CBFO RH-TRU waste characterization program proposes the use of acceptable knowledge (AK) as the primary method for obtaining required characterization information. The use of AK involves applying knowledge of the waste in light of the materials or processes used to generate the waste. Documentation, records, or processes providing information about various attributes of a waste stream, such as chemical, physical, and radiological properties, may be used as AK and may be applied to individual waste containers either independently or in conjunction with radiography, visual examination, assay, and other sampling and analytical data. RH-TRU waste cannot be shipped to WIPP on the basis of AK alone if documentation demonstrating that all of the prescribed limits in the RH-WAC are met is not available, discrepancies exist among AK source documents describing the same waste stream and the most conservative assumptions regarding those documents indicates that a limit will not be met, or all required data are not available for a given waste stream.« less

  16. 20 CFR 627.455 - Reports required.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... outlays on an accrual basis. If the recipient's accounting records are not normally kept on the accrual basis, the recipient shall develop such accrual information through an analysis of the documentation on...

  17. Reaching for the Stars, Goals for the Library Profession

    ERIC Educational Resources Information Center

    Bloomfield, Masse

    1971-01-01

    Space colonization will require the microforming of all of man's worded knowledge which will take leadership and dedication for the library profession information service or documentation. (2 references) (AB)

  18. 5 CFR 2100.4 - Requirements for identification.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... must provide their full name and as much information as possible in order that a proper search for..., military or annuitant identification card, or any official document as acceptable identification validation...

  19. 77 FR 60132 - Agency Information Collection Activities; Crew Member's Declaration

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-10-02

    ... requirements, supplemental immigration documentation, agricultural quarantine matters, and the importation of... is accessible at http://forms.cbp.gov/pdf/CBP_Form_5129.pdf . Current Actions: This submission is...

  20. Promoting North-South partnership in space data use and applications: Case study - East African countries space programs/projects new- concepts in document management

    NASA Astrophysics Data System (ADS)

    Mlimandago, S.

    This research paper have gone out with very simple and easy (several) new concepts in document management for space projects and programs which can be applied anywhere both in the developing and developed countries. These several new concepts are and have been applied in Tanzania, Kenya and Uganda and found out to bear very good results using simple procedures. The intergral project based its documentation management approach from the outset on electronic document sharing and archiving. The main objective of having new concepts was to provide a faster and wider availability of the most current space information to all parties rather than creating a paperless office. Implementation of the new concepts approach required the capturing of documents in an appropriate and simple electronic format at source establishing new procedures for project wide information sharing and the deployment of a new generation of simple procedure - WEB - based tools. Key success factors were the early adoption of Internet technologies and simple procedures for improved information flow new concepts which can be applied anywhere both in the developed and the developing countries.

  1. Mars Transportation Environment Definition Document

    NASA Technical Reports Server (NTRS)

    Alexander, M. (Editor)

    2001-01-01

    This document provides a compilation of environments knowledge about the planet Mars. Information is divided into three catagories: (1) interplanetary space environments (environments required by the technical community to travel to and from Mars); (2) atmospheric environments (environments needed to aerocapture, aerobrake, or use aeroassist for precision trajectories down to the surface); and (3) surface environments (environments needed to have robots or explorers survive and work on the surface).

  2. 30 CFR 285.632 - What documents must I submit before I may construct and install facilities under my approved COP?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... construct and install facilities under my approved COP? 285.632 Section 285.632 Mineral Resources MINERALS... FACILITIES ON THE OUTER CONTINENTAL SHELF Plans and Information Requirements Activities Under An Approved Cop... COP? (a) You must submit to MMS the documents listed in the following table: ER29AP09.124 (b) You must...

  3. Air Force Technical Objective Document FY 87

    DTIC Science & Technology

    1985-12-01

    Air Force Systems Command Edwards Air Force Base. Cal ifornia 93523-5000 NOTICES THIS DOCUMENT IS FOR INFORMATION AND GUIDANCE ONL Y This...acquisition of Air Foree weapon systems . Each Air Foree laboratory annually formulates Q Research and Technology (R& T) Pion in response to available...guidance based on USAF requirements, the identification of scientific and technological opportunities, and the needs of present and projected systems

  4. Spatial patterns of land cover in the United States: a technical document supporting the Forest Service 2010 RPA Assessment

    Treesearch

    Kurt H. Riitters

    2011-01-01

    Land cover patterns inventoried from a national land cover map provide information about the landscape context and fragmentation of the Nation’s forests, grasslands, and shrublands. This inventory is required to quantify, map, and evaluate the capacities of landscapes to provide ecological goods and services sustainably. This report documents the procedures to...

  5. Template protocol for clinical trials investigating vaccines--focus on safety elements.

    PubMed

    Bonhoeffer, Jan; Imoukhuede, Egeruan B; Aldrovandi, Grace; Bachtiar, Novilia S; Chan, Eng-Soon; Chang, Soju; Chen, Robert T; Fernandopulle, Rohini; Goldenthal, Karen L; Heffelfinger, James D; Hossain, Shah; Jevaji, Indira; Khamesipour, Ali; Kochhar, Sonali; Makhene, Mamodikoe; Malkin, Elissa; Nalin, David; Prevots, Rebecca; Ramasamy, Ranjan; Sellers, Sarah; Vekemans, Johan; Walker, Kenneth B; Wilson, Pam; Wong, Virginia; Zaman, Khalequz; Heininger, Ulrich

    2013-11-12

    This document is intended as a guide to the protocol development for trials of prophylactic vaccines. The template may serve phases I-IV clinical trials protocol development to include safety relevant information as required by the regulatory authorities and as deemed useful by the investigators. This document may also be helpful for future site strengthening efforts. Copyright © 2013 Elsevier Ltd. All rights reserved.

  6. Using Process Redesign and Information Technology to Improve Procurement

    DTIC Science & Technology

    1994-04-01

    contrac- tor. Many large-volume contractors have automated order processing tied to ac- counting, manufacturing, and shipping subsystems. Currently...the contractor must receive the mailed order, analyze it, extract pertinent information, and en- ter that information into the automated order ... processing system. Almost all orders for small purchases are unilateral documents that do not require acceptance or acknowledgment by the contractor. For

  7. 78 FR 65334 - Agency Information Collection Activities; Submission for Office of Management and Budget Review...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-10-31

    ... information, including certain labeling information, to FDA for approval to market a product in interstate... and in a form that FDA can process, review, and archive. This requirement is in addition to the....12(b) in table 1 of this document. In July 1997, FDA revised Form FDA 356h ``Application to Market a...

  8. 17 CFR 240.15g-100 - Schedule 15G-Information to be included in the document distributed pursuant to 17 CFR 240.15g-2.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... page] Important Information on Penny Stocks The U.S. Securities and Exchange Commission (SEC) requires... 17 Commodity and Securities Exchanges 3 2010-04-01 2010-04-01 false Schedule 15G-Information to be... Commodity and Securities Exchanges SECURITIES AND EXCHANGE COMMISSION (CONTINUED) GENERAL RULES AND...

  9. Approval of information collection requirements for the joint interim rules for health insurance portability for group health plans, and the individual market health insurance reform: portability from group to individual coverage; federal rules for access in the individual market; state alternative mechanisms to federal rules--IRS, DOL, HCFA. Interim rules with request for comments; approval of information collection requirements.

    PubMed

    1997-07-02

    On April 8, 1997, the Department of the Treasury, the Department of Labor, and the Department of Health and Human Services (Departments) published joint interim rules governing the access, portability and renewability requirements for group health plans and issuers offering group health insurance coverage in connection with a group health plan. The rules implemented changes made to certain provisions of the Internal Revenue Code of 1986 (Code), the Employee Retirement Income Security Act of 1974 (ERISA), and the Public Health Service Act (PHS Act) enacted as part of the Health Insurance Portability and Accountability Act of 1996 (HIPAA). In the April 8 publication, the Departments submitted the group market information collection requirements, for, among other things, establishing creditable coverage, notice of special enrollment rights, and notice of pre-existing condition exclusion periods, to be Office of Management and Budget (OMB) for emergency review under the Paperwork Reduction Act of 1995 (PRA 95). In addition, on April 8, 1997 the Department of Health and Human Services submitted the HIPAA individual market information collection requirements to OMB for emergency review under the PRA 1995. This document amends the April 8 Federal Register documents to properly display the OMB control numbers.

  10. Evaluation Methodologies for Information Management Systems; Building Digital Tobacco Industry Document Libraries at the University of California, San Francisco Library/Center for Knowledge Management; Experiments with the IFLA Functional Requirements for Bibliographic Records (FRBR); Coming to Term: Designing the Texas Email Repository Model.

    ERIC Educational Resources Information Center

    Morse, Emile L.; Schmidt, Heidi; Butter, Karen; Rider, Cynthia; Hickey, Thomas B.; O'Neill, Edward T.; Toves, Jenny; Green, Marlan; Soy, Sue; Gunn, Stan; Galloway, Patricia

    2002-01-01

    Includes four articles that discuss evaluation methods for information management systems under the Defense Advanced Research Projects Agency; building digital libraries at the University of California San Francisco's Tobacco Control Archives; IFLA's Functional Requirements for Bibliographic Records; and designing the Texas email repository model…

  11. Analysis of Data in Accordance with Space Flight Mission Environmental Requirements

    NASA Technical Reports Server (NTRS)

    Shei, Monica

    2011-01-01

    The Environmental Assurance Program sets forth standards to ensure that all flight hardware is compatible with the environments that will be encountered during a spacecraft mission. It outlines the design, test and analysis, and risk control standards for the mission and certifies that it will survive in any external or self-induced environments that the spacecraft may experience. The Environmental Requirements Document (ERD) is the most important document in the Environmental Assurance Program, providing the design and test requirements for the project's flight system, subsystems, assemblies, and instruments. This summer's project was to assist Environmental Requirements Engineers (ERE's) in completing the Environmental Assurance Program Summary Report for both the Juno Project and Mars Science Laboratory (MSL) Project. The Summary Report is a document summarizing the environmental tests and analyses of each spacecraft at both the assembly and system level. It compiles a source of all relevant information such as waivers and Problem/Failure Reports (PFRs) into a single report for easy reference of how well the spacecraft met the requirements of the project.

  12. Power Sector Variability

    EPA Pesticide Factsheets

    This Technical Support Document (TSD) provides information in support of section IV.F, “Emission Reduction Requirements Including Variability”, in the preamble to the proposed Transport Rule (now known as the Cross-State Air Pollution Rule).

  13. 50 CFR 300.172 - Vessel list.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ..., phone number where the owner can be reached, the USCG documentation number (or state registration number... phone number. On the date that NMFS receives a request that includes all the required information, NMFS...

  14. 77 FR 4559 - Information Collection Being Reviewed by the Federal Communications Commission

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-01-30

    ... the Commission's Rules to Deregulate the Equipment Authorization Requirements for Digital Devices. (a... authorizing equipment for marketing. (d) Finally, testing and documentation of compliance are needed to...

  15. 50 CFR 300.172 - Vessel list.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ..., phone number where the owner can be reached, the USCG documentation number (or state registration number... phone number. On the date that NMFS receives a request that includes all the required information, NMFS...

  16. 50 CFR 300.172 - Vessel list.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ..., phone number where the owner can be reached, the USCG documentation number (or state registration number... phone number. On the date that NMFS receives a request that includes all the required information, NMFS...

  17. 50 CFR 300.172 - Vessel list.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ..., phone number where the owner can be reached, the USCG documentation number (or state registration number... phone number. On the date that NMFS receives a request that includes all the required information, NMFS...

  18. 50 CFR 300.172 - Vessel list.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ..., phone number where the owner can be reached, the USCG documentation number (or state registration number... phone number. On the date that NMFS receives a request that includes all the required information, NMFS...

  19. Automatic editing of manuals

    NASA Technical Reports Server (NTRS)

    Rich, R. P.

    1970-01-01

    The documentation problem is discussed that arises in getting all the many items included in a computer program prepared in a timely fashion and keeping them all correct and mutually consistent during the life of the program. The proposed approach to the problem is to collect all the necessary information into a single document, which is maintained with computer assistance during the life of the program and from which the required subdocuments can be extracted as desired. Implementation of this approach requires a package of programs for computer editorial assistance and is facilitated by certain programming practices that are discussed.

  20. Semantic Metadata for Heterogeneous Spatial Planning Documents

    NASA Astrophysics Data System (ADS)

    Iwaniak, A.; Kaczmarek, I.; Łukowicz, J.; Strzelecki, M.; Coetzee, S.; Paluszyński, W.

    2016-09-01

    Spatial planning documents contain information about the principles and rights of land use in different zones of a local authority. They are the basis for administrative decision making in support of sustainable development. In Poland these documents are published on the Web according to a prescribed non-extendable XML schema, designed for optimum presentation to humans in HTML web pages. There is no document standard, and limited functionality exists for adding references to external resources. The text in these documents is discoverable and searchable by general-purpose web search engines, but the semantics of the content cannot be discovered or queried. The spatial information in these documents is geographically referenced but not machine-readable. Major manual efforts are required to integrate such heterogeneous spatial planning documents from various local authorities for analysis, scenario planning and decision support. This article presents results of an implementation using machine-readable semantic metadata to identify relationships among regulations in the text, spatial objects in the drawings and links to external resources. A spatial planning ontology was used to annotate different sections of spatial planning documents with semantic metadata in the Resource Description Framework in Attributes (RDFa). The semantic interpretation of the content, links between document elements and links to external resources were embedded in XHTML pages. An example and use case from the spatial planning domain in Poland is presented to evaluate its efficiency and applicability. The solution enables the automated integration of spatial planning documents from multiple local authorities to assist decision makers with understanding and interpreting spatial planning information. The approach is equally applicable to legal documents from other countries and domains, such as cultural heritage and environmental management.

Top