Nourish Integration

mark.thompson@oneadvanced.com Updated by mark.thompson@oneadvanced.com

WIP Nourish Integration

The Nourish Integration:

  • takes Persons records from the Nourish system and Creates/Updates them in Care Business Management
  • takes System User records from Care Business Management and Creates/Updates them in Nourish

The mapping between the systems is shown below:

Scope

The cohort of data to be in scope for Integration between Nourish and CBM is determined by a common value that is saved both in CBM and Nourish for Person and Staff Records.

In CBM the value is stored on the 'Provider' record within the 'Nourish Integration ID' field, and can only be seen by user with the “Nourish Admin" Security Profile after the "Enable Nourish Integration" field is set to 'Yes' and the record has been saved.

The corresponding value in Nourish can be accessed via the /configuration/service-list API and is used in the APIs listed below to select the appropriate records. - Configuration Reader - Nourish Integrations API Documentation

CBM

Nourish

Supplied by Nourish

Integration-id

core/data/team/NourishIntegrationID

Integration-token

Person Records

New System Users records are made using the following mappings:

CBM API - core/data/person

Nourish API - /v2/clients/reader - Client Reader (v2) - Nourish Integrations API Documentation

CBM API Field

CBM Label

CBM Required

CBM Ref Data

CBM Pick List

Nourish API Field

Derived

Id

Y

n/a

System Generated

Legacy Id

ID

Person Type

Y

n/a

"Person We Support"

Responsible Team

Y

Y

TBC

Use the Responsible Team of the Provider matching the NourishIntegrationID

Ethnicity

Y

Y

ethnicity

Fist Name

N

first_name

Last Name

Y

last_name

DOB

Y

birth_date

Proposed Funding Type

Y

Y

n/a

Set to "Nourish Integration"

Proposed Service Type

Y

Y

n/a

Set to "Nourish Integration"

DOB and Age

Y

Y

n/a

Set to 'DOB'

Address Type

Y

Y

n/a

Set to 'Residential'

Street

room_or_street

Town/City

post_town

County

county

Postcode

postcdoe

Country

country

Latitude 

latitude

Longitude 

longitude

System Users / Staff Profiles - TBC

New and Updates System Users Contracts records are taken from CBM and made in Nourish using these mappings:

CBM API -

  • core/data/systemuseremploymentcontract
  • core/data/staffreviewsetupbusinessunit,
  • core/data/provider

Nourish API

  • /staff/writer (used to write staff)

Scope

Take System Users where the Employment Contract 'Responsible Team' has a "Business Unit" which has a "Provider" linked to it with a matching "Nourish Integration ID" to the Integration Instance

CBM API Field

CBM Label

CBM Required

CBM Ref Data

CBM Pick List

Nourish API Field

Nourish Label

Derived

Title

Fist Name

First name

Last Name

Last Name

Preferred Name

Job Title

Date Of Birth

Contact Number

Email

Status

Set to 'Active'

Start Date

National Insurance No.

Employee ID

Pre-Req

Add "Nourish Integration" in the Proposed Funding Type and Service Type Reference Data

Sync Ethnicity Table Refe Data

Was this article useful?

Tribepad and Access Integration

CM2000 Export

Contact