SECURING PATIENT VITAL SIGN DATA AND CONFIGURING VITAL SIGN DATA FOR REMOTE ACCESS BY HEALTHCARE PROVIDERS

Abstract

Disclosed herein are systems, devices, and methods for remotely measuring one or more vital signs of a patient, securely storing and communicating the resulting vital sign data, and configuring the vital sign data for secure access by a healthcare provider computer system to enable remote monitoring of the patients vital signs. One or more vital sign monitoring devices detect patient vital signs and securely transmit the resulting vital sign data to an external computer device such as the patients smart phone or abase station computer device. The external computer device communicates with a server system, such as a secure cloud storage system, which configures the vital sign measurement data and received patient identification data and makes it accessible to one or more healthcare provider computer systems.

Description

BACKGROUND

Hospitals and other healthcare facilities routinely monitor patients' vital signs. The conventional equipment used to detect and monitor patients is typically large, bulky, and expensive. While such equipment may be workable in certain settings, it can limit the freedom of movement and comfort of the patient. Further, the vital sign data collected with the conventional equipment is typically not made readily available to the patient or other caretakers. For example, although the patient or caretaker may be able to look to a bedside display to see some vital sign information, the equipment is often designed simply to periodically monitor the patient and sound an alarm (typically an audible alarm) if the measured vital sign falls above or below some threshold level.

In addition, some patients may require health monitoring outside of a dedicated healthcare facility, such as in their own homes. In cases where monitoring is insufficient or the gathered vital sign data is not properly managed, complications may arise and emergency situations may develop. In many cases these complications are preventable and can be avoided if the patient's health is properly monitored and communicated.

Typically, for patient monitoring outside of a dedicated healthcare facility, a healthcare provider must send personnel to the home of the patient or the patient must make frequent visits to the healthcare provider. This conventional practice is limited by the frequency at which the healthcare provider can monitor the patient. Often, personnel limitations prevent the healthcare provider from checking on a patient more than a few times a week. Likewise, a patient may not be able visit the healthcare provider with sufficient frequency. Complications may arise between visits that could be avoided with more frequent health monitoring.

Accordingly, there is a long felt and ongoing need for systems, devices, and methods for enabling remote monitoring of patients. Providing remote monitoring of patients presents several technical challenges. For example, monitoring devices used to gather patient vital sign information may fail to properly communicate with remote computer systems. Loss of vital sign data could result in a failure to identify a critical health situation. In addition, whenever sensitive patient data is being handled and communicated, there is a risk of disclosing data that should be secured. Finding a proper balance between enabling effective utilization of the vital sign data while protecting personal information is a serious challenge.

SUMMARY

The present disclosure describes systems, devices, and related methods for remotely measuring one or more vital signs of a patient, securely storing and communicating the resulting vital sign data, and configuring the vital sign data for secure access by a healthcare provider computer system to enable remote monitoring of the patient's vital signs. One or more vital sign monitoring devices detect patient vital signs and securely transmit the resulting vital sign data to an external computer device such as the patient's smart phone or a base station computer device. The external computer device communicates with a server system, such as a secure cloud storage system, which configures the vital sign measurement data and received patient identification data and makes it accessible to one or more healthcare provider computer systems.

In one embodiment, a computer system for securing vital sign measurement data and configuring the vital sign measurement data for accessibility by a remote system is configured to generate a unique patient identifier relating to a patient to which one or more wearable vital sign monitoring devices are associated. The system is also configured to receive, from a user-associated computer device, patient identification information relating to the patient. Based on the received patient identification information, and based on the unique patient identifier, the system generates a patient identity database unique to the patient to store the patient identification information (such as patient protected health information (PHI)).

The system also receives, from the user-associated computer device, vital sign measurement data indicative of one or more vital signs of the patient/user as measured by one or more wearable vital sign monitoring devices worn by the patient/user. Based on the received vital sign measurement data, and based on the unique patient identifier, the system generates a vital sign measurements database unique to the patient to store the vital sign measurement data. The vital sign measurements database is separate from the patient identity database. The system is also configured to send the vital sign measurement data from the vital sign measurement database to one or more remote computer systems to thereby enable remote monitoring of the one or more vital signs while protecting the patient's personal information.

In another embodiment, a wearable vital sign monitoring system configured to enable remote monitoring of vital sign measurements comprises a sensor assembly and an internal controller. The internal controller is configured to receive vital sign measurement data from the sensor assembly, and to locally store the vital sign measurement data. The controller may then determine a connectivity status to an external computer device (e.g., a user-associated device such as the patient's smartphone, tablet, or personal computer).

Based on the determined connectivity status, when a connection is confirmed, the controller sends the vital sign measurement data to the external computer device and flags the vital sign measurement data for deletion from local storage. Alternatively, when no connection is confirmed, the controller maintains the vital sign measurement data in local storage and continue to periodically determine the connectivity status. The controller may also generate an alarm/alert/notification to notify the patient/user of the issue.

Additional features and advantages will be set forth in part in the description that follows. It is to be understood that both the foregoing summary and the following detailed description are exemplary and explanatory only, and are not to be read as limiting the disclosure to any particular set of embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description will be rendered by the embodiments illustrated in the appended drawings. It is appreciated that these drawings depict only exemplary embodiments of the disclosure and are therefore not to be considered limiting of its scope. In the accompanying drawings:

FIGS. 1A and 1B illustrates exemplary vital sign monitoring systems comprising wearable monitoring devices;

FIG. 2 illustrates an exemplary computer architecture for a vital sign remote monitoring system;

FIG. 3 is a schematic of a server system, showing various database types that may be included within the server system;

FIGS. 4 through 6 illustrate data structures that may be included within the various databases of the server system;

FIG. 7 is a schematic of a wearable monitoring device showing various components associated with the wearable monitoring device;

FIG. 8 is a schematic of a user-associated device communicatively linked to the wearable monitoring device of FIG. 7 and the server system of FIG. 3, showing a vital sign measurement application and its associated components;

FIG. 9 is a schematic of a device associated with a healthcare practitioner or facility communicatively linked to the server system, showing a differently configured vital sign measurement application; and

FIGS. 10 through 12 illustrate exemplary computer-implemented methods for configuring vital sign measurement data and enabling remote monitoring of vital sign measurement data.

DETAILED DESCRIPTION

FIG. 1A illustrates an exemplary vital sign monitoring system 100 configured to monitor one or more vital signs while worn by a user. The wearable monitoring system 100 includes a torso monitoring device 102 and a limb monitoring device 104. The torso monitoring device 102 is preferably positioned on the user's chest wall as shown, and the limb monitoring device 104 is preferably positioned on the user's upper arm as shown. The monitoring system 100 may be used, for example, to monitor blood pressure, temperature, respiration rate, pulse rate, and the like.

The torso monitoring device 102 and limb monitoring device 104 may include one or more position sensors (e.g., a 9-axis sensor includes a 3-axis gyroscope, a 3-axis accelerometer, and a 3-axis magnetometer) that enable determination of the spatial position of the limb monitoring device 104 relative to the torso monitoring device 102. This spatial position data can be utilized to calibrate blood pressure readings obtained using the limb monitoring device 104. The torso monitoring device 102 and limb monitoring device 104 are communicatively linked to one another through a suitable communication network, such as via a Bluetooth connection and/or other personal area network (PAN).

In FIG. 1A, the torso monitoring device 102 is shown placed on the torso wall at the fourth intercostal space in a mid-axillary position. The torso monitoring device 102 is also tilted relative to the transverse plane of the user in order to better receive the electrocardiogram signal from the user. This position also provides an effective baseline level of the height of the heart, which is useful when the torso monitoring device 102 is used in conjunction with the limb monitoring device 104. While this represents a typical placement of the torso monitoring device 102, it will be understood that placement may vary according to particular application requirements and according to particular user preferences, needs, and/or anatomy. Further, while the components of the monitoring system 100 are shown here as being worn on the user's right side, one or both components may be worn on the left side.

FIG. 1B illustrates an alternative vital sign monitoring system 600 with several similarities to the system 100. The system 600 includes a torso monitoring device 602 and a limb monitoring device 604. The separate monitoring devices 602 and 604 are communicatively linked to one another and are configured to monitor vital signs in the same manner as like components of system 100.

FIG. 2 illustrates an exemplary computer system architecture for a remote monitoring system 101. The system 101 enables remote monitoring of vital signs and configuring of the vital sign data for accessibility by a healthcare entity. The limb monitoring device 104 is communicatively linked to one or both of a user device 106 and a base station 108. The torso monitoring device 102 may additionally or alternatively be connected to the user device 106 and/or base station 108, though preferred embodiments allow the limb monitoring device 104 to manage these connections in order to minimize the size/complexity of the torso monitoring device 102.

The user device 106 and the base station 108 (also referred to herein as “external computer devices”) receive the vital sign data collected and sent by the monitoring devices 102 and/or 104. The user device 106 may be a user's smartphone, tablet, or personal computer, for example, and will typically be associated with the monitoring devices 102, 104 in a home monitoring setting. The base station 108 may be a hospital or healthcare provider computer system, and will typically be associated with the monitoring devices 102, 104 in a healthcare facility setting.

The user device 106 and/or base station 108 are preferably connected to the monitoring device 104 and/or monitoring device 102 with a PAN or NFC link, though they may additionally or alternatively be connected via other wired or wireless networks (with wireless being more preferred) such as a local area network (LAN), wide area network (WAN), and/or the Internet. While the remainder of the connections illustrated in FIG. 1 are preferably secured, the connection between monitoring devices 102 and 104 may simply be encrypted, as data transferred between the monitoring devices 102 and 104 will only include vital sign information and will not include sensitive patient identifying data. It is therefore less critical to have high level protection.

The user device 106 and/or base station 108 are configured to relay the vital sign measurement data to a secure server system 110, which may be a dedicated computer system, a distributed computer environment, and/or a cloud computing environment. In this description and the following claims, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The connection to the secure server system 110 should be secured, as it will likely contain private, identifying patient data. The user device 106 and/or base station 108 may communicate with the server system 110 via a secured cellular network connection or secured Internet connection (e.g., WiFi or Ethernet), for example.

As shown, the server system 110 may be connected to one or more computer systems or devices associated with a healthcare facility, such as healthcare facility system 112 and/or practitioner device 114 (also referred to herein as remote devices or systems). The healthcare facility system 112 may include, for example, a monitoring station computer device where a nurse or other caretaker can see vital sign information from multiple patients at the same time. For example, the healthcare facility system 112 may include an application enabling the system 112 to pull vital sign data from the server system 110 related to multiple patients within a ward, floor, or other division of a hospital or clinic. The practitioner device 114 may be, for example, a tablet or smartphone device that a doctor or nurse can interact with to visualize patient vital sign data pulled from the server system 110.

FIG. 3 schematically illustrates components that may be included in the server system 110. As shown, the server system 110 may include a patient ID database 116. When a new patient is entered into the system, a patient ID from the patient ID database 116 is assigned. The patient ID preferably omits any information related to region, time, date, or other information related to private patient data. The patient ID may be, for example, a random string of characters. A start time is also recorded, at the time the patient ID is assigned, to function as a baseline for determining the relative time of subsequent vital sign measurements.

FIG. 4 provides an example of an entry 301 that could be included within the patient ID database 116. The entry 301 includes a patient ID 302, a “used” field 304 indicating whether it has been assigned to a patient, and a start time 306. As shown, the patient ID 302 is preferably a pre-defined, unique, random number of at least 8 digits, though other embodiments may include differently configured patient IDs. The start time 306 may be based on Greenwich Mean Time, as shown, or may utilize any other suitable base time measurement.

The server system 110 may also include separate databases created for each patient. For example, once a patient ID has been recorded as assigned in the patient ID database 116, a vital sign measurement database 118 and a protected health information (PHI) database 120 are each separately created for the patient. The vital sign measurement database 118 includes de-identified vital sign measurements related to the patient and the relative time the vital sign measurements were obtained, and the PHI database 120 includes private protected health information (PHI) such as name, age, weight, etcetera.

FIG. 5 illustrates an example of a vital sign measurement entry 307, and FIG. 6 illustrates an example of a patient identity data entry 317. The data within the vital sign measurement entry 307 is de-identified from any PHI related to the patient, and the private PHI information stored within the patient identity data entry 317 is only linkable to the other data by way of the unique patient ID 302. As shown, the vital sign measurement entry 307 includes the patient ID 302, the relative time 310 since the start time that the measurement was taken, the data type 312 (e.g., vital sign measured), the data value 314 in units according to data type 312, and a data quality score 316 assigned based on the determined accuracy or quality of the measurement.

The patient identity data entry 317 separately stores PHI such as patient name, address, birthdate/age, height, weight, gender, and the like. Generating and storing separate databases 118 and 120 for vital sign measurement data and patient identification information, respectively, beneficially “quarantines” the private PHI to reduce or eliminate the risk of unintended dissemination of PHI. At the same time, the vital sign measurement data is made remotely accessible to healthcare personnel and/or caretakers remote from the user. The vital sign measurement data is not directly linked to any identifiable patient, and can only be linked to a particular patient using the unique patient ID 302. The PHI database 120 may have greater security than the vital sign measurement database 118, and will only be accessible to those with authority, such as the user and possibly the user's primary physician.

FIG. 7 schematically illustrates components that may be included as part of the vital sign monitoring device 102 and/or 104. A sensor assembly 172 is configured for measuring one or more of the patient's vital signs, as described above. A controller 161 includes memory 162 and a processor 164. As with other processors described herein, the processor 164 can perform Boolean logic or can produce a pre-determined output based on input.

The processor 164 can include ROM memory, programmable logic device (PLD), programmable array logic (PAL), generic array logic (GAL), complex programmable logic device (CPLD), field programmable gate arrays (FPGA), logic gates, processors, or any other logic function. As with other memory components described herein, the memory 162 may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other physical and tangible storage medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computing system. Such memory devices may also be referred to herein as “computer-readable storage media” or a “hardware storage device.”

The vital sign monitoring device 102 and/or 104 also includes a communication module 166 to enable communications with one or more external devices (e.g., the user device 106 and/or base station 108). Preferably, these communications utilize NFC and/or a PAN, such as through a Bluetooth connection. The connection between the vital sign monitoring device(s) and the user device 106 and/or base station 108 may additionally or alternatively include a hardwired connection and/or the use of other communication modalities that utilize other communication media, such as optical (e.g., infrared), ultrasound, or infrasound transmissions.

The communication protocol is intended to allow seamless connection between the monitoring device(s) and the user device 106 and/or base station 108. In particular, the typical user may not be technically savvy and the pairing process should therefore be straightforward and relatively simple. In one embodiment, for example, the pairing process utilizes one or more of Bluetooth BR/EDR Secure Simple Pairing (SSP) and Bluetooth Low Energy (BLE) Out-of-Band (OOB) pairing protocols. The benefits of a simple pairing process should be balanced against the need to provide sufficient security, however, because the transmitted data will include sensitive health information. As such, some preferred embodiments utilize BLE at reduced power to ensure that the transmissions are limited to the proximity of the linked monitoring device(s). For example, whereas a standard class 1 Bluetooth device has a range of about 100 m, the disclosed connection transmissions may limit this by about 25%, or by about 50%, or by about 75%, or by about 90%.

The vital sign monitoring device 102 and/or 104 also includes a connectivity determiner 170 configured to determine the connectivity status between the monitoring device 102 and/or 104 and the external device. The connectivity determiner 170 operates in conjunction with a vital sign data router 171 to minimize the risk of vital sign data loss. For example, when the connectivity determiner 170 determines that there is an adequate connection to the external device, the vital sign data router 171 operates to send the vital sign data to the external device and flags the vital sign data for deletion (e.g., upon acknowledgment from the external device that the communication has been received). On the other hand, when the connectivity determiner 170 determines that there is no or insufficient connectivity to the external device, the vital sign data router 171 operates to store vital sign data in local storage/memory 162 until an adequate connection can be established.

These operations ensure that no vital sign data is lost due to connectivity issues. At the same time, once connectivity is established, sent vital sign data may be flagged for deletion to minimize data storage requirements at the monitoring device 102 and/or 104. Of course, the vital sign data that has been confirmed as sent does not need to be immediately deleted. Even sent data may be stored for a predetermined time period or until another event occurs to provide for deletion. However, such “flagged for deletion” data will be managed differently than data that has not been sent to the external device. Such unsent data should be locally stored for as long as possible until a connection can be established.

The connectivity determiner 170 may also operate to give a notification or warning to alert the user when connectivity is lost. For example, the monitoring device 102 and/or 104 may include a light, display, and/or speaker configured to give an audio and/or visual notification when no connection is determined.

FIG. 8 schematically illustrates components that may be included as part of the user device 106 and/or the base station 108 (referred to hereafter for simplicity as the user device 106). The user device 106 includes memory 122, a processor 124, and a communications module 126 configured to enable communications with the monitoring device(s) 102 and/or 104 and to enable communications with the server system 110. The user device 106 may include a vital sign application 128 configured to provide several features related to vital sign monitoring. In a typical embodiment, these features are included as part of the vital sign application 128, but they need not all be provided as part of the same dedicated application, and one or more of the illustrated modules/operations may be provided by other applications and/or by the native programming of the user device 106 itself.

In the illustrated embodiment, the vital sign application 128 includes a connectivity notifier 130 configured to notify a user of the connection status of the user device 106 to the monitoring device 102, 104 and/or to the server system 110. The vital sign application 128 also includes a vital sign data display 132 configured to organize the received vital sign data into displayable results for display on a user interface of the user device 106. The application 128 also includes a vital sign data configuration module 134 that enables a user to configure the vital sign data transmitted to the server system 110. The configuration module 134 may provide user-selectable options controlling, for example, an on/off state of data transmission, how often vital sign data is sent, which vital sign data types to send, and time periods in which vital sign data is sent (e.g., off during the day, on at night).

The illustrated application 128 also includes vital sign monitoring device controls 136 which provides user-selectable controls for configuring the monitoring device 102 and/or 104. The monitoring device controls 136 may include controls related to, for example, power settings, device registration, account settings, monitoring frequency, vital signs to monitor, monitoring time periods, and on/off controls. The application 128 may also include a patient ID information interface 138 configured to provide for input and control of the user's identification information such as the patient information shown in FIG. 6. The interface 138 may be secured (e.g., via password, biometric key, and/or other security feature) so that only the authorized user is able to access and input patient identity information.

The user device 106 may include components that cause it to locally store sufficient vital sign data to minimize or reduce data loss. For example, similar to the monitoring devices 102 and/or 104, the user device 106 may locally store the received vital sign data until connection with the server system 110 has been confirmed and the data has been securely transmitted. Once transmitted, the data may be flagged for deletion, or at least flagged to be deleted or overwritten prior to any non-transmitted vital sign data.

FIG. 9 schematically illustrates components that may be included as part of a healthcare facility system 112 and/or practitioner device 114. The illustrated device includes memory 142, a processor 144, and a communications module 146 to enable communication with the server system 110. The vital sign application 148 may be similar to the vital sign application 128 of the user device 106, except it may omit certain features that are unique to the user device 106 and that are preferably maintained under user control. For example, while the application 148 includes a connectivity notifier 150 and a vital sign data display 152, it omits a vital sign data configuration module, leaving control over the frequency and type of available vital sign data to the user. The illustrated embodiment includes vital sign monitoring controls 156, allowing healthcare personnel to adjust the acuity, vital sign type, or sampling rate of the monitoring device as needed.

In another example, the application 148 includes a patient ID display 158, which may allow patient ID information to be visualized but not edited. Thus, a doctor or nurse with access permission may be able to visualize, but not change, the patient's private information. Other embodiments may include other differences between the vital sign application at the user device and at the healthcare facility device. For instance, some of the features omitted from vital sign application 148 in the illustrated embodiment may in some circumstances be included, such as where it is beneficial to allow healthcare personnel to configure/control the gathered vital sign data. Some embodiments may omit or limit the vital sign monitoring device controls 156 of the application 148, leaving the user with greater control over the related options.

FIG. 10 illustrates an example method 200 of configuring vital sign data using the remote monitoring system 101 and in particular the server system 110 as shown in FIG. 3. The system determines whether the patient is a new patient (step 202). For new patients, the system then initializes the patient into the system by getting or generating a patient ID from the patient ID database (step 204), marks the patient ID as used (step 206), and defines and records a start time associated with the patient ID (step 208). The system also creates two separate databases for each patient by creating a patient vital sign measurement database (step 210) and a patient private PHI database (step 212).

If the patient has already been initialized into the system, the method 200 determines whether it is time for a new reading (step 214). This may be done according to a predefined schedule and/or may occur based on a push command (e.g., initiated at the user device 106) or a pull command (e.g., initiated at the server system 110). Upon receipt of a new vital sign reading, the system records the vital sign data in the vital sign measurement database (step 216) and records the associated relative time of the measurement in the vital sign measurement database (step 218). The method 200 may also determine whether to update patient private PHI (step 220), and if needed, update the patient private PHI database (step 222).

FIG. 11 illustrates an exemplary method 400 of configuring the transmission of vital sign data using the monitoring device(s) 102 and/or 104 as shown in FIG. 7. The controller 161 of the monitoring device receives vital sign measurement data from the sensor assembly 172 (step 402). The received vital sign data is then locally stored (step 404). The controller 161 determines a connectivity status to an external computer device (e.g., the user device 106 and/or base station 108) (step 406). Based on the determined connectivity status, when sufficient connectivity is established, the controller 161 sends the vital sign data to the external computer device and flags the vital sign data for deletion from local storage (step 408).

Alternatively, when connectivity is not established, the controller maintains the vital sign measurement data in local storage and continues to periodically determine the connectivity status (step 410). As described above, vital sign data that has been “flagged for deletion” does not necessarily need to be immediately deleted. However, such data will be deleted or overwritten prior to any vital sign data that has not yet been confirmed as transmitted.

FIG. 12 illustrates an exemplary method 500 of configuring the transmission of vital sign data using the user device 106 and/or base station 108 as shown in FIG. 8. The device receives vital sign data from the monitoring device(s) 102 and/or 104 (step 502) and locally stores the vital sign data (step 504). The device determines a connectivity status to the server computer system (step 506). Based on the determined connectivity status, the device sends the vital sign measurement data to the server computer system (step 508) or maintains the vital sign data in local storage and generates a notification message (e.g., for display at an interface of the user device 106/base station 108) indicating a lack of connectivity (step 510).

The terms “module,” “component,” and the like refer to a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods, and so forth, that may be executed on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media.

Within this disclosure, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors (of the associated computing system that performs the act) direct the operation of the computing system in response to having executed computer-executable instructions that constitute an executable component. For example, such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product.

Terms such as “approximately,” “about,” and “substantially,” as used herein represent an amount or condition close to the stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a stated amount or condition.

Specific elements or components described in relation to any particular embodiment described herein may be substituted for or combined with elements described in relation to any other embodiment described herein. For example, any of the methods described in FIGS. 10 through 12 may make use of any of the computer system embodiments and components shown in FIGS. 1 through 9.

Claims

1. A computer system for securing vital sign measurement data and configuring the vital sign measurement data for accessibility by a remote system to enable remote monitoring of one or more patient vital signs, the computer system being communicatively coupled to one or more wearable vital sign monitoring devices, the computer system comprising:

one or more processors;

one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to generate a unique patient identifier relating to a patient to which one or more wearable vital sign monitoring devices are associated; receive, from a user-associated computer device, patient personal information relating to the patient; based on the received patient personal information, and based on the unique patient identifier, generate a patient protected information database unique to the patient to store the patient personal information; receive, from the user-associated computer device, vital sign measurement data indicative of one or more vital signs of the patient as measured by the one or more wearable vital sign monitoring devices; based on the received vital sign measurement data, and based on the unique patient identifier, generate a vital sign measurements database unique to the patient to store the vital sign measurement data, the vital sign measurements database being separate from the patient protected information database; and send vital sign measurement data from the vital sign measurement database to one or more remote computer systems to thereby enable remote monitoring of the one or more vital signs.

2. The computer system of claim 1, wherein the computer-executable instructions are further configured to cause the computer system to generate a time stamp representing a start time when the unique patient identifier is generated.

3. The computer system of claim 2, wherein the computer-executable instructions are further configured to cause the computer system to, for each vital sign measurement stored within the vital sign measurements database, generate a relative time stamp representing a relative time at which the vital sign was measured with respect to the start time.

4. The computer system of claim 1, wherein vital sign measurement data is received at pre-determined intervals.

5. The computer system of claim 1, wherein the vital sign measurement data includes data associated with one or more vital signs selected from the group consisting of; temperature, pulse rate, respiration rate, blood pressure, and body part position.

6. The computer system of claim 1, wherein the one or more remote computer systems includes a computer system associated with a healthcare facility and/or a healthcare practitioner.

7. The computer system of claim 1, wherein the computer-executable instructions are further configured to cause the computer system to:

receive, from the user-associated computer device, an initiation or stop command for collecting patient vital sign measurement data, and

based on the initiation or stop command, initiate or stop receiving vital sign measurement data from the user-associated computer device.

8. The computer system of claim 1, wherein the computer-executable instructions are further configured to cause the computer system to:

receive, from the remote computer system, a vital sign measurement data request;

receive, from the remote computer system, the unique patient identifier; and

based on the received vital sign measurement data request and the received unique patient identifier, send corresponding vital sign measurement data to the remote computer system.

9. The computer system of claim 8, wherein the computer-executable instructions are further configured to cause the computer system to limit or block the sending of patient personal information from the patient protected information database to the remote computer system to a greater degree than the vital sign measurement data from the vital sign measurement database.

10. A wearable vital sign monitoring system configured to enable remote monitoring of vital sign measurements, the system comprising one or more wearable vital sign monitoring devices adapted to be worn by a patient and to measure one or more patient vital signs, the system comprising:

a sensor assembly for measuring the one or more patient vital signs;

an internal controller physically connected to at least one of the one or more vital sign monitoring devices, the internal controller including one or more processors and one or more hardware storage devices having stored thereon computer-executable instructions which are executable by the one or more processors to cause the controller to receive vital sign measurement data from the sensor assembly, locally store the vital sign measurement data, determine a connectivity status to an external computer device, and based on the determined connectivity status, send the vital sign measurement data to the external computer device and flag the vital sign measurement data for deletion from local storage, or maintain the vital sign measurement data in local storage and continue to periodically determine the connectivity status.

11. The system of claim 10, wherein the one or more wearable vital sign monitoring devices includes an arm band monitoring device.

12. The system of claim 10, wherein the one or more wearable vital sign monitoring devices includes a torso monitoring device.

13. The system of claim 10, further comprising an indicator configured to activate when the internal controller determines a lack of connectivity.

14. The system of claim 10, wherein the external computer device is a user-associated device communicatively coupled to the one or more vital sign monitoring devices via a Personal Area Network.

15. The system of claim 10, the system further comprising the external computer device, the external computer device comprising:

one or more processors;

one or more hardware storage devices having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computer system to

receive vital sign measurement data from the internal controller of the one or more vital sign monitoring devices;

locally store the vital sign measurement data;

determine a connectivity status to a server computer system; and

based on the determined connectivity status, send the vital sign measurement data to the server computer system, or generate a notification message identifying lack of connectivity.

16. The system of claim 15, wherein the notification message is delivered for display at an interface of the external computer device.

17. The system of claim 15 or claim 16, wherein the notification message is delivered to the internal controller of the one or more vital sign monitoring devices.

18. The system of claim 17, wherein the controller is configured to, upon receiving the notification message, activate an indicator on the one or more vital sign monitoring devices.

19. The system of claim 18, wherein the indicator includes a light and/or speaker.

20. The system of claim 15, wherein the server computer system is the computer system as in claim 1.