Information Delivery is in essence the baseline structure of how an individual (or User) based current state of life is captured, maintained, and used as a foundation for information delivery. This innovation uses layers of categories, attributes, and sub-attributes to capture and store information about a person’s life. These categories and attributes include ALL aspects of a person’s life. For example, demographic information relating to your sex, age, ethnicity, etc. is all captured, as well as what types of sports you like, movies you watch, movies you own, health information, political orientations, schedules, hobbies, work, relationships, your family, your children’s sports and interests, and much more. If you’re thinking, “Wow, that’s a lot of information to store about me”, you’re right! Read on, as security, encryption, and privacy are key foundational assumptions in SpotMi.
As you might assume, this is a lot of information for a person to keep track of. Again, you’re right, it is. Again, there are countless options of how Organizations might choose to work through this, but one way we see as an option is to use Application Program Interfaces or APIs. APIs are programs that are built to load and standardize the flow of information between two entities.
The first thing APIs do is that they allow large amounts of information to be loaded between two entities, since they are programs that run and automate the entry of information. Depending on the speed, processing power, etc., APIs can load thousands of records in minutes, even seconds. The next thing APIs do is they ensure that the information that is loaded uses a common structure. So if two entities are sharing information about an apple, the API ensures that the two entities understand how the information about the apple will be shared.
For example, one organization might send information about the apple it will sell to another (maybe a User). There may be a bunch of attributes about that apple, and even the name of the apple or how it’s identified might be different between the Organizations (the apple might just be called “apple” or it could be “Red Delicious Apple”. Because of this, the Organizations define the API, which allows them to agree on each piece of information. For example, a record for the apple might look like the following:
Description: Apple, Non-Organic, Red Delicious
This standardization is important as there are many permutations of how one might reference the apple or the different varieties of the apple. There are also differences in opinion on the types of information, extent of information, etc. The API addresses all of these. So accordingly, between the use of APIs and a User making updates and/or refinements, is more than sufficient to ensure that the information about the User is available.
So now that we have every part of information available about a person’s life, we need to ensure that it’s secure and accessed properly. A key component of SpotMi’s innovations is that not only does your information have security and encryption, but there is also the capability that a User can determine which parts of their information are accessible, to who they’re accessible, and to what extent. That means that if a User wanted to keep all of their health information confidential, yet make their entertainment preferences public, then that can be done. If a User wishes to make information like a specific ailment viewable only to their doctors, and everything else confidential, that’s also possible. Any combination of general categories, attributes, or sub-attributes can be made accessible, or confidential. And that’s only the beginning.
These security controls are highly customizable, so a User can custom define how long the information can be used, and how the information can be used. This means if a User desires to allow information about career and job seeking to be used by recruiting firms and Organizations looking to hire, but not available to the User’s current employer or other people that work for the employer, that’s also possible.