Key activities

• Specification revision & improvement
• Specification testing against implementation
• Development & improvement of tools
• Education
  • Courses, tutorials, screencasts...
• Community consolidation
  • Registry: we have to know from where are the local and regional communities, who are the referents/leaders, who is part of these communities, and what are their interests in OpenEHR.
    • Communities:
      • Where: region, country, organization, ...
      • Why are they forming this community?: learn another standard? modeling clinical information? modeling clinical knowledge? creating commercial systems? just for research?
        • We can set more attractive goals, if we know what motivates them.
    • Members:
      • Name, profile (clinical, IT profesional, industry/commercial agent, researcher, etc.), ...
  • Promotion & evangelization & member empowerment:
    • Create some kind of "OpenEHR award" to recognize the member's contribution to the community, it's also a way of motivation.
      • The contributions must be oriented by the global objectives, yearly goals, and general guidelines.

Funding

• Courses, certifications, events (like IHE Connectathon), selling books, t-shirts, coffe cups, etc... (donations are always welcome).
• Certification (see below)
• Association and membership
• There are many national funding programs to research and development projects, this is good for local communities that can get some funding to reach annual local objectives.

Standards

• Harmonization with other standards
  • Tend and build bridges to other standards rather than criticize them.
• Integration of other standards (DICOM, 13606, CDA, ...)
  • How openEHR-based systems can integrate other standards
• IHE profiling of openEHR-based systems
  • This can help to:
    • Test interoperability between HL7/DICOM & openEHR based systems
    • As another way to certificate an openEHR-based system

Archetypes and Templates

• Development & improvement of archetypes and templates

Software certification

• Software and process certification
  • This is also a way of funding...
  • Slogan: If you pass the tests, you can use the openEHR logo on your system.

Specific objectives for 2011

• Complete the service model specification
• Complete the openEHR terminology service specs
• Tool development
• Community testing of openEHR systems (an openEHR Connectathon)
• We can set specific goals and and with help from the academic domain, we can solve our problems with tooling, specifications, testing, etc.
• ...

Local/regional communities annual objectives:

• Guided by mission, vision, action lines and global annual objectives.
• Activities must be coordinated with the central boards (just to tell the rest who is working on what).
• ...