W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > May 2016

Re: FHIR on schema.org

From: Marc Twagirumukiza <marc.twagirumukiza@agfa.com>
Date: Fri, 27 May 2016 09:31:45 +0200
To: r@iannel.la
Cc: "its@lists.hl7.org" <its@lists.HL7.org>, w3c semweb HCLS <public-semweb-lifesci@w3.org>
Message-ID: <OF5CE39FC9.F89B391B-ONC1257FC0.0028C56C-C1257FC0.00295C07@agfa.com>
re:https://schema.org/Physician


Hi Renato, 
Some of your thoughts need a deep discussions. Can you attend one of 
ScheMed or FHIR RDF group meetings and raise such points? This will allow 
to associate other's views as well.

I will just make a small comment on the https://schema.org/Physician.

This need an improvements (in definition I mean) and this on way! This is 
not the only one term/Type/concept to be improved, there are couple of 
such terms under improvements. This is the work being done by ScheMed W3C 
CG.
https://github.com/schemaorg/schemaorg/issues?utf8=%E2%9C%93&q=Physician+

https://github.com/schemaorg/schemaorg/issues/1114

etc..

Kind Regards,

Marc Twagirumukiza



From:   Renato Iannella <r@iannel.la>
To:     "its@lists.hl7.org" <its@lists.HL7.org>, w3c semweb HCLS 
<public-semweb-lifesci@w3.org>
Date:   27/05/2016 09:13
Subject:        Re: FHIR on schema.org




> On 27 May 2016, at 11:09, David Booth <david@dbooth.org> wrote:

> I think it is important to distinguish two separate and orthogonal 
concerns:
> 1. What data should be shared or exchanged?
> 2. What does the data mean?
> Security and privacy are all about #1 -- not #2. 
> Schema.org and healthcare vocabularies address #2 -- not #1.

I don’t think that is the case. Schema.org's dual purpose is to "promote 
schemas for structured data on web pages", so this includes the exchange 
of such data as a key driver behind creating the terms on schema.org.

Hence, whether we like it or not, just specifying personal data as a 
property in schema.org does not mean we can then not address how privacy 
is handled. This is especially relevant for healthcare data.

My (other related) point is *why* do we need to create a set of schema.org 
URIs for the same FHIR URIs ?

For example, we already have http://hl7.org/fhir/MedicationOrder

We do we now need (and maintain): http://schema.org/MedicationOrder

??

> They are all about creating a shared understanding of what the data 
means, in order to achieve interoperability between parties that have 
already decided to exchange data.

As an aside, look at the schema.org definition for a Physician:
  https://schema.org/Physician

I hope that is not shared too widely ;-)


Renato


Received on Friday, 27 May 2016 07:32:14 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 May 2016 07:32:14 UTC