Baby Steps

As you view this Website, you will probably feel that the Initiative and System do look overly ambitious, complex, and a very large effort. This is an artifact of trying to show the potential of the System for a lot of different users. The System is really based on some basic System building block capabilities, and then allow different applications and devices to be built using them. This is similar to what has happened with Smartphones and Tablets, where basic building blocks of a computer, audio, video, and network have created millions of applications, many already in the Healthcare and Whole Healthcare space.

One of the Goals is to envision as much of the potential of the Initiative and System to be able to create a rich set of standards, tools, and hooks, to meet those goals, and empower others to create and add new capabilities to the System.

Rome was not built in a day and either is this System. The System is very modular and organic, allowing it to grow in different directions based on available resources and the interest in different areas. Using standards and some basic features, it can support multiple developers from different companies and organizations to create the building blocks and the associated applications and devices.

The System also envisions incorporating existing applications and devices through HW and/or SW gateways, as well as a rich set of Object Interfaces and Methods that can be incorporated into their products to make them compatible and provide them with a rich set of additional features and capabilities.

Step 1:

The initial step is to define the basic user interface for the System and create a rudimentary Identity and Information System (IIS). This will form the basis to create the initial base system. From here there are a wealth of additional system add-ons and applications that can be created, many that have not even been envisioned yet. Many of the envisioned Applications are identified could be created by Universities as department and student projects <Read more about potential University involvement>.

The ISS would be designed using existing technologies as a basis. The ISS would use Object based Methods, Interfaces, and toolkits on Smartphones, Tablets, and PCs, and leveraging off of their existing application services. Ideally it would also include cloud storage, and common login Services, to further reduce development, align with future capabilities, and provide additional security and availability.

This initial application will help in the location, identification, and special alerts about individuals that may not be able to communicate (dementia, Alzheimer’s, small children, severe injuries), as well as the location and identification of lost, misplaced, or stolen items. This could be a for profit or "name recognition" venture.

On the end-user side, the ISS would create a simple and basic Identity and Information System to allow people to register, order, and manage identity QR code and/or RFID tags to support an end-user defined display of information and their notification when one of their tags is scanned.

On the System side, it would create a portal for the accounts and data, and create a center that can take orders, print tags, and ship the tags using standard printers and mailing envelopes (as well as be able to respond to email questions).

The ISS would be designed with hooks to support future applications and tools, such as:

Support for the linking of IDs between different Organizations and groups
Linking and protections of different types data within and between different System deployments
Localization (multiple language support)

Some of the add-on Features that can be easily added include:

Postal App <Read more about the Postal App>
At-Risk APP <Read more about the "At Risk" App>
I Am OK APP <Read more about the I Am OK" APP>
“Electronic Fence” (to monitor when an individual enters or exits an area)
Event Logging and Audit Features
OA&M/NMS Features <read more about OA&M/NMS Features>
As well as linking Medical and a host of other Information that can be collected on an Individual that can be shared and analyzed

Step 2:

This is where initial Marketing material and definition of the Organization that will manage the Initiative. <Read more under the Vision Center tab>

This stage also includes the definition of additional standards, tools, and hooks, so that the other parts of the System can be created. Not necessarily developed, but defined to a certain level. Some of these can be adapted from existing tools and applications, while others have already been started.

These would include:

Data Definition, Protection, Collection, Storage, and Retrieval
General Analysis and Graphing Capabilities
Audio and Visual Aids
Personal Service ToolsTest, Demo, and Training Tools
Localization and Nationalization Services
Assorted Documentation

Step 3:

There are many different directions that the System and Initiative can take at this point. This is where there needs to be more input and

direction from the company, group(s), and/or organization(s) want to go, and prioritize the effort. This is where additional buy-in and acceptance from different industries and organizations, as well as the potential assignments of certain parts of the System could be assigned to different groups and organizations.