See also: IRC log
FHIR now is now structured into modules: http://build.fhir.org/index.html
The Linked Data module: http://build.fhir.org/ontology-module.html
(Currently called the "Ontology Module", but will be rename to "Linked Data Module"
)
Suggestion for links to FHIR examples is to be listed "XML JSON Linked Data (JSON-LD or Turtle)"
that would appear in each example table like this one: http://build.fhir.org/allergyintolerance-examples.html
Eric: I prefer "RDF" there instead of "Linked Data", because it is more specific
AGREED: We'll see if we can change the example links to say "XML JSON RDF (JSON-LD or Turtle)"
http://wiki.hl7.org/index.php?title=FHIR_Custom_Resources
http://fhir.hl7.org.au/fhir/rcpa/Colorectal-Colorectal-genexample-1.xml.html
<ericP> -> http://rdf-vocabulary.ddialliance.org/discovery.html#fig-vocabulary-overview DISCO <whoo!>
<ericP> examples
harold: Next steps were to come up with use cases. We're going to pick up that thread and show something end of Nov, to have a poster for it at SWAT4LS
eric: With the excitement around FHIR, people are creating custom resources
<ericP> Custome Resources
<ericP> example
eric: People say "FHIR is great!
We'll do everything in FHIR!"
... Custom resources are being used for aggregates of data
plucked from other resources.
... Can I turn existing data into custom resources?
... Variables from a study become attributes in a FHIR
resource.
... We are spitting out FHIR structure definitions.
... Is this worthwhile?
dbooth: That allows the FHIR protocols to be reused, but others will not understand the custom resources.
eric: Harmonization between custom resources: two studies use some of the same questions, using the same URLs.
<ericP> https://www.w3.org/2016/11/ddi-disco/
eric: Goal here is, DDI is well ahead of FHIR in terms of these aggregations. If we provide a mechnical transformation to do a schema-schema transformation to produce a FHIR struture def from a DDI def, then ittakes advantage of what the DDI folks have done and brings it into FHIR.
dbooth: So one main benefit is that this causes DDI to coordinate consistent semantics between same-named/same-URI FHIR elements that appear in different custom FHIR resources? And the other benefit is the auto-generation of the custom FHIR structure defs?
eric: Not quite. The sameness is ensured by generating from the same DDI dictionary.
dbooth: How will someone seeing only custom resource A and custom resource B know that element X in A is the same as element Y in B?
eric: Additional triples are
needed to say that.
... FHIR does not have any way to indicate that two elements in
different resources have the same meaning.
dbooth: Does this process at least ensure that the FHIR local names are the same?
eric: No, it depends on whether
it is called the same variable in different studies.
... Lloyd has on his to-do list to figure out how to express
sameness across FHIR elements
ADJOURNED
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: dbooth Inferring Scribes: dbooth Present: EricP David_Booth Harold_Solbrig Found Date: 01 Nov 2016 Guessing minutes URL: http://www.w3.org/2016/11/01-hcls-minutes.html People with action items:[End of scribe.perl diagnostic output]