Abstract: Access is temporarily allowed to selected enterprise resources. A request to carry out an action is received from a private device. The private device is associated with an enterprise device, which has one or more enterprise policies in place. One or more steps for carrying out the requested action are defined, and it is determined that at least one policy from the enterprise policies is required for at least one of the steps. It is also determined that the at least one policy is in place on the private device. The private device is then allowed to carry out the requested action according to the at least one policy.

Abstract: Access is temporarily allowed to selected enterprise resources. A request to carry out an action is received from a private device. The private device is associated with an enterprise device, which has one or more enterprise policies in place. One or more steps for carrying out the requested action are defined, and it is determined that at least one policy from the enterprise policies is required for at least one of the steps. It is also determined that the at least one policy is in place on the private device. The private device is then allowed to carry out the requested action according to the at least one policy.

Abstract: Access is temporarily allowed to selected enterprise resources. A request to carry out an action is received from a private device. The private device is associated with an enterprise device, which has one or more enterprise policies in place. One or more steps for carrying out the requested action are defined, and it is determined that at least one policy from the enterprise policies is required for at least one of the steps. It is also determined that the at least one policy is in place on the private device. The private device is then allowed to carry out the requested action according to the at least one policy.

Abstract: Access is temporarily allowed to selected enterprise resources. A request to carry out an action is received from a private device. The private device is associated with an enterprise device, which has one or more enterprise policies in place. One or more steps for carrying out the requested action are defined, and it is determined that at least one policy from the enterprise policies is required for at least one of the steps. It is also determined that the at least one policy is in place on the private device. The private device is then allowed to carry out the requested action according to the at least one policy.

Abstract: Approaches for generating an alert in an absence of a radio-frequency identification (RFID) tag in proximity to a mobile device are provided herein. RFID tags are detected in proximity to the first mobile device, which has a RFID receiver. The alert is generated in response to alert conditions, including a determination that a RFID tag identifier stored in a first profile list is not among detected RFID tags and that an RFID tag stored in the first profile list is not in proximity to a second device. The alert is transmitted to the second mobile device, wherein the alert adds, responsive to the stored RFID tag not being among the detected RFID tags at the first device, the stored RFID tag to a second profile list associated with the second mobile device for storing RFID tag identifiers, wherein the second profile list is separate from the first profile list.

Abstract: A method for generating an alert on a mobile device in an absence of a radio-frequency identification (RFID) tag in proximity to the mobile device is provided herein. The method comprises defining an event. A profile list for storing RFID tag identifiers is related to the event. The method also comprises sharing the event data together with the profile list using a social media network, storing all received RFID tag identifiers at a time within the duration of the event after an event start time in the profile list if the profile list was empty before the event start time, and generating the alert under alert conditions. The alert conditions comprise a determination that the profile list was not empty before the event start time, and that one RFID tag identifier stored in the profile list is not among the received RFID tag identifiers during the event duration after the event time.

Abstract: Approaches for generating an alert in an absence of a radio-frequency identification (RFID) tag in proximity to a mobile device are provided herein. RFID tags are detected in proximity to the first mobile device, which has a RFID receiver. The alert is generated in response to alert conditions, including a determination that a RFID tag identifier stored in a first profile list is not among detected RFID tags and that an RFID tag stored in the first profile list is not in proximity to a second device. The alert is transmitted to the second mobile device, wherein the alert adds, responsive to the stored RFID tag not being among the detected RFID tags at the first device, the stored RFID tag to a second profile list associated with the second mobile device for storing RFID tag identifiers, wherein the second profile list is separate from the first profile list.

Abstract: Methods, computer program products, and systems are presented. The methods, computer program products, and systems can include, for instance: detecting, by machine logic, an event in a patient environment, wherein the event includes a body part of a patient moving to a location within a threshold distance of a point of interest, the point of interest being a location in the patient environment which if subject to contact by the body part poses risk to the patient; determining, by machine logic, one or more action to perform to control movement of the body part in response to the detecting the event in the patient environment; performing the one or more action to control movement of the body part in response to the detecting the event in the patient environment.

Abstract: A method for generating an alert on a mobile device in an absence of a radio-frequency identification (RFID) tag in proximity to the mobile device is provided herein. The method comprises defining an event. A profile list for storing RFID tag identifiers is related to the event. The method also comprises sharing the event data together with the profile list using a social media network, storing all received RFID tag identifiers at a time within the duration of the event after an event start time in the profile list if the profile list was empty before the event start time, and generating the alert under alert conditions. The alert conditions comprise a determination that the profile list was not empty before the event start time, and that one RFID tag identifier stored in the profile list is not among the received RFID tag identifiers during the event duration after the event time.