Google Health PHR and CCR Hacking

Ron Sweeney on 2010-06-02 21:56:58 UTC

Got to playing around with the Google Health API and got myself up to speed on the CCR architecture, im digging the “subsection” implementation of the document and like the RESTFUL ways of the force.

One quick point blares out about PHR’s that I particularly dont like:

1. The ability to put in your own result.  This may seem like the point, but flag it somewhere as “user inputted data.”  If you want to track your own health I see the point, but for a repository of “certified” and “bought and paid for” results leave them the way of storage commit.  Seems to me that if you mix the two data elements, ones inputted directly by a user, and data elements certified coming from a hospital or care provider, the whole value of the record depreciates in value.  If I were a diggy diggy doc, Id HAVE to take the data presented to me in the CCR with a grain of salt for legal survial and order all the tests again.  Physicians work with the concept of “study” not discrete results.

After being blessed with the development sprint for Google Health, I gazed over the way of HealthVault and made some observations.

1. HealthVault has a visions for use cases that are WELL thought out.  I think a lot of folks kind of scratch their head and say, yeah, well what is THAT going to do for me?


2. HealthVault does not have a dll you can slap in a GUI and use, its all web based.  There is a reason for this, but its a difference worth noting.


3. HealthVault device integration looks like it was built in the land of awesome.

With that being said, I have some homework to do with HealthVault, a follow up post is definitely in order.

With Google Health, I am pleased to announce that I was able to pull results from an ESB, then format it to CCR.  I was then able to apply an XSLT transform supplied by CCR Acceleration Resources Project over at sourceforge, and also jam it into my Google Health PHR.

I rock.

Web Service Calls with Delegation

Ron Sweeney on 2010-05-02 21:52:02 UTC

Anybody needing a snippet to asynchronously call a web service without freezing the app, its below. It may or may not be the right way to do it, but I’ve standardized on it for my own use.

The “”http://gist.github.com/271312">gist" if what is going on below is:

1. Provide a user action to fire off the web service call, in the class a button click. This builds a delegate instance.

2. Provide a method to begin invocation, this is the call itself, this is the beef of the web service call.

3. Setup a landing spot for the call, FinishResult. In here I do the activity indicators and what not that the call is complete, but I pass any of the results from the call to the Result Step.

4. The ResultStep has the result back which can be used throughout the app.

Enjoy.

Expensive Xpath Node Grabber

Ron Sweeney on 2009-12-03 08:54:00 UTC

I use this, you shouldn’t.

Im so enterprisey with my xpath and shit.

Call Buttons for Radiologists - Optimus 3

Ron Sweeney on 2008-05-19 16:35:00 UTC

Have you ever seen an "Optimus 3 Keyboard?":http://www.artlebedev.com/everything/optimus-mini/. Cool toy, fairly inexpensive, and can be hacked to work in about any environment... even Radiology. The idea here is to give some control outside of the diagnostic workstation, and offer a "press of the button" type service in the event of issue... and it was entirely possible due to the OSS Driver, "OM3 Controller":http://optimus.codecrater.at... What was I able to do with it? I was able to manipulate the buttons, change the status, fire on the events when buttons were "pressed" or "pushed" and even able to integrate it with a webservice for some cool interactions and notification ... In particularly, page a person, launch a 3rd party viewer, and also launch into a web workflow with the touch of a button. Cool eh?

Nokia 770 and openDicom.NET - Me Too

Ron Sweeney on 2007-01-07 15:39:00 UTC

Thanks to Shara Kalthoff’s response over at Albert Gnandt’s blog, I am now just as cool with the power of dicom-file-navigator on my Nokia 770 internet tablet. It’s as simple as 1-2-3. 1. Install the Mono Runtime (http://www.mono-project.com/Downloads) on the N770. 2. Download all opendicom-debian-packages, release 0.1.0. 3. Extract these debian-packages ( ar -x opendicomdebs*) and copy them to the N770. That’s it. From command line the dicom-file-navigator. Bask in the glory.