>
>
> It seems to me that privacy needs to be addressed at the level of
> protocols and policies. What are you suggesting relevant to
> vocabularies, such as schema.org?
>
well, the vocabularies often need to support this. The most relevant
thing is to tag the information with consent to share in
tion and PoC as you will see in
> pointers from the minutes.
>
> Kind Regards,
>
> * Marc *
>
>
>
> From:Grahame Grieve
> To:Marc Twagirumukiza/AXPZC/AGFA@AGFA
> Cc:r...@iannel.la, "i...@lists.hl7.org" , w3c
>
people are already trying to use FHIR as a standard for sharing their
healthcare data for research. While organizations can't share other
people's data in public, there's plenty of anecdotal evidence that the
people will do it themselves. So the use case isn't impossible, it's only a
policy questio
well, this is tricky. technically, it's not strictly required, but it's a
lossy transform (lossy in both ways, in fact). One of the attractions of
fhir;reference for me is that you can have an absolute reference for RDF
and preserve the original fhir url
Grahame
On Wed, Apr 27, 2016 at 3:01 AM,
Hi Eric
We already do - the rdf page in the spec, and the generated turtle files
are supposed to do this. Once we stop iterating on the instances, I will
bring all that up to date
Grahame
On Wednesday, 16 March 2016, Eric Prud'hommeaux wrote:
> * David Booth > [2016-03-14 18:35-0400]
> > Agend
hi David
I think my comment may have created more concern than is warranted. RDF
> does have named graphs, which we could use to delineate a certain set of
> triples. But we haven't been doing that for FHIR RDF and I don't think it
> is needed either. In practice, the FHIR resource that you get
f decoupled systems will recieve U without knowing they'd
> dereferenced a link to a FHIR resource?
>
>
> In principle, we also have to convince ourselves that the benefit of
> f3 exceeds the deployment pain teaching existing RDF tools about a new
> "+turtle" convention. Th
:
> Yes, there is no explicit way to tell whether a URI itself represents a
> FHIR resource. However, the way you get the URI tells what the URI you're
> about to request is for.
>
> Regards,
> James
>
> On Wed, Feb 17, 2016 at 9:30 AM Grahame Grieve <
> grah..
can easily figure out what the
> URI represents. Your search criteria or a property that links one resource
> to another says what the URI is for.
>
> Best regards,
> James
>
> On Wed, Feb 17, 2016 at 9:08 AM Grahame Grieve <
> grah...@healthintersections.com.au> wrote:
a fhir:AllergyInterance resource, for example.
>
> Actually, I'm noticing that our current example is lacking the explicit
> mention of fhir:AllergyIntolerance, so I've raise an issue about that:
> https://github.com/w3c/hcls-fhir-rdf/issues/8
>
> David
>
> On 0
le to look at the RDF triples to see that it contains a
> > fhir:AllergyInterance resource, for example.
> >
> > Actually, I'm noticing that our current example is lacking the explicit
> > mention of fhir:AllergyIntolerance, so I've raise an issue about that:
>
hame
>
> With RDF, you retrieve it and make rules that apply to the
> vocabularies used in it (properties, types etc).
>
> On Tue, Feb 16, 2016 at 8:10 PM, Grahame Grieve
> wrote:
> > So how do you know that a piece of turtle is a resource? The theory of a
> > restf
So how do you know that a piece of turtle is a resource? The theory of a
restful interface is that you make rules that apply to a mime type, but
evidently not in the case of rdf...
Grahame
On Wednesday, 17 February 2016, David Booth wrote:
> Hi Grahame,
>
> On today's call
> http://www.w3.org/2
Correct. javascript does not retain the precision
Grahame
On Wed, Aug 5, 2015 at 6:53 AM, Andy Stechishin
wrote:
> James,
>
> Am I correct in thinking that Javascript does employ a library to do JSON,
> it is part of the language and as such, would not retain precision using
> the current form
stated otherwise, the opinions and positions
> expressed in this e-mail do not necessarily reflect those of my employer,
> my clients nor the organizations with whom I hold governance positions
>
> On Tue, Aug 4, 2015 at 7:39 AM, Grahame Grieve <
> grah...@healthintersections.com.au>
yes. It appears that for some tool stacks, the code generation schemas
might need to use xs:string instead of xs:decimal - but not others. So I
think that we should make a note about this in the code generation schemas.
Grahame
On Tue, Aug 4, 2015 at 11:36 PM, Lloyd McKenzie wrote:
> I think t
t; owned by the FHIR Infrastructure group, and co-sponsored by M&M and ITS,
> instead of being under ARB, though it is fine for it to start under ARB.
>
> - We added some additional names to the Project Team: Grahame Grieve,
> Lloyd McKenzie and Rob Hausam. Grahame was the only one whose na
HI David
I cannot let this go by without some comment.
Therefore implementers are required to create their own workarounds to
> bridge these standards and overcome the incompatibilities. However, because
> implementers use different approaches, data still lacks interoperability
> between implemen
you thinking of a new
> representation unique to FHIR?
>
> Claude.
>
> On Tue, Mar 24, 2015 at 1:21 PM, Grahame Grieve <
> grah...@healthintersections.com.au
> >
> wrote:
>
>> I don't think that we could decide that servers SHALL do RDF
>> I had ex
I don't think that we could decide that servers SHALL do RDF
I had expected that we'd define an RDF format directly rather making it a
transform from one of the existing formats - but, in fact, if we have a
transform from one of the existing formats, it's just a question of who
runs the transform?
gt; think an @context can produce any implied triples.
>
> Another choice point for this idea is whether to allow @context lines in
> the brief JSON. Two downsides of allowing them: (a) regular JSON
> processors would have to ignore them; and (b) it may be confusing to allow
>
I'm not sure that I undestand this discussion. Every Fhir structure
defintion and value set (and other definitional resource) already has an
IRI.- it's an inherent part of the design. So the IRI for the structural
definition of patient is http://hl7.org/FHIR/StructureDefinition/Patient.
All valuese
22 matches
Mail list logo
