The role of chief medical information officer (CMIO) s is a relatively new job in the healthcare industry, although one that is becoming increasingly important since the acceleration of government efforts to establish a national record-keeping system for health records. To understand where the role fits in the eHealth landscape, IDM spoke with Dr Ronnie Ptasznik, appointed CMIO at Victoria's Monash Health in 2015. in addition to his duties as CMIO and an Associate Professor at Monash University, Dr Ptasznik maintains a senior clinical role as Deputy Director of Monash Health Diagnostic Imaging over its five campuses.
In this article, Kapish Consultant Jon Grundy explores HP’s latest solution to regaining control of the growing records governance and compliance issues associated with snowballing SharePoint content in the enterprise. Jon Grundy is a highly experienced TRIM consultant with a diverse range of industry experience including nine years of HP TRIM/HP RM administration and support. Jon worked with both TOWER Software and HP before joining Kapish in December 2013.
The Happy Accident, which is often cited as a principal ROI of enterprise social networks, refers to the chance discovery of the right person or the right piece of enterprise knowledge to solve a business or process challenge. For instance, Bruce in Melbourne, dealing with a corporate crisis, fires off an anxious Yammer/Jive/Tibbr post at 6.00pm in the evening Sydney time, before heading off to a nervous sleep. Meanwhile, as Bruce slumbers fitfully, at 3.00am the following morning Colleen logs in from Dublin and comes across the post and immediately fires back with the critical data. Bruce did not know Colleen was the one to turn to, nor even how to find here, it was all a Happy Accident. Enterprise Social wins again!
Is private email used by government ministers or prime ministers accessible to freedom of Information (FOI) requests? Malcolm Turnbull’s office is only certain that this may "potentially" be the case. Experts are even less sure.
The New Zealand government has announced plans to build a single, national electronic health record (EHR) able to be accessed via portals and apps running on a variety of devices.
The aim of records management is simple: keep what you need and discard what you don’t. When this aim is achieved, organizations are less exposed to risk. The question is, how can we achieve this simple goal?
Is there any domain that has a broader mix of terminologies that need to be comprehended, or a greater need for system integration? Over the years doctors developed their own specialised languages and lexicons to help them store and communicate general medical knowledge and patient-related information efficiently. The promise of a global standard for Electronic Health Care Records is still years away.
I might be a little old fashioned, but I came up through an Electronic Content Management (ECM) and Transaction Content Management (TCM) community where you never put BLOBs directly in your database. By BLOBs, I am referring to Binary Large Objects (not the 1988 thriller movie) which are chunks of images or other large data stored as a single object. I was taught that the database should hold pointers to BLOB content stored on another inexpensive storage system like SAN or NAS drives. However, when I entered the world of SharePoint, I realised that everyone was storing BLOBs in their databases.
Acaveo, a provider of File Analysis software for analysing and managing unstructured data, has been awarded a Build in Canada Innovation Program (BCIP) contract to deploy its software at Employment and Social Development Canada (ESDC).
Anyone who's had the responsibility to manage an end-user centred system has heard this refrain when asking people to get rid of old emails, documents, files, voice mail recordings, pictures, or any other electronically stored information (ESI). "I need it to do my job" or "It has business value and I need to save it".
