projects:vocab-study
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| projects:vocab-study [2018/01/18 12:19] – created sigfried | projects:vocab-study [2018/01/18 13:48] (current) – sigfried | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| <WRAP box justify round> | <WRAP box justify round> | ||
| + | **Objective: | ||
| - | * **Objective: | ||
| - | * Convene as a temporary study group to learn and discuss external standards and tools relevant to OHDSI' | ||
| - | * ** Motivations (and potentially interested parties): ** | ||
| - | * The **Architecture Working Group** has started to consider API specifications for Concept Sets | ||
| - | * We lack sufficient knowledge to determine the costs or benefits of attempting to accommodate or synchronize with standards and efforts beyond OHDSI | ||
| - | * The (currently suspended) **Vocabulary-Visualization Working Group** and people working on vocabulary system interfaces should not proceed while Concept Set specifications are liable to significant change | ||
| - | * The **FHIR Working Group** has yet to establish guidelines on mapping or interfacing between OHDSI and FHIR vocabulary and value set services | ||
| - | * The **CDM Working Group** and the **OHDSI collaborator community** at large must consider whether and when and how our standards and tools interoperate with those in other domains that depend on electronic health data | ||
| - | | ||
| **Project Lead: | **Project Lead: | ||
| Line 17: | Line 9: | ||
| **Meeting link:** [[https:// | **Meeting link:** [[https:// | ||
| - | |||
| </ | </ | ||
| + | |||
| + | ** Motivations (and potentially interested parties): ** | ||
| + | * The **Architecture Working Group** has started to consider API specifications for Concept Sets and we need better understanding to determine the costs or benefits of attempting to accommodate or synchronize with standards and efforts beyond OHDSI. Also, the (currently suspended) **Vocabulary-Visualization Working Group** and people working on vocabulary system interfaces should not proceed while Concept Set specifications are liable to significant change | ||
| + | * The **FHIR Working Group** has yet to establish guidelines on mapping or interfacing between OHDSI and FHIR vocabulary and value set services | ||
| + | * The **CDM Working Group** and the **OHDSI collaborator community** at large must consider whether and when and how our standards and tools interoperate with those in other domains that depend on electronic health data | ||
| + | |||
| + | ** Possible discussion topics: ** | ||
| + | * OHDSI' | ||
| + | * Which others? (UMLS, CTS2, FHIR, etc., plus many commercial offerings) | ||
| + | * Are they alternatives, | ||
| + | * OHDSI' | ||
| + | * Which others? (VSAC, FHIR, PCORNet, Sentinel, commercial...) | ||
| + | * How do they relate to phenotypes and other functional or conceptual entities in the OHDSI framework? | ||
| + | * Long-term vision and short-term strategies for interoperability, | ||
| + | * How should we relate these to external standards and resources, if at all? | ||
| + | * And at what level? Concept/ | ||
| + | * Are there usable, open source tools that we should consider leveraging for our vocab/ | ||
| + | * Who can we bring into the discussion to help us understand and discuss these issues? | ||
| + | |||
| + | Clarification: | ||
projects/vocab-study.1516277948.txt.gz · Last modified: by sigfried
