care pathway automation on fhir - health level seven...
TRANSCRIPT
Issued commercial in confidence © Kainos Evolve Limited 2016 – no reproduction without prior consent.
Care Pathway Automation on FHIR
Alastair Allen7th December 2017
@AlastairAllen @KainosEvolve #EvolveIntegratedCare
Evolve enables healthcare delivery organizations to
transform how they deliver patient care through
Care Pathway Automation
• 35 NHS trusts with 150+ hospitals depend on Evolve
• 700+ care pathways implemented
• Apple MPP, one of only 12 in healthcare and one of only 3 which are considered to have global potential
• new platform live or being deployed at 4 major U.S. hospital networks - expect 100+ hospitals live by March 2018
• a division Kainos Group PLC www.kainos.com
Why Care Pathway Automation?
GLOBAL HEALTHCARE CHALLENGES
AGING POPULATION
AND CHRONIC
DIDEASES
AFFORDABILITY OF
HEALTHCARE
INCREASING
SHORTAGE OF
CLINICAL EXPERTS
How do we address these challenges?
BI-MODAL
HEALTHCARE
RAPID RE-ENGINEERING
OF CLINICAL PROCESSESACCESS TO
COMPREHENSIVE PATIENT
DATA
EASY COLLABORATION
Examples of Care Pathway Automation?
Enabling our customers to deliver
high-quality, patient-centric care
through better visibility of patient
information and management of
care pathways across teams and
organizations
Enabling our partners to accelerate
their innovation, bringing healthcare
technology solutions to care
providers, whilst reducing time and
cost-to-market
Typical FHIR Use Cases
v2
v3
FHI
R
FHI
R
Database
API
Application
EHR
FHI
RIntegration Engine
MODEL A – REPOSITORY + API MODEL B - EXCHANGE MODEL C – EHR
Model A• Repository + API
Model A – Repository (for Care Pathway Data)
• Care Pathway Data
• All data collected within an Evolve Care Pathway
is exported to the Evolve FHIR Repository and
then exchanged with the System of Record
• Documents
• Documents can be stored natively within the
Evolve Content Repository or referenced from
other content repositories
• Implemented using the FHIR DocumentReferene
Repository
• Audit
• All audit data across all Evolve micros-services
stored in an audit log implemented using the FHIR
AuditEvent Resource
12
Model A – Repository (for Medical Calculators)
• >20 Medical Calculators (e.g.
NIHSS, Alteplase etc.) built using the
FHIR Questionnaire Resource
• Calculators stored using FHIR
Observation Resource
• Open Source Opportunity?
Model B• Exchange
Model B - Exchange
• Regional Shared Care Record
in the NHS for 650,00 Patients
• Information integrated across
systems from primary,
secondary and tertiary care
• All data exchanged and
normalized to FHIR STU3
• 100’s of data-items exchanged
over 10’s of FHIR Resources
• No FHIR extensions required
Model C• EHR
Model C - EHR
THE FUTURE
PLUG ‘N PLAY
INTEROPERABILITY
@alastairallen
@KainosEvolve
https://www.kainosevolve.com/
Questions
Issued commercial in confidence © Kainos Evolve Limited 2016 – no reproduction without prior consent.
Commercial Statement© Kainos Evolve Limited 2016Kainos Evolve Limited ("Evolve") is a company registered in the UK under company number NI622515.
This presentation (and each slide and its content individually) is the copyright of Evolve, commercial in
nature and issued in confidence. It must not be reproduced, in whole or in part, for any purpose, without
the prior written consent of Evolve.
Evolve® is a registered trademarks of Kainos Evolve Limited. All rights are reserved. You may not delete,
change or modify any copyright or trademark notice. The information supplied shall be deemed, for the
purpose of the Freedom of Information Act 2000, to be "sensitive information". The information has been
provided in confidence by Evolve and disclosure may be prejudicial to the commercial interests of Evolve.
Where features, functionality or services are described in the content, these are a summary guide only
and are not a representation that all features, functionality or services will be made available on any
particular deployment of Evolve.