This is the fourth in a series of posts (first, next, previous) in which I am exploring five key technology themes which will shape our work in the coming decade: The Emergence of the Individual Narrative;The Increasing Perfection of Information;The Primacy of Decision Contexts;The Realization of Rapid Solution Development;The Right-Sizing of Information Tools. The Primacy of … Continue reading Five Key Technology Themes Which Will Shape the Coming Decade, Part 4: The Primacy of Decision Contexts
Tag: data architecture
Five Key Technology Themes Which Will Shape the Coming Decade, Part 3: The Increasing Perfection of Information
This is the third in a series of posts (first, next, previous) in which I am exploring five key technology themes which will shape and inform information technology work in the coming decade: The Emergence of the Individual Narrative;The Increasing Perfection of Information;The Primacy of Decision Contexts;The Realization of Rapid Solution Development;The Right-Sizing of Information Tools. … Continue reading Five Key Technology Themes Which Will Shape the Coming Decade, Part 3: The Increasing Perfection of Information
Five Key Technology Themes Which Will Shape the Coming Decade, Part 1: Purpose, Introduction, and Approach
Purpose Healthcare today is largely an information business. With the exception of the few moments of physical interactions with patients in diagnosis and treatment, prescriptions, and medical equipment, we all trade in information. Payers manufacture only good will. They sell and service a binding promise to pay some part of a person’s or family’s health-related … Continue reading Five Key Technology Themes Which Will Shape the Coming Decade, Part 1: Purpose, Introduction, and Approach
Your Knowledge Strategy: And Magic Filled the Air
In my last post, 'You Don't Need a Data Strategy, You Need A Knowledge Strategy,' I painted a high level sketch of why we need knowledge strategies, and the key features they need to address. I skipped ahead pretty quickly, rambling on<the time is now to sing my song /Zep> to cover a breadth of … Continue reading Your Knowledge Strategy: And Magic Filled the Air
You Don’t Need a Data Strategy, You Need a Knowledge Strategy
In my post "Throw Off Those 1960's Data Strategy Shackles" I suggested that the days of the Inmon/Kimball model strategy for analytics are past, sketched out a couple of notes on making events the atoms in our data strategies, and promised a longer answer to what our future states should look like. Continuing on that … Continue reading You Don’t Need a Data Strategy, You Need a Knowledge Strategy
At Any Event, or at Every Event?
Still on the trail of conceptual clarity around events. In the last post in this - this is the third, so let's say 'series' - we discussed the difference in knowledge and data. I used the familiar-to-most query against a relational database to illustrate the difference. Let's return to that example for a moment. The … Continue reading At Any Event, or at Every Event?
The Event Re-Renaissance Continued: Knowledge vs. Data
In my last post, we started digging into the re-emergence of complex event processing and event-driven architectures which has been enabled by the latest generation of stateful stream processors such as Spark Streaming, Samza, Kafka Streams, Apache Flink, and Google DataFlow. Today let's start to develop a clear line of sight into the underlying conceptual … Continue reading The Event Re-Renaissance Continued: Knowledge vs. Data
Throw Off Those 1960’s Data Strategy Shackles
(This is the first in a series of posts on data strategy. Next post here.) I’ve been reviewing and providing feedback on a number of data strategies lately, each presented as a future state ‘conceptual’ architecture which is mixed-level-of-abstraction Dagwood technology sandwich with an implied left-to-right flow. You know the kind of diagram I mean: … Continue reading Throw Off Those 1960’s Data Strategy Shackles
Health IT Architect 