The System is envisioned to be designed with Reliability and Availability Features at every level leveraging heavily on existing and emerging technologies and large volumes to make them affordable, robust, and make them virtually “invisible to end-users”. Many of the features of the System support multiple areas of Availability and Reliability and heavy reliance on existing technology, so there is some overlaps of Features to the type of Availability/Reliability that they provide.

 

End User APPs

 

End User APP can be run virtually anywhere there is a Smartphone, Tablet, or PC. Individuals can log-n under their role profile and be able to perform the tasks they are authorized for as well as get any alerts and escalations (note: alerts and escalations can be viewed through the APP, txt, and/or email depending on how they are configured). Since they are supported through one or more server (local, enterprise, and/or cloud) they are likely to be able to connect somewhere. Most are available through APP stores and can be added, deleted, replaced and upgraded as needed through almost any connection.

 

Application Servers

 

There are many different Applications associated with the System. Some are individual System dependent, and some are public and may or may not access personal account information. These are basically the same as any other APP server supporting a wide variety of publically and privately available APPs for PCs, Tablets and Smartphones, and use the same basic technologies that they use for redundancy, availability, and security. Some of these will be hosted on general System APP Servers, specific System APP or Process and Control Servers, and others will be hosted by third parties.

 

System Process and Control Servers

 

Each Object, Device, and Service needs to be associated with a System Process and Control Computer. The System Process and Control Computers can be PCs, Tablets, Smart Phones, Enterprise Servers, or Virtual Cloud Servers.  There are also some APPs that need to run on specific System servers for security or regulatory reasons. These are all just server computers.

 

These computers can be made up of multiple computers, a single computer, or a primary computer with backup shadow computers that can be used as needed (major upgrades, server failures, network outages.

 

Each System Process and Control Computer server belongs to a System, and can interface with other Systems to share data based on security access lists. Servers are typically at the local, enterprise, and/or cloud level to provide the best redundancy and availability.  In addition to individual Systems owned by different organizations, there is a Public System, to cover “Public” services.

 

The System contains many different “System Processing and Control” Availability and Reliability Features.

• Status monitoring between standalone, primary and backup computers within a System to determine Master/Slave Relationships between System Process and Control Systems and their associated Data Servers

• Ability to switch, share, or failover for Objects, Devices, and Services to other designated physical and/or virtual computer servers within a system

• Ability to switch back to a primary or backup server when they are available

 

Data

 

Data is a critical part of the System to be able to allow it to work in many different modes as well as different parts being able to be shared and protected under specific safeguards and rules. Data includes instructions, help, account data, configuration data, SW, patient data, schedule data, etc.  Although there is a lot of redundancy built into the System, there are cases, where...

• A System (e.g. Home, Portable Emergency System, and/or other Emergency System) is not connected nor have access to outside data

• A System may be down for a period of time, and data storage needs to be temporarily stored locally on a device or local System

• Data Storage and retrieval need so be permanently or temporarily switched to a different Data Storage and Retrieval Server

 

In all of these cases, data needs to be accessible, cannot be lost, needs to be backed up, synchronized, and some of the data needs to be able to be securely accessed and shared with other authorized Systems.

 

The System contains many different “Data” Availability and Reliability Features.

• Status monitoring between Systems to determine Master/Slave Relationships between Data Servers and their associated System Process and Control Systems

• Storage in one or more locations (devices and local, enterprise, and/or cloud data servers)

• Different System Security Levels and Access Control Lists for the sharing and access of different types of data

• Data File and Transaction Processing Synchronization of data

• Local Storage of data (devices and local Systems) to be able to perform functions when not connected with other Systems (Instructions/Troubleshooting, Configurations, SW, Patient Data, etc.)

• Standard and recommended backup and synchronization capabilities for portable, standalone, enterprise, and cloud data servers

 

Devices

 

The System envisions a standard as well as many available common SW and HW libraries to assist in the development or new compatible devices, that will be plug and play with the System. The libraries are created to support brand new, as well as existing devices to make the necessary changes. There are also Legacy SW and HW Gateways envisioned to provide support for partially and non-compliant devices.

 

The System contains many different “Device” Availability and Reliability Features.

• Built-in power saving modes (turn off when not needed, automatic wake-up, shutdown if not critical, etc.)- even for legacy devices

• Available power reduction HW and SW Libraries and components

• Available high availability features (e.g. automated monitoring, self-diagnosis, self-correcting capabilities; auto alerts and scheduling for calibration and maintenance; A/B side configurations and SW for auto recovery; push new versions of SW and Configurations to fix known problems; verification of compatibility between versions and configurations, etc.)

• Ability for Devices to go into a standalone mode, or switch autonomously  switch to another server when the primary server is down (as well as the ability to synchronize with a server and report if more than one server thinks that it is primary)

• More thoroughly tested Common and 3rd Party SW and HW across multiple configurations

• Automated reporting of issues

• Secure remote support and management

• Remote analysis on devices and types of devices to help identify any trends or bugs that may need attention (manufacture date, HW/SW versions, configuration parameters, failures)

• Local storage of help and configuration information

• Control and Data storage/retrieval and synchronization (locally, enterprise, and/or cloud)

• Battery backup for devices

 

Network

 

With new devices requiring supporting multiple network interfaces and technologies, more can be done to provide redundancy.

 

The System contains many different “Network” Availability and Reliability Features, as well as direct leverage off of commercially available technologies.

• Use of multiple backhaul technologies for devices (satellite, cellular, cable, fiber, Wi-Fi/Wi-Max) for individuals and/or areas

• Battery backup for Network and other Devices

• Device capabilities to handoff between different technologies and devices depending on availability and signal strength

• Prioritized network traffic

• Ability to turn on and off (and test different) network connectivity based on need or schedule to save on costs as well as power in a power constrained environment (relying on battery backup)

 

Power

 

With newer devices requiring less power, and wider capabilities to provide charging and extended power, more can be done to provide redundancy.

 

System contains many different “Power” Availability and Reliability Features, as well as direct leverage off of commercially available technologies.

• Power Management Features that can help reduce power consumption

• Integrated and extra batteries or external battery packs for electronic devices (laptops, tablets, Smartphones)

• Hardware Legacy Gateways that can provide power and power management capabilities for devices

• Small UPS and Battery Systems for Homes

• Easy Registration for Automated Alerts/Lists of At Risk Individuals that are dependent of power

• UPS and Battery Systems for small to large organizations

• Generators

• Solar Chargers

• Kiosks and Emergency Centers that can provide small device charging

 

People

 

People may sound like an odd category of Availability and Reliability, but to provide Healthcare or Whole Healthcare, people do need to be involved and involved reliably.

 

The System contains many different “People” Availability and Reliability Features.

• Ability to set up Family, Friends, Guardians, Social Advocacy Groups, Call Centers, Medical and Retirement Centers, and Emergency Services to help monitor and provide services to individuals

• Automated alerts and alarms to monitor changes in individuals conditions and lack of contact or movement of an individual

• Role based scheduling and schedule/event escalation to support multiple levels of support and backup

• Applications allowing individuals with passive (e.g. Postal Application) and active (“Personal Service Providers” feedback) for extra eyes and ears on individuals

• Applications to take active action for Individuals or Organizations (e.g. ”Information and Identity Services”,  “At Risk”, “Information Board”, “Community Information Board” , “Telemedicine”, “Remote Presence”) for emergencies (lost, injured, outages, disasters)