Data Use for a Limited Data Set Sample Clauses

Data Use for a Limited Data Set. 6.1 The PHI to be provided by Covered Entity will include the following hospital outcome measures for patients who suffered an out-of -hospital cardiac arrest (“OHCA”) event: a) Essential Elements (1) Emergency department outcome; (2)Hospital outcome;
AutoNDA by SimpleDocs
Data Use for a Limited Data Set a. Covered Entity agrees to participate in the CARES surveillance registry described in the cover letter attached to this Agreement, and as a participant, will provide certain PHI regarding OHCA patients to the Business Associate for the purposes described in this Section. The PHI to be provided by Covered Entity will include the following EMS datapoints for patients who suffered an out-of -hospital cardiac arrest (“OHCA”) event: 1) Address of Cardiac Arrest (town/city, State and zip code only); 2) Name, Age, Date of Birth, Gender, Race/Ethnicity of patient; 3) EMS Agency ID; 4) Date of Cardiac Arrest; 5) Call Number (and Booklet Number, where applicable); 6) ID of First Responder(s) Involved in Incident; 7) ID of Destination Hospital; 8) Time Elements Including “Time of First CPR,” “ROSC Time,” “CPR Termination Time,” “Time of First Defibrillation,” approximate times of “EMS Notified,” and “EMS Arrived at Scene;” 9) Location Type; 10) Witnessed Status of Arrest and Whether Arrest was Witnessed Prior to or After the Arrival of EMS;
Data Use for a Limited Data Set a. Covered Entity agrees to participate in the CARES surveillance registry described in the cover letter attached to this Agreement, and as a participant, will provide certain PHI regarding OHCA patients to the Business Associate for the purposes described in this Section. The PHI to be provided by Covered Entity will include the following hospital outcome measures for patients who suffered an out-of -hospital cardiac arrest (“OHCA”) event: (1) Emergency department outcome; (2) Hospital outcome; (3) Disposition from hospital; (4) Hypothermia treatment if provided; and (5) Neurological outcome at discharge from hospital. b. Business Associate will have the right to use and disclose PHI provided to it by the Covered Entity for research, public health or health care operations purposes, as provided in Section 3.a above. The Limited Data Set will be used in connection with the CARES surveillance registry, which is created for the health care operations and public health activity purposes further described in the attached cover letter to this Agreement. Without limiting the foregoing, the Limited Data Set will be available to and may be used by Business Associate, Covered Entity and other local emergency medical system administrators, medical directors, and 911 systems personnel, as well as epidemiologist and researchers studying OHCA events in an effort to better understand methods to improve survival from these events. The Limited Data Set also will be provided to the CDC staff in the Chronic Disease Branch on a regular basis. c. Business Associate will not use or further disclose the information contained in the Limited Data Set other than as permitted by this Agreement or as Required By Law. d. Business Associate will use appropriate safeguards to prevent the use or disclosure of the information contained in the Limited Data Set other than as permitted in this Agreement. e. Business Associate will not attempt to identify the Individuals to whom the information contained in the Limited Data Set pertains, or attempt to contact such Individuals. f. Business Associate will report to Covered Entity any use or disclosure of the information contained in the Limited Data Set not provided for in this Agreement of which Recipient becomes aware. Business Associate will take reasonable steps to limit any further such use or disclosure. g. Business Associate will ensure that any of its agents or subcontractors to whom it provides the Limited Data Set agrees in writing t...

Related to Data Use for a Limited Data Set

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Communications Relating to Portfolio Securities Subject to the provisions of Section 2.3, the Custodian shall transmit promptly to the Fund for each Portfolio all written information (including, without limitation, pendency of calls and maturities of domestic securities and expirations of rights in connection therewith and notices of exercise of call and put options written by the Fund on behalf of the Portfolio and the maturity of futures contracts purchased or sold by the Portfolio) received by the Custodian from issuers of the securities being held for the Portfolio. With respect to tender or exchange offers, the Custodian shall transmit promptly to the Portfolio all written information received by the Custodian from issuers of the securities whose tender or exchange is sought and from the party (or his agents) making the tender or exchange offer. If the Portfolio desires to take action with respect to any tender offer, exchange offer or any other similar transaction, the Portfolio shall notify the Custodian at least three business days prior to the date on which the Custodian is to take such action.

  • Unbundled Voice Loop SL2 (UVL-SL2) loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NuVox. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on SL2 loops. The OC feature will allow NuVox to coordinate the installation of the loop with the disconnect of an existing customer‟s service and/or number portability service. In these cases, AT&T will perform the order conversion with standard order coordination at AT&T‟s discretion during normal work hours.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • 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 C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Your Billing Rights: Keep this Document for Future Use This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

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