Stakeholder registry Sample Clauses

Stakeholder registry. The stakeholder registry combines the collected contact information from interviews, workshops, encounters in events, and other contacts, with the exception of the internet based survey responders. The stakeholder registry is only for internal project purposes and is not supposed to be accessible for people outside the EU-MACS consortium. A protected version of the stakeholder registry is available in the protected common work space of the project. The stakeholder registry will be evicted after the conclusion of the project.
Sample 1
AutoNDA by SimpleDocs
Stakeholder registry. Since the sister project XXXXX is partly addressing the same stakeholder groups, a shared stakeholder registry for EU-MACS and XXXXX will be established. It will be located in a password-protected part of one of the projects’ work spaces. A limited number of people within the two consortia will be accredited to access the registry. The registry will include guidelines on reporting and maintenance. In case of technical questions about the registry, contact Xxxxxxx Xxxxxx (XXXXX). The Project Management Handbook chapter 7 on Ethics (D7.11 available in the EU-MACS workspace in the sub-folder ‘Submitted deliverables’) provides further guidelines on the principles of handling and storage of stakeholder contact information. Consecutive interactions with stakeholders from group 2 (above) and with those practically transferring from group 3 to group 2 should each be registered. Annex 1 contains an example from the registry.
Sample 1
Stakeholder registry. Stakeholder Engagement The public o Informed via public facing channels such as website, advertisements, printed and electronic materials, and social media o Information collected via listening sessions, workgroup meetings, special events, and via directed communication o Engage with workgroup(s) and Advisory Committee. Employees covered through PFMLI o Informed via public facing channels o Reached directly through impacted employers o Provided with program information/forms o Engage with workgroup(s) and Advisory Committee. Employees covered by an employer’s equivalent plan o Informed via public facing channels o Reached directly through impacted employers o Provided with program information/forms o Engage with workgroup(s) and Advisory Committee. Self-employed / Independent Contractors o Informed via public facing channels o Informed via trade associations and professional groups o Engage with workgroup(s) and Advisory Committee. Employees with multiple employers o Informed via public facing channels o Reached directly through impacted employers o Provided with program information/forms o Engage with workgroup(s) and Advisory Committee. Home care/child care employees o Informed via public facing channels o Reached directly through impacted employers o Provided with program information/forms o Engage with workgroup(s) and Advisory Committee. Employers that: • Don’t offer a plan • Offer an equivalent plan • Contribute to PFMLI o Reached through engagement with business, industry, and trade groups as well as other state agencies o Reached directly through a business registry for PFMLI and equivalent plans registry o Invited to participate in workgroup and Advisory Committee discussions o Provided toolkits and materials o Engage with workgroup(s) and Advisory Committee. Small Employers o Reached through engagement with business, industry, and trade groups as well as other state agencies o Reached directly through a business registry for PFMLI o Invited to participate in workgroup and Advisory Committee discussions o Provided toolkits and materials o Engage with workgroup(s) and Advisory Committee. Business, industry, and trade groups (e.g. xxxxxxxx of commerce, unions, Oregon Business Council, Pharmaceutical Research and Manufacturers of America (PHRMA), Oregon Employer Council, Oregon Farm Bureau, Small Business Development Centers, Main Street o Informed and consulted through presentations, meetings, and direct communication with PFMLI staff o Invited to p...
Sample 1
Stakeholder registry. For each of the stakeholders mentioned in WP4 we keep the information presented in the table below. Name Email Tel Fax Stakeholder Category Comment Appendix 2: Calendar of Events openMedicine - calendar of relevant events 2015 January 14 2015 Kick-off meeting openMedicine Bonn Germany February 09- 14 2015 GS1 GS1 Global Forum 0000 Xxxxxxxx Xxxxxxx March 16- 20 2015 GS1 GS1 Global Standards Event (Spring) Jersey City USA April 12 - 17 2015 HIMSS US HIMSS Annual US Conference Chicago USA April 19 2015 JIC JIC Executive Council Meeting San Francisco USA April 21- 23 2015 GS1 GS1 Global Healthcare Conference (Spring) Mexico City Mexico April 26 - 30 2015 IHTSDO IHTSDO April Business Meeting Copenhagen Denmark May 04- 08 2015 CDISC CDISC Europe Interchange 2015 Basel Switzerland May 10- 15 2015 HL7 WG meeting Xxxxx Xxxxxx Xxx 00- 00 0000 Xxxxxx / HIMSS Europe eHealth week / World of Health IT Riga Latvia May 00- 00 0000 XXXX XXX 0000 Xxxxxx Xxxxx May 28- 29 2015 AMIA iHealth 0000 Xxxxxxxxxx Xxxxxx XXX May 29- 30 2015 COACH Global Health 0000 Xxxxxxx Xxxxxx June 22- 26 2015 CDISC CDISC Xxxxx Xxxxxxxxxxx 0000 Xxxxx Xxxxx July 13- 15 2015 OMICS Asia Pacific Pharma Congress Beijing China July 20- 22 2015 OMICS World Congress on Pharmacology Brisbane Australia July 27- 29 2015 OMICS International Congress on Florida USA clinical trials August 3-5 2015 OMICS 5th International Conference on Pharmaceutical affairs Florida USA August 10- 12 2015 OMICS 4th International Conference Pharmacovigilance & Clinical Trials London UK August 10- 12 2015 OMICS Global Pharma Summit Philadelphia USA August 11- 13 2015 OMICS International Conference Drug Discovery & Designing Frankfurt Germany August 19- 23 2015 Medinfo Medinfo2015 - 15th World Congress on Medical and Health Informatics Sao Paulo Brazil August 25- 27 2015 OMICS European Pharma Congress Valencia Spain Aug/Sept 30- 06 2015 EMBC 37th Annual International Conference Milan Italy September 26- 30 2015 AHIMA AHIMA 0000 Xxxxxx Xxxxxxxxxx Xxx Xxxxxxx XXX October 4-9 2015 HL7 29th Annual Plenary & WG Atlanta USA October 12- 16 2015 GS1 GS1 Global Standards Event (Autumn) Warsaw Poland October 17- 23 2015 WHO-FIC WHO - Family of International Classifications meeting Manchester UK October 19- 22 2015 GS1 GS1 Global Healthcare Conference (Autumn) Budapest Hungary October 25- 30 2015 IHTSDO IHTSDO October Business Meeting & SNOMED CT Expo 2015 Montevideo Uruguay November 02- 06 2015 ISO/TC215 ISO/TC215 Health Informatics Plenary (...
Sample 1

Related to Stakeholder registry

  • Sex Offender Registry Pursuant to law, information about specified registered sex offenders is made available to the public. Tenant understands and agrees that they are solely responsible for obtaining any and all information contained in the state or national sex offender registry for the area surrounding the Premises, which can be obtained online or from the local sheriff’s department or other appropriate law enforcement officials. Depending on an offender’s criminal history, this information will include either the address at which the offender resides or the community of residence and zip code in which he or she resides.

  • Registry Borrower hereby designates Lender to serve as Borrower’s agent, and Lender hereby designates Servicer to serve as its agent, solely for purposes of this Section 9.7, to maintain at one of its offices a copy of each Assignment and Acceptance delivered to it and a register for the recordation of the names and addresses of each Assignee, and the principal amount of the Loan (or portions thereof) owing to, each Lender pursuant to the terms hereof and the Note Sales Agreement from time to time (the “Register”). Failure to make any such recordation, or any error in such recordation shall not affect Borrower’s obligations in respect of the Loan. With respect to any Noteholder, the transfer of the rights to the principal of, and interest on, its interest in the Loan and a Note shall not be effective until such transfer is recorded on the Register maintained by Servicer with respect to ownership of such Loan and a Note and prior to such recordation all amounts owing to the transferor with respect to such Note shall remain owing to the transferor. The registration of a transfer of all or part of the Loan and a Note shall be recorded by Servicer on the Register only upon the acceptance by Servicer of a properly executed and delivered Assignment and Acceptance by the assignor and assignee. Such Register shall be available for inspection by Borrower from time to time. At the assigning Noteholder’s option, concurrently with the delivery of an Assignment and Acceptance pursuant to which an interest of such Noteholder in the Loan and Note was assigned to such Assignee, the assigning Noteholder shall surrender to Borrower its Note, if any, evidencing the portion of the Loan corresponding to the interest so transferred and Borrower shall deliver to Noteholder one or more new promissory notes in the same aggregate principal amount issued to the assigning Noteholder and/or the Assignee.

  • Abuse Registry The Contractor agrees not to employ any individual, use any volunteer, or otherwise provide reimbursement to any individual in the performance of services connected with this agreement, who provides care, custody, treatment, transportation, or supervision to children or vulnerable adults if there is a substantiation of abuse or neglect or exploitation against that individual. The Contractor will check the Adult Abuse Registry in the Department of Disabilities, Aging and Independent Living. Unless the Contractor holds a valid child care license or registration from the Division of Child Development, Department for Children and Families, the Contractor shall also check the Central Child Protection Registry. (See 33 V.S.A. §4919(a)(3) & 33 V.S.A. §6911(c)(3)).

  • Per-­‐Registrar Transactions Report This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-­‐TLD, the A-­‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 02 iana-­‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

  • Voter Registration When designated by the Secretary of State, the Contractor agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.

  • Registry Lock Registry Operator may offer the Registry Lock service, which is a registry service that allows an authorized representative from the sponsoring Registrar, request the activation or deactivation of any of the following EPP statuses: serverUpdateProhibited, serverDeleteProhibited and⁄or serverTransferProhibited. SPECIFICATION 1 CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

  • Minimum Data Necessary Shared The Provider attests that the Student Data request by the Provider from the LEA in order for the LEA to access the Provider’s products and/or services is limited to the Student Data that is adequate, relevant, and limited to what is necessary in relation to the K-12 school purposes for which it is processed.

Time is Money Join Law Insider Premium to draft better contracts faster.