Smartphone Applications Sample Clauses

Smartphone Applications. If the Health Plan uses smartphone applications (apps) to allow enrollees direct access to Agency-approved member materials, the Health Plan shall comply with the following: 1. The smartphone application shall disclaim that the app being used is not private and that no PHI or personally identifying information should be published on this application by the Health Plan or end user; and 2. The Health Plan shall ensure that software applications obtained, purchased, leased, or developed are based on secure coding guidelines; for example: a. OWASP [Open Web Application Security Project] Secure Coding Principles – xxxx://xxx.xxxxx.xxx/index.php/Secure_Coding_Principles; b. CERT Security Coding – xxxx://xxx.xxxx.xxx/secure-coding/; and c. Top 10 Security Coding Practices – 32. Attachment II, Core Contract Provisions, Section XII, Reporting Requirements, Item A., Health Plan Reporting Requirements, sub-item 1.c. is hereby amended to now read as follows:
AutoNDA by SimpleDocs
Smartphone Applications. If the Health Plan uses smartphone applications (apps) to allow enrollees direct access to Agency-approved member materials, the Health Plan shall comply with the following: 1. The smartphone application shall disclaim that the app being used is not private and that no PHI or personally identifying information should be published on this application by the Health Plan or end user; and 2. The Health Plan shall ensure that software applications obtained, purchased, leased, or developed are based on secure coding guidelines; for example: a. OWASP [Open Web Application Security Project] Secure Coding Principles – xxxx://xxx.xxxxx.xxx/index.php/Secure_Coding_Principles; b. CERT Security Coding – xxxx://xxx.xxxx.xxx/secure-coding/; and c. Top 10 Security Coding Practices – xxxxx://xxx.xxxxxxxxxxxx.xxxx.xxx/confluence/display/seccode/Top+10+Secure+Coding+Practices WellCare of Florida, Inc., Medicaid HMO Non-Reform Contract
Smartphone Applications. ‌ As more communities around the world obtain access to smartphones and similar devices, the use of these tools to improve health outcomes in those communities has embellished the mHealth field. For example, a systematic review conducted by Xxxx et al. (2013) discovered that text-messaging interventions increased adherence to antiretroviral therapy in a low-income setting and smoking cessation in high-income environments. The authors suggested a stricter, randomized controlled trial (RCT) design with measured, objective primary outcomes in order to be able to establish a relationship between the mHealth program and the health of the beneficiaries. An important conclusion from this systematic review discusses how most mHealth interventions are one-dimensional (only using text-messaging or voice-messaging capabilities and no inclusion of other, potentially beneficial components). By making mHealth interventions multi-faceted, their effects on health behaviors, and the self-management of disease can be further elucidated. Most importantly, however, the authors even suggested the use of application software, which could result in a considerably interactive platform that is available on one’s device at any time and could also have significant implications for health behaviors and disease management (Free et al., 2013). Other more recent studies in the field of mHealth have built on the observations of Free et al., implementing more interventions in low and middle-income countries, “particularly in view of the high coverage of mobile technologies in these settings” (Free et al., 2013). For example, a study conducted in Bangladesh evaluated the process through which a mHealth approach was proposed for the delivery of a phone-based, cholera prevention WaSH program called CHoBI7-- Cholera-Hospital-Based-Intervention-for-7-Days. They conducted interviews with government stakeholders to determine scalability and discovered support for the mHealth delivery format among diarrhea patients and their families. To fine-tune the text and voice messages delivered through the program, workshops were held to determine stakeholder preferences. Finally, a pilot implementation of the mHealth program revealed high user acceptability and how feasible it was to deliver the mHealth program to diarrhea patients arriving at a health facility in Bangladesh. Most of the trials evaluated in the Free et al. 2013 meta-analysis were involving text-messaging or voice-messaging technologies, b...

Related to Smartphone Applications

  • Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Regulatory Applications (a) Western and PNB and their respective Subsidiaries shall cooperate and use their respective reasonable best efforts to prepare all documentation, to effect all filings and to obtain all permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary to consummate the transactions contemplated by this Agreement. Western and PNB shall use their reasonable best efforts to make all required bank regulatory filings, including the appropriate filing with the Regulatory Authorities. Each of Western and PNB shall have the right to review in advance, and to the extent practicable each will consult with the other, in each case subject to applicable laws relating to the exchange of information, with respect to all material written information submitted to any third party or any Governmental Authority in connection with the transactions contemplated by this Agreement. In exercising the foregoing right, each of the parties hereto agrees to act reasonably and as promptly as practicable. Each party hereto agrees that it will consult with the other party hereto with respect to the obtaining of all material permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary or advisable to consummate the transactions contemplated by this Agreement and each party will keep the other party appraised of the status of material matters relating to completion of the transactions contemplated hereby. (b) Each party agrees, upon request, to furnish the other party with all information concerning itself, its Subsidiaries, directors, officers and shareholders and such other matters as may be reasonably necessary or advisable in connection with any filing, notice or application made by or on behalf of such other party or any of its Subsidiaries to any third party or Governmental Authority.

  • PROHIBITION ON CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT To the extent applicable, Supplier certifies that during the term of this Contract it will comply with applicable requirements of 2 C.F.R. § 200.216.

  • Provisional Application Upon signature of this Compact, and until this Compact has entered into force in accordance with Section 7.3, the Parties will provisionally apply the terms of this Compact; provided that, no MCC Funding, other than Compact Implementation Funding, will be made available or disbursed before this Compact enters into force.

  • General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!