- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Wed, 21 Jul 2010 10:01:39 -0400
- To: conor dowling <conor-dowling@caregraf.com>
- Cc: public-semweb-lifesci@w3.org, Ben Adida <ben@adida.net>, "Zabak, Steve" <Steve.Zabak@childrens.harvard.edu>, Thomas Gambet <tgambet@w3.org>, Michel_Dumontier <Michel_Dumontier@carleton.ca>
* conor dowling <conor-dowling@caregraf.com> [2010-07-18 21:20-0700] > Eric, > > sorry, if this is a "late to the party" question - is this to translate the party's just starting, as far as i know. > records of existing patients coded in this XML form (indivo) into > equivalents in RDF OR is it to go the other way? both, in fact. TMO has some cooked up patient records in an XML structure. that structure had a bit of resemblance to Indivo, but was mostly made up within the group. a while ago, i XSLT'd that stuff into an equally made-up RDF structure. i wanted to clean that XSLT but reallized that what i really wanted was an XSLT from Indivo to TMO. i'm pushing the XML into an Indivo structure and then I'll work on XSLT from that to Indivo. > I ask because right now, I'm involved in turning RDF graphs of patients into > CCDs, which though CCDs appear (all that markup, mostly static) more complex > than the CCR-like schema you're using, is, I think, the same task - if you > are going RDF to XML-document flavor: take a graph of patient data, it chief > nodes, its bnodes and subordinate nodes and serialize into some flavor of > schema'ed XML. is it reasonable to do that with SPARQL queries and then an XSLT of the resulting XML structure? > Conor > > -- > Caregraf promotes "Semantic Health": http://www.caregraf.org > > On Sun, Jul 18, 2010 at 7:56 PM, Eric Prud'hommeaux <eric@w3.org> wrote: > > > Thomas Gambet and I have been transforming the XML patients (ordinary > > citizens like you and me, tragically afflicted with XML) to follow the > > Indivo schema. Indivo uses a bunch of small schemas to represent > > e.g. contacts and problems, so we've put together an envelope schema > > which references the Indivo schema for most of its meaty data. We > > still have some coding to go, but folks can go take a look at > > data: > > > > http://dvcs.w3.org/hg/TMO-Indivo/file/tip/syntheticPatients/AD_PCHR_1-indivo.xml > > schema: > > > > http://dvcs.w3.org/hg/TMO-Indivo/file/tip/syntheticPatients/indivo-schemas/envelope.xsd > > > > Places where the envelope schema reference other schmeme types, e.g. > > <xs:complexType name="PrescriptionsType"> > > <xs:sequence> > > <xs:element name="Prescription" type="indivo:Prescription" > > minOccurs="0" maxOccurs="unbounded"/> > > </xs:sequence> > > </xs:complexType> > > , have been mapped to Indivo. Places where we have lots of elements > > defined didn't have a pre-existing Indivo schema. Lots of thanks to > > Thomas for working on this stuff. > > > > Folks in the HCLS IG have commit privileges on this Mercurial > > repository. Once we finish coding the patient encounters, we'll get > > serious about mapping out the patient RDF ontology. The XSLT we use > > for this will also be useful for mapping anyone's Indivo data to RDF. > > > > Thoughts? Suggestions? > > -- > > -ericP > > > > -- -ericP
Received on Wednesday, 21 July 2010 14:02:17 UTC