We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Non-Nursing Functions Sample Clauses

Non-Nursing FunctionsFollowing the implementation of this Agreement, evidence shall be presented by employer to relieve nursing practitioners of those tasks and responsibilities which, in the judgment of the Director of Nursing and the Council of Nursing Practitioners, constitute non-nursing functions.
Non-Nursing FunctionsThe hospital will make reasonable and continuing efforts to minimize the need for bargaining unit nurses to perform non-nursing functions supportive to nursing care such as housekeeping, dietary, clerical functions, or the transport of supplies or stable patients.
Non-Nursing FunctionsThe parties recognize that Registered Nurses are highly educated professionals whose chief responsibility is patient care. The Employer recognizes the desirability of having nurses perform non-nursing duties such as Medicaid applications, screening telephone calls, transporting patients, transporting supplies, arranging for food stamps, duplicating, hole punching, other routine clerical work, hand- delivering doctor’s orders, messenger functions, etc. as little as practicable.
Non-Nursing FunctionsThe parties recognize that Registered Nurses are highly educated professionals whose chief responsibility is patient care. The Employer recognizes the desirability in terms of effective and efficient operations of eliminating or minimizing the performance by Registered Nurses of non-nursing duties such as Medicaid applications once social workers are assigned, screening telephone calls, locating records, transporting patients, transporting supplies, arranging for food stamps, completing E-CAP forms, duplicating, hole punching, other routine clerical work, etc., except as necessary or required by the Employer. The Registered Nurses also recognize that an important element in this continuing process is their duties and responsibilities in connection with the direction of the work of support personnel designated to perform such non-nursing duties. However, in order to avoid confusion, the Registered Nurse shall have made available to them a copy of the current job description of the support personnel responsible for those functions, and a description of how such support personnel are to be directed in the performance of those functions.
Non-Nursing FunctionsThe Employer and the Association recognize that the performance of non- nursing functions by registered nurses impedes their ability to deliver quality, cost-effective patient care and is not intended to be a part of their responsibilities. The Employer, therefore, agrees that registered nurses shall not perform non- nursing functions such as: 1. Ordering/stocking supplies; 2. Emptying garbage; 3. Washing/making beds upon discharge and for admissions, except bed- changing that is part of ongoing care;
Non-Nursing Functions. PMC recognizes that in addition to appropriate registered nurse staffing, appropriate inter-professional support and ancillary services are necessary to maximize safe patient care and quality outcomes. Such appropriate inter-professional support and ancillary services include at a minimum, effective and efficient support services (e.g. transport, clerical, housekeeping, and laboratory, and one-to-one observers).
Non-Nursing Functions. In the interest of high quality patient care, the parties agree that it is in the interests of the Hospital employees and patients to maximize the utilization of Registered Nurses in nursing functions and to minimize their use in non-nursing functions. Except in emergency situations, except where functions are extensions of patient care, and except where failure to do so would immediately jeopardize or impede patient care, employees covered by this Agreement will not perform the following functions ordinarily provided by housekeeping, maintenance, laundry, clerical, dietary, and transport departments: wash beds or other equipment or furniture; mop floors, clean up vomit or other substances from environmental surfaces or empty garbage cans; move furniture or equipment; transport patients for tests or procedures unless a nurse is required; transport cadavers; transport, blood, urine and/or specimens off unit; clean dialysis equipment and surgical equipment; staff scheduling. The Employer will use its best efforts to provide ancillary personnel to perform the above tasks.
Non-Nursing FunctionsEmployees covered by this agreement will not perform any of the following listed functions except where patient care is immediately jeopardized or those situations requiring the supervision of a professional nurse: a. Transportation of cadavers or specimens. b. Defrosting and cleaning of nourishment refrigerators; defrosting and cleaning of medication refrigerators after removal of medications by the Nursing Department. c. Cleaning of medication carts after the removal of medication by the Nursing Department. d. Obtaining and moving of equipment, including, but not limited to, beds, furniture, and orthopedic equipment. e. Caring for patient's personal clothing. f. Removal of paste from patient's hair after EEG. g. Cleaning of patient's units, including beds, over-bed tables, and cabinets. h. Terminal cleaning of patient-related equipment, including bedside utensils. i. Removal of substances on environment surfaces except where immediate safety is compromised. j. Collection of data, except that which directly pertains to the nursing process. After evaluation by the appropriate Divisional Director of Nursing, requests for data will be made in writing.

Related to Non-Nursing Functions

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • Training Fund Employers and/or individuals who manage, operate, assist or own, either partially or wholly, a company or companies working non-union in the construction industry on Mainland Nova Scotia within the craft jurisdiction of xxx Xxxxxxxxxx Local 83 shall not be eligible to be appointed to serve, or to continue to serve, as trustees on any trust fund referred to within this Collective Agreement. This provision shall apply to management trustees and union trustees alike. 30.01 Subject to the approval of xxx Xxxxxxxxxx Joint Training Fund Trustees, direct costs for upgrading the safety training of Union members described in Article 2.01 of this Agreement in Occupational Health and Safety courses required by Nova Scotia law, shall be paid by the fund.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Operations Support Systems Functions 9.1 Effective as of February 8, 2021, notwithstanding any other term or condition of the Amended Agreement or a Verizon tariff or SGAT, and subject to the transitional provisions set forth in Subsection 9.2 below, unbundled access to Operations Support Systems Functions will not be available from Verizon on or after February 8, 2021, except when such functions are used to manage other UNEs that remain available from Verizon, local interconnection, or local number portability. 9.2 Any unbundled access to Operations Support System Functions eliminated pursuant to Section 9.1 above will continue to be provisioned for the period in which unbundled access is available to the UNE managed through the use of such functions, but not after such period.

  • Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

  • Contract for Professional Services of Physicians, Optometrists, and Registered Nurses In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 2254.008(a)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.