Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

View Transaction

View Transaction Information

Id: 43

Keyword: ITI-1

Name: Maintain Time

Description: NTP transactions used to maintain time synchronization.

TF Reference:

Status: Final Text

Id
Keyword
Name
Description
Action
47 CT Consistent Time Consistent Time Profile defines mechanisms to synchronize the time base between multiple actors and computers. Various infrastructure, security, and acquisition profiles require use of a consistent time base on multiple computers. The Consistent Time Profile provides median synchronization error of less than 1 second. Configuration options can provide better synchronization. The Consistent Time profile specifies the use of the Network Time Protocol (NTP) defined in RFC 1305.
48 ATNA Audit Trail and Node Authentication The ITI Audit Trail and Node Authentication (ATNA) Profile establishes the characteristics of a Basic Secure Node: It describes the security environment (user identification, authentication, authorization, access control, etc.) assumed for the node so that security reviewers may decide whether this matches their environments. It defines basic security requirements for the communications of the node using TLS or equivalent functionality. It defines basic auditing requirements for the node. The profile also establishes the characteristics of the communication of audit messages between the Basic Secure Nodes and Audit Repository nodes that collect audit information.
84 PIV2009 DEPRECATED: 2009 Point-of-Care Infusion Verification This profile entry represents the structure of actors and options in the PIV profile as published in 2009 and tested at NA2010. The documentation was updated in 2010, and the new profile entry, PIV, represents the updated structure.
137 T16 HITSP T16: Consistent Time US HITSP: T16: Consistent Time. The Consistent Time Transaction provides a mechanism to ensure that all of the entities that are communicating within the network have synchronized system clocks.
209 SMD Secure Message Delivery ATS 5822:2010 E-health secure message delivery
243 epSOS Security epSOS Security This profile is for handling the security aspects of epSOS
315 SEDI Secure Exchange of Dental Information The Secure Exchange of Dental Images (SEDI) Content Profile provides DICOM SOP Instances and image related documents using a reliable web based messaging service. It also allows for the option to support email transport of these imaging documents. SEDI permits direct imaging document interchange between an Imaging Document Source and other healthcare IT imaging document-capable systems.
376 CH:CT Consistent Time Swiss Extension
Id
Keyword
Name
Description
Action
10SNSecure NodeA system unit that validates the identity of any user and of any other node, and determines whether or not access to the system for this user and information exchange with the other node is allowed. Maintains the correct time.
11TSTime ServerA system unit that knows, maintains and distributes the correct time in the enterprise.
28TIME_CLIENTTime ClientEstablishes time synchronization with one or more Time Servers using the NTP protocol and either the NTP or SNTP algorithms. Maintains the local computer system clock synchronization with UTC based on synchronization with the Time Servers.
86SASecure ApplicationThe difference between the Secure Node and the Secure Application is the extent to which the underlying operating system and other environment are secured. A Secure Node includes all aspects of user authentication, file system protections, and operating environment security. The Secure Application is a product that does not include the operating environment. The Secure Application provides security features only for the application features. See section 9.7 for the relationships among a Secure Node, Secure Application, and other actors.
117IOPInfusion Order ProgrammerThe Infusion Order Programmer (IOP) actor sends the information comprising an order to the Infusion Order Consumer (IOC). The mechanism by which the IOP obtains the order information is outside the scope of this profile.
118IOCInfusion Order ConsumerThe Infusion Order Consumer (IOC) actor receives the order information from the IOP actor and in turn programs the pump. The mechanism by which the IOC programs the pump with the received information is outside the scope of this profile.
175SMD_SSMD SenderSecure Message Delivery Sender
176SMD_RSMD ReceiverSecure Message Delivery Receiver
177SMD_SISMD Sender IntermediarySecure Message Delivery Sender Intermediary
178SMD_RISMD Receiver IntermediarySecure Message Delivery Receiver Intermediary
1228DENTAL_DOC_SOURCEDental Document Sourcesends DICOM SOP Instances and image reports and associated documents.
1229DENTAL_DOC_RECIPIENTDental Document Recipientreceives DICOM SOP Instances and image reports and associated documents.
Assertion Id
Description
ITI1-1 The Time Server shall support NTP define in Network Time Protocol Version 3. RFC1305.
ITI1-10 The Time Client may also support for automated discovering of the Time Server address.
ITI1-11 Implementations must support a time synchronization accuracy with a median error of less than one second.
ITI1-2 The Time Server shall support SNTP define in Simple Network Time Protocol RFC4330.
ITI1-3 The Time Server may support Secure NTP.
ITI1-4 The Time Client shall support at least SNTP (RFC4330) or NTP v3 (RFC1305).
ITI1-5 The Time Client may support Secure NTP.
ITI1-6 The Time Client grouped with a Time Server shall support NTP and NOT implement SNTP.
ITI1-7 The "High accuracy" Time Client shall support NTP and NOT implement SNTP.
ITI1-8 The Time Client shall at least support a manual configuration of Time Server IP address.
ITI1-9 The Time Client may also support for automated retreiving of the Time Server address from DHCP.

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top