Metro Hospital Compact Emergency Resource Request Process Sample Clauses

Metro Hospital Compact Emergency Resource Request Process. Healthcare facility needs resources during incident* Request non-medical resources from local jurisdiction EOC (if EOC not open – appropriate public safety agency). E.g.: water, gas, traffic Medical resource? No Yes Contact corporate chain partners, vendors/alternate vendors, usual mutual aid partners for assistance. If not resolved, contact RHRC on-call for assistance 000-000-0000 or via EMH-CALL Advise local EOCs, MDH / agencies of actions as appropriate (especially if life safety issues or likely ongoing needs) Resource request and coordination – for multiple requests, advise facilities use MnTrac Resource Request system (paper backup form if needed). Coordinate fulfillment and allocation among metro hospital compact hospitals. Issue resolved? RHRC conducts situation analysis. Determines if multiple facilities will be affected and/or ongoing demand. Opens MnTrac Coordination Center room and issues alerts as necessary. Share information with stakeholder partners Yes Pool resource requests and prioritize if partial fulfillment. Send to EOC for the jurisdiction in which the incident occurred for referral to SEOC. If multi-jurisdictional (e.g. pandemic), pass pooled requests to EOC in county in which RHRC located (e.g. at HCMC – Hennepin County). EOC receiving request shares information on resource requests/fulfillment with other affected jurisdiction EOCs as appropriate No * Resources required but no emergency incident – use usual corporate partners, alternate vendors, direct request to department at other facility Appendix 2 Metro Hospital Compact Scarce Resource Triage: Concept of Operations
Sample 1
AutoNDA by SimpleDocs

Related to Metro Hospital Compact Emergency Resource Request Process

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Quality Control Program The Contractor shall describe the Quality Control Program in a written document which shall be reviewed by the Engineer prior to the start of any production, construction, or off-site fabrication. The written Quality Control Program shall be submitted to the Engineer for review at least ten (10) calendar days before the start of construction. The Quality Control Program shall be organized to address, as a minimum, the following items:

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from CBB to Verizon, CBB, at CBB’s own expense, shall:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • PROFESSIONAL DEVELOPMENT AND EDUCATIONAL IMPROVEMENT A. The Board agrees to implement the following:

Time is Money Join Law Insider Premium to draft better contracts faster.