@bengoldacre @swardley Currently limited. My own EPR publishes structured data but everything else is application-bound or administrative and not usually clinically meaningful. It is, therefore, aspirational. Bedrock is meaningful data in open structured formats.
@bengoldacre @swardley Thinking about it, it depends what you mean by API. If you are asking whether they exist as a specification, product or commodity, then yes - either running as a repository or a facade via HL7 FHIR.
@bengoldacre @swardley And we know Apple have used that for their Health app, and Google DeepMind for it, to federate laboratory data across multiple sites from different sites for their Streams app.
@bengoldacre @swardley But our problem is people thinking that they can solve user needs via a portal, by mandating that portal and preventing access to the current non standard often proprietary API to anyone else except that portal.
@bengoldacre @swardley This mapping exercise was an attempt to focus on the missing bit: liberating clinically meaningful data and recognising the need for a rethink of many of the architectural designs made previously.
@bengoldacre @swardley I guess driven somewhat by my first hand experience of trying to be a client of that enterprise when building this and having to deal with, quite frankly, an incoherent and product-focused mess with very little meaningful clinical data.
@bengoldacre @swardley So I just want to switch to Internet-era thinking in how we build technology for healthcare. This ranges from how we develop, test, evaluate and deploy. That all means changing structures and using small cross functional teams. To do that, you need to change hearts and minds.
