Membership Terms & Conditions

INTEROPen is now OPEN to all (organisations or individuals) with an interest in contributing to the implementation of INTEROPERABILITY open standards in the UK health and social care ecosystem.

Background reading:

In registering to be part of INTEROPen, you declare that you/your company/organisation believes in openness, transparency, and in the context of INTEROPen’s activities, putting commercial interests aside to design open interoperability standards to deliver the new models of care that our health and social care ecosystem needs.
In declaring this, and in the spirit of INTEROPen, you support INTEROPen in naming your company’s/organisation’s name in our shared vision through tweets or interviews by the collective membership.
*Application for membership as an “individual” – as opposed to an application on behalf of an organisation – must be accompanied by disclosure of any affiliation with any care provider/IT organisation/commercial entity. We operate a transparent culture regarding who our
members are.*

As the techUK article states: “Members [of the supplier group are self-selected but] must be willing to dedicate their own time and intellectual energy to the work….There is no direct funding [for suppliers’ time] and facilitating meeting spaces may be required”

A reminder of the group’s primary focus:
1. Data exchanges between the different care domain systems e.g. GP, acute, community, mental health, child heath, maternity, social care. This data exchange will favour structured data whenever possible, with development proposals where it is lacking.
2. The establishment and validation, both clinical and technical, of FHIR based profiles for the exchange of granular transactional data between systems. These standards will operate alongside other standards such as CDA, which is targeted at document exchange. We will work in partnership with the Professional Records Standards Body (PRSB) to establish FHIR profiles and CDA standards that are ‘clinically’ fit for purpose.
3. The definition of APIs with associated trigger events to carry the data, particularly real time requests and posts.
4. Informing the requirements for the technical governance rules, security mechanisms, and regional architectures that will be necessary to safely exchange data in an acceptable manner.