Dion Hinchcliff over at ZDnet had a thought provoking post Who should be in charge of Enterprise 2.0? It provides some interesting insight into the value and approach various organizations have to their collaboration strategy. I’ve stated before that Enterprise 2.0 is a term I have problems with, but the concept of collaboration is still important.
The post did make me ask other questions like:
- Who should be measured on the value and effect of Enterprise 2.0 within the enterprise?
- Who would do the measuring?
- What kinds of metrics would be important for an organization to assess their progress?
- What other IT initiatives should be linked with collaboration?
These issues have been talked about for quite a while, and just like the “Who’s in charge?” question the answer always seems to be it depends. I do firmly believe though that organizations need to have objectives for their collaboration approach. Something beyond “let a thousand flowers bloom” and then assess progress periodically, after all collaboration can take many forms. If you don’t have expectations and adjust based on performance, it's more of a hobby than a business activity.
To me this means there needs to be someone steering the boat, even if it may take it a while to turn the ship.
HP Labs has introduced what it calls a "geo-tagging experiment". The experiment, which has been dubbed Gloe, has the goal of tying web content to a person's location. HP is showcasing the capability on the Android and Blackberry - since HP is buying Palm maybe it will be on WebOS soon as well.
This geek.com article has numerous screen shots and background information.
The application implements a geo-aware browser with numerous features:
- "Pre-populated content from Wikipedia, review and photo sharing sites. The index of locations and content is already large and smart.
- Automatic tag-clouds to see content type by category.
- A bookmarklet lets you add any content from around the web to the database, tied to a specific location on the map. This part is barely usable, but it's a great idea.
- Google Gears support to add geolocation to your laptop browser.
- Facebook Connect integration to provide either universal or friend-network views of what's most important in a location.
- Vote budgeting, allowing you to put multiple votes in favor of an item in case it's extra important to you that it gets voted up.":
Since it is has a whole toolkit (API) of capability to support Gloe:
And it should be easily expanded in other ways as well.
I was reading SD Times the other day while riding an exercise bike at the gym (hey, you have to do something to keep your mind occupied) and I came across an article on the Open Mashup Alliance. I had quite a number of questions about the OMA. Although it is not really a standards body, OMA is working to create a standard for the creation of mashups.
This standard is called Enterprise Markup Mashup Language (EMML).
"EMML is a Domain Specific Language (DSL) that was designed specifically to address the important characteristics that make mashups easier to create and reuse:
- EMML is a declarative XML-based language and, as such, leverages and complements existing XML capabilities inherent in XQuery, XPath, and XSLT.
- EMML has been in development for several years. It also has already been tested in dozens of real-world production mashup implementations.
- EMML is an open language specification. This type of common and free-to-use language (and technologies that embed or use it) have a much better chance of meeting the needs of enterprise developers than a proprietary language."
I was surprised and pleased to see that HP was a member, working on this. I guess I'll have to track those folks down.
There are some people who view this consortium positively, while others are a bit more cautious. Mashups have become a standard technique to generate useful information from various sources across an enterprise or a business. Even though formal mashups are relatively immature, having a standards effort should help improve the quality and predictability of results. It's definitely something I'll keep watching.
There is a good interview of Tim O'Reilly that validated many of the posts we've made in this blog over the last 5 years. He also published a white paper that goes into more details.
The way business value is generated in the future will be changing, as we have the intersection of sensors and edge computing with large databases of information and context. The kinds of skills needed by the personnel will be changing as well. As value is generated by having people focus on the unique aspects of the business instead of being involved in "normal". Some may think this mimics science fiction, but really it will just become the new normal.
The interview provides some good examples and greater understanding of a holistic view of the intersection of technologies that we'll likely see coming out of this downturn.
In 2008, the Department of Defense (DoD) developed a prototype, Personal Health Record (PHR), and piloted it at Madigan Army Medical Center (MAMC). A PHR is typically a health record that is initiated and maintained by an individual.
MiCare is designed to help members of the military and their families more effectively to manage their health and wellness, regardless of their location. They will need to seek care inside and beyond the Military Health System. In essence, MiCare serves as a patient-centric health record, aggregating documentation and information from all sources of healthcare in a location accessible to the beneficiary. Based on the success or the pilot, the DoD is now determining how to expand it more widely according to InformationWeek.
It is important to note that PHRs are not the same as EHRs (Electronic Health Records). An Electronic Health Record (EHR)refers to an individual patient's medical record in digital format. The Veterans Affairs (VA) EHR system is called the Veterans Health Information Systems and Technology Architecture (VistA). Like the data recorded in paper-based medical records, the data in EHRs are legally mandated notes on the care provided by clinicians to patients. There is no legal mandate that compels a patient to store his or her personal health information in a PHR.
Can the combination of a patient maintained health record like MiCare and a clinician maintained health record like VistA provide a new model of Health and Wellness Record (HWR) that improves wellness, quality, care, and reduce overall healthcare costs?
Let's hear from you.