Service Access and Delivery Clause Samples

The Service Access and Delivery clause defines how and when a customer can use and receive the services provided under an agreement. It typically outlines the methods of accessing the service, such as through a web portal, API, or physical delivery, and may specify requirements like user authentication or service availability windows. This clause ensures both parties understand the logistics of service provision, reducing misunderstandings and setting clear expectations for service delivery.
Service Access and Delivery. These components are responsible for facilitating the end-to-end collection and distribution of data that is either entered or requested by a user. These components include all functions necessary to communicate in a client-server environment. Examples of these components include, but are not limited to, web browsers, Virtual Private Network (VPN), Remote Authentication Dial-In User Service (RADIUS), Peer-to-peer, Section 508 compliance, HyperText Transfer Protocol (HTTP), File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP).
View SourceView Similar (57)
Service Access and Delivery. These components are responsible for facilitating the end-to-end collection and distribution of data that is either entered or requested by a user. These components include all functions necessary to communicate in a client-server environment. Examples of these components include, but are not limited to:  Web browsersVirtual Private Network (VPN)  Remote Authentication Dial-In User Service (RADIUS)  Peer-to-peer  Section 508 compliance  Hypertext Transfer Protocol (HTTP)  File Transfer Protocol (FTP)  Simple Mail Transfer Protocol (SMTP) SECTION C - CONTRACT SCOPE OF WORK AND PERFORMANCE WORK STATEMENT C.4.1.2 Service Platform and Infrastructure These components include all functions necessary for processing and storing data. These components provide and manage the resources available for Application Services. Examples of these components include, but are not limited to:  Desktops, laptops, servers, mainframes, routers, switches, and printers.  Asynchronous Transfer Mode (ATM) and T1  Digital Subscriber Line (DSL), Ethernet, Windows/UNIX, Java/.NET  Web server/portal  Database, data storage, data warehouseSoftware development tools  Testing, modeling, versioning, and configuration management. C.4.1.3 Component Framework These components consist of the design of application or system software that incorporates interfaces for interacting with other programs and for future flexibility and expandability. These components define higher level logical functions to provide services in a way that is useful and meaningful to users and other Application Services. Examples of these components include, but are not limited to:  Digital certificates, biometrics;  Business logic: JavaScript, Visual Basic  Data interchange  Simple Object Access Protocol (SOAP)  Resource Description Framework (RDF)  Data management  Structured Query Language (SQL), Open DataBase Connectivity (ODBC), and Online Analytical Processing (OLAP). C.4.1.4 Service Interface and Integration These components define the discovery, interaction and communication technologies joining disparate systems and information providers. Application Services leverage and incorporate these components to provide interoperability and scalability. Examples of these components include, but are not limited to:  Messaging-Oriented Middleware (MOM)  Object Request Broker (ORB)  Enterprise Application Integration (EAI)  Extensible Markup Language (XML)  Electronic Data Interchange (EDI)  Web ...
View SourceView Similar (4)
Service Access and Delivery. Access Channels will include a wireless PDA for the patient and may include a Desktop Web Interface for the caregiver, family member, and provider. Collaboration/Communications will be impacted as the SMART on FHIR app must collaborate with the Wi-Fi enabled medication dispenser and communicate with the patient’s EMR. The Delivery Channel will be the Internet as the data will be sent via the Internet to the EMR system. Service Requirements include federal, state, local legislation including HIPAA compliance. Authentication will be impacted with the least privileges principle for the Provider, Caregiver, Pharmacist, Family Member, and Patient. Service Transport will be impacted as the data will be sent via the Internet with an encrypted and secured connection. Support Platform: wireless/mobile on the patient’s smart phone. Delivery Servers: Application Servers collect info from patient, Web Servers will collect info into the EMR and from Caregiver, Provider, and Family Member optionally. Hardware/Infrastructure impacted is Wireless Area Network (WAN) on which the medication dispenser and app communicate and collaborate, and Network Devices and Standards will be impacted as the data will be sent to the patient’s EMR over the Internet and there is a modem and router and standards for the network. Database/Storage will be impacted because this app will store all of the medication adherence data as well as pharmaceutical history. User Presentation/Interface will utilize voice guidance. Data Management will have visualization tools so that the provider can visually graph trend data per patient or groups of patients. Integration will be impacted within Enterprise Application Integration as the data will get integrated into the patient’s EMR in a specific Medication Reconciliation Tab that will be monitored by a Care Coordinator that can monitor the group of Seniors with CHF and view the group’s medication adherence and ADE statistics and history.
View Source
Service Access and Delivery. Access Channels- Service delivery may be impacted by this project due to the interoperability requirements of the application and existing Emory Healthcare systems. These links will require communication between systems and also push notifications to providers through patient EHRs. • Service Requirements- Existing Emory Healthcare service requirements for the protection of Emory Healthcare patients and their data must be adhered to for both the application and registry. • Software Engineering- An API will be created for the application data that will flow between the registry, application, and Emory Healthcare systems. • Database/Storage- Additional databases must be constructed in order to house data for the application and registry. • Security- Security will be impacted due to the need to protect patient data. User access will be restricted to patients and physicians enrolled. Authentication procedures will be put in place in order to appropriately grant user access. • User Presentation/Interface- With the addition of the World’s Ear application, user interface will be tailored to provide a user friendly experience. The registry presentation will be simple in order to streamline physician efforts. • Data Management- Data management will be affected due to the need for connectivity to other systems involved. Additionally, data management will come into play as the visualization capabilities are utilized by providers and patients. • Data Interchange- Data will be shared among the registry, application, and Emory Healthcare systems. • Interoperability- The project will require interoperability of Emory HealthCare Powerchart, World’s Ear application, World’s Ear registry, and patient EHR. SKILLS/ROLES NEEDED FOR PROJECT IMPLEMENTATION
View Source

Related to Service Access and Delivery

  • Services and Deliverables The Services and the required Deliverables for the Services are specified below. Service Type Output Measure Quantity per annum Number of Service Users Funding amount per annum (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Service Type Output Measure Quantity per annum Number of Service Users Funding amount (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $

  • Payment and Delivery Payment for the Option Shares shall be made on the Option Closing Date by wire transfer in Federal (same day) funds, payable to the order of the Company upon delivery to you of certificates (in form and substance satisfactory to the Underwriters) representing the Option Shares (or through the facilities of DTC) for the account of the Underwriters. The Option Shares shall be registered in such name or names and in such authorized denominations as the Representative may request in writing at least one (1) full Business Day prior to the Option Closing Date. The Company shall not be obligated to sell or deliver the Option Shares except upon tender of payment by the Representative for applicable Option Shares.

  • Tasks and Deliverables A description of and the schedule for each task and deliverable, illustrated by a ▇▇▇▇▇ chart. Start and completion dates for each task, milestone, and deliverable shall be indicated. Must include deliverables specified in SOW-RFP as well as other deliverables that may be proposed by Contractor.

  • Authorization, Execution and Delivery The execution and delivery of this Note by the Borrower and the performance of its obligations hereunder have been duly authorized by all necessary corporate action in accordance with all applicable Laws. The Borrower has duly executed and delivered this Note.

  • Shipment and Delivery Seller grants the Company the right at any time to specify the carrier and/or method of transportation to be employed in conveying any part or all of the Goods covered herein. In the event that Seller uses an unauthorized carrier and/or method of transportation, then all shipping expenses shall be assumed by Seller. Unless otherwise stated in the Order, all Goods will be shipped FCA shipment point. FCA shall be interpreted in accordance with the version of Incoterms valid at the time of the Seller’s acceptance of the Order. The Seller shall be responsible for preparing and filing all export documentation for all shipments. The Company shall not be obligated to accept early deliveries, partial deliveries or excess deliveries. If Goods are incorrectly delivered, the Seller shall be responsible for any additional expense incurred in delivering the Goods to the correct destination. The delivery date set forth on the Order is of the essence of the Contract. If the Seller anticipates that it will not be able to deliver the Goods upon the agreed delivery date, then the Seller shall immediately notify the Company thereof in writing; provided, however, that such notice shall not relieve the Seller of its responsibilities and liabilities with respect to on-time delivery hereunder. In such event, the Company may request that the Seller expedite delivery to the maximum extent possible at the Seller’s sole expense. If the Seller does not deliver the Goods by the agreed delivery date, then the Company shall be entitled to liquidated damages as agreed between the parties, up to and including the total Order value. Notwithstanding the foregoing, the Company reserves the right to claim repayment for any and all costs, losses, expenses and damages incurred by the Company that are attributable to the Seller’s delay in delivery. Such liquidated damages shall be paid at the Company’s written demand. Partial deliveries shall not relieve the Seller from liability for any late delivery hereunder. If the Seller discovers that it has shipped any non-conforming Goods to the Company, it shall immediately (and not more than 24 hours after such discovery) notify the Company thereof in writing; provided, however, that such notice shall not relieve the Seller of its responsibilities and liabilities with respect to defective goods hereunder.