...
All kinds of localisation activities with the purpose of enabling openEHR's penetration into each jurisdiction's eHealth environment national/regional eHealth environments with a different mix of languages, cultures, objectives and resources. This includes translation and adaptation of specifications and related artifacts or their extensions as well as instantiation of new content. It is imperative that we support the creation of educational materials in local languages, actively engage with the communication and dissemination of these materials and events, get involved in R&D projects (e.g. with local universities), and liaise with other local standards (clinical guidelines, manuals, white papers, ebooks, etc.)
...
The Localisation Program consists of Qualified Members for the Localisation Program, Localisation Program Committee (LPC) and Local openEHR openEHR Representative(s) and Organisations. In addition, individuals that are enthusiastic about openEHR openEHR who work with the openEHR openEHR Representative(s) (most probably affiliated with Local Organisations if any) are also recognised as Local Members. 
Qualified Membership (QM): local openEHR activity will happen through qualified members where individuals can join from any jurisdiction country or region (can be a specific territory, language group etc. depending on what local needs are). Acceptance will be based on relevant experience and skills required for localisation activities. It is this group that will do most of the work!
...
Local Representative(s): A Qualified Member (can be more than one depending on local needs and skills available) to be designated to lead local work and officially represent openEHR in their own jurisdictioncountry/region. LPC will assist QM to nominate, propose and get permission from the Board to represent one or more national representatives. These appointments should be approved by the Board before one can be appointed as the national openEHR representative.
Chapter Organisations: when there's some maturity around localisation in one jurisdiction country/region and firm demand, instead of individual leadership around openEHR Representatives, establishing a formal organisation that would function as a Chapter organisation Organisation might be advantageous. In the open and free spirit of openEHR these need to be not-for-profit organisations and bound by openEHR Foundation's principles and rules. It is expected that existing organisations relevant in this area (e.g. national HL7 affiliates, health informatics associations, local standardisation bodies etc.) might actually act as the umbrella organisation saving hassle and cost of new establishments. It is yet to be decided as to how membership and money matters can be dealt with within an organisation with other purposes though. This organisation should be approved by the Board before it can be appointed as the national openEHR Chapter.
Local Membership: these are enthusiastic individuals who have an interest in and potential to contribute to openEHR but limited in experience, skills and/or resources to become Qualified Members. This local membership will provide recognition in this space (e.g. as evidence of peer esteem for academics etc.) and the grounds to work with them. They will most likely be formal members of local organisations (e.g. not-for-profit associations etc.). They will be led by qualified members but have no representative or executive powers.TB: possibly add a diagram, and also a better understanding of what 'local jurisdictions' means - is it within a country? What is the relationship of 'chapters' to countries? Probably need more detail on what each group of people would do, how they relate to each other.
Qualified Members (QM)
This is the body of people who will do the actual work and is not locale specific (e.g. there is only one group). New members (either self nominated or by existing QM) can be added by the decision of LPC based on membership criteria.
...
- carry on day to day operations of the Localisation Program
- propose and set the agenda; such as defining common principles and conventions, resources, contents and materials all localization initiatives should consider (to avoid starting from scratch or overlaps). Determine issues that needs to be discussed with the Board (e.g. openEHR certification)
- monitor the agenda and work items,
- discuss within the group on issues arising
- tweak if necessary
- advise LPC is there's a need for decision makingresolution of issues
- meet regularly (period TBCTBD) to discuss issues arising and report on progress
- keep website, training material and other localisation assets up-to-date and correct
- develop ideas around promotion, projects, collaborations, partnerships etc.
- disseminate outputs
- attend local conferences, showcases etc.
- publish scholarly articles, newsletters, whitepapers etc.
- make education a high priority
- organise tutorials, workshops, special courses etc.
- contribute to educational programs, curricula
- foster research
- contribute to local research environment
- seek funding for projects, students, travel etc.
Outputs
TB: how does the 'agenda' get set? what decisions are taken? By whom? what things can just be done by individuals? What are the products of the QM?
PP: before "monitor agenda" I would add "agenda design and agreement", and mention some examples of agenda items that could be defined by us These comprise:
- translation of specifications, clinical models and other existing resources (e.g. documents, presentations, marketing and training material, schemas, etc.)
- localisation of existing software (e.g.
...
- translation and adaptation of tools, components etc.)
- development of new resources with a particular locale
- common resources (e.g. document/web templates, styles, conventions etc.) and guidelines for use by all locales
Membership
This section describes the conditions for membership for Qualified Members.
...
Note that a high level of technical competency is not a necessity as Localisation work will involve substantial amount of work related with content (which may actually require clinical or organisational skills more than technical). However a basic level of technical knowledge will be required to appreciate the foundational principles of openEHR as well as skills around software localisation when adapting tools and components.
TB: how are qualifications demonstrated? E.g. filling out some form?
PP: I was thinking of creating some kind of standard form to evaluate openEHR skills, the main areas could be: study, training, research, development, community.
...
Candidates should submit, in writing, where they stand with regards to the cause of openEHR and provide evidence about their qualifications in these main areas:
- background/training: degree(s) obtained, training/certification etc.
- research and development: openEHR related research and/or design/software artefacts developed
- community: active participation to the lists and the wiki? other activities?
Process
- A new nomination is sent to any co-chair of the LPC, who will announce and discuss with existing QM.
- the nomination may be rejected on formal grounds, such as lack of qualification
- LPC may take a formal vote if unanymous decision cannot be reached (n.b. koray: I'm not entirely happy with this but still recognise it might be a necessity - TBD).
...
- creative thinking around locale specific issues; including
- keeping vision aligned with changing requirements, advances, paradigms etc.
- keeping an eye on local assets (e.g. training material, consistency etc.) making sure that the credit/value doesn't go to certain individuals or organisations but to the community. [TB: can this be stated better with some kind of rules of copyright / attribution?]
- how to empower local users to get things done
- trying to find workarounds to address local pecularities due to language, culture etc. but fair enough not to compromise the Foundation's values, principles and more importantly its assets.
- managing Qualified Membership:
- setting the criteria for Qualified Membership
- reviewing nominations from existing QM or from the Foundation and deciding who can become QM
- maintaining an appropriate balance of individuals (e.g. academics, government workers, vendors etc. as well as in terms of technical, organisational and other desired skills) [TB: how would this be done? What are the criteria?]
- etc.
- Supporting leadership and support for Qualified Members:
- help with their local establishments (e.g. assist preparing their local TOR)
- resolving local/global IP issues
- publishing local content
- mediating local training strategies, material development and maintenance
- help with promotion strategies in local environments
- communication to the Foundation and the wider openEHR community of issues of interest; including [TB:suggest to treat comm. to Foundation and comm. with other communities separately - one is internal, one is external]** any local issues arising which needs Board's attention
- getting promotion support and material (e.g. endorsements, MoUs etc.)
- aligning local strategies and works with that of the Foundation
- advise of requirements and prioritisation of work or any other business
...