projects:vocab-study
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| projects:vocab-study [2018/01/18 12:53] – 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: |
| **Project Lead: | **Project Lead: | ||
| Line 12: | Line 12: | ||
| ** Motivations (and potentially interested parties): ** | ** Motivations (and potentially interested parties): ** | ||
| - | * The **Architecture Working Group** has started to consider API specifications for Concept Sets | + | * The **Architecture Working Group** has started to consider API specifications for Concept Sets and we need better understanding |
| - | * We lack sufficient knowledge | + | * The **FHIR Working Group** has yet to establish guidelines on mapping or interfacing between OHDSI and FHIR vocabulary and value set services |
| - | * 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 **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 |
| - | * 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: ** | ** Possible discussion topics: ** | ||
projects/vocab-study.1516279986.txt.gz · Last modified: by sigfried
