IT-tillämpningar

Kommittébeteckning: SIS/TK 189 (Innemiljö och energianvändning i byggnader)
Källa: CEN
Svarsdatum: den 8 mar 2020
Se merSe mindre
 

The purpose of ISO 16484-5:2017 is to define data communication services and protocols for computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.

Kommittébeteckning: SIS/TK 334 (Hälso- och sjukvårdsinformatik)
Källa: CEN
Svarsdatum: den 16 mar 2020
Se merSe mindre
 

The scope of this project is to define a general object-oriented information model that may be used to structure information and identify services used in point-of-care (POC) medical device communications. The scope is primarily focused on acute care medical devices and the communication of patient vital signs information.

Kommittébeteckning: SIS/TK 269 (Information för byggande och förvaltning)
Källa: CEN
Svarsdatum: den 7 apr 2020
Se merSe mindre
 

This document provides a methodology and process to create data templates for construction products that are covered by harmonised technical specifications (harmonised product standards (hEN) and European Assessment Documents (EAD)), under Regulation (EU) No 305/2011 - the Construction Products Regulation (CPR).

Kommittébeteckning: SIS/TK 448 (Teknik och stödsystem för personlig identifiering)
Källa: ISO
Svarsdatum: den 20 apr 2020
Se merSe mindre
 

The purpose of this document is to standardize interface specifications for the implementation of a driving licence in association with a mobile device (mDL). This document standardizes the interface between the mDL and mDL Reader, and the interface between the mDL Reader and the issuing authority infrastructure. The standard also allow parties other than the issuing authority (e.g. other issuing authorities, or mDL Verifiers in other countries) to:

a) use a machine to obtain the mDL data,

b) tie the mDL to the mDL Holder,

c) authenticate the origin of the mDL data, and

d) verify the integrity of the mDL data.

The following items are out of scope for this document:

a) how user consent to share data is obtained

b) requirements on storage of mDL data and mdL private keys