Josh,
Thanks very much.
I'll give the search tool a shot.
I'll follow up in a bit with an updated gist, but wanted to respond to 2:
This is my intuition as well.
I think what makes most sense for me, in putting all this together, is to have some kind of git-phr tool that creates and stores a serialized version of a single patient's ehr graph in a git repo. This helps me as the user retain control over who has made what changes to my medical record. I wonder if this makes sense to anyone on the smart/indivo side? Eg, serialize my graph, and use git to do audit tracking and establish transport independence? This way, all I have to do during my device check-in process is add data to my raw (text?/n3?/json?) records, update the manifest, and git commit; git push. I understand you are doing a per-record level type of write transaction using POST/PUT, but unclear how audit trails are captured.
Otherwise we are currently undertaking exactly the kind of inventory you suggest, will have more soon, I hope. I thought the finger sticks would be a nice entry point, it appears if I look hard enough many of our values will be there. I see that there are even codes for estimates and averages.
You may find the csv under the analysis/bewest-pump directory more useful. Some csv is from a test pump with little data. I updated the gist comments to help reflect this. I have additional data I'd like to upload soon; at some point I imagine someone will update our wiki or pages with this material.
Thanks very much!
HTH,
-bewest
On Sat, Feb 16, 2013 at 11:16 AM, Josh Mandel
<jma...@gmail.com> wrote:
Hi Ben,
Great work already, just pulling resources together! A couple of quick thoughts on LOINC codes and modeling:
1. You may have an easier time making sense of LOINC using either the online search tool (
http://search.loinc.org) or the downloadable program RELMA.
2. My initial instinct (which you may disagree with) would be to explicitly separate out "medical" data into glucose readings and insulin administration snippets; and then separately model the "device" data (battery status notifications; reservoir state, etc).
Where are they?
Best,
Josh