Saturday, August 27, 2011

Changing Roles

Healthcare IT is different from other IT in that our customers typically operate 24/7. Thus, our maintenance windows are usually in the wee hours of the morning. You cannot work on healthcare IT any other time.

I've been involved in these early morning sessions for eight years. In my new role as architect, I don't have any real work to do. But, old habits die hard. We performed a maintenance change to a customer's Master Patient Index (MPI) earlier this week. We were able to start that process shortly after 9pm, which is when the last clinic closed. I joined the bridge line and watched the webex as the team worked through the process. I recorded start and stop times for each of the steps in the process and produced a summary for leadership. Even though I wasn't actually at the keyboard doing the work, I felt that just being there and contributing one or two suggestions showed the team that I was part of the team.

This weekend, we are upgrading one of my sites and activating another. The window to perform this work begins at midnight on Sunday morning. I'll try to dial in and listen to progress. I work with a great team, so they will be successful.

ONC S&I Framework Face to Face Meeting in October

This arrived in my inbox yesterday.

I attended the first ONC S&I Framework Face to Face Meeting in DC back in June. I'm not sure that I will get to go to this one, but I will put in the request. I am one of the team leads for the CDA Implementation Guide Documentation Work Group.

Our next S&I Framework is just around the corner.

Make sure you mark your calendars so you don't miss these important working sessions.

See the attachment or contact us via email for more details.

We hope to see you in Arlington in October!

ONC October F2F Support Team

S&I Framework F2F Meeting | October 18-19, 2011
Hyatt Regency Crystal City at Reagan National Airport
2799 Jefferson Davis Highway, Arlington, VA 22202

ONC S&I Framework F2F

Tuesday, August 2, 2011


I was reviewing the HL7 ballot that opened this week and noticed something interesting. HL7 is ballotting an Emergency Medical Services (EMS) Domain Information Model. Among the items in this model is one titled "Automated Collision Notification." This model is described like so:

"This package represents data from automobiles equipped with automated telematic systems. When a vehicle so equipped has a collision, the system reports information to a central provider, who may forward the information to an emergency dispatch controller in the vicinity of the incident. "

Now, I started work for Covisint in May. Covisint developed and operates OnStar for General Motors. So, we are the "automated telematic system" that this standard talks about.

The way that this would work is like so:

* OnStar vehicle is in a collision.
* Message is sent from Vehicle to OnStar
* OnStar operator contacts the vehicle and gathers additional information.
* If necessary, the information on the collision and any injuries will be sent electronically to the EMS (instead of a phone call as happens today).
* This information can also be cc'd to the nearest Emergency Department to let them know
* The EMS can also enter additional information on what they did at the scene before transporting the patient(s) to the ED. This information can also be sent electronically to the ED that the patient(s) will be transported to.

So, we have most of the infrastructure in place. We'll just be adding electronic messaging of the information to the process.

This is still early in the process. The standards won't be ready until sometime next year, at the earliest. But, we should be able to implement this when the standards are done. If we make this work, it will save lives.