I think that any ontology we create will have to be produceable in an
automated fashion from the FHIR artifacts. Any introduction of
hand-editing would be unacceptable from a maintainability and consistency
perspective. So we're looking at mechanical, no matter what. The question
is what the mec
Possibly a dream ontology would link to more other ontologies, such as
upper level ontologies, but other than that I view it as more of a
stylistic difference: more oriented toward a human conceptualization
that is natural to express in RDF (i.e., reflecting RDF's natural style).
But one probl
Lloyd,
Agreed that the FHIR/RDF would only be for FHIR. Other standard mappings would
be independent.
Tony
From: Lloyd McKenzie [mailto:ll...@lmckenzie.com]
Sent: Monday, December 08, 2014 3:03 PM
To: Anthony Mallia
Cc: David Booth; w3c semweb HCLS; i...@lists.hl7.org
Subject: Re: Minutes of la
Hi Tony,
Well, from a publication perspective, the RDF and OWL/etc. representation
of FHIR will become a core part of the FHIR specification and will not
include any v2, v3 or other aspects.
I think v3 is mostly done. V2 will be particularly challenging because
there's little consistency in how
Hi David
On 12/08/2014 01:35 PM, Lloyd McKenzie wrote:
>
>> I think we need to define our objectives for the RDF representation.
>> Mine are as follows:
>>
>
> Great list! My comments . . .
>
>
>> 1. It must be possible to round-trip from XML/JSON through RDF
>> representation
>>
>
> +1
>
> * Th
Lloyd and David,
We should formally collect the requirements for the effort.
Rob and I have started thinking about the vision of where this might go. Making
a transliteral or verbatim representation of FHIR is certainly a stepping point
but I believe that there are other mappings which need to
Hi Lloyd,
On 12/08/2014 01:35 PM, Lloyd McKenzie wrote:
I think we need to define our objectives for the RDF representation.
Mine are as follows:
Great list! My comments . . .
1. It must be possible to round-trip from XML/JSON through RDF
representation
+1
* This includes retaining inf
I think we need to define our objectives for the RDF representation. Mine
are as follows:
1. It must be possible to round-trip from XML/JSON through RDF
representation
* This includes retaining information about order of repeating elements
* Needs to allow for extensions where-ever they can appea
I'm so sorry I forgot to send these out last Tuesday, but here are draft
minutes from our call, with Eric Prud'hommeaux reviewing his FHIR
ontology approach:
http://www.w3.org/2014/12/02-hcls-minutes.html
and below in plain text.
Also, as a reminder, tomorrow's call (Tuesday) will continue with
Hi all,
On the call today we discussed the issue [1] of linking a symbol in
a triple (e.g. a subject, a predicate, *or* an object) to a dataset.
The use case for this is twofold : to provide a direct link between
data items and their datasets in a Linked Data manner, and to survey
the use of data
Summer/Fall 2015 Clinical Informatics Internship at Mayo Clinic Kern Center for
the Science of Health Care Delivery
Position Summary:
The Clinical Informatics Program at the Mayo Clinic Kern Center for the Science
of Health Care Delivery
(http://www.mayo.edu/research/centers-programs/robert-d-p
11 matches
Mail list logo