*To be removed from our mailing list, please respond to this message with
UNSUBSCRIBE in the subject line*
*
INTERNATIONAL WINTER SCHOOL ON BIG DATA
BigDat 2015
Tarragona, Spain
January 26-30, 2015
Organized by
Rovira i Virgili University
h
Hi Vipul,
First, we would never define a specialized resource. As much as possible,
all resources are orthogonal and never exist in a hierarchical
relationship. Condition is a structure that includes a code (saying what
kind of condition), time of onset, who diagosed it, the patient who has the
Hi Vipul,
To me, your first two points go together. The only reason to do an RDF
> representation is to support implementations that want to make use of
> semantic web technologies for inference purposes.
>
>
>
> VK> Partially agree with you. Another reason for taking up RDF/OWL
> representation
SNOMED can not and should not map to FHIR resources. This is the
difference between clinical models that capture who, when where and why
with the medical terminologies like SNOMED that are only the what.
In HL7 V3, the information model has the entities in roles that
participate in acts. That
Agenda for Tuesday's teleconference:
* Review of Cecil Lynch's FHIR ontology approach
* FHIR ontology requirements:
http://wiki.hl7.org/index.php?title=FHIR_Ontology_Requirements
Complete agenda page:
http://wiki.hl7.org/index.php?title=ITS_RDF_ConCall_Agenda
TO SPEED UP THE START OF OUR CA
I think it would benefit for this discussion to be based on a concrete example
– to make sure we are on the same page:
Advance apologies for inappropriate use of terminology (as I am new to FHIR)
FHIR has a Resource called Condition.
Let’s say we define a new Resource called Diabetes (since
I agree with John – the best way forward is to have “purpose based ontologies”
and incrementally generalize them where there is clear value and need for doing
so.
From: john.e.matti...@kp.org [mailto:john.e.matti...@kp.org]
Sent: Thursday, December 11, 2014 9:55 AM
To: grah...@healthintersec
If every FHIR element was mapped to a snomed term, then you could represent
that in RDF no problems.
VK> Would propose that FHIR could be the hub – and we could leverage RDF/OWL
constructs to map FHIR elements to Snomed, MedDRA, ICD11, RxNorm, etc.?
However the problem with this is tha
To me, your first two points go together. The only reason to do an RDF
representation is to support implementations that want to make use of semantic
web technologies for inference purposes.
VK> Partially agree with you. Another reason for taking up RDF/OWL
representation is to make these d
