This document defines the HBES Information Model and a corresponding data exchange format for the Home and Building HBES Open Communication System.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Early Hearing Detection and Intervention (EHDI) programs exist world-wide to help identify children with hearing loss. Because newborn hearing loss is a neuro-developmental emergency, children with hearing loss need to be identified shortly after birth to help them achieve better communication outcomes. This implementation guide focuses on the transmission of the hearing screening data elements from the hearing screening device to a recipient of data, which may be an electronic health record (EHR) or a Public Health Information System.
The Electronic Nutrition Care Process Record System (ENCPRS) Functional Profile is based on the Electronic Health Record System Functional Model R2 (EHRS-FM). The intent is to develop a standard list of functions and criteria needed for full integration of both the Nutrition Care Process (NCP) and the representative terms from the Nutrition Care Process Terminology (NCPT). The NCP serves as a systematic approach to providing high quality nutrition care. This standardization will encourage the acquisition of EHR systems by nutrition health providers and promote information interoperability between nutrition and food systems and other areas of healthcare. These requirements have been mapped into this functional profile and identify those portions of the HL7 EHR-S Functional Model that apply to patient care in the Nutrition Care Process. Further, these requirements identify functionality toward facilitating ease of use for those involved in patient care using the NCP, thus providing EHR vendors with conformance criteria that are specific to regulated tasks within the NCP in the HL7 International formats.
This project developed an implementation guide constraining CDA Release 2. The implementation guide supports electronic submission of HAI data to the National Healthcare Safety Network. CDC provided NHSN developers, vocabulary experts and CDA experts to support this project.
The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling interoperable implementations of the architecture and provides extension points to enable new communication mechanisms as they evolve.
The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies.
The Internet of Things (IoT) is predicted to become one of the most significant drivers of growth in various technology markets. Most current standardization activities are confined to very specific verticals and represent islands of disjointed and often redundant development. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.
This standard specifies how the MAC Service is supported by Virtual Bridged Local Area Networks, the principles of operation of those networks, and the operation of VLAN-aware Bridges, including management, protocols, and algorithms. Incorporates IEEE Std 802.1Q-2005, IEEE Std 802.1ad-2005, IEEE Std 802.1ak-2007, IEEE Std 802.1ag-2007, IEEE Std 802.1ah-2008, IEEE Std 802-1Q-2005/Cor-1-2008, IEEE Std 802.1ap-2008, IEEE Std 802.1Qaw-2009, IEEE Std 802.1Qay-2009, IEEE Std 802.1aj-2009, IEEE Std 802.1Qav-2009, IEEE Std Qau-2010, and IEEE Std Qat-2010. The PDF of this standard is available at no cost, compliments of the IEEE 802 group. http://grouper.ieee.org/groups/802/1/
This standard defines a protocol and procedures for the transport of timing over bridged and virtual bridged local area networks. It includes the transport of synchronized time, the selection of the timing source (i.e., best master), and the indication of the occurrence and magnitude of timing impairments (i.e., phase and frequency discontinuities). The PDF of this standard is available at the IEEEGET program. The "IEEE Get Program" grants public access to view and download individual PDFs of select standards at no charge. Visit http://standards.ieee.org/about/get/index.html for details.
This standard specifies formats and methods for floating-point arithmetic in computer systems: standard and extended functions with single, double, extended, and extendable precision, and recommends formats for data interchange. Exception conditions are defined and standard handling of these conditions is specified.
Master-Slave/Token-Passing (MS/TP) is a medium access control method for the RS-485 physical layer and is used primarily in building automation networks. This specification defines the frame format for transmission of IPv6 packets and the method of forming link-local and statelessly autoconfigured IPv6 addresses on MS/TP networks.