...
Function | CIEL | MCL/OCL | OCC | Apelon | IMO |
|---|---|---|---|---|---|
1 | √ |
| √ |
| √ |
2 | +/- | √ | √ |
|
|
3 | √ | √ |
| √ |
|
4 |
| √ |
| √ | √ |
5 |
|
|
| √ |
|
6 | √ | √ |
|
| √ |
7 |
|
|
|
| +/- |
8 |
|
|
| √ |
|
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
...
- Requirements generation and overall map of process started above .(done)
- Ensure short term maintenance of existing terminology functions, including resource requirements (partially complete)
- Identify potential partners for sustainability (partially done)
- Develop integration plan with OpenHIE and other reference implementations (not done)
2014 Goals
- Further documentation of OpenMRS terminology management.
- Continue to ensure short term maintenance of existing terminology functions
- Continue to identify potential partners for sustainability
- Develop integration plan with OpenHIE and other reference implementations (specifically Kenya EMR, Rwanda MOH, etc.)
- Synch with Road Map and ensure content coverage for Reference application.
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