When an admin or a service provider adds the information Suitabilities are presented as part of the main service entry and SEND needs are under the 'this service is part of the local offer' checkbox.
Some notes on the fields:
Suitabilities and SEND needs are two distinct categories. Suitabilities are much more freeform, where as SEND needs relate more closely to guidance and standardised categories. NB the accessibilities field relates specifically to the location.
send_needs:
Autism
Hearing impairment
Visual impairment
Mobility
Cognitive
suitabilities:
Autism
Learning difficulties
Mental health/acquired brain injury
Visual and / or hearing impediment
Physical disabilities
Older people
Dementia
accessibilities:
Accessible toilet facilities
Hearing loop
Car parking
Changing facilities
British sign language (bsl)
Disabled car parking space
Hoist
Baby changing facilities
Parking nearby
Bus stop nearby
Building has lift
Wheelchair accessible entrance
Partial wheelchair access
possible solutions:
Local offer send_needs and suitabilities are made mutually exclusive for all Outpost instances
Local offer checkbox changes the UI in a more significant way
More customisability around field descriptions for each Outpost instance
related to #92 there is a question about how different instances treat suitability and send needs fields.
For example on Buckinghamshire the FIS directory only allows filtering on send needs field whereas the BOD directory only allows filtering on the Suitability fields.
When an admin or a service provider adds the information Suitabilities are presented as part of the main service entry and SEND needs are under the 'this service is part of the local offer' checkbox.
Some notes on the fields: Suitabilities and SEND needs are two distinct categories. Suitabilities are much more freeform, where as SEND needs relate more closely to guidance and standardised categories. NB the accessibilities field relates specifically to the location.
send_needs:
suitabilities:
accessibilities:
possible solutions: