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).
Guiding Goal: Group deliverables and health care sector data harmonization.
White paper proposal: "How OCA Differs from JSON-LD and Why You Need Both" (Paul—10 mins)
What is Linked Data?
What is a Database Model?
A database model shows the logical structure of a database, including the relationships and constraints that determine how data can be stored and accessed. Common kinds of data models include Hierarchical database model, Relational model, Network model, Object-oriented database model, Entity-relationship model, Document object model, Entity-attribute-value model, Star schema and Object-relational database model. These common database models can be harmonized using OCA.
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.
Define-XML is required by the United States Food and Drug Administration (FDA) and the Japanese Pharmaceuticals and Medical Devices Agency (PMDA) for every study in each electronic submission to inform the regulators which datasets, attributes, controlled terms, and other specified metadata were used.
We then hammer it home by flagging all attributes that could potentially unblind the identity of a governing entity and create entry, label and information overlays in English and Chinese for language resolution at the application layer.
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.
OCA-FHIR FG weekly meeting
Participants (Name / Location / Time zone / Affiliation):
Burak Serdar / Denver, CO, USA / MST / Cloud Privacy Labs
John Walker / Bay Area, USA / PDT / SemanticClarity, CCI
Mukundan Parthasarathy / Bay Area, USA / PDT / SemanticClarity
Mark Lizar / Toronto, Canada / EDT / Open Consent Group
Scott Whitmire / Scottsdale, AZ, USA / MST / Mayo Clinic
Steven Milstein / Montreal, Canada / EDT / Colab Ventures
Subra Subramaniam / Bay Area, USA / PDT / CyberKnowledge
Leadership positions:
(Note: We plan to instigate an official submissions, nominations and voting process. In the meantime, please put your name down if you are interested in volunteering for either a Chair or Vice-chair position.)