...

1. Core terminology content development including mapping to standards (code mapping)
2. Specialized domain content development (including subsetting of content, expansion of content, etc.)
3. Mapping of user requirements to specific concepts (field mapping)
4. Deployment of content within the software platform (including searching within forms, data capture tools, etc.)
5. Meta-data modeling and information modeling including schema design
6. Ontolological work including building of aggregate indicators and measures (including maps to standard quality measures, etc.)
7. Reporting/Analysis using common algorithms, formulae and concepts
8. Transactional translation or tagging for on-the-fly encoding of concepts including natural language processing

#1, 3, and 4 are minimally essential for success of the platform. Currently, different players perform these functions.

Responsibilities

• Elucidate overall plan for meta-data and terminology management
• Identify partners or community members to fill functional requirements of plan
• Be point person with OpenMRS community on terminology issues
  • Including content delivery
  • Content tools
  • Terminology roadmap
• Point person for standards mapping (assessing need for mappings, oversee mapping work) 
• Editorial control to ensure that content meets certain minimum standards

...

• Further documentation of OpenMRS terminology management .(not done)
• Continue to ensure short term maintenance of existing terminology functions (done)
• Continue to identify potential partners for sustainability (partially done)
• Develop integration plan with OpenHIE and other reference implementations (specifically Kenya EMR, Rwanda MOH, etc.) (OCL)
• Synch with Road Map and ensure content coverage for Reference application. (not done)

2015 Goals

• Further documentation of OpenMRS terminology management
• Clarify leadership for Terminology and Meta-data
• Continue to ensure short term maintenance of existing terminology functions
• Close deals with potential partners for sustainability
• Deploy integration technology to allow for subscription of reference content and subsetting of curated dictionary content (e.g., OCL)
• Synch with Road Map and ensure content coverage for Reference application. (not done)

Not Responsible for...

• Doing all the work
• Deciding on what content should or should not go into the dictionary (only how)
• Directly funding the work
•