Writing an EHR facade for a web application

[Bayard Randel]

Hi there,

Would hData be the appropriate technology to use for writing an
intermediate api between an emrs and a web application? I current work
on a clinical decision support system that pulls data from an emr that
has a proprietary javascript api. The API is very poorly defined, and
what I've done is to create my own representation of a patient in the
form of a javascript 'patient' object. I am doing this on the client,
but what I think would be an improvement would be to have a restful
webservice that I could deserialise a json patient object from in some
kind of standardised form. I must admit I find most of the HL7
architecture documents completely baffling, and am really just looking
for a pragmatic simple solution.

thanks for your time!

[George Lilly]

You should take a look at the SMArt framework. It is very like hData but is focused on just the kind of "container" that you describe.

http://www.smartplatforms.org/

... and it's open source.

gpl

[Bayard Randel]

This looks interesting, thank you George!

On May 31, 10:28 am, George Lilly <gli...@glilly.net> wrote:
> You should take a look at the SMArt framework. It is very like hData but is
> focused on just the kind of "container" that you describe.
>
> http://www.smartplatforms.org/
>

> <http://www.smartplatforms.org/terms#Participant>... and it's open source.

[Sam]

Hi Baynard

The problem you are addressing is a massive one and applications have
found it very difficult to do this. The reality is that you need some
sort of logical model that you subscribe to and then go get what you
can. If enough people subscribe to the logical model things will get
easier.

I work on the openEHR approach (openehr.org) which means we define the
content in terms of a relatively simple model (RM). The approach does
allow for APIs to function (RM classes only) with queries being
determined by the content definitions (called archetypes in openEHR).
So you have a way of querying and writing to the EHR that is
independent of the actual repository format. Obviously openEHR ready
repositories can use the APIs natively.

I guess you can think of the models as microformats but the RM
provides much of the power. I have copied Thomas Beale who may be
worth calling to get a better understanding.

Cheers, Sam

[Salvatore D'Agostino]

Does the recent investigation/guidance on xcert impact?

On Jun 4, 2011 7:18 PM, "Sam" <sam....@oceaninformatics.com> wrote:

Hi Baynard

The problem you are addressing is a massive one and applications have
found it very difficult to do this. The reality is that you need some
sort of logical model that you subscribe to and then go get what you
can. If enough people subscribe to the logical model things will get
easier.

I work on the openEHR approach (openehr.org) which means we define the
content in terms of a relatively simple model (RM). The approach does
allow for APIs to function (RM classes only) with queries being
determined by the content definitions (called archetypes in openEHR).
So you have a way of querying and writing to the EHR that is
independent of the actual repository format. Obviously openEHR ready
repositories can use the APIs natively.

I guess you can think of the models as microformats but the RM
provides much of the power. I have copied Thomas Beale who may be
worth calling to get a better understanding.

Cheers, Sam

On May 31, 6:42 am, Bayard Randel <k...@nocturne.net.nz> wrote:
> Hi there,
>

> Would hData be the ...