The Future of Healthcare Data Management Jamie Clifton Director Product Management BridgeHead Software
The Future of Healthcare Data Management
• The Future of Healthcare Data Management?
• Since I can see the future at the end of the presentation I will give you – National Lottery results for June 18th 2012 – Winner of the 2013 Derby
• We will be talking about the steps you can do today to get to the future – It’s a journey not a destination
Today’s talk: Castles built on Sand
GOAL: IT & Clinical Workflow In Sync
GOAL: IT & Clinical Workflow In Sync
GOAL: IT & Clinical Workflow In Sync
Healthcare Data Management Platform
Reduces the cost of storage
Helps protect all your data
Increases data ownership
Improves data access
Facilitates data sharing
Supports Healthcare standards
The HDM Journey
Radiology
Pathology
Cardiology
Ophthalmology
Scanned patient documents
Healthcare Information Systems
Laboratory Information Systems
Office files & Email Systems
Shared Protected Stored
Storage Requirements
Requirement Radiology Other ‘ology
HIS EMR
Rapid Access to content √ √ √ √
Access Likelihood for old content
< 5% <5 % < 5% < 5%
Cost effective √ √ √ √ Scale √ √ √ √ Future proof √ √ √ √
Every data source has the same requirements.
Protection ‘Problems’
• 47.1% Organisations haven't tested DR plans – 38.3% globally
• 20.6% ‘Robust tied and tested DR plan in place’ – 26.1% globally
• 20.6% ‘need to put A solution in place’ – 12.2% globally
• Current CDS model isn’t going to fix this issue
For Healthcare Organizations Surveyed by BridgeHead in 2011
Protection ‘Problems’
• 30% of all the worlds storage is now medical
• 85%+ of all the data you own and store will never be accessed again
Answer:
• Understand your data profile, how and when data is used
• Manage static data differently to active data
• Create automated transition from active to static
How do I protect data better?
Share – With Whom?
• National Sharing – Little appetite
• Regional Sharing – Where the investments are being made
• What about in your facility?
• Typical Answer has been ‘interface engines’ – Good idea for data that is ‘in-flight’ like HL7 messages – Not a great idea for data that is ‘at rest’ like medical
images
Create a virtual relationship between your healthcare data and its storage and applications and clinical workflow.
Share – The Internet Experience
• The Internet already allows us to share vast quantifies of disjointed information
• In basic terms information is sent and the browser interoperates the results – Yes the web server can spot and aid the browser
• AH but that requires plug-ins and they are BAD – Yes but the HTML5 STANDARD removed this
• In Healthcare we interoperate the results and then send them – Constant migration / translation and scaling issues
Share – Between Applications
PACS A PACS B Scanned Docs
PACS A database
PACS B database
Scan database
RIS
EPR
Share – Between Applications
PACS A PACS B Scanned Docs
Clinical Records Storage
RIS
EPR
Share – Between Applications
PACS A Scanned Docs
Clinical Records Storage
RIS
EPR
Share – Between Applications
PACS A Scanned Docs
Clinical Records Storage
RIS
EPR
PACS C
16 BridgeHead Software / Healthcare Data Management
Share – Migrating from CDC
• We all know the issues regarding timings • What are you migrating RIS / PACS / VNA? • Do you know the standards you are setting?
• Make this the last ‘painful’ migration
Share – Journey’s End
Clinical Records Storage
RIS
EPR
DICOM IN
HTTPS
XDS(++)
What have we seen?
• Share is the future / ‘journey’
• Create a fluid relationship between applications and data
• Migrate applications (workflow), not data
• Standards are key (e.g. DICOM / XDS) – Customisation is inevitable (e.g. Webservices)
Thanks
• Lottery - six numbers between 1 and 49
• Grand National - a horse
• Questions?
Break