Esileht»Infoteenus

35 INFOTEHNOLOOGIA

Tagasi peagrupi juurde

Uued standardid


EVS-EN ISO 13606-2:2019
Hind 20,74 EUR
Identne ISO 13606-2:2019; EN ISO 13606-2:2019
Health informatics - Electronic health record communication - Part 2: Archetype interchange specification (ISO 13606-2:2019)
This document specifies a means for communicating part or all of the electronic health record (EHR) of one or more identified subjects of care between EHR systems, or between EHR systems and a centralised EHR data repository. It can also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components) that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system. This document will predominantly be used to support the direct care given to identifiable individuals, or to support population monitoring systems such as disease registries and public health surveillance. Uses of health records for other purposes such as teaching, clinical audit, administration and reporting, service management, research and epidemiology, which often require anonymization or aggregation of individual records, are not the focus of this standard series but such secondary uses might also find it useful. This document defines an Archetype Model to be used to represent Archetypes when communicated between repositories, and between archetype services. It defines an optional serialised representation, which may be used as an exchange format for communicating individual archetypes. Such communication might, for example, be between archetype libraries or between an archetype service and an EHR persistence or validation service.

EVS-EN ISO 13606-4:2019
Hind 15,40 EUR
Identne ISO 13606-4:2019; EN ISO 13606-4:2019
Health informatics - Electronic health record communication - Part 4: Security (ISO 13606-4:2019)
This document describes a methodology for specifying the privileges necessary to access EHR data. This methodology forms part of the overall EHR communications architecture defined in ISO 13606-1. This document seeks to address those requirements uniquely pertaining to EHR communications and to represent and communicate EHR-specific information that will inform an access decision. It also refers to general security requirements that apply to EHR communications and points at technical solutions and standards that specify details on services meeting these security needs. NOTE Security requirements for EHR systems not related to the communication of EHRs are outside the scope of this document.

EVS-EN ISO 13606-3:2019
Hind 23,62 EUR
Identne ISO 13606-3:2019; EN ISO 13606-3:2019
Health informatics - Electronic health record communication - Part 3: Reference archetypes and term lists (ISO 13606-3:2019)
This document specifies a means for communicating part or all of the electronic health record (EHR) of one or more identified subjects of care between EHR systems, or between EHR systems and a centralised EHR data repository. It can also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components), or personal health applications and devices, that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system. This document defines term lists that each specify the set of values for the particular attributes of the Reference Model defined in ISO 13606-1. It also defines normative and informative Reference Archetypes that enable frequently-occurring instances of EHR data to be represented within a consistent structure when communicated using this document.

EVS-EN ISO 13606-5:2019
Hind 10,19 EUR
Identne ISO 13606-5:2019; EN ISO 13606-5:2019
Health informatics - Electronic health record communication - Part 5: Interface specification (ISO 13606-5:2019)
This document specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This document is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this document but such secondary uses could also find the document useful. This document defines a set of interfaces to request and provide: — an EHR_EXTRACT for a given subject of care as defined in ISO 13606-1; — one or more ARCHETYPE(s) as defined in ISO 13606-2; — an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in ISO 13606-4. This document defines the set of interactions to request each of these artefacts, and to provide the data to the requesting party or to decline the request. An interface to query an EHR or populations of EHRs, for example for clinical audit or research, are beyond its scope, although provision is made for certain selection criteria to be specified when requesting an EHR_EXTRACT which might also serve for population queries. This document defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces. This document effectively defines the payload to be communicated at each interface. It does not specify the particular information that different transport protocols will additionally require, nor the security or authentication procedures that might be agreed between the communicating parties or required by different jurisdictions.

EVS-EN ISO 13606-1:2019
Hind 22,15 EUR
Identne ISO 13606-1:2019; EN ISO 13606-1:2019
Health informatics - Electronic health record communication - Part 1: Reference model (ISO 13606-1:2019)
This document specifies a means for communicating part or all of the electronic health record (EHR) of one or more identified subjects of care between EHR systems, or between EHR systems and a centralised EHR data repository. It can also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components), or personal health applications and devices, that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system. This document will predominantly be used to support the direct care given to identifiable individuals or self-care by individuals themselves, or to support population monitoring systems such as disease registries and public health surveillance. Uses of health records for other purposes such as teaching, clinical audit, administration and reporting, service management, research and epidemiology, which often require anonymization or aggregation of individual records, are not the focus of this document but such secondary uses might also find the document useful. This Part 1 of the multipart series is an Information Viewpoint specification as defined by the Open Distributed Processing - Reference model: Overview (ISO/IEC 10746-1). This document is not intended to specify the internal architecture or database design of EHR systems.

EVS-EN 16495:2019
Hind 19,05 EUR
Identne ISO/IEC 27002:2013; EN 16495:2019
Air Traffic Management - Information security for organisations supporting civil aviation operations
This document provides guidance based on EN ISO/IEC 27002:2017 applied to organisations supporting civil aviation, with a focus on air traffic management operations. This includes, but is not limited to, airspace users, airports and air navigation service providers. Not included are activities of the organisations that do not have any impact on the security of civil aviation operations like for example airport retail and service business and corporate real estate management. The basis of all guidance in this document is trust and cooperation between the parties involved in Air Traffic Management.

ISO/IEC 14496-5:2001/Amd 40:2019
Hind 14,24 EUR
Printing material and 3D graphics coding for browsers reference software
Amendment to ISO/IEC 14496-5:2001

ISO/IEC 29167-19:2019
Hind 158,38 EUR
Information technology -- Automatic identification and data capture techniques -- Part 19: Crypto suite RAMON security services for air interface communications
This document defines the Rabin-Montgomery (RAMON) crypto suite for the ISO/IEC 18000 series of air interfaces standards for radio frequency identification (RFID) devices. Its purpose is to provide a common crypto suite for security for RFID devices that can be referred to by ISO/IEC for air interface standards and application standards. This document specifies a crypto suite for Rabin-Montgomery (RAMON) for air interface for RFID systems. The crypto suite is defined in alignment with existing air interfaces. This document defines various authentication methods and methods of use for the cipher. A Tag and an Interrogator can support one, a subset, or all of the specified options, clearly stating what is supported.
Asendab ISO/IEC 29167-19:2016

ISO 11783-5:2019
Hind 122,79 EUR
Tractors and machinery for agriculture and forestry -- Serial control and communications data network -- Part 5: Network management
This document describes the management of source addresses (SAs) for control functions (CFs) of electronic control units (ECUs), the association of addresses with the functional identification of a device and the detection and reporting of network-related errors. It also specifies procedures for initialization of network-connected ECUs.
Asendab ISO 11783-5:2011

ISO 21812-1:2019
Hind 122,79 EUR
Graphic technology -- Print product metadata for PDF files -- Part 1: Architecture and core requirements for metadata
The document part metadata in a PDF file that conforms to this document can be used to communicate the intended appearance of print products and their components. Examples of intended use are: direct interpretation within a production process, creation of job tickets such as XJDF, or populating records in an MIS. This document builds on the DPart syntax as specified in ISO 16612-2 (PDF/VT) and ISO 32000-2 (PDF 2.0) which is designed for encoding metadata related to pages or groups of pages in PDF files. NOTE The document part metadata provided in this document applies to individual document parts, whereas XMP metadata typically applies to the scope of the entire document. XMP can apply to the scope of an individual page or part of a page but this usage is very uncommon. Thus, XMP is not applicable for the case where metadata is required for sets of pages such as multiple recipients or binding information. For example, XMP is used within PDF/X for file conformance identification and is also used for additional file level information such as author. This document defines standardized metadata to: - provide product intent specifications such as paper media selection and binding information; - identify the type of product that the content pages are intended to represent (e.g. a brochure, letter or postcard); - identify the intended recipient of each of the content pages for variable document printing applications. This document defines a base conformance level that includes the syntax of the metadata framework and the semantics of a core set of metadata.

ISO/IEC 23000-21:2019
Hind 140,58 EUR
Information technology -- Multimedia application format (MPEG-A) -- Part 21: Visual identity management application format
This document specifies the standard representation of the set of signalling and data used in the process of preserving privacy for storage sharing image/video.

ISO/IEC 21122-2:2019
Hind 140,58 EUR
Information technology -- JPEG XS low-latency lightweight image coding system -- Part 2: Profiles and buffer models
This document defines a limited number of subsets of the syntax specified in ISO/IEC 21122-1 and a buffer model to ensure interoperability between implementations in the presence of a latency constraint.

ISO/IEC 23008-3:2019/Amd 1:2019
Hind 140,58 EUR
Audio metadata enhancements
Amendment to ISO/IEC 23008-3:2019

ISO 9241-210:2019
Hind 122,79 EUR
Ergonomics of human-system interaction -- Part 210: Human-centred design for interactive systems
This document provides requirements and recommendations for human-centred design principles and activities throughout the life cycle of computer-based interactive systems. It is intended to be used by those managing design processes, and is concerned with ways in which both hardware and software components of interactive systems can enhance human?system interaction. NOTE Computer-based interactive systems vary in scale and complexity. Examples include off-the-shelf (shrink-wrap) software products, custom office systems, process control systems, automated banking systems, Web sites and applications, and consumer products such as vending machines, mobile phones and digital television. Throughout this document, such systems are generally referred to as products, systems or services although, for simplicity, sometimes only one term is used. This document provides an overview of human-centred design activities. It does not provide detailed coverage of the methods and techniques required for human-centred design, nor does it address health or safety aspects in detail. Although it addresses the planning and management of human-centred design, it does not address all aspects of project management. The information in this document is intended for use by those responsible for planning and managing projects that design and develop interactive systems. It therefore addresses technical human factors and ergonomics issues only to the extent necessary to allow such individuals to understand their relevance and importance in the design process as a whole. It also provides a framework for human factors and usability professionals involved in human-centred design. Detailed human factors/ergonomics, usability and accessibility issues are dealt with more fully in a number of standards including other parts of ISO 9241 (see Annex A) and ISO 6385, which sets out the broad principles of ergonomics. The requirements and recommendations in this document can benefit all parties involved in human-centred design and development. Annex B provides a checklist that can be used to support claims of conformance with this document.
Asendab ISO 9241-210:2010

IEC TS 62872-1:2019
Hind 284,72 EUR
Industrial-process measurement, control and automation - Part 1: System interface between industrial facilities and the smart grid
IEC 62872-1:2019(E) defines the interface, in terms of information flow, between industrial facilities and the “smart grid”. It identifies, profiles and extends where required, the standards needed to allow the exchange of the information needed to support the planning, management and control of electric energy flow between the industrial facility and the smart grid. The scope of this document specifically excludes the protocols needed for the direct control of energy resources within a facility where the control and ultimate liability for such control is delegated by the industrial facility to the external entity (e.g. distributed energy resource (DER) control by the electrical grid operator).
Asendab IEC/TS 62872:2015

IEC 63119-1:2019
Hind 62,28 EUR
Information exchange for electric vehicle charging roaming service - Part 1: General
IEC 63119-1:2019 establishes a basis for the other parts of IEC 63119, specifying the terms and definitions, general description of the system model, classification, information exchange and security mechanisms for roaming between EV charge service providers (CSP), charging station operators (CSOs) and clearing house platforms through roaming endpoints. It provides an overview and describes the general requirements of the EV roaming service system. IEC 63119 (all parts) is applicable to high-level communication involved in information exchange/interaction between different CSPs, as well as between a CSP and a CSO with or without a clearing house platform through the roaming endpoint. IEC 63119 (all parts) does not specify the information exchange, either between the charging station (CS) and the charging station operator (CSO), or between the EV and the CS.

CEN/TR 17370:2019
Hind 25,03 EUR
Public transport - Operating raw data and statistics exchange
2.1 Introduction The OpRa work scope is the definition of a minimum set of Public Transport raw data needed as PT quantitative analysis enabling factor. To obtain this considering all the several aspects involved in this complex domain, the work has been conducted through the following phases: 1) assessment; 2) use cases definition and classification; 3) indicators definition; 4) raw data identification. OpRa work does not go into the field of service quality measurement and reporting: service quality analysis will of course use data provided by OpRa, but quality definition remains a contractual level issue between a Public Transport Authority and a Public Transport Operator or an operator’s internal choice for a purely private service. OpRa mainly only reports unbiased actual data (i.e. measured or observed), described and aggregated in a shared and understandable way. The OpRa work documented in detail in this document is coherent with EU Directive 2010/40. In particular, it relates to the Article 4 of the Delegated Regulation EU 2017/1926, as regards the historic data. OpRa proposes to complement NeTEx (dedicated to the static scheduled information), for the historic data based on the underlying conceptual data reference model Transmodel EN 12896, similarly to the requirement of the Delegated Regulation EU 2017/1926 referring to the static scheduled information. (...)

CEN ISO/TS 19091:2019
Hind 31,07 EUR
Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections (ISO/TS 19091:2019)
This document defines the message, data structures, and data elements to support exchanges between the roadside equipment and vehicles to address applications to improve safety, mobility and environmental efficiency. In order to verify that the defined messages will satisfy these applications, a systems engineering process has been employed that traces use cases to requirements and requirements to messages and data concepts. This document consists of a single document that contains the base specification and a series of annexes. The base specification lists the derived information requirements (labelled informative) and references to other standards for message definitions where available. Annex A contains descriptions of the use cases addressed by this document. Annexes B and C contain traceability matrices that relate use cases to requirements and requirements to the message definitions (i.e. data frames and data elements). The next annexes list the base message requirements and application-oriented specific requirements (requirements traceability matrix) that map to the message and data concepts to be implemented. As such, an implementation consists of the base plus an additional group of extensions within this document. Details on information requirements, for other than SPaT, MAP, SSM, and SRM messages are provided in other International Standards. The focus of this document is to specify the details of the SPaT, MAP, SSM, and SRM supporting the use cases defined in this document. Adoption of these messages varies by region and their adoption can occur over a significant time period. This document covers the interface between roadside equipment and vehicles. Applications, their internal algorithms, and the logical distribution of application functionality over any specific system architecture are outside the scope of this document.

Asendatud või tühistatud standardid


EVS-EN 13606-3:2008
Identne EN 13606-3:2008
Health informatics - Electronic health record communication - Part 3: Reference archetypes and term lists
This Standard addresses the communication of part or all of electronic health records (EHR) of a single identified subject of care between EHR systems, or between EHR systems and a centralised EHR data repository. It may also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components) that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system. This Standard, Part 3 of the 13606 EHR Communications Standard Series, defines term lists that each specify the set of values that particular attributes of the Reference Model defined in Part 1 of this Series may take. It also defines informative Reference Archetypes that correspond to ENTRY-level compound data structures within the Reference Models of openEHR and HL7 Version 3, to enable those instances to be represented within a consistent structure when communicated using this standard.
Keel: Inglise

EVS-EN 13606-4:2007
Identne EN 13606-4:2007
Health informatics - Electronic health record communication - Part 4: Security
This part of this multipart standard on Electronic Health Record Communication describes a methodology for specifying the privileges necessary to access EHR data. This methodology forms part of the overall EHR communications architecture defined in Part 1 of this standard. This standard seeks to address those requirements uniquely pertaining to EHR communications and to represent and communicate EHR-specific information that will inform an access decision. It also refers to general security requirements that apply to EHR communications and points at technical solutions and standards that specify details on services meeting these security needs.
Keel: Inglise

EVS-EN 13606-2:2007
Identne EN 13606-2:2007
Health informatics - Electronic health record communication - Part 2: Archetypes interchange specification
This work item consists of the revision of the four part standard ENV 13606 to a full European standard (EN). This standard specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This standard is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person’s care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people’s records, are not the focus of this standard but such secondary uses could also find the standard useful.
Keel: Inglise

EVS-EN ISO 13606-5:2010
Identne ISO 13606-5:2010; EN ISO 13606-5:2010
Health Informatics - Electronic Health Record Communication - Part 5: Interface specification
This part of ISO 13606 specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This part of ISO 13606 is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this part of ISO 13606, but such secondary uses could also find this document useful.
Keel: Inglise

EVS-EN ISO 13606-1:2012
Identne ISO 13606-1:2008; EN ISO 13606-1:2012
Health informatics - Electronic health record communication - Part 1: Reference model (ISO 13606-1:2008)
This part of ISO 13606 specifies the communication of part or all of the electronic health record (EHR) of a single identified subject of care between EHR systems, or between EHR systems and a centralized EHR data repository. It may also be used for EHR communication between an EHR system or repository and clinical applications or middleware components (such as decision support components) that need to access or provide EHR data, or as the representation of EHR data within a distributed (federated) record system. This part of ISO 13606 will predominantly be used to support the direct care given to identifiable individuals, or to support population monitoring systems such as disease registries and public health surveillance. Uses of health records for other purposes such as teaching, clinical audit, administration and reporting, service management, research and epidemiology, which often require anonymization or aggregation of individual records, are not the focus of this part of ISO 13606 but such secondary uses might also find this document useful. This part of the multipart series, ISO 13606, is an information viewpoint specification as defined in ISO/IEC 10746-1[13]. This part of ISO 13606 is not intended to specify the internal architecture or database design of EHR systems.
Keel: Inglise

EVS-EN 16495:2014
Identne EN 16495:2014
Air Traffic Management - Information security for organisations supporting civil aviation operations
This European Standard defines guidelines and general principles for the implementation of an information security management system in organisations supporting civil aviation operations. Not included are activities of the organisations that do not have any impact on the security of civil aviation operations like for example airport retail and service business and corporate real estate management. For the purpose of this European Standard, Air Traffic management is seen as functional expression covering responsibilities of all partners of the air traffic value chain. This includes but is not limited to airspace users, airports and air navigation service providers. The basis of all requirements in this European Standard is trust and cooperation between the parties involved in Air Traffic Management.
Keel: Inglise
Asendatud EVS-EN 16495:2019

CEN ISO/TS 19091:2017
Identne ISO/TS 19091:2017; CEN ISO/TS 19091:2017
Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections (ISO/TS 19091:2017)
ISO/TS 19091:2017 defines the message, data structures, and data elements to support exchanges between the roadside equipment and vehicles to address applications to improve safety, mobility and environmental efficiency. In order to verify that the defined messages will satisfy these applications, a systems engineering process has been employed that traces use cases to requirements and requirements to messages and data concepts. This document consists of a single document that contains the base specification and a series of annexes. The base specification lists the derived information requirements (labelled informative) and references to other standards for message definitions where available. Annex A contains descriptions of the use cases addressed by this document. Annex B and Annex C contain traceability matrices that relate use cases to requirements and requirements to the message definitions (i.e. data frames and data elements). The next annexes list the base message requirements and application-oriented specific requirements (requirements traceability matrix) that map to the message and data concepts to be implemented. As such, an implementation consists of the base plus an additional group of extensions within this document. Details on information requirements, for other than SPaT, MAP, SSM, and SRM messages are provided in other International Standards. The focus of this document is to specify the details of the SPaT, MAP, SSM, and SRM supporting the use cases defined in this document. Adoption of these messages varies by region and their adoption may occur over a significant time period. ISO/TS 19091:2017 covers the interface between roadside equipment and vehicles. Applications, their internal algorithms, and the logical distribution of application functionality over any specific system architecture are outside the scope of this document.
Keel: Inglise

Kavandite arvamusküsitlus


prEN 17412
Identne prEN 17412
Tähtaeg 16.09.2019
Building Information Modelling - Level of Information Need - Concepts and principles
This document specifies concepts and principles to establish a methodology for specifying level of information need and information deliveries in a consistent way when using Building Information Modelling (BIM). This document specifies the characteristics of different levels used for defining the detail and extent of information required to be exchanged and delivered throughout the life cycle of built assets. It gives guidelines for principles required to specify information needs. The concepts and principles in this document can be applied for a general information exchange and whilst in progress, for a generally agreed way of information exchange between parties in a collaborative work process, as well as for a contractually specified information delivery. The level of information need provides methods for describing information to be exchanged according to exchange information requirements. The exchange information requirements specify the wanted information exchange. The result of this process is an information delivery. The concepts and principles contained in this document are applicable to all those involved in the asset life cycle. This includes, but is not limited to, the asset owner/operator, the project client, the asset manager, the design team, the construction supply chain, the equipment manufacturer, the system specialist, the regulator, and the end-user.
Keel: Inglise

prEN ISO 19650-5
Identne ISO/DIS 19650-5; prEN ISO 19650-5
Tähtaeg 16.09.2019
Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management using building information modelling - Part 5: security-minded approach to information management (ISO/DIS 19650-5:2019)
This proposed ISO standard will specify requirements for the security-minded management of projects utilizing digital technologies, associated control systems, for example building management systems, digital built environments and smart asset management. It outlines security threats to information during asset:. • conception, strategy and briefing; • procurement; • design; • construction; • commissioning and handover; • operation and maintenance; • performance management; • change of use/modification; and • disposal/demolition. It will explain the need for, and application of,trustworthiness and security controls throughout a built asset’s lifecycle (including the full project lifecycle) to deliver a holistic approach encompassing: • safety; • authenticity; • availability (including reliability); • confidentiality; • integrity; • possession; • resilience; and • utility. The standard will address the steps required to create and cultivate an appropriate safety and security mindset and culture across many partners, including the need to monitor and audit compliance. It will provide a foundation to support the evolution of future digital built environments, for example intelligent buildings, infrastructure and smart cities, but does not detail technical architectures for their implementation. While the processes contained within it may be applicable to other data management systems, this PAS does not specifically address issues relating to these systems.
Keel: Inglise

prEN ISO/IEC 27000
Tähtaeg 16.09.2019
Information technology - Security techniques - Information security management systems - Overview and vocabulary (ISO/IEC 27000:2018)
EN ISO/IEC 27000 provides the overview of information security management systems (ISMS). It also provides terms and definitions commonly used in the ISMS family of standards.
Keel: Inglise