Comments
yourfanat wrote: I am using another tool for Oracle developers - dbForge Studio for Oracle. This IDE has lots of usefull features, among them: oracle designer, code competion and formatter, query builder, debugger, profiler, erxport/import, reports and many others. The latest version supports Oracle 12C. More information here.
Cloud Expo on Google News
SYS-CON.TV
Cloud Expo & Virtualization 2009 East
PLATINUM SPONSORS:
IBM
Smarter Business Solutions Through Dynamic Infrastructure
IBM
Smarter Insights: How the CIO Becomes a Hero Again
Microsoft
Windows Azure
GOLD SPONSORS:
Appsense
Why VDI?
CA
Maximizing the Business Value of Virtualization in Enterprise and Cloud Computing Environments
ExactTarget
Messaging in the Cloud - Email, SMS and Voice
Freedom OSS
Stairway to the Cloud
Sun
Sun's Incubation Platform: Helping Startups Serve the Enterprise
POWER PANELS:
Cloud Computing & Enterprise IT: Cost & Operational Benefits
How and Why is a Flexible IT Infrastructure the Key To the Future?
Click For 2008 West
Event Webcasts
Controlling Your Personal Records
Controlling Your Personal Records

The health-care industry is about to lead the way in personalization, but I'm afraid their example won't be a good one to follow. In the wireless industry we discuss personalized content, commerce, and advertising. The principles and challenges are the same, and so is the solution.

According to an article recently published in The Industry Standard, the Bush administration has endorsed the sweeping medical privacy rules issued in the final days of the Clinton administration. The stunned health-care industry (which gave the Republicans over $25 million for the last election and lobbied vigorously against these regulations) says that implementation will cost billions of dollars and take more than the two years allowed. I believe it may take forever without incorporating three components that are key to all personalization and privacy schemes: permissions, synchronized data, and identification. They all need to work together to make medical records (and any other set of personal information) work for consumers, rather than against them.

Under these new rules, patients can request that custodians of their medical records provide an audit trail to show who has seen their health information. That means every doctor's office, medical insurer, and hospital must devise a system to track patients' data, and limit information released to third parties. But privacy is just one part of the new rules. They also require the adoption of uniform standards for electronic transactions by October 2002. To complicate matters, regulations have yet to be issued to establish standards to ensure the security of patients' medical information, as required by the law.

We talk about personalization in the realm of business to consumer (B2C), which usually takes one of two approaches: (1)How can a business maximize one-to-one marketing without offending their customers? or (2) How can customers use a tool or e-wallet to store and retrieve their information whenever they wish? This article addresses a different method, one I feel is needed in order to accommodate a future where the environment adjusts itself to the individual, not the other way around. It uses an ever-evolving set of shared, synchronized preferences geared to and controlled by the individual, yet doesn't depend on a device or even a relationship with an individual vendor.

Companies need a return on investment to justify the technology required to store and incorporate personalized information. Consumers need to control who accesses this information, and how it is used. Security is assumed as a given, and requires a whole different set of standards and implementation guidelines. This article focuses on how personalization can be maximized by vendors, yet controlled by consumers.

Let's use something less vital than medical records as an example. Renting a car is an experience that can already be personalized by signing up for a "premium membership" with a vendor. Once you fill out and send in the forms (with your personal information), renting a car is much more convenient. You simply call the car company (or go to their Web site), identify yourself, and specify when and where you want the car, and it will be waiting for you when you arrive, sometimes with the trunk open and the motor running. One more identification point (as you leave the parking lot) and you're on your way. All the credit card transactions, obtaining keys, or waiting in line are either eliminated or run "in background."

That is, unless you want to rent a car from a different company. Then you have to go through the whole sign-up process again. All that personal information that could be reused stays with the original company. From a consumer standpoint this is tedious, time-consuming, and downright boring. From a company standpoint it's an asset that will keep you coming back to them for your car rental needs. It's also a big roadblock to creating a personalized future, where a customer can pick a vendor, and the vendor automatically knows the right amount of personal information about the customer to provide him or her with the level of service desired.

The wallet approach is not the answer. Wallets get lost, they have to be managed, and as they get fat with the consumer's information, they get complicated. You don't want the rental-car company to know about your medical information, for instance. And having the individual companies keep track of your personal information beyond your control invites misuse. There must be a way to give consumers enough control, and vendors enough access over personalization. Let's start with the first of the three key components I mentioned earlier: permissions.

The concept of permissions has been around for quite some time. If you work in a networked company, you log in to your computer, which gives you permission to access some, but not all, of the company's data assets. You can look at Internet sites, for instance, but not at the human resources records of your fellow employees. Permissions are one key to enabling what I call shared personalization. The consumer can specify what information can be shared and what can't - by the vendor. Thus the consumer is in control of his or her preferences and other personal information, even though it's stored in a remote location. The consumer can specify, "This information (such as favorite destinations and airline seating) can be shared by all vendors, but this other information (such as credit card information) must be granted only by my permission. Ask me before you use it."

Then the information can be used only when the consumer is actually interacting with a vendor, unless the permission is stated differently. That way a portion of the consumer's information can be used for data mining by vendors; the rest can not. These permission points must become a part of the personalized information, so that each piece of information is branded with a permission and controlled only by the consumer.

The second key to shared personalization is synchronized data. The consumer's personal information must be available to all vendors so that when the consumer wants to interact with a new vendor, the necessary information is immediately available. Using synchronized data, a consumer can rent a car from any rental company, and receive the same convenience and rapid processing from signing up to driving out the gate. This requires a peer-to-peer synchronization server, one that stores and forwards the user's information to whoever needs it. Each time a consumer adds or modifies a piece of personal information, it would be synchronized - along with the consumer's permissions - with all the other servers that have that information. These servers would also provide an audit trail for what happens to every individual piece of information and who used it.

The third key is identification, and can exist in many forms, from the e-wallet that would contain all of a consumer's information (and also be part of the peer-to-peer synchronization described above). Or a consumer could use a unique number, fingerprint, retinal scan, or other method that would uniquely identify him or her as the owner of a set of personal information. In this way, even if a wallet was lost or unavailable, the consumer could still be identified, and receive personalized and hassle-free service.

Together, these three keys enable a system that would allow business vendors to offer the one-to-one services and marketing opportunities that they need, and enable consumers to control and tune just how personalized they want their interactions with vendors to be.

But why would vendors give up their customers' information? Why would consumers allow their data to be used for marketing and advertising? What's the incentive? For medical records, of course, the consumer incentive is apparent, as is the patient's need to control the flow of the information. For businesses, part of the synchronization server's process would enable a payment system, so that vendors and consumers could actually be paid for giving up the information.

And what about consumers who don't want to give up any personal information? They can set all of their information to private so they're notified each time the information is requested. Or they can continue to fill out the vendor's forms each time they initiate a transaction.

In order to implement a system that the medical and any other industry can use to share a consumer's personal information, standards must be set by the organizations that are already involved with setting standards for storing and retrieving information. They need to add standards for permissions and for identification that will enable a system such as the one I've described. It's not just for consumer comfort and vendor ROI. I want a world where the environment knows what I like and adjusts itself accordingly. But now it's more than convenience. It's about personal health, life, and death.

About Ron Dennis
Ron Dennis, Wi-Fi editor of Wireless Business & Technology, is a technology pioneer and a Palm fanatic. He's now reporting for WBT from the islands of Hawaii. He cofounded Livemind, Inc., led the third-party developers group at AOL, and created AOL's Web Hosting Service and Software Greenhouse. He has also guided several Internet startups.

In order to post a comment you need to be registered and logged in.

Register | Sign-in

Reader Feedback: Page 1 of 1

Latest Cloud Developer Stories
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, an...
SYS-CON Events announced today that Conference Guru has been named “Media Sponsor” of the 22nd International Cloud Expo, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. A valuable conference experience generates new contacts, sales leads, potentia...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (Clo...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enter...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood...
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
Click to Add our RSS Feeds to the Service of Your Choice:
Google Reader or Homepage Add to My Yahoo! Subscribe with Bloglines Subscribe in NewsGator Online
myFeedster Add to My AOL Subscribe in Rojo Add 'Hugg' to Newsburst from CNET News.com Kinja Digest View Additional SYS-CON Feeds
Publish Your Article! Please send it to editorial(at)sys-con.com!

Advertise on this site! Contact advertising(at)sys-con.com! 201 802-3021



SYS-CON Featured Whitepapers
ADS BY GOOGLE