Abstract: Techniques for managing the registration of medical devices with servers and/or other computing systems in an efficient manner are provided. These techniques may include use of partial or delayed registration. When a medical device, such as an infusion pump, initially connects to a server, such as a health management system or an intermediary, the medical device may register with the server. For a period of time after completion of the registration, the medical device may not be required to re-register when a network connection is interrupted and reestablished. To reestablish communications, a secure connection may be established using a process by which the medical device proves its identity. The medical device may then resume normal network communication using the secure connection, without performing a full registration process. Full registration may be delayed until a period of time has expired.

Abstract: Techniques for managing encoded communications for medical devices in a clinical environment are provided. Different versions of signal coding libraries are generated for different devices in a communication path. A first signal coding library may be generated using a first signal definition that includes a set of fields. A second signal coding library may be generated using a second signal definition that includes a subset of the fields of the first signal definition, and excludes one or more of the fields of the first signal definition. A message encoded using the first signal coding library may not be completely decodable using the second signal coding library. By selectively deploying the signal coding libraries to different systems, devices, and components in a clinical environment, access to information in message fields can be effectively managed.

Abstract: Techniques for managing secure communication certificates for medical devices in a clinical environment are provided. A short-lived, limited-use token may be uniquely assigned to a medical device. The medical device can self-provision a secret key and corresponding public key based on a unique identifier in the token. The medical device generates a certificate signing request (“CSR”) that includes the public key, and sends the CSR and the token to a verification system that serves as an intermediary between medical devices and a certificate authority. The intermediary may only send the CSR to the certificate authority (“CA”) for a certificate if the intermediary is able to validate the token.