Agenda for 2012 – What’s so interesting, anyway?

I have a long and complicated relationship with blogs. My first attempt was in 1997, hosted on my personal site at Yale. The term “blog” was a couple of years from being coined at that point, so the site was a set of essays in the style of Philip Greenspun, who had recently invented Internet-based exhibitionism (in a good way). This was all wonderful but lead to one major problem – I didn’t really have all that much to say. I was in college, and still working on my first startup. So I was learning a lot, but I hadn’t come to very many firm conclusions. When I graduated and that site slipped off the Internet and was not much missed.

Subsequent blogs included a personal blog (2001-2003), an O’Reilly Network blog (now apparently lost to the web as well, although it did feature a great review of various trade show tote-bags), and blog I started when I went to MIT for graduate school. The latter was essentially killed when I took a job working on healthcare IT policy for the US Government, and was told that I really couldn’t publish on any topic which was in the general remit of my job or my agency. At the time, that was almost everything I was likely to have a comment on.

The original incarnation of info.rmatics (this blog) was a group effort with some colleagues. That worked pretty well, but we never came up with a consistent voice or focus. Readers who were interested in hearing about JavaServerFaces didn’t want to wade through discussions of FTC disclosure rules for breaches of confidential patient data. The reverse also applied.

The strange thing is that in more than ten years of blogging I never really allowed myself to just sit down and write about what was interesting to me at the time. If my ruminations are useful for other people, that’s great – I hope they are. But I’m not going to worry about making every post interesting for every potential reader (although you can always subscribe by category).

Here’s the list. Off the top of my head, at 1:10 pm, Friday, December 30th, 2011, as I sit in a Starbucks in Southborough, Massachusetts, waiting for the nice people from 1-800-Got-Junk to call me to confirm that they’ll be coming to pick up a large pile of old furniture from my wife’s old house down the road. This is a unique moment in time, and I reserve the right to be distracted by other bright, shiny ideas at any point:

Business

  • What’s fundable and what isn’t? What makes a start-up likely to succeed?
  • Angel Investing. How can you create a strategy around small investments in very early stage companies?
  • Sales and marketing. Simple products solving common problems are great. But what happens when you have a (moderately) complex product that solves a complex problem? How do you reach and educate your potential users.
  • Measurement – how can you tell when a team is doing well? What metrics are most useful for companies at any given size?
  • Customer Service – how can you create the best possible experience for your customers even if your resources are highly limited?

Healthcare

  • How can we make the healthcare system more consumer-friendly?
  • How can we take waste and repetition out of healthcare delivery?
  • How can technology make life more fun and rewarding for physicians? Today’s electronic health records and related tools are a burden for clinicians – rare indeed is the doctor who will tell you that their tools make them a better physician.
  • What’s the government up to?

Software

  • What makes a software development team successful?
  • How can groups of stakeholders – developers, users, designers, testers, managers and others – communicate their ideas cleanly and effectively? Previous experiments in this area helped spawn the Clickframes project.
  • How do you hire and retain a talented software development team?
  • What’s the best way to use Microsoft technologies to build a scalable web-based application?
  • What’s up with HTML5 and JavaScript? The old patterns for building web applications are clearly obsolete. Books that I wrote six or seven years ago (and which provided great advice back then) are not merely out of date, they’re positively dangerous.

Everything Else

  • Cameras. Cool technologies. Current affairs.

And so that’s the agenda for 2012 and beyond.

 

Yes, it’s been a little quiet around here…

Summertime, and all that. However, the big reason has been the impending release of a pretty major project we’ve been working on for the last several months. We took a couple of government databases, some existing systems at Harvard Medical School, the latest lightweight, web based productivity tools, put them all in a blender, and kept the really good bits.

It’s not available to the public yet, but we’re planning for later in August – development is done, and we’re in integration and scalability testing right now. If you do academic research, you’re going to like this this one.

In the meantime, blogging to intensify.

Wordle for the Blog

I’m actually not that big on visualizing data. Some people are textual thinkers, and that’s the category I tend to fall into.  But good visualizations are powerful things, and that’s one reason I like tag clouds – words made into a picture. Everybody’s happy.

Which is why I spent a little too much time last night playing with Wordle, a service that lets you take a bunch of text and make a cloud out of it. Here’s one I made using the RSS feed for the blog:

The info.rmatics wordle

It looks like we’re pretty interested in open source development, health, and Twitter.

Welcome Chilmark Research visitors!

John Moore probably just quadrupled our readership overnight. Welcome!

Coming up, we’ve got our first post from somebody other than me, and our first venture into technical content: Steven Boscarine’s explanation of how to use Maven and other open source tools to dramatically speed up a critical part of the software development cycle for Java.  I’ve read it, and it’s good!  Steven, by the way, is a Principle Engineer in the Informatics Solutions Group at the Children’s Hospital Informatics Program, where we’ve been using this technique to great effect.

Most Chilmark readers may be more interested in the healthcare policy and HIT topics, but don’t worry, there’s plenty of that on the agenda as well.

Another HIT-focused Site Worth the Follow « Chilmark Research.

And we’re off!

I wrote a blog for two years. It was called “The Integrative Stream”, and it ran to 170 posts, some of which were marginally interesting. That blog stopped in 2006 for a very simple reason – I moved down to DC to spend a year working for the US government, as a member of the policy staff at the Centers for Medicare and Medicaid Services. Working for the government is an interesting experience, but it has a couple of drawbacks. One is that you’re not supposed to publish anything related to your area of responsibility without going through many, many layers of approval. My blog, which focused on the healthcare and software businesses, certainly fell into that category.

So now it’s 2009.  After my year in government I moved back to Boston, and started working on a project to build a “Translational Informatics” group at the Children’s Hospital Informatics Program. Starting with projects in the Personally Controlled Health Record area, we built up a great team, and developed some interesting new technologies and processes for doing software development, better, in healthcare. It’s a great team, and when I started thinking about doing a blog again, I decided to invite them all to join me.

So we’ve got quite a group: a software architect turned MBA healthcare policy wonk, a couple of computer scientists, a user interaction designer, and a doctor. They’ll introduce themselves over the next week or so, and this blog is going to cover quite a few areas. At one end of the spectrum, we’ll look at companies and business models in the Health IT space and policy issues for promoting the use of technology in healthcare.  But we like to do things on the ground, so we’ll be covering a lot of brass tacks topics too. So expect to see Java code, thoughts on the software development process, and explorations of user-centric, goal-oriented design as applied to healthcare software. There may also be recipes.

Should you read it? Yes. Obviously, the healthcare policy audience may not be interested in software development processes or neat Java tricks, so we’ve organized the blog into categories that should make it an easier read.  If you have any suggestions or comments, you can reach us at info (AT) rmatics.org.