Patient Access API. To allow patients to easily access their claims information, including cost, as well as a defined subset of clinical information.
Patient Access API Sample Clauses
Related to Patient Access API
User Access Transfer Agent shall have a process to promptly disable access to Fund Data by any Transfer Agent personnel who no longer requires such access. Transfer Agent will also promptly remove access of Fund personnel upon receipt of notification from Fund.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.
CUSTOMER SERVICE ACCESS The Competitive Supplier agrees to provide, or cause to be provided, certain customer services to Participating Consumers. Such services shall be reasonably accessible to all Participating Consumers, shall be available during normal working hours, shall allow Participating Consumers to transact business they may have with the Competitive Supplier, and shall serve as a communications liaison among the Competitive Supplier, the Town, and the Local Distributor. A toll-free telephone number will be established by Competitive Supplier and be available for Participating Consumers to contact Competitive Supplier during normal business hours (9:00 A.M. - 5:00 P.M. Eastern Standard Time, Monday through Friday) to resolve concerns, answer questions and transact business with respect to the service received from Competitive Supplier. The Town will post program-related information on the Town’s website which will be available to Participating Consumers for general information, product and service information, and other purposes.
PROJECT ACCESS The Grantee shall ensure that the State, the Governor of the State, or any authorized representative of the foregoing, will have safe and suitable access to the Project site at all reasonable times during Project construction and thereafter for the term of this Agreement.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
Customer Access The Customer is responsible for the access to the Cloud Services and is responsible for maintaining the confidentiality of its access methods such as usernames and passwords and agrees to notify the Supplier via the Cloud Services support channel if a password is compromised. The Customer is responsible for all activities that occur under its Account.
Site Access Dell requires the right to access the APEX System in a timely way and as provided in the Service Offering Description to provide the Support Services. Failure to ensure that Customer provides Dell with timely access to a Site will relieve Dell of the Support Services obligations and Dell may also, at Dell’s discretion, suspend the APEX Service.
