Data Transfer Process Sample Clauses

Data Transfer Process o The Contractor shall create a secure automated data transfer process that meets the functional and operational needs of the OCEMS system. o The automated data transfer process will be initiated immediately based on the following conditions, triggers, and filters:  When the initiator (e.g. Paramedic filling out ePCR) marks his / her PCR as “Complete” and posts his/her chart to Service Bridge; and  The initiator marks the data Field “Transporting Agency” (IT5.50) with the desired transporting EMS provider. o The NEMSIS XML file that is transferred for each EMS event will be made available on a secure/HIPAA Compliant web-service that will be hosted by the Contractor. o The NEMSIS XML file will include a Portable Document File (PDF) for each patient care record exported. o EMS provider agencies and/or their agents will be provided the tools that they need to access the Contractor hosted web-service so that they may establish their own data retrieval methods. o The web-service must be capable of partitioning provider data so that only those agencies that should have access to specific EMS events are the only one’s permitted to do so. o The following provides an example of the workflow:  Fire Department A initiates a ePCR, marks the run as “Complete”, selects Ambulance Company B as the “Transporting Agency”, and then posts their run to Service Bridge.  Based on the triggers and filters defined above, a NEMSIS XML file for the event is automatically generated and made available on the Contractor’s secure web-service specific to Ambulance Company B.  Representatives for Ambulance Company B access the web-service using Contractor supplied credentials at an interval that meets their operational needs (every thirty (30) seconds, every minute, every five (5) minutes, etc.).

Data Transfer Process. Client may order Mass Data Migration Services (the “Services”) through the IBM Cloud Control Portal (the “Portal) at the price set forth in the Portal subject to the following terms: (a) After Client places the Order, SoftLayer will send a portable storage device (“Device”) to the address specified by Client (“Client’s Address”). (b) Client will copy Client’s content (data) onto the Device, and the Device will automatically encrypt the data. Client will then ship the Device to the datacenter designated by IBM in the region selected by Client via one of the common carriers approved by IBM for this purpose. (c) SoftLayer will connect the Device to Client’s specified SoftLayer hardware (“Hardware”), transfer Client’s data from the Device to the Hardware, and delete all data from the Device after the transfer is complete. (d) Client is responsible for all charges associated with shipping, delivery, insurance, taxes and any other charges related to delivery of the Device to Client and to the agreed SoftLayer datacenter. (e) Client is not authorized to transfer the Device to any address other than the selected SoftLayer datacenter unless approved in advance by the IBM Cloud Global Trade Compliance team. Client’s removal of the Device from the country in which Client’s Address is located will automatically terminate this Agreement, and IBM will deem this a loss of the Device by Client for purposes of Section 5 liability. (f) The Device is for the exclusive use of Client for the purpose of the Services, and the Device may not be used for any other purpose. Client may not transfer the Device into the possession of a third party unless approved in advance by the IBM Cloud Global Trade Compliance team. (g) Only authorized account users may request the Services. (h) Client is solely responsible for and assumes the risk of harm caused by the actions of any third parties authorized by client to assist with transfer of the data, and indemnifies SoftLayer for all damages caused thereby.

Data Transfer Process o The Contractor shall create a secure automated data transfer process that meets the functional and operational needs of the OCEMS system. o The automated data transfer process will be initiated immediately based on the following conditions, triggers, and filters:  When the initiator (e.g. Paramedic filling out ePCR) marks his / her PCR as “Complete” and posts his/her chart to Service Bridge; and  The initiator Service/Agency ID is one of twelve (12) fire departments.  Anaheim Fire Department (30005)  Brea Fire Department (30010)  Costa Mesa Fire Department (30020)  Fountain Valley Fire Department (30025) County of Orange Health Care Agency 27 MA-042-14010212 Orange County – Medical Emergency Data System HCA ASR 14-000839 Page 27 of 56  Fullerton Fire Department (30030)  Garden Grove Fire Department (30035)  Huntington Beach Fire Department (30040)  Laguna Beach Fire Department (30045)  Los Angeles County Fire Department (19110)  Newport Beach Fire Department (30055)  Orange City Fire Department (30060)  Orange County Fire Authority (30065) o The NFIRS XML file that is transferred for each EMS event will be made available on a secure/HIPAA Compliant web-service that will be hosted by the Contractor. o EMS provider agencies/fire departments and/or their agents will be provided the tools that they need to access the Contractor hosted web-service so that they may establish their own data retrieval methods. o The web-service must be capable of partitioning provider data so that only those agencies that should have access to specific EMS events are the only one’s permitted to do so. o The following provides an example of the workflow:  Fire Department A initiates a ePCR, marks the run as “Complete”, and then posts their run to Service Bridge.  Based on the triggers and filters defined above, a NFIRS XML file for the event is automatically generated and made available on the Contractor’s secure web-service specific to the initiators Service/Agency ID.  Representatives for Fire Department A access the web-service using Contractor supplied credentials at an interval that meets their operational needs (every thirty (30) seconds, every minute, every five (5) minutes, etc.)