Your data and the Patient is in app

The Patient is in app uses two types of data: 

  1. Data needed to ensure authorized access
    The Patient is in app connects your staff through an encrypted local peer-to-peer network using WiFi. This requires that the app use the WiFi network name and device location to ensure authorized access.
    For redundancy, the Patient is in app also connects your staff through iCloud and the Microsoft Azure cloud. These network connections are also encrypted. This requires that you are logged into an iCloud account while using the app. The Patient is in app never has access to your iCloud account information or data from other apps. It is perfectly fine for a staff member to create a new, work-only iCloud account. All iCloud accounts must be unique.
  2. Data needed for patient assignments
    Staff names
    For a doctor to be assigned to a room to treat a patient, your charge nurse must be able to identify your doctors on the Patient is in iPad app. Rather than collecting the real names of your staff, the Patient is in app uses the iPhone or Apple Watch device name. It is perfectly fine to rename your iPhone, iPad, and Apple Watch as you see fit.

    Location data
    At many medical facilities, it is important to know the location of your staff. The Patient is in apps use Apple’s micro-location iBeacon technology to provide the charge nurse with the approximate location of your onsite staff. Specifically, if a doctor has installed the Patient is in iPhone app and the iPhone is in the vicinity of a charge nurse’s iPad unto which the Patient is in iPad app is installed, then the charge nurse will have access to the doctor’s onsite location. Onsite location will be described in broad terms such as “near Nurse Station 2” and “left ICU Nurse Station”. The doctor may disable reporting of this information to the charge nurse through a toggle in the Patient is in iPhone app. Onsite location updates are turned off by default.

    The charge nurse may also need to know the location of offsite doctors who may be traveling to your medical facility, perhaps for emergency surgery. The Patient is in iPad app provides a live map with a traffic view of your offsite staff. Specifically, if a doctor has installed the Patient is in iPhone app, then the charge nurse will have access to the doctor’s offsite location. The doctor may disable reporting of this information through a toggle in the Patient is in iPhone app. Offsite location updates are turned off by default.

    Conference calls with FaceTime and Skype for Business
    The Patient is in apps are integrated with FaceTime on the iPad, iPhone, and Apple Watch. To protect your staff member’s personal FaceTime contact information, the Patient is in apps do not access a device’s built-in address book. Rather, the Patient is in apps allow your staff to provide a FaceTime work phone number or email as their FaceTime contact. Furthermore, the Patient is in iPhone app can instruct the Skype for Business iPhone app to connect to a contact if the Skype for Business iPhone app is installed.

    Patient notes
    When your charge nurse uses the Patient is in iPad app to assign a doctor to a room to see a patient, she may provide optional comments about the patient such as if the patient has elevated vital signs or other symptoms which require a quick response from the doctor. It is recommended that these comments describe the patient’s condition and do not contain personally identifiable information such as the patient’s name. Nonetheless, all of this data is transferred through encrypted network connections.

    Announcing patient assignments using AirPlay compatible speakers 
    The Patient is in app is integrated with AirPlay allowing your charge nurse to announce that a doctor has a new patient assignment. Specifically, the Patient is in iPad app can announce that a doctor (as defined above in the section “Staff names”) has a patient assignment in a specific room. The Patient is in iPad app will not announce the patient notes.

This privacy policy will be updated and your questions and suggestions are welcomed. 

Updated on February 5, 2018 in support of version 2.5