W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > September 2011

Re: A Fresh Look Proposal (HL7)

From: M005994 <Jiang.Guoqian@mayo.edu>
Date: Mon, 19 Sep 2011 20:35:18 -0500
To: "Hau, Dave (NIH/NCI) [E]" <haudt@mail.nih.gov>, Kerstin Forsberg <kerstin.l.forsberg@gmail.com>
CC: Jim McCusker <james.mccusker@yale.edu>, conor dowling <conor-dowling@caregraf.com>, "public-semweb-lifesci@w3.org" <public-semweb-lifesci@w3.org>
Message-ID: <CA9D5806.4BF8%Jiang.Guoqian@mayo.edu>
FYI...

We at Mayo had some preliminary investigation on representing HL7 detailed
clinical models using OWL through levering the ISO 11179 standard.

We had an AMIA proceeding paper about this topic available at
http://proceedings.amia.org/16p9j9/1,

-Guoqian


On 9/18/11 5:46 PM, "Hau, Dave (NIH/NCI) [E]" <haudt@mail.nih.gov> wrote:

> Thanks Kerstin.  The DCM spreadsheet is informative for me.  There are several
> clinical model sources I had not known previously.
>  
> I think the DCMs or archetypes could potentially be defined as graph patterns
> via SPARQL queries, involving concepts from standard domain ontologies.  These
> DCMs could be resources exposed by REST as documents in sections according to
> the hData record proposal.  In addition to that, the SPARQL endpoint could be
> a query resource in the REST service as well, supporting more granular queries
> or for other graph queries, under an access control mechanism.  The SPARQL
> query for a DCM would provide a level of semantic validation for a submitted
> RDF.  Further validation could be via the Pellet Integrity Constraint
> Validator (ICV) for example, involving reasoning on the data definition
> together with the value set as we discussed before.  Any other thoughts or
> comments are welcome!
>  
> - Dave 
>  
>  
>  
> 
> From: Kerstin Forsberg [mailto:kerstin.l.forsberg@gmail.com]
> Sent: Sunday, September 18, 2011 6:21 AM
> To: Hau, Dave (NIH/NCI) [E]
> Cc: Jim McCusker; conor dowling; public-semweb-lifesci@w3.org
> Subject: Re: FW: A Fresh Look Proposal (HL7)
>  
> 2011/9/18 Hau, Dave (NIH/NCI) [E] <haudt@mail.nih.gov>
>> 
>> Jim, I was thinking more about units of content as in a container storing
>> properties from different classes, for a clinical purpose.  The classic
>> example here is when an EHR needs to store or report a blood pressure
>> measurement, what are the various data elements that need to be reported to
>> provide enough context to interpret the reading.
> 
>  
> 
> Here's a nice overview of Detailed Clinical Models
> 
> https://docs.google.com/document/d/11xGZs4drfwb7TY15Iwpk52UIxZcFhqMcMp1i3yV4To
> 8/edit?hl=en_US&pli=1
> 
>  
> 
> For the classical BP, and other Vitals Signs examples, it would be interrsting
> to see see a real example of clinical data using the BFO based Vital Signs
> Ontology
> 
> http://bio-ontologies.knowledgeblog.org/155
> 
>  
> 
> Kerstin Forsberg
> 
> AstraZeneca  
> 
Received on Tuesday, 20 September 2011 01:35:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:21:00 UTC