Dataflow Map
A simple ‘As is’ model of the OpenActive ecosystem is given, below, showing the data-flow of the OpenActive data-set. Data can be consumed from an RDPE feed or through the Imin API. It also shows that reports are gleaned from the consuming applications (Social Prescribing applications) and the activity providers themselves. The result of the OpenActive data-flow is that a service of an activity is offered to a service user which is the client of the Social Prescribing Link Worker (SPLW). Money can then digitally change hands through securing a booking or paying the activity provider. It was noted that Social Prescribing policy comes from the NHS.
The ‘To be’ is given below the ‘As is’ and includes the following suggestions:
The ODI should define a standard REST API such that innovators can develop them to aggregate feeds to make them more accessible to developers. Activity & Provider Quality Assurance Innovators could develop a means to verify activity quality if it is provided in an activity providers data-set. Innovators could develop a means to capture professional ratings of an activity and store against the unique identifier of an activity. They could then provide an API call to understand the aggregated rating of that activity or indeed the individuals of the rating. This is to give confidence to the SPLW about that activity. Volunteer Management Systems Alignment Innovators could find a way to couple a volunteer management system with a social prescribing application to request an activity buddy to support the service user in attending an activity. Central to Sector Taxonomies Activity-type, Accessibility and Target Audience would be three taxonomies to describe the activity. SNOMED could be used to map its terms to these three taxonomies which would remove the need for the activity providers to understand the NHS SNOMED terms.
Data ecosystem mapping roles
Stakeholders
As is
To be
Organisations by Stakeholder
OpenActive application providers
Social prescribing application provider