A method comprising: storing, at a mobile device management, MDM, server, location-to-device mapping data indicating mobile devices assigned to locations at a healthcare facility, wherein the location-to-device mapping data indicates that a first mobile device is assigned to a first location at the healthcare facility and that a second mobile device is assigned to a second location at the healthcare facility, and wherein the first location is distinct from the second location; receiving, at the MDM server, a message indicating receipt of user input that indicates a patient identifier and a particular location associated with a patient; in response to determining, based on the location-to-device mapping data, that the particular location corresponds to the first location: associating the patient with the first mobile device; and sending configuration setting data to the mobile device, the configuration setting data triggering the first mobile device to provide a username and password to a web-based healthcare application to: enable the patient to access the web-based healthcare application without entering the username and a password; and prompt the patient to verify patient information in the web-based healthcare application; sending healthcare information associated with the patient to the first mobile device, the healthcare information stored in a database accessible to the MDM server; and in response to determining that the patient is no longer associated with the first mobile device, sending a remote reset command from the MDM server to the first mobile device to erase the healthcare information associated with the patient stored in a memory device of the first mobile device. storing, at a mobile device management, MDM, server, location-to-device mapping data indicating mobile devices assigned to locations at a healthcare facility, wherein the location-to-device mapping data indicates that a first mobile device is assigned to a first location at the healthcare facility and that a second mobile device is assigned to a second location at the healthcare facility, and wherein the first location is distinct from the second location; receiving, at the MDM server, a message indicating receipt of user input that indicates a patient identifier and a particular location associated with a patient; in response to determining, based on the location-to-device mapping data, that the particular location corresponds to the first location: associating the patient with the first mobile device; and sending configuration setting data to the mobile device, the configuration setting data triggering the first mobile device to provide a username and password to a web-based healthcare application to: enable the patient to access the web-based healthcare application without entering the username and a password; and prompt the patient to verify patient information in the web-based healthcare application; associating the patient with the first mobile device; and sending configuration setting data to the mobile device, the configuration setting data triggering the first mobile device to provide a username and password to a web-based healthcare application to: enable the patient to access the web-based healthcare application without entering the username and a password; and prompt the patient to verify patient information in the web-based healthcare application; enable the patient to access the web-based healthcare application without entering the username and a password; and prompt the patient to verify patient information in the web-based healthcare application; sending healthcare information associated with the patient to the first mobile device, the healthcare information stored in a database accessible to the MDM server; and in response to determining that the patient is no longer associated with the first mobile device, sending a remote reset command from the MDM server to the first mobile device to erase the healthcare information associated with the patient stored in a memory device of the first mobile device.