Category Archives: Digital Health Ecosystem

It’s not about Open Source

Readers of the blog will know that I am an enthusiastic supporter of open platforms and was pleased to be able to contribute to the recent publication of “Defining an an Open Platform” by the Apperta Foundation. Assiduous readers will have noticed that the eight principles in this document are a evolution of those that first appeared here 18 months ago in 2016.

I had thought that “Defining an Open Platform” makes it clear that open platforms are agnostic with regard to software licensing and IPR. However, I’m receiving comments where people continue to conflate open platforms and open source.So to be clear:

Open platforms are about open standards they are not about and do not require open source software.

An open platform can be created without a single line of open source code or indeed without a single line of proprietary code if that’s what those building it want. While, in practice neither of those extreme choices is either likely or desirable both are possible.

Open platforms are about standards and while these standards will often be, but are not always,  “open source” the software that implements them need not be.

The core principle  of an open platform is that access to data and services on the platform is via a set of open APIs that accept and return data in an open, shareable and computable format. Definitions of these APIs need to be open so that any willing party can freely implement them. As long as all participants in a open platform ecosystem conform to these APIs both applications and data are portable and vendor lock-in is no more, irrespective of whether components and applications are open source or proprietary.

Today, most large scale implementations of open platforms (e.g. that in Moscow) consist primarily of proprietary applications running on a proprietary platform – Moscow uses the Marand openEHR Clinical Data Repository and the Forcare implementation of IHE-XDS, both are proprietary implementations of open standards. The key difference is that Moscow can, and indeed has, switch out these proprietary products and replace them with an alternatives if a vendor fails to deliver performance or value.

There are of course open source alternatives to these proprietary products and the existence of these is important in ensuring proprietary vendors stay true to the standards. It’s also true that proprietary implementations often contain open source components (many of which come from the proprietary vendors themselves who understands the wisdom of sharing and open sourcing certain components.)

My expectation is that successful open platform ecosystems will be a mixed economy of open source and proprietary components and applications. I think it more likely that economically sustainable open source models will emerge in relation to platform infrastructural components than for applications However, there is nothing in the definition in “Defining and Open Platform” that mandates an open source.

Defining an Open Platform – The Reformation of Digital Health

On the 31 October 1517 Martin Luther nail his “Ninety-Five Theses” on to the door of a chapel in Wittenberg, Germany and started the Reformation.

500 years later on the 32 October 2017 Apperta published “Defining an Open Platform”. Being the modest folk we are it contains a mere eight principles and we launched it less theatrically at EHI LIve, but I think it might be the start of a Reformation in Digital Health that will finally enable digital technology to have the transformative effect in our sector that has so far eluded us.

Open Platforms are about opening up the data in health and care systems to innovation, they are about open standards, they are about ending vendor lock-in, by making data and applications portable.

The Foreword by two eminent clinicians say’s it better than I can.

Health and care face a crisis, with growing demands and spiralling costs. In other sectors we have seen digital technology transform the way services are delivered, but so far, despite substantial investment, such transformational effects have eluded us in health and care.

The Apperta Foundation believes innovative technologies can achieve the transformation that we seek, yet if we want a different outcome from future investment we are going to have to do things differently and break away from 20th century technology and business models that lock data in proprietary formats and customers into obsolete systems.

Change requires innovation and innovation does not come from the incumbent players. If we look to other sectors we can see that it was Amazon not Foyles, eBay not Exchange and Mart, Wikipedia not Encyclopedia Britannica that transformed their sectors through digital innovation.

In health and care, the complexity of the environment in terms of the informatics, regulation governance and culture make the barriers to entry for innovative new players much higher than they were in other sectors  In health and care we have seen no new entrants to the market reach discernible scale in the last twenty-five years.

We believe that open digital platforms based on open standards can lower barriers to entry, stimulate innovation and enable successful startups rapidly get to scale.

This is not just our view one shared by global experts and the major consultancies, more than this it is an approach that has already been proven at scale elsewhere.

We want to create an ecosystem where health and care communities can deploy and scale up an open platform implementation confident that the data they store in it and the applications that run on it are portable to any other. This requires an unambiguous definition of what we mean by an open platform and the standards on which it should be based.

This document is an attempt to propose such a definition, based on standards that have been proven to work worldwide including HL7 FHIR, SNOMED-CT, IHE_XDS and openEHR.

We put this document forward asa blueprint to enable and support those pioneers keen to progress on the journey to take digital health and care into the 21st Century.

Bill Aylward MA MB BChir FRCS FRCOphth MD 
Chair Apperta Foundation

Rebecca Wassall BDS  PhD
CEO Apperta 

Clinical Lecturer / StR in Special Care Dentistry
Newcastle University

You can find the document at openplatforms.apperta.org Apperta are asking for comments. I urge you to read it and join the debate.

 

Open Digital Platform Challenge Fund

Many  will be aware of the proposal that Tony Shannon and I have been promoting to persuade the decking to allocate 1% of the money they plan to spend on an “Open Digital  Platform Challenge Fund” to stimulate the development of an open digital ecosystem based on open standards.

We have had a positive response so far and will shortly be presenting out plans to the NHS CIO and CCIO. We want to be able tell them that there are enough people and projects committed to an Open Digital Ecosystems to make good use of the money we are asking for and give then a good idea of the projects that might come forward if they take up our suggestion.

To this end we have been asking people for expressions of interest via this link . We are looking for expressions of interests from people who support the approach and the specific standards laid out in our document. In not onerous to fill in the form which does not imply a fixed commitment just a general indication of interest.

If you have not already done so I’d urge you to let us have your ideas

Full details below

 

Globe (1)

Untitled drawing

1) Executive Summary

An NHS open digital platform challenge fund will stimulate the development of an open platform in the NHS. Open digital platforms are independently forecast by McKinsey and Co to reduce the delivery of care costs across the NHS by 11%. They will support widescale entry and growth of suppliers into the market, injecting innovation at all levels of service delivery to support improved care outcomes for our patients.

In the context of an NHS struggling through a perpetual winter, open digital platforms present a realisable opportunity to massively stimulate new ways of working, process innovation and a new digital health and care market, based around services. This is independently forecast by McKinsey and Co who predict a positive financial impact in excess of 11% across the whole of health and social care.

By creating an open digital platform and a move towards a services market, the NHS opens up the market to innovative commercial and social enterprises who presently have great difficulty breaching the significant barriers to entry. At the same time it creates an environment where health and care professionals can readily create, contribute and share new digital tools to support transformational new models of care, radically improving the care outcomes of our patients and building a sustainable care ecosystem that is fit for the future.

There is little disagreement that platforms represent the future for digital health. Rather the present debate is about who should own them, and how and when they will emerge. The “status quo” retains the closed platform frameworks, introducing open interfaces for exchange of information. This provides a short term stimulus, supporting improvements in patient care and operational efficiencies. However in the longer term, by seeking to control the rules of engagement and restricting the mobility of data, the retention of closed platform frameworks will stifle competition, impede innovation, and continue to drive-up costs.

Open digital platforms are a radical alternative that overcome the serious shortcomings of closed platforms.
They present the most assured approach to achieve consistent, long term and affordable growth in innovation-led service transformation across the complexities of health and social care. They will enable the full competitive aspects of market supply to be exploited, with associated benefits of the injection of innovations on a massive scale. For this reason, open digital platforms are manifestly in the interest of both the NHS and its patients.

The purpose of the proposed Open Digital Platform Challenge Fund is to stimulate the development of an open platform ecosystem through kick-starting the creation of open platforms, building on work already well underway, and the development of exemplar applications to exploit them.

We propose that the fund is created through diverting 1% of the investment each year in NHS digitisation into the challenge fund. This fund would be made available via an annual open competition in the form of relatively small awards to innovative organisations (public, private and third sector). The selection of projects will be balanced to stimulate and develop an open ecosystem of shareable and reusable applications to service across health and social care. We are inviting submissions of expressions of interest into this Open Platform Fund. In so doing, we will gauge the wider interest in this Open Platform fund proposal to then quickly bring these related responses to the attention of both NHS Digital and NHS England by the end of February 2017 and seek the related funding.

2) Current Situation

To introduce this bid for funding we need to review the current situation with important context on the bigger picture issues that are at play. We need to acknowledge and understand the current mediocre state of health IT, as an immature and problematic market with mixed/relatively poor value for money and results seen from billions of £ and $ of investment from the UK to the US and elsewhere.

We also need to recognise the related digitisation of the NHS has been over promised and under delivered for some considerable time. Compounding this people/process/technology problem is the ongoing and perpetual winter faced by the frontline in the NHS that is in the news.

We restate the need to continue the critical push towards more personalised, integrated care at home and in the community to meet the 2020 vision. This clearly requires an underpinning patient centred infrastructure to do so. Last February Jeremy Hunt announced £4.2 billion for NHS Health IT. In the last 18-24 months while there have been plans in the form of Integration Pioneers, Vanguards, Local Digital Roadmaps (LDRs), Sustainability Transformation Plans (STPs), there has been little/no allocated funding to date to make these happen.

In Autumn 2016 we were able to read and digest the latest review of the NHS IT, authored by US physician Dr Bob Wachter. Dr Wachter built his reputation as establishing the hospitalist as a medical specialty in the US. In recent years he has become a fearless and honest critic of the state of Healthcare IT in the US, with his book “Digital Doctor : Hope, Hype & Harm at the Dawn of Medicines Computer Age” (2015) exposing the real mediocre state of the health IT market in the US. The book and related opinion pieces on the state of health IT industry he explains some of the real problems with the current supplier market is clear. In a New York Times Op Ed piece on “Why Health Care Tech Is Still So Bad” (2015) he highlights that

“In today’s digital era, a modern hospital deemed the absence of an electronic medical record system to be a premier selling point…That hospital is not alone. A 2013 RAND survey of physicians found mixed reactions to electronic health record systems, including widespread dissatisfaction. Many respondents cited poor usability, time-consuming data entry, needless alerts and poor work flows”.

However in the NHS, Dr Wachter’s recent review led to funding being provided to “digital exemplars” all of which are a small group of hospital trusts in the NHS who will invest in those very same health IT monoliths. While understandable as a means to “do something”, rather than nothing, given the state of affairs is understood, it is sadly limited in its thinking and perpetuates the usual tactics that we have seen in the NHS IT for years, i.e. investing in the same 20th Century monoliths of old. We know that doing the same thing over and over and expecting different results is futile.

Simply put, if a small elite are getting the focus of funding for investments in 20th Century health IT monoliths over the next years then inequity within the system will increase, while original ideas in the sector to bring care into the modern era will decrease.

We have been left asking where has the requirement for integrated person centred care gone, that is ingrained in the other plans that NHS and local authorities have been working towards with STPs and LDRs etc.

What is sorely missing is the open patient centric platform that Dr Wachter looks forward to and that healthcare awaits. As this is a glaring omission, our paper recommends a focussed investment towards that end as part of a bimodal strategy for NHS IT at this challenging time.

3) What can be done

The changes required are radical, if we are to simply survive, yet alone thrive in the years ahead. We know we need a mix of people + process + technology changes. We know too that the leaders of the NHS understand and value the role of innovation and the crucial role of information technology in achieving same.

3.1) The role of an open platform

For some time now leading thinkers on both sides of the Atlantic, in the NHS and indeed the US has been calling for a move towards a more open platform approach. From within the US market, the establishment of Healthcare Services Platform Consortium aims to address the mediocrity of the “big 6” monoliths and the concurrent problem of the thousands of small unrelated vendors.

“EHRs are becoming commodity platforms. The winner will be the EHR vendor that provides the best platform for innovation – the most open and most extensible platform.”

In this we wholeheartedly agree and concur with our US colleagues.

We believe there is now a compelling case for a small but useful investment in Health IT from the bottom up, to the princely sum of 1% of the planned £4 Billion NHS IT expenditure, aimed deliberately at the integrated, patient centred care vision of Personalised Care 2020, based on the principle that all projects should aim to leverage elements of a common open platform.

4) 1% Case for an open platform

We are making a case for an investment of just 1% of available NHS IT funds to offer a way forward to improve the care of 99% of the population. To do so we have highlighted Dr Watchers analysis and writings to focus on the key problems and issues we seek to address;

Usability

“This principle of user-centered design is part of aviation’s DNA, yet has been woefully lacking in health care software design.

Interoperability

“[There are] Political obstacles to overcome, put in place mostly by vendors and healthcare systems that remain reluctant to share.”

Vision for patient centred care

“In essence, there will no longer be an EHR in the traditional sense, an institution-centric record whose patient portal is a small tip of the hat to patient-centeredness. Rather, there will be one digital patient-centered health record that combines clinician-generated notes and data with patient-generated information and preferences. Its locus of control will be, unambiguously, with the patient.”

So in order to address these real issues and support the national ambitions – usability, interoperability and patient centred care we will use the investment fund available to benefit the broader public. We wish to draw attention to that part of the population who could be better served by the NHS with an improved patient centric platform today. We are also mindful of the need to support;

  • Prevention, Self care and management
  • GP patients
  • Community Care Patients
  • Mental Health Patients
  • Social Care

We look to the leadership provided by the Gov UK Digital Service standard to highlight the principles to underpin the approach we commend.

Pursue User Centred Design & Agile Development

Leverage Open Source & Open Standards

In our work to date (on the Ripple programme and Code4Health platform based on openEHR) we have deliberately pursued these principles to useful effect and recommend them to others who wish to transform healthcare with information technology. We welcome wider scrutiny of our open platform work to date. Our work and the leading work of others (such as the Endeavour Foundation and the INTEROPen CareConnect API Collaborative) in this field, leads us to believe there is now a real, significant appetite for wider and deeper moves towards an open digital platform in the NHS.

By creating an open digital platform ecosystem, the NHS opens up the market to innovative commercial and social enterprises who presently have great difficulty breaching the significant barriers to entry. At the same time it creates an environment where health and care professionals can readily create, contribute and share new digital tools to support innovative new models of care.

We firmly believe that a small but focussed 1% investment can deliver against some of the key challenges in Personalised Health and Care 2020 on an open service oriented platform- to stimulate the public & private sector. An open healthcare platform fit for the 21st Century.

 

5) What is an Open Platform?

Platform based architectures power the internet, with the platform providing the plumbing (the infrastructure, data and services) that applications need, freeing the application developer to focus their efforts on their application without the need to build the infrastructure it needs to operate. Platform approaches speed development, make applications more robust and interoperable and open up a new services market in healthcare IT, where suppliers compete on services and the value they add rather than on the proprietary nature of their software.

An Open Platform is based on freely available open standards, so that anyone can play. As no one party can control the platform – they must collaborate – just like the Internet.

An Open Platform has the following characteristics:

  • Open Standards Based – The implementation should be based on wholly open standards. Any willing party should be able to use these standards without charge to build an independent, compliant instance of the complete platform;
  • Share Common Information Models – There should be a set of common information models in use by all instances of the open platform, independent of any given technical implementation;
  • Support Application Portability – Applications written to run on one platform implementation should be able to run with either trivial or no change on another, independently developed;
  • Federatable – It should be possible to connect any implementation of the open platform to all others independently developed, in a federated structure to allow the sharing of appropriate information and workflows between them;
  • Vendor and Technology Neutral – The standards should not depend on particular technologies or require components from particular vendors. Anyone building an implementation of the open platform may elect to use any available technology and may choose to include or exclude proprietary components;
  • Support Open Data – Data should be exposed as needed (subject to good information governance practice) in an open, shareable, computable format in near to real-time. Implementors may choose to use this format natively in their persistence (storage) layer of the open platform itself or meet this requirement by using mappings and transformations from some other open or proprietary format;
  • Provision of Open APIs – The full specification of the APIs (the means by which applications connected to the platform a should be freely available.

The key to an open platform is the definition of a set of standard interfaces (APIs) to the range of services that might be provided on a platform defined by an open process that all interested parties can participate in (like Internet standards) and that are freely available for all to use.

While it may be encouraged, not all elements in an open platform need to be open sourced. We believe that “infrastructural” components that are generic, reusable and utility like (e.g see Appendix 1 below) should be open sourced, while the overlying applications do not necessarily need to be open sourced, as long as they leverage open data models and offer open APIs.

6) Why an open digital platform?

We have seen across all sectors how platforms are changing the way people lead their everyday lives, from how we communicate and interact, how we travel and where we stay, how we manage our finances to how we shop, to name but a few. Platforms transform. An open digital platform supports:

  • Unconstrained innovation – ideas and ambitions can be shared by people across the office, street or globe
  • Collaboration – clinicians and care professionals inherently want want to share their good work with the rest of the medical world.
  • Alignment to medical science progression, been based on the spread of ideas – health IT can do the same.
  • “Publish or perish” culture of modern medicine demands that healthcare advances are laid open for scrutiny by our peers
  • Grassroots progress – Complex adaptive systems require decentralized control so people can locally innovate. Amendments and improvement can come from the grassroots and bottom up, without the bureaucracy that innovators often face.
  • A shift in the market towards a healthy, commercially sustainable, services oriented marketplace.

7) Open Platform Fund mechanism

The main aim of this Open Platform bid is;

Support the development of services towards Personalised Care 2020 –

support the development of an NHS ecosystem around an open digital platform

To be clear, while we do not currently have any secured funding for an open platform fund, our aim is to gauge interest in this approach and make the evidence based case to NHS Digital.

The fund is intended to support innovative projects that stimulate the creation of an open digital ecosystem and as such aims to support a large number of small projects that are unlikely to be supported as part of “business as usual” investment by health and care organisations. The aims are to driving innovation and transformation that is scalable, shared, flexible and adaptable and ultimately improve health IT for clinicians and improve care outcomes for patients. Winners will show that they will concentrate their efforts on usability, interoperability, patient centred care that meet the vision. To do so we suggest;

7.1) Request for Expressions of Interest

We initially invite the submission of expressions of interest into this Open Platform Fund. In so doing, we wish to gauge the wider interest in this Open Platform fund proposal to then quickly bring these related responses to the attention of both NHS Digital and NHS England by the end of February 2017 and seek the related funding .

Please submit a brief expression of interest (1-3 page) via this Google forms link; https://goo.gl/forms/4SaNvAgkAe2AfLZ82 by Friday 10th February 2017.


We will acknowledge expressions of interest, collate and feedback the results of our findings, pass on related submissions and summary findings to the Apperta Foundation CIC which we believe is ideally placed to independently oversee this process and support the case for funding from NHS Digital and NHS England. The Apperta Foundation is a not-for-profit community interest company supported by NHS England and NHS Digital led by clinicians to promote open systems and standards for digital health and social care.

While the focus of this paper relates to the NHS in England, we know that colleagues in the health systems of Scotland, Wales, Northern Ireland and indeed the Republic of Ireland are facing the same challenges at the frontline, while aware of the same opportunity on offer from an open platform from a 1% investment, particularly if done openly and collaboratively. Therefore we invite related submissions towards an open platform fund on an All Islands basis – which we also will pass onto the Apperta Foundation and the UK and Ireland CCIO Networks.

7.2) Outline of Proposed Allocation

A) Infrastructural component projects

45% of £40m = £18m over 3 years (until 2020)
Open source tooling & infrastructure components – underpinning standards and compliant components that provides services useful in an open ecosystem (See Appendix 1 examples)

B) Personalised Care: Innovation Incubation and Exemplar Implementations

50% of £40m = £20m over 3 years (until 2020)

Open APIs & open data models based projects as showcases of an open platform in action. (e.g. may include open APIs (e.g. INTEROPen CareConnect FHIR based APIs) + open data models +/- open source data repository (e.g. openEHR based). Examples may include Person Held Records/Electronic Patient Record/Integrated Digital Care Record etc. related projects.

C) Oversight/Custodian of process by an independent CIC such as the Apperta Foundation

Along with the CCIO Network and INTEROPen Collaborative to oversee clinical merit and technical connectathons.

5% of £40m = £2m over 3 years (until 2020)

7.3) Eligibility

We suggest that this open platform fund is open to:

  • UK Registered for-profit commercial entities (Companies and LLPs) and
  • UK Registered not-for-profit entities (CICs,Trusts,Companies limited by guarantee and other recognised forms) meeting UK definition of an SME (In the UK a company is defined as being an SME if it meets two out of three criteria: it has a turnover of less than £25m, it has fewer than 250 employees, it has gross assets of less than £12.5m)
  • UK Public Sector bodies (NHS Bodies, Government agencies and local authorities etc.) irrespective of size.

7.4) Match funding obligations

We suggest that applicants will be required to match fund any award from the fund as follows

  • Social or commercial micro-enterprises 1
    No match funding obligation
  • Social or commercial SMEs 2
    Match funding equal to 50% of the award
  • Public sector bodiesMatch funding equal to 100% of the award

 

1 A business with less than 10 employees and (a turnover < £2 million euro or a balance sheet total of less than £2 million euro)
2 A business with less than 250 employees and (a turnover < £50 million euro or a balance sheet total of less than £43 million euro)
These are the current official definitions applying in the UK

8) Criteria

We suggest that an Open Platform fund is open to projects that stimulate and support both the creation and adoption of an open digital ecosystem which meet the definition in section 5 of What is an Open Platform.

While the main aim of all projects will be to improve NHS services towards personalised health and care 2020, the criteria by which the funding from this fund will be allocated will depend on the concurrent creation of value add in the form of;

  • Collaborative – all projects must establish open channels of communication and means of engagement with other parties in the bid at the time of their application (e.g. INTEROPen Ryver etc).
  • Transparent – all projects must be willing and evidence how they will partake in regular clinical and technical reviews. We suggest these should be in the form of bi-annual CCIO Network led review along with INTEROPen led Connectathons with a minimum of 3 out of 6 Connectathons undertaken.
  • Share Ideas, Knowledge, Experience – i.e. willing and able to openly collaborate with others in this initiative (e.g via online community building via tools such as the Open Health Hub, Ryver etc) and partake in Open Data connectathon against INTEROPen FHIR APIs

9) Judging process

Initial Bid and Review Point Principles

We suggest the related submissions into this fund will need to evidence the following as part of their bids and progress at agreed review points:

  • Clinical merit – against the Personalised Health and Care 2020 Vision
  • Technical merit – against the open platform principles outlined
  • Clinical gap / need / demand
  • Clinical Leadership – all projects need nominated clinical lead
  • User Centred Design – include/demonstrate a commitment to open publish UX design
  • Alignment with Agile Development methodologies
  • Business readiness (preparatory work, governance etc in place)
  • Collaboration with other parties in the open platform bid
  • Open Source track record

10) Conclusion

If public monies are for one purpose, they should be for the common good. Our proposal aims to ensure the efficient and effective allocation of public monies to projects that can impact the health and care of millions of citizens in England, supporting local NHS & Social Care organisations in their hour of need, while leveraging Britain’s long held reputation for industry and innovation to enable a new global open platform fit for the 21st Century.

Our proposal for an open platform technology fund aims to offer a means towards the integrated care vision of Personalised Care 2020 that is in the best interests of the NHS. In aligning patient, clinical and care needs with the investment potential offered by open platforms in healthcare, we believe there is a clear win-win on offer here.

At times of challenge and change the natural instinct may be to withdraw from risk or novel action, yet all our instinct is telling us that now is very time to embrace this challenge and seek the opportunity – which is why we are taking a public lead in getting this Open Digital Platform for Healthcare into action and welcome your interest and support in this effort.

Dr Tony Shannon, Ewan Davis
14th January 2017

Questions or Comments?
Email us at 1percentfund@ripple.foundation or tweet @rippleosi with #1percentfund

11) Declarations of Interest

Both of the authors are unashamedly proponents of an open platform in healthcare for some time. One might argue that this constituents a conflict of interest with the proposed approach. Rather we would suggest that our track record in leading the effort to disrupt the market towards an open platform, equates to a confluence of interest with the approach now required.

Dr Tony Shannon, Director – Ripple Foundation C.I.C
Director – Frectal Ltd

Ewan Davis, Director – Synapta C.I.C
Director – Handi Health C.I.C
Director – Open Health Hub C.I.C
Director – Operon Ltd
Director – Woodcote Consulting Ltd

12) Related Links

Ripple Foundation Community Interest Company http://rippleosi.org/
HANDI Health Community Interest Company http://handihealth.org/
Synapta Community Interest Company http://synapta.org.uk/
Endeavour Health Charitable Trust http://www.endeavourhealth.org/
Apperta Foundation Community Interest Company http://www.apperta.org/
INTEROPen Collaborative http://www.interopen.org/
openEHR Foundation http://openehr.org/
HL7 FHIR https://www.hl7.org/fhir

Appendix 1 – Open Platform Infrastructural Component Candidates

The aim here is to initially outline examples/suggestions of a “top 10” set of federated service components in a Service Oriented Architectural world that would be useful to in healthcare. In doing so we welcome further suggestions and related expressions of interest that would aim to provide open source solutions to plug gaps / provide enhancements towards the open digital platform movement. The fund may support the open sourcing of existing components or their development.

Identification & Authorisation
Master Patient Index
User Interface framework
Integration technologies
Clinical Data Repository
Terminology services
Workflow services
Rules engine
Scheduling
Business intelligence
Clinical content collaboration/authoring tools (i.e. openEHR/FHIR etc)

Applications for these open source infrastructure projects are encouraged to state their preferred OS license (weighting towards non copyleft (Apache 2/MIT/BSD) or AGPL licensing)

 



 

Hiding the Onions – Interop and Open Platforms


With McKinsey telling us that open platforms can save more that 11% of total health care costs, we really have to sweep away the barriers and make it happen. This means moving to an open platform architecure meeting the principles I described in my last blog, which require open standards, open data and open APIs. While most in the vendor community understand this and some actively promote it for others asking them to open up their systems and data and adopt open standards is like asking the turkey’s to help make the stuffing – They might help you find the sage, but they are  going to hide the onions.

Many existing vendors recognise the need to move open standards, open data and open interfaces (APIs) but while some are moving in the right direction, they are not there yet Others drag their feet knowing their current success relies on existing proprietary solutions, customer lock and their pseudo-ownership of customer data. Getting to the tipping point at which open platforms can really take off is going to require new players challenging the status qou and a willingness from the health and care community to help them successfully engage.

The objective is to move towards what is now being described as a Post Modern EHR  this is an architecture that separates data (describing both record content and work-flows) from the applications that create and process it storing it in an open computable format available to all authorised applications.

There are almost certainly no vendors who think interoperability is a bad thing and this is exemplified by the techUK Interoperabity Charter, to which many vendors have signed up . While some have described this as “Motherhood and Apple Pie” in nonetheless contains some specific commitments and there is certainly no justification for any health or care organisation to do business with companies that are not signatories (it is not necessary to be a member of techUK to sign up to the charter). Having  signed the Charter should be a mandatory condition in the PQQ of any IT procurement in Health and Care.

However, vendors commitment to interoperability is not always what it seems and varies between companies and within companies depending on what particular aspect of interoperability at issue.

Most vendors are keen to facilitate interoperability that enhances the range and quality of data in their systems or which adds functionality that they don’t and and have no desire or ability to provide. Vendors are less keen to support interoperability that allows competitors products more easily to replace some or all of their system or which loosens their peusdo-ownership of their customers data – True interoperability does both of these things.

For a system to be fully interoperable the following needs to be true:

  • It should be possible to access all of the data in a system in an open, shareable and computable format, either for an individual patient or any cohort of patients (include all patients). Interfaces should be provided to efficiently access data and where the customer wishes to maintain a near real-time replica of the data in a parallel system.
  • It should be possible to upload to a system any data that could otherwise be manually entered into a system, subject to relevant  user defined work-flows and quality assurance.
  • All business functions that can be executed using a system should be exposed via an appropriate API to allow them to be executed by an authorised external application.

Looking at the API’s than vendors are now providing, few come close to meeting the criteria above. For some systems and to some extent there are real technical barriers to opening up systems and making the data they hold available in an open format, but there can also be pressing commercial reason for not opening up systems and it can be very difficult for customers to determine the extent to which vendors have genuine technical challenges to overcome or are simple looking for excuses to hang on the commercial benefits of limiting what can be done through their APIs.

Customers need to push vendors towards open platform architectures, open standards, open data and open APIs, but need to recognise that this transition cannot be achieved overnight and will require investment by vendors that will ultimately need to be paid for by customers. The trick is to link new business to an evolution to open standards without making unrealistic demands, that in the end you will have to allow vendors to ignore.

Vendors need to appreciate the value of open platforms and the commercial opportunities they bring. The increasing complexity of digital health means that I can foresee only two future options:

  • The first based on open platforms creates opportunities for vendors, particularly innovative SMEs, to enter the market and compete with the larger players on a level playing field and forces vendors to compete on quality, performance, support and value rather than relying on customer lock-in and pseudo-ownership of customer data.
  • The second is increasing market consolidation with a few very large  vendors owning competing proprietary platforms, that allow access to other vendors on their terms with customers locked into their platform

The first option drives innovation and value, creating a competitive market  for both the provision of  federatable open platforms and the applications that run it. The second will result poor value and reduces both the opportunity and motivation for innovation and gives the platform provider too much influence in the way health and care services are provided.

There is a great future for vendors of all sizes in an open platform environment, which by delivering value to the health and care system, will result in market growth delivering greater revenue opportunities for those that can adapt their business models to take advantage – For those that can’t there always the cranberry sauce.

Stuffed Turkey
By No machine-readable author provided. Chensiyuan assumed (based on copyright claims). – No machine-readable source provided. Own work assumed (based on copyright claims)., CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=1491125

Defining an Open Platform


It is widely agreed that the future of digital health lies in an “Open Platform”. However, it’s not clear as to exactly what an Open Platform is or how we get there. With McKinsey tell us that health care systems that create an open platform can save more than 11% of total health care cost this is a question we urgently need to answer

“…….each national or federal health system should consider an open innovation platform that holds healthcare data ……………., and provides data access that is enabled for application programming interfaces as well as common technical IT services such as identity, access, or consent management. This platform would serve as the basis for an ecosystem of digital-health-services innovation……”

“In 2014, we did considerable research into the economic value of digital technologies in healthcare and found ……..  net economic benefits of 7 to 11 percent of total healthcare spending. Over this past year, our work on the ground has confirmed this original analysis. However …………  we believe an even greater impact can be achieved through coordinated joint effort. This would involve the interconnection of all digital-health stakeholders through an open innovation platform.”

McKinsey and Co., Jan 2016

This blog is an attempt to do so on which feedback from others would be welcomed..

While any given instance of an Open Platform will be a specific implementation of a set of software components owned and operated by a particular organisation (this might be a health and social care organisation or a third party, operating the platform on behalf of a local health and care community), it is most usefully defined by a set of principles rather than the specific details of a particular implementation.

Open Platform Principles

Any platform implementation that is truly to meet the definition of being ‘open’ should comply with the following principles:

  • Be Open Standards Based – The implementation is based on open standards which any willing party can use, free of charge, to build an instance of the Open Platform – what these standards are will be described later in this article.
  • Share Common Information Models – There should be a set of common information models used by all instances of the Open Platform, independent of the specific technical details of a particular implementation.
  • Support Application Portability – Applications written to run on one implementation of the Open Platform can run with little or no change on another independently developed implementation.
  • Be Federateable – Any implementation of the Open Platform can be connected with all other independently developed implementations in a federated structure  to allow the sharing of appropriate information and workflows between them.
  • Be Vendor and Technology Neutral While those building an implementation of the Open Platform will chose particular technologies and may choose to use or include proprietary components, the standards should not depend on particular technologies or require components from particular vendors.
  • Support Open Data – An implementation of the Open Platform can expose all of the data it contains in an open, shareable, computable format in near real-time; it is for implementors to decide if they choose to use this format natively in their persistence (storage) layer of the Open Platform, or meet this requirement by means of mappings and transformation from some other open or proprietary format.
  • Provide Open APIs – APIs are the means by which applications connected to the Open Platform are able to access and update the data it contains. There are a number of available open APIs (see below) and ideally any platform should support a number of these to give the maximum flexibility for applications that wish to connect to it.

Open Platform Standards

Meeting these characteristics implies the use of certain approaches and the adoption of certain standards. However, it is important to understand that by its very nature an open platform, just as with the Internet, is not something that can be rigidly defined and indeed is something that will continually evolve. There are multiple ways to build an open platform and for these to work together we don’t need and can’t have rigorous standardisation; we need just enough of a common approach to make things work. This approach is different to that historically adopted in NHS IT, but it is the model on which the Internet and World Wide Web were built and have succeeded. See these two pieces on my blog here and here.

At the core of an open platform is the need for common information models, which define the clinical content (information) to be represented on the platform and which provide a sharable, open and computable format for that information. Currently there are only two approaches that have current support from the global health informatics community.  These are the Clinical Element Models (CEMs) and openEHR. They adopt very similar approaches, coordinated through the CIMI initiative. In the NHS, the HSCIC has chosen to use openEHR; which is the model that has achieved the most widespread global acceptance and use.

Information models, such as those created by openEHR can be used natively in the persistence (storage) and messaging components of the platform or be used simply to inform the design of these components using either another open standard such as HL7 FHIR, XML, JSON, or by using proprietary approaches. The critical point is that  an open platform can produce and consume data in a form compatible with the standard information models. It is for the designers of the platform to decide how to do this, but I would expect those building from scratch to use openEHR natively in the persistence layer and those adapting existing systems to converge their internal representation on these standards over time.

Open Platform Architecture

The architecture of an open platform will evolve over time and it is likely that different implementations of the platform will vary in the detail of the architecture and the particular components included. What’s important is not that different implementations are identical, but that they comply with the principles described above. The diagram below proposes a possible architecture. Any open platform of this kind is likely to have similar components, arrayed in a functionally equivalent architecture and to implement a similar set of standards.

Open Platform Architecture

The heart of the platform is an Enterprise Service Bus (ESB) which links the components together and provides authentication along with the management of the Application Programming Interfaces (APIs), which serve both platform components or services and external systems connected to the platform.

Core components of the platform include:

  • repositories for both structured and unstructured data (documents, images, etc);
  • a Master Patient Index (MPI) and Registry which stores basic demographic data and provides a locator service to help find where the records for a particular patient are held (e.g. on the platform, elsewhere in the local health community or on other federated platforms);
  • knowledge services that provide access to knowledge (particularly workflows, processes and decision support);
  • a range of external connectors which allow applications on the platform to connect to existing systems relevant to the local health community including other local systems and national services (such as NHS Spine);
  • a range of platform services, none of which are essential, but which, if available, remove the burden of dealing with the functions they support from application developers. These might include:
    • terminology services;
    • identity management;
    • consent management; and,
    • access control (role based access (RBAC) legitimate relationships (LRs) and workgroups.
  • Connectors and federation services to other platforms to allow platforms to be connected in a federated web allowing an authorised user to discover and access any relevant data in any location.

It is my strong view that the right choice for a structured data repository is openEHR and the right choice for the unstructured data store is IHE-XDS. (IHE-XDS also provides a suitable option for the registry). Both of these open standards are well supported by vendors with a number of proven proprietary implementations and emerging open source options. However, there are alternative approaches that could comply with the principles described above.

I don’t have fixed views with regard to the best approach with regard to the knowledge repository, but the work of Synapta to draw together a number of available standards including BPMN 2.0, GDL, CMMN, Drools and PROforma looks promising.

Examples of Open Platforms

There are a number of examples of open platforms that adhere to the principles outlined here and a number of people working to create more.

Established platforms that include both openEHR and IHE-XDS, working together include Moscow City support health and social care for 12 million patients and Slovenia support the entire population of 2 million. There are many more examples based on one or other of these standards that could easily be extended to do the same, including a number of UK projects.

There are also a number of other projects in the UK working together to refine the definition of an open platform and build implementations these include.

  • NHS England Code4Health This is based on my work with Dr Ian McNicoll for HANDI. The Code4Health Platform provides a simulated environment where people can explore open platform concepts and APIs and build applications to test their ideas.
  • Ripple who have an operational open platform based on openEHR in Leeds.
  • The Endeavour Health Charity who are building a platform using HL7 FHIR and a number of connectors to legacy systems.
  • Operon who are developing Synapta to provide components to support open workflow standards including BPMN 2.0, GDL, CMMN, Drools and PROforma

All of these projects are working together coordinated by the Apperta Foundation  (a clinically led not-for-profit company established with initial grant aid from NHS England) and are already committed to using a common set of information models created using the openEHR tools. The aim is to agree a common set of standards and components which will enable them to build implementations of open platforms which comply with the principles here. Each implementation will be different, enabling us to learn what works best, but similar enough to enable federation and interoperability.

We are actively talking to a number of projects in the pipeline and some other existing projects already using one or more of the core standards described here, so we expect to see many more open platforms complying with the principles outlined here. If you like to join us get in touch ewan@woodcote-consulting.com

 

The Future of Applications


I was recently passed a link to an interesting paper from Accenture “The Future of Applications – Three Strategies for the High-velocity, Software-driven Business”. This paper is directed at a general business audience, but has much of relevance for the digital health world and in particular resonates with the points I was trying to make in my recent blog  “Would you like to build Health and Care Software 100 times Faster?”

Picking up a few key points from Accenture:

“The fact is, many companies are trying to compete in the world of social, mobile, analytics and cloud with applications that were designed for another era. Monolithic applications are often built from the ground up— slow to implement and slow to change. “

Very true of the systems in health and care, not just the big megasuites, but most of the applications in use today.

“What’s needed is a new way to build software—faster, flexible and more liquid—with reusable components that allow for rapid assembly of applications in support of dynamic business needs. This approach requires modular architectures……”

In the context of health and care this sounds very much like openEHR.

The other two other key points the paper makes: The need to build intelligent applications and to build and nurture  [open] ecosystems also seem to provide further support for the work I’ve been in with colleagues in NHS Englands Code4Health Programme.

There is much more in the Accenture paper which is well worth reading and thinking about how we can apply its recommendations in the context of health and care. You will find the paper on the Accenture web site here.

Would you like to build health and care software 100 times faster?


I’ve written before about openEHR and how I think its time has come. I been talking to lots of people about openEHR and it’s clear it takes a while to really understand its power – It took me 15 years. In this blog I try and summarise what I think makes it different and special. If you are new to openEHR I suggest you read this first and then go to my previous blog and openEHR.org  for more detail.

OpenEHR is not a piece of software it’s an open specification from which software can be built. It has it roots as a way of creating electronic health records, but can be used to build records across the whole of the health and social care domain.

Its key benefits are:

  • It enables those designing systems to work at the information level rather than at the level of a particular technology separating
    • “content” – the domain of the clinician or social care professional
    • from “technical infrastructure” – the domain of the software engineer
  • enabling both to concentrate on their own domain without needing to worry about the complexity of the other.
  • It’s independent of any particular vendor or technology – There are multiple implementations from a number of vendors, built on various technologies, including open source options.
  • There is a vibrant global openEHR clinical community creating archetypes (the building blocks of openEHR), which are generally “open source” and can thus be freely shared, used and adapted. See Wooland’s  Cat for more on this 
  • There is an active vendor community which supports the clinical content development and a number of examples of implementation at scale, mainly outside the UK where it was invented!
  • The specifications are amazingly rich. There is very little than its creators have not covered including:
    • Interoperability, openEHR makes it easier to achieve interoperability than not.
    • Multilingual support and language independence
    • Federated multi-vendor implementations, with cross vendor querying
    • Complex access control capabilities
    • Intermittently connected devices
    • Versioning and backward comparability
    • Cybersecurity
    • Privacy protection and consent management
    • Terminology bindings

However, the most remarkable and powerful feature of openEHR is its ability to support new requirements with minimal changes to systems. To support a new requirement it is simply necessary to create new archetypes. These will be immediately deployable, storable and queryable; will not require any database schema changes, won’t affect parts of the system not connected with the new requirement and won’t break anything – This means that new requirements can often be deployed in hours rather than months. Let me explain further:

New requirements generally mean new information has to be collected and stored. Anybody, who has worked at the database level will know how problematic this can be. You have to modify the database schema, modify existing tables, maybe create new ones and then migrate data from the old schema to the new. In a database of any complexity it’s easy to break things and can require the rework of lots of software unconnected with the new requirement. While modern databases have tools that can help developers avoid schema changes like the plague and when they do consider them, the rework and testing required means that changes will be expensive and slow if they happen at all often leaving people with no recourse than another  Feral System

Supporting new models of care means being able to meet new requirements 10 – 100 faster, by utilising openEHR’s ability to incorporate changes simply by creating new archetypes, the large preexisting set of open source archetypes, its openAPIs we can now achieve this.

If you not looked an openEHR already then I suggest you do and if you loked at it a while ago I suggest you look again.

This video produced by Dr Wai Keong Wong (@wai2k )provides a useful introduction to openEHR

Nobody should (can) “own the platform”


I’m sitting in the Interoperability Workshop in London being jointly organised by NHS England, The Health and Social Care Information Centre and The Local Government Association (3 June 2015).

In the UK like there are a large number of projects trying to deliver integrated care that need to achieve integration of IT systems and data across multiple organisations and systems. Most of those speaking here today are trying to follow an open approach but some seem to be achieving more rapid progress implementing proprietary systems. In many ways this is to be applauded, but there is a risk that it leads people down a cul-de-sac and creates vendor lock-in.

Globally the health informatics community agree that we need to move away from enterprise based monolithic systems and bespoke “best-of-breed” integrations to community wide systems based on a platform architecture that allows components to plug-and-play sharing information, knowledge and work flows in a computable format.

For vendors the commercial opportunity of “owning” the platform is massive and many vendors from the very large, to wildly ambitious start-ups are trying to achieve this. However, in my view, and that of a growing number of others, is that an “own the platform” approach is both doomed to failure and not in the public interest,

It’s not in the public interest because it creates vendor lock-in and while in the short-term the right vendor might offer the lowest risk approach to short-term success in the medium-term vendor lock-in mitigates against agility, innovation and the achievement of good service and best value.

It’s doomed firstly because governments, health and care providers and payers increasingly understand my point above, secondly because of competitive pressures in the market; google won’t let apple, won’t let Microsoft, won’t let amazon, won’t let IBM, won’t let EPIC, won’t let TPP won’t let Orion etc and finally because unless we adopt open approaches we won’t be able to address the federation of platforms which is essential to deal with the inevitable flows between communities.

The smart money will invest in the creation of open platforms (spending a lot less than is required for an “own the platform|” play) and build business models that exploit rather than own the platform (like the Internet works!)

Those responsible for commissioning digital systems need to ensure open standards, open interfaces and open data and avoid being seduced by the vendors of proprietary solutions.

openEHR a Game Changer Comes of Age


I’ve been watching openEHR over more than fifteen years, and although I have always been impressed by its potential to enable us to do things differently, I must admit it has been a slow burn, and take up has been limited, particularly in the UK where it was invented. However, due to some recent developments, I think this is about to change, and that openEHR is going to take off in a big way. This is going to revolutionise how we think about and do digital health, and it should increase the speed at which we can do it by at least two orders of magnitude. Why do I say this, and what evidence is there to support my assertion?

openEHR has come of age with a large number of successful small implementations, and a few much larger ones (1) which have proven the approach works at scale. We have also seen the use of openEHR by governments and major health providers across the globe, including the NHS (2), as the mechanism for the creation and curation of clinical content standards in their territories. In addition, changes to the openEHR Foundation have made it unarguably an open source organisation with a global user community; a growing vendor community has developed offering both open source and proprietary tools and components supporting the standard; and there is serious interest from major system integrators. These changes make openEHR look like a much better alternative to the hegemony of the big US megasuite providers, who still want to shape health and care systems in their image and who own the platforms on which these providers will increasingly depend.

UPDATE (12 April 16)

Possibly the best explanation of openEHR I’ve seen “openEHR technical basics for HL7 and FHIR users” Well worth reading.

UPDATE (15 March 16)

Some great videos here which provide an easy way to understand various aspects of openEHR.

In particular:

Clinician-led e-health records – An introduction to openEHR for clinicians

National governance of openEHR archetypes in Norway – A national approach to building information models with openEHR. Many lessons here for HSCIC who have just started doing something similar here.

UPDATE (13 July 15)

In their PQQ which kicks of the procurement for the Datawell to support Devo Manch,  Manchester have mandated openEHR along with other established standards including IHE-XDS. This could potentially lead to the largest implementation of openEHR in the UK with Manchester building on pioneering work in Moscow and Leeds

UPDATE  (24 Apr 15) Further information and news about the growing interest in openEHR will be found here

Firstly, everything I read and all of the people I talk to across the globe about digital health agree on a couple of things.

  • Firstly, we need to move towards a platform architecture into which we can plug the thousands of apps and hundreds of traditional systems that we currently use in health and care; an architecture which will enable all of these to interoperate and work together.

  • Secondly, we need to separate content (the data, information and knowledge that applications consume and update) from the applications that process it; and that content needs to be expressed in a modular, computable and reusable format.

Beyond this, agreement breaks down – people do argue about business models (who should own and control the platform), and also the details of the particular standards and technology to be used – but on the core principles, everyone with any credibility agrees.

When it comes to business models, some would like to own the platform, because doing so would create a massive commercial opportunity. And while some still pursue this goal, most significantly Apple, others have decided, as I have, that ownership of the platform is neither achievable (competitive and customer pressures mean even the mighty Apple can’t win this battle) nor is it desirable from the perspective of citizens, health and care providers and payers – none of whom wish to be locked in or to pay the ‘fruit tax’ or its equivalent.

Others, including me, and more significantly some big players, have come to the view that while it might be great to own the platform, that isn’t going to happen and so we need to move to an open platform which nobody owns (in the sense that nobody owns the Internet). As for commercial opportunities, they will still exist higher up the value chain, and the existence of the platform will create such opportunities by the spadeful. Surely it’s more fruitful to concentrate on these, rather than waste time and resource on a battle no one can win.

On the details of implementation, disagreement is less significant. The two major contenders, openEHR and the Healthcare Consortium, both have similar approaches, and they are already converging through the Clinical Information Modeling Initiative (CIMI) to reduce their differences to the point where they really don’t matter and can be dealt with at a purely technical level, with their components being easily interchangeable.

So, if we want to create an open platform, what do we need? We need openEHR or something like it – and frankly there is nothing else as mature or as well supported as openEHR.

OpenEHR is not software, nor is it a particular technology. It’s an open specification or standard for the representation of a key bit of content – the health and care record. The specification is open source (insofar as you can apply this term to something that is not software), and it’s curated by the openEHR Foundation, which is a not-for-profit company democratically controlled by those who choose to be part of the global openEHR community (and anybody can). The community is truly global and growing, and consists of both users and developers; and is supported by a number of vendors who can offer tools, components and services supporting the standard.

openEHR provides a simple, robust and stable over-arching reference model (3) which defines a formalism for the representation of the modular components of a health and care record. openEHR calls these ‘archetypes’ and they define the elements of a record, their properties, and how they are represented (including bindings to terminologies and classifications). Archetypes are intended to represent a superset of all those properties that might be associated with the concept they represent (at a high level these will be either an observation, an evaluation, an instruction or an action). Archetypes can then be constrained and/or combined in a ‘template’ to provide practical interoperable components for use in a particular context or system.

The tools available for the creation of archetypes and templates are open source (as are the vast majority of the archetypes and templates created with them), and this makes openEHR easily accessible to clinicians and other domain experts while also providing system developers with robust components to handle many of the technical complexities. openEHR enables clinicians to concentrate of the clinical stuff, and developers to concentrate on the technical stuff, without needed to understand more about the other domain than they want to.

By building systems using openEHR, system development work shifts from the technical level to the domain level. A repository that has been built to store an openEHR health and care record does not need to take account of the particular content of a given archetype. Whatever that archetype might represent, the repository will be able to store it, and you will be able to query that repository about its content. This feature of openEHR is the key enabler of much faster application development, because the addition of new features will not require changes to database schemas (with all the associated testing and data migration that entails). Instead, all that is needed is the addition of some archetypes and/or templates – and these may already be available as the result of work by others in the community, or else they can be created rapidly by a relevant domain expert – plus the creation of some new user interface components, and these can often be generated automatically from the underlying templates. In this way changes can be made by end users, or by people close to them. This will reduce the time to add new features from months to hours, and the time to build new systems from years to weeks.

openEHR is also technology independent. Applications don’t need to concern themselves with the technology of a particular implementation of an openEHR repository – that’s purely a matter for the implementer, who can chose whatever technology works best for them at a particular time and in a particular context. The applications that use it will not be affected, so long as they remain compliant with the standard. We can see this happening in the dozen or so existing implementations of openEHR repositories: they use different operating systems, different databases (SQL and NOSQL) and various development tools to create both open source and proprietary implementations of the standard. Compliant implementations of the standard from different vendors are interchangeable, and a single query can be executed across multiple implementations. openEHR is vendor independent, and it eliminates vendor lock-in.

Suppliers of openEHR repositories will have to compete on performance, security, robustness, value and service – they cannot rely on customer lock-in, as the vendors of many traditional EHR systems have in the past. From the perspective of health and care providers, openEHR puts them back in charge of their own destiny. This contrasts with most of the current successful approaches to the delivery of enterprise-wide EHR, where customer institutions have adopted one of the four big US megasuites, and then have had to adapt internal processes and organisation to fit with the chosen system – in effect, you become an EPIC, Cerner, Allscripts or Meditech institution, rather than a customer who calls the shots.

The ‘megasuite model’ has worked spectacularly well (if expensively) in a number of big US hospitals, particularly for EPIC, but that model starts to break down when you seek to extend the scope of a system from an institution to an integrated health and care community. It also fits badly with UK and other European models of health and care, which are not so close to the US model as the megasuite vendors might hope them to be.

Of course European health and care providers don’t want to remodel their processes along American lines – why would relatively successful European providers want to adopt systems designed primarily for the inequitable and unsustainable US system? According to the well respected US Commonwealth Foundation the United States ranks last among eleven leading developed countries on measures of access, equity, quality, efficiency, and healthy lives (and, by the way, the UK’s NHS takes the number one spot).

Much of my conviction about openEHR comes from work I’ve been involved in with HANDI, in building HANDI-HOPD – the HANDI Open Platform Demonstrator, which has now been adopted by NHS England as the NHS England Code4Health Platform. This platform provides a simulation environment for any system or service that wants to expose an API (interface) within an open ecosystem, and it includes an openEHR repository loaded with test data from the Leeds Lab Project.

We have exposed SMART and FHIR APIs, as well as the native openEHR service API, on top of the repository; we have used this to build a number of apps, and also demonstrated how you can simply plug in apps that were developed elsewhere using the SMART API. We have also used this platform to prototype a UK localisation of an open source ePrescribing product (www.openep.org), and the speed at which we have been able to carry out the localisation and meet some special mental health requirements has been impressive – indeed so impressive that we will shortly be announcing the first NHS Trusts who will be taking the system live.

Work is currently being completed to re-brand the HANDI platform as the NHS Code4Health Platform, and this will shortly be available for those who want to learn more and experiment with this and other open technologies.

openEHR has come of age – If you don’t believe, me give it a try.

Notes:

This is a slightly updated version of the original with a few minor changes to make it more readable to the general reader and correct some typos my thanks for this to my friend and colleague Conrad Taylor.

1) Large scale implementations of openEHR include:

Moscow – Integrated health and social care 12 million population 

Slovenia – Country wide 2 million population

Brazil – Unimed Medical cooperative

2) Health systems using openEHR to create curate and publish clinical content.

NHS HSCIC

NHS Scotland

Australia

Norway

Slovenia

Brazil

openEHR Foundation 

Applications built on openEHR platform

OPENeP EPMA product www.openep.org

Marand Think!Med Clinical, Ljubljana Children’s Hospital http://www.marand-thinkmed.com

Ocean Multiprac Infection control, Queensland Health, Australia http://www.multiprac.com/?portfolio_4=infection-control-2

Ocean LinkedEHR, Western Sydney, Australia  http://openehr.org/news_events/industry_news.php?id=121

DIPS Arena, Norway http://openehr.org/news_events/industry_news.php?id=97

mConsole, Mental Health patient portal, Code24, Netherlands

Clinical Decision Support, Cambio, Sweden http://www.cambio.lk/News-and-facts/Produktnytt/COSMIC-Clinical-Decision-Support1/

See also http://www.openehr.org/who_is_using_openehr/healthcare_providers_and_authorities

3 Some key documents on OpenEHR

OpenEHR Architecture Overview

OpenEHR Reference Model

Supporting New Models of Care


“I’m pretty certain that the health informatics community know how to create the open digital ecosystem we need to support the emerging new models of care, but I have concerns that a lack of knowledge and experience amongst policy makers, vested interests in the care, informatics and vendor communities and a naive belief in the Tooth Fairy. Might mean we don’t achieve what’s possible.”

There are two things it is certain that we need to do to help address challenges that an ageing population creates for health and care. Firstly, we have to get much closer integration of health and care and move care nearer to the patient. Secondly, we have to leverage digital technology to support this change using both big data and small data to deliver more appropriate care more effectively.

I’m pretty certain that the health informatics community know how to create the open digital ecosystem we need to support the emerging new models of care and that there are examples of successful approaches that we can draw from. However, I have a number of concerns, that:

  • Policy makers don’t have sufficient knowledge of the available options or the technical understanding of Informatics and digital health and care to make informed decisions.
  • Informaticians and technologist from outside of the domain don’t have sufficient understanding of health and care to provide good quality advice to policy makers and worse believe that they have.
  • Organisations on the ground also lack sufficient knowledge and technical understanding which means they are not able to critically appraise proposed solutions from vendors and may be tempted to implement solutions that appear to address immediate priorities but which are not scalable or sustainable and which create vendor lock-in.
  • That many in the NHS, vendor and digital health communities have existing positions and conflicts of interest which disincline them from taking the radical steps necessary to work towards the creation of the open digital ecosystem we need.

The imperatives outlined in my introduction are recognised by policy makers and are the thrust of the approach outlined in NHS England Five Year Forward View Central to policy is the creation of new models for the delivery of health and care and policy makers are, rightly in my opinion, facilitating and encouraging various approaches to create new organisation and structures to deliver care. At the heart of all of these is the creation of some form of accountable care organisation (ACOs) with total responsibility for the health care of a given population. ACOs could emerge from various directions including General Practice, NHS Trust, Local Authorities ,the private and third sector. Yesterday NHS England announced 29 Vanguard sItes   to implement 3 approaches These are: multispecialty community providers (or MCPs), primary and acute care systems (or PACS), and enhanced health in care homes. We also already have work around the Integrated Care Pioneers  with the initial 14 now expanded to 25 and work under the Prime Minister Challenge Fund to improve access to GPs also has relevance and finally we have the ambitious plans announced for Manchester, which are likely to be replicated elsewhere.

All of these initiatives have massive implications for new and existing digital technologies, both to mobilise data and to enable the digital delivery of services to citizens. It will be necessary to create interoperability between existing systems across health and care and changes to make it easier to implement and integrate new digital services and apps. This integration requires interoperability both of data and workflows to allow the sharing of both information and tasks across multiple actors in care communities and needs to liberate information in open and computable formats to facilitate big data analytics to help us understand needs, what we are achieving and how we might do it better.

All of this has to happen in an environment where privacy, information sharing and governance issues are addressed but while this is in many ways the biggest challenge, it’s something that I’ll leave for a future blog.

There are many companies developing new and existing products to meet these challenges and while many of these have a more open approach than has traditionally been the case most are still based on solutions tied to particular vendor or technology. My view is that such approaches which give a small number vendors a dominant position are unlikely to have long term sustainability and even where they do create a degree of vendor lock in that is against the public interest. As far as possible we need to create solutions based on open standards independent, of particular technologies which allow multiple vendors to play allow the easy replacement of any single proprietary component to avoid vendor lock-in.

If we are to achieve progress policy makers need to recognise their lack of knowledge and be aware that those advising them both public sector IT specialists and vendors may a have vested interests which mean their advice must be critically appraised. This can only be achieved by a more open, collaborative and transparent process. All of us have our own agenda seeking some mixture of money, power, sex and glory with concerns about how we pay the bills. No individual or organisation can offer informed and impartial advice and it’s only if we are all honest about our motivations and concerns and debate the options openly that we can make progress – I’m in it mainly for the glory, have paid off the mortgage but could still use a bit more cash and a gentlemen never tells.

I outlined one approach I think has great promise in my previous blog

For more about ACOs see:

Kings Fund http://www.kingsfund.org.uk/publications/accountable-care-organisations-united-states-and-england