W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > March 2010

Re: semantic web for EHRs

From: conor dowling <conor-dowling@caregraf.com>
Date: Fri, 12 Mar 2010 09:08:34 -0800
Message-ID: <fdad151a1003120908vb49165bi9d814a4fae6ed31b@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: public-semweb-lifesci@w3.org
> Now, on the face of it, such data is meaningless outside this VistA. We
>> need a "mapping layer", an "RPC". A "type-mapper". A reformatter. Layers ...
>> BUT WE KNOW (on this group) that it is trival to do something like ...
>>                        :120.51/1 ---- same as -----> SNOMED:392570002
>> and heh presto, your vitals are "linked". Were Christopher lucky enough to
>> end up in the Cleveland Clinic then this and his other data would be trivial
>> to query - no longer site or even VA-specific.
>>
>>  Is there going to be an RDF model based Linked Data View over this data?
> Or are you looking for help re. Linked Data publishing etc?
>

Kingsley, the OWL representation of the VistA schema is one of a number of
steps needed to round out FMQL - there's a rough list:
http://www.caregraf.org/semanticvista/fmql-specification#Profile

Right now, I need advise on the best way to demonstrate linkage such as the
above - a VistA data dictionary linked to standard dictionaries, VistA
Vitals -> SNOMED equivalents. VistA immunizations to CVX etc.

Are such standard datasets (SNOMED, RxNORM) in public end points already?
Where's a good list of what's available? I want to minimize local "mirrors"
- I've played with a few at http://www.caregraf.org/datasets and I could put
SNOMED etc in there but want to avoid any and all duplication.
Received on Friday, 12 March 2010 17:09:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:00:58 GMT