Centralized Communication Database Sample Clauses

Centralized Communication Database. The MCO must develop a centralized database to record: The special communication needs of all MCO members (e.g., those with limited English proficiency, limited reading proficiency, visual impairment, and hearing impairment, and those in need of auxiliary aids and services); and The provision of related services (e.g., MCO materials in alternate format, oral interpretation, oral translation services, written translations of MCO materials, and sign language services). The MCO's centralized database must include all MCO member primary language information, as well as all other special communication needs information for MCO members, as indicated above, when identified by any source, including ODM, the SPBM, the OhioRISE Plan, ODM's consumer hotline, MCO staff, providers, and members. This centralized database must be readily available to MCO staff and be used in coordinating communication and services to members, including the selection of a PCP who speaks the primary language of a limited English proficiency member when such a provider is available. Unless otherwise specified by a member, the MCO must ensure that the special communication needs identified by a member (e.g., large print) are applied to subsequent communications with the member so that a member does not have to repeatedly request the accommodation. The MCO must share information on member-specific communication needs with its providers (e.g., PCPs, subcontractors, and Third Party Administrators) as applicable. Upon ODM's request, the MCO must submit information regarding the MCO's members with special communication needs to ODM. Such information may include but is not limited to individual member names, their specific communication need, and any provision of special services to members (i.e., those special services arranged by the MCO as well as those services reported to the MCO that were arranged by the provider).
AutoNDA by SimpleDocs
Centralized Communication Database a. The MCO must develop a centralized database to record:
Centralized Communication Database. The OhioRISE Plan must develop a centralized database to record: The special communication needs of all OhioRISE Plan's members (e.g., those with Limited English Proficiency, limited reading proficiency, visual impairment, and hearing impairment, and those in need of auxiliary aids and services); and The provision of related services (e.g., OhioRISE Program materials in alternate format, oral interpretation, oral translation services, written translations of OhioRISE Program materials, and sign language services). The OhioRISE Plan's centralized database must include all OhioRISE Plan's member primary language information, as well as all other special communication needs information for OhioRISE Plan's members, as indicated above, when identified by any source, including ODM, the SPBM, the MCOs, the ODM’s consumer hotline, OhioRISE Plan's staff, providers, and members. This centralized database must be readily available to OhioRISE Plan's staff and must be used in coordinating communication and services to members. The OhioRISE Plan must share information on member-specific communication needs with its providers, including CMEs, subcontractors, and Third Party Administrators as applicable. Upon ODM's request, the OhioRISE Plan must submit information regarding the OhioRISE Plan's members with special communication needs to ODM. Such information may include but is not limited to individual member names, their specific communication need, and any provision of special services to members (i.e., those special services arranged by the OhioRISE Plan as well as those services reported to the OhioRISE Plan that were arranged by the provider, including the CMEs).

Related to Centralized Communication Database

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, VarTec must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

  • Third Party Websites The Service may contain or reference links to websites operated by third parties ("Third Party Websites"). These links are provided as a convenience only. Such Third Party Websites are not under our control. We are not responsible for the content of any Third Party Website or any link contained in a Third Party Website. We do not review, approve, monitor, endorse, warrant, or make any representations with respect to Third Party Websites, and the inclusion of any link in the Service, Debit Rewards Offers or any other services provided in connection with them is not and does not imply an affiliation, sponsorship, endorsement, approval, investigation, verification or monitoring by us of any information contained in any Third Party Website. In no event will we be responsible for the information contained in such Third Party Website or for your use of or inability to use such website. Access to any Third Party Website is at your own risk, and you acknowledge and understand that linked Third Party Websites may contain terms and privacy policies that are different from ours. We are not responsible for such provisions, and expressly disclaim any liability for them.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • 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.

  • Web site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

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