Inquiry Search
Rec-ID | Code | Recommendation |
---|---|---|
REC286-2067 | 24 - Govt responsibility | Improve integration of health information systems. |
REC286-1479 | 6 - Insurance and legal liability | Ensure appropriate levels of insurance of public assets from flood risks. |
REC286-2028 | 8 - Communications and warnings | Review community information and warning systems to ensure they cater for heatwave messages |
REC286-2063 | 24 - Govt responsibility | Review Tas Govt interoperability arrangements. |
REC286-1475 | 8 - Communications and warnings | Integrate existing capabilities into a Total Flood Warning System. |
REC286-2077 | 6 - Insurance and legal liability | Improve working relationship with the insurance industry to access impact information. |
REC286-2027 | 8 - Communications and warnings | Develop arrangements to identify and communicate with people vulnerable to heat stress |
REC286-2059 | 24 - Govt responsibility | Enhance business continuity planning by the Tasmanian Health Service. |
REC286-2074 | 8 - Communications and warnings | Continue the enhancement of forecast and warning services. |
REC286-2020 | 6 - Insurance and legal liability | Improve insurance affordability. |
REC286-2058 | 24 - Govt responsibility | Clarify the relationship between the DHHS and THS in the establishment of flu services. |
REC286-2069 | 24 - Govt responsibility | Implement a database management approach for notifiable disease record systems. |
REC286-2019 | 24 - Govt responsibility | Assess water supply resilience in the case of an interruption. |
REC286-2047 | 6 - Insurance and legal liability | Raise public awareness of the limitations of general insurance relating to landslide. |
REC286-2068 | 24 - Govt responsibility | Develop a disaster client record system. |
REC286-2016 | 6 - Insurance and legal liability | Review legal liability of participants in prevention and mitigation preparedness, response and recovery activities. |
REC286-2033 | 24 - Govt responsibility | Incorporate heatwave surge response planning into business continuity planning. |
Rec-ID | Code | Recommendation |
---|---|---|
REC285-2517 | 38 - Agency/Department Reporting | The report recommends that Ambulance Tasmania collects data to allow regular and meaningful comparison of clinical outcomes at the regional level, to better allocate resources and to rapidly identify problems. |
REC285-2525 | 38 - Agency/Department Reporting | The report recommends that Ambulance Tasmania outline what KPIs are measured and provide targets or benchmarks to define what is good or poor performance. |
REC285-2518 | 38 - Agency/Department Reporting | The report recommends that regional summary reports of clinical reviews be standardised to facilitate review and comparison across regions. |
Rec-ID | Code | Recommendation |
---|---|---|
REC245-2598 | 24 - Govt responsibility | That government considers the establishment of a separate unit to implement and operate a Whole of Government network if existing stakeholders fail to make significant progress toward an agreed Whole of Government solution. |
REC245-2596 | 24 - Govt responsibility | That the Whole of Government project’s objectives should include meeting entity requirements and the consultant be asked to reevaluate the revised set of objectives. |
Rec-ID | Code | Recommendation |
---|---|---|
REC140-3558 | 6 - Insurance and legal liability | DHHS need to confirm adequate accident insurance coverage for staff working in retrieval medicine. Coverage specific to helicopter and fixed wing duties is required. |
REC140-3575 | 24 - Govt responsibility | The preferred model for the Tasmanian Medical Retrieval Services is to have TMRS and NETS staff based in RHH. The fixed wing would remain based in Launceston (for the present) with the helicopter to remain based in Hobart. |
REC140-3574 | 38 - Agency/Department Reporting | Formation of a subcommittee of the DHHS Tasmanian Medical Retrieval Services Committee to identify risk exposures, system problems and potential solutions. The subcommittee should review data, problem cases, system issues and generate a risk register. Meetings should occur at least quarterly. |