| Line 3 was replaced by line 3 |
| - What mechanisms should be considered for building community participation and support for an observational data model standard? Similarly, what community-based efforts should be considered for coordinated technology development? |
| + !Breakout-Group Products |
| Line 5 was replaced by lines 5-6 |
| - * How should the standard observational data model be developed and maintained? |
| + * __A list of recommendations for building community participation and support for a shared observational data model__ |
| + * __Include surrounding issues that should be addressed__ |
| Removed line 7 |
| - * What are possible organization models for developing, maintaining, and encouraging adoption of a shared model? |
| Line 9 was replaced by line 9 |
| - * How broad should the model be, e.g., what scientific communities should be targeted? |
| + !Background |
| Line 11 was replaced by line 11 |
| - * What lessons can be learned from other communities (e.g., the GO Consortium, UMLS, other standardization efforts) |
| + This session aims at defining mechanisms for building community participation and support for a shared observational data model. A community-based effort will help avoid the creation of largely redundant, potentially incompatible technology solutions, and foster interoperability and robustness of the applications that are developed. In addition to discussing how to best achieve a broadly participatory framework to move this effort forward, this session will also consider the needs for training, and support for the products created by a coordinated development effort. |
| Line 13 was replaced by line 13 |
| - * What protocols should be used to make make changes or adopt extensions to the model? How will changes be reviewed? How will conflicts among communities be resolved? How will extension models be validated? |
| + !Discussion topics |
| Line 15 was replaced by line 15 |
| - * What tools should be developed or endorsed to facilitate the creation, maintenance, and use of ontologies? |
| + What mechanisms should be considered for building community participation and support for an observational data model standard? Similarly, what community-based efforts should be considered for coordinated technology development? |
| At line 16 added 7 lines. |
| + Possible issues: |
| + * How should the standard observational data model be developed and maintained? |
| + * What are possible organization models for developing, maintaining, and encouraging adoption of a shared model? |
| + * How broad should the model be, e.g., what scientific communities should be targeted? |
| + * What lessons can be learned from other communities (e.g., the GO Consortium, UMLS, other standardization efforts) |
| + * What protocols should be used to make changes or adopt extensions to the model? How will changes be reviewed? How will conflicts among communities be resolved? How will extension models be validated? |
| + * What tools should be developed or endorsed to facilitate the creation, maintenance, and use of ontologies? |
| At line 17 added 1 line. |
| + * What are the staffing issues and levels needed for creation, maintenance, and curation of a community-based and shared observational data model and associated applications? |
| Line 19 was replaced by line 27 |
| - * What are the staffing issues and levels needed for creation, maintenance, and curation of a shared observational data model and its associated applications? |
| + !Session notes and results |
