Skip to content
Project Deliverables

Data Requirements

The table below is filtered on the ‘currency’ column to show all the attributes requested by SPLW to be included in OpenActive.
The label, under the currency column, of ‘proposed SP ready’ indicates an attribute that has been highlighted by the user research.
The label of ‘proposed’ indicates an attribute proposed by the technical review and a link to the technical document will be provided in the adjacent column.
The label of ‘current OA’ indicates where a field is already present in the current OpenActive dataset.
The label of ‘current OR’ indicates where a field is present in the Open Referral dataset.
Social Prescribing data dictionary
1
Data standard
Attribute
Defintion
Currency
Link to Technical document
Attribute value
1
OpenActive
Activity intensity
This may come from a taxonomy or use an encoded list (list of types) with common meaning to publishers
Proposed SP Ready 🌟
2
OpenActive
Activity lead
A selection from the proposed new data field for OpenActive
@Facilitator type
Proposed SP Ready 🌟
activity_lead
3
OpenActive
Activity type
Existing within OpenActive and needing validation for correct use from the
@Activity
List
Proposed 🌟
Current OA
ConceptScheme
4
OpenReferral
Assured date
The date that the information about the service was last checked. This gives confidence that information remains current, even if it was added some time ago
Proposed 🌟
Current ORUK
assured_date
5
OpenReferral
Attending access
How an activity can be accessed from a selection of: appointment, drop-in, membership and referral
Proposed 🌟
Current ORUK
attending_access
6
OpenReferral
Attending type
How to attend this service from a selection of: phone, online, venue, home visit. Social prescribers would like the option to also include group, one-to-one and self
Proposed 🌟
Current ORUK
attending_type
7
OpenActive
Befriender
A selection from the proposed new data field for OpenActive
Proposed SP Ready 🌟
befriender
8
OpenActive
Carer
A selection from the proposed new data field for OpenActive
@Facilitator type
Proposed SP Ready 🌟
carer
9
OpenReferral
Eligibility
Beyond age and gender restrictions,
@OA
makes no provision for eligibility requirements. This information is sufficient for most sports opportunities although later provision might be made for the wider eligibility options available to
@ORUK
via a Circumstance taxonomy.
A query parameter
Proposed 🌟
Current ORUK
eligibility
10
OpenActive
Facilitator type
From a selection of:
@Activity lead
,
@Befriender
,
@Carer
,
@Meet & greet
,
@Reception
,
@welcome
Proposed SP Ready 🌟
facilitator_type
11
OpenActive
Further info
Social prescribers have requested more details of an activity such as links to FAQs, videos and photographs (e.g. to help convey accessibility information). See
@Activity further info
. The
@ORUK
Service URI gives the opportunity to link to such information. More specific links to content such as photographs will allow activity finders (including those in social prescribing software) to present a fuller picture of an activity.
Proposed SP Ready 🌟
12
OpenActive
Location
A supporting REST method listing all the locations of activities.
A query parameter
Proposed 🌟
Place
13
OpenActive
Meet & greet
A selection from the proposed new data field for OpenActive
@Facilitator type
Proposed SP Ready 🌟
meet_greet
14
OpenActive
Modified date and time
The date and time a record was added or last modified is needed to make incremental updates to copies of data held and to give a degree of confidence in its likely up-to-dateness. Such a date and time is used by and included in RDPE feeds but not within the data structure.
A query parameter
Proposed 🌟
15
OpenActive
Payment
Cash or card; Commission with invoice
Proposed 🌟
payment
16
OpenActive
OpenReferral
Proximity
Specified by a postcode and a given distance (radius) from the postcodes centroid.
A query parameter
Proposed 🌟
17
OpenActive
Reception
A selection from the proposed new data field for OpenActive
@Facilitator type
Proposed SP Ready 🌟
reception
18
OpenReferral
OpenActive
Target audience
An indented audience taken from a taxonomy such as the
@LGA Circumstances list
,
@OpenActive hierarchical concepts
List or
@Open Eligibility
situations branch. A query parameter
Proposed 🌟
19
OpenReferral
OpenActive
Taxonomy
the OR data structure uses “
@Service Type
” to describe the type of service delivered from a controlled/shared vocabulary. This approach is matched by the “
@Activity
” object in OA. ORUK (and version 2 of OR) extends the standard via link_taxonomy which supports taxonomies describing service properties other than the
@Service Type
, such as
@Eligibility
@Accessibility
,
@Target audience
, organization type,
@Cost option
. See a fuller discussion of taxonomies below. Taxonomy terms apply to these activity attributes that are important to social prescribers:
Activity accessibility 🌟
@Activity type
🌟 - existing within OpenActive and needing validation for correct use from the Activity List
Location accessibility 🌟
@Target audience
🌟 - taken from a taxonomy such as the
@LGA Circumstances list
, Open Active’s
@Activity
Concept List or
@Open Eligibility
situations branch
Proposed 🌟
20
OpenActive
Welcome
A selection from the proposed new data field for OpenActive
@Facilitator type
Proposed SP Ready 🌟
welcome
No results from filter
Note
NHSX is currently consulting on the requirements for social prescribing software under its Health Systems Support Framework (HSSF). The requirements will be set out using the following headings but they will not be published until the end of 2021.
Demographic information (about me)
Presenting need (what matters to me)
Social Prescribing Intervention (what I was offered)
Outcomes (what was the result)
The HSSF data requirements focus mainly around the patient whereas this research is focused on the physical activity data which will be used to identity a suitable ‘intervention’.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.