Hi David
Not sure what you mean by too fine... If you are planning not to
atomise any data and just communicate in blobs then you are right!
openEHR can handle blobs but is designed to enable recording of
atomised, validated and computable data which is obviously what you
would need to enable true communication between systems.
regards Hugh
David Guest wrote:
Andrew
wrote:
Your idea of tipping the database fields into the pot is exactly what I
thought of years ago but had no idea how to describe it so succinctly.
Well done.
Now all we need to do is to get NEHTA (or whatever they are called this
week) to achieve it.
Or
We could go to the next conference were most developers will attend,
Jointly sponsor a dinner for them,
Get them all tipsy and work it out in one evening.
Much cheaper for the Australian taxpayers, and as long we only serve
red wine at the dinner , better for everyone’s health.
Andrew.C
PS: who’s up to sponsor ?
While waiting for the Feds to finance the Common Electronic Health
Record format, I was wondering if anyone had views on what it should
look like. I presume openEHR is focussed on the micro level which may
be too fine for our purposes, but some of the NEHTA, Standards
Australia documents describe the transmission of medical data and so
have an underlying data model.
I think Horst, Ian and presumably JJ have looked at this in the past so
I would be interested in what the consensus was.
David
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
__________ NOD32 2355 (20070626) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
|
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
