Versions Compared

Old Version 8

changes.mady.by.user David Luchuk

Saved on

compared with

New Version Current

changes.mady.by.user Paul Knowles

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Send an email to semantic-domain-wg@lists.trustoverip.org to request a calendar invite (you can subscribe to the mailing list at lists.trustoverip.org).

Agenda

Guiding Goal: Group deliverables and health care sector data harmonization.

  • Welcome (Paul—2.5 mins)
  • Newcomer Introductions (WG, 2.5 mins)
  • Task Force Updates (WG, 5 mins)

  • White paper proposal: "How OCA Differs from JSON-LD and Why You Need Both" (Paul—10 mins)

    • Article remit
      • In that <10 page paper, which needs to include a few key easy-to-digest diagrams, we will lay out how and why the two technologies are different and when you would use which one for what.

    • What is Linked Data?

      • Linked Data is data expressed on a website that can traverse (via links) to other websites. Common formats of data include HTML, JSON, XML, CSV and RDFa. These common data formats can be linked together using JSON-LD.

    • What is a Database Model?

    • Potential story board

      • Maybe a nice walkthrough in the white paper would be to think of a health care scenario where you want to utilise CDISC:SDTM data (clinical trials) with FHIR data (medical records). Two very different database models that, despite large incentives to do so, have never been harmonised. In the walkthrough, we can demonstrate how that can be done by ingesting and flattening the two database models using OCA. We can even show how JSON-LD might fit into the equation as metadata for any tabular dataset in SDTM is described in XML whereas metadata in FHIR is described in JSON.

...

  • Setting up an OCA-CDISC Focus Group for clinical research database model harmonisation (Paul—10 mins)
    • CDISC SDTM Implementation Guide v.3.2 here
  • Demo: Dynamic data flow with explicit consent between two Hyperledger Aries agents (Robert—20 mins)

    • For consent schema structure, see OPN: Open Notice (+ Consent) Receipt Schema here

  • Logistics and miscellaneous (Paul—10 mins)

    • SDWG representative for the new Operations Team

      • The purpose of the Operations Team is to create a small group of ToIP members who will share information on the workplans of our WGs, help ensure that draft deliverables are advancing as intended through the stages of the ToIP workflow, resolve any bottle-necking that arise around decision-making/approvals and discuss issues such as (for example) introducing firmer parameters for the creation of TFs under all WGs.

      • The Operations Team will not be directing or otherwise interfering with the development of content and deliverables in the WGs themselves.
    • Official name, Semantic Domain Working Group, approved by the Steering Committee
    • Static wiki page for Passive Identifiers rather than a new TF
    • Leadership positions
    • Meeting schedule

      1. OCA-FHIR FG weekly meeting

      2. Decentralized Semantics WG weekly meeting

Meeting Notes

Recording


Participants (Name / Location / Time zone / Affiliation):

...