2013_1209_packet - Laserfiche WebLink

Home

570 5.8.6 Authentication is used to ensure that only authorized users may access the 571 System. 572 5.8.6.1 Members must use authentication methods that comply with 573 applicable state and federal security requirements. 574 5.8.6.2 Members are responsible for the costs to implement and maintain 575 authentication. 576 5.9 Interfaces —these are software programs developed specifically to link other 577 software applications to the System. For cost allocations, refer to section 8. 578 5.9.1 The entities named below will be responsible to ensure the identified 579 interfaces or their replacements or version changes listed below operate 580 according to applicable specifications. 581 5.9.2 County Responsibilities. 582 5.9.2.1 The County is responsible for both "ends" of the following 583 interfaces: 584 5.9.2.1.1 Alphanumeric paging 585 5.9.2.1.2 ANI /ALI /E9 -1 -1 586 5.9.2.1.3 BCA LEMS 587 5.9.2.1.4 Apparatus move -up management (one -way data 588 export out of System) [DECCAN Live MUM at the time 589 of the original Agreement] 590 5.9.2.1.5 Fire Department /Station alerting (one -way from 591 System to alerting application) 592 5.9.2.1.6 Knowledge Center (Emergency Management) 593 5.9.2.1.7 Pictometry 594 5.9.2.2 The County is responsible for the County's "end" of the following 595 interfaces: 596 5.9.2.2.1 CAD -to -CAD interface with Allina Medical. Note: Allina 597 Medical will pay for its end, both initially and ongoing. 598 5.9.2.2.2 Fire Records Management System (one -way data 599 export out of System) [ImageTrend at the time of the 600 original Agreement]. 601 5.9.2.2.3 HazMat, pre -plan, and premise information [via 602 ImageTrend at the time of the original Agreement]. 603 5.9.2.2.4 Law Enforcement Records Management Systems (one- 604 way data export out of System). 605 5.9.2.2.5 EMS RMS (one -way data export out of System) [Sansio 606 ePCR at the time of the original Agreement]. CAD and Mobile Data Agreement Ramsey County and User Members Page 16 of 48