Case study · Cascade Health Systems

Urgent Salesforce Developer Backfill for Cascade Health Systems

Engagement summary

ForceFolks supplied a senior Salesforce developer to Cascade Health Systems five business days after signing. From 8 April to 26 July 2024, the developer joined Cascade’s Salesforce scrum team and rebuilt its care-intake workflow. Cascade kept backlog and release decisions. Its Service Cloud case records show median processing time falling from 42 to 29 minutes in the 30 days after release.

Client and Engagement Facts

Cascade Health Systems: Client and Engagement Facts
FieldEngagement detail
ClientCascade Health Systems
Industry and client locationHealthcare payer and provider network in Portland, Oregon
Salesforce scope and toolsHealth Cloud, Service Cloud and MuleSoft. Jira, GitHub, Copado and Salesforce CLI.
Staffing and datesOne full-time senior Salesforce developer from 8 April to 26 July 2024
Delivery arrangementNearshore delivery with six shared hours each working day in Pacific Time
Client ownershipCascade’s Salesforce Engineering Manager assigned backlog work. Its technical lead reviewed pull requests. The Director of Care Operations Technology approved the release.

Why the Client Added Capacity

Cascade’s Health Cloud developer resigned three weeks before its intake deadline. The six-person Salesforce team already had a Jira backlog and release calendar. It needed a developer who knew the Health Cloud data model and Apex and could take on the intake work in the existing sprint.

Client corroboration

“We had a deadline and no internal Health Cloud depth. ForceFolks gave us one developer who was in our Jira and shipping reviewed code inside two weeks. The intake workflow passed UAT on the first attempt, which our own team did not expect.”

Marcus Webb, Director of Care Operations Technology, Cascade Health Systems

Role Contributions and Acceptance

Cascade Health Systems: Role Contributions and Acceptance
ForceFolks roleWork and outputsClient review or acceptance
Senior Salesforce developerRebuilt member intake with two Apex triggers and a service class for validation and duplicate checks. Added a Flow for care-coordination triage and a MuleSoft eligibility check to replace a manual step.Cascade’s engineering manager assigned the work. Its technical lead reviewed the pull requests, and its Director of Care Operations Technology signed off in UAT.

Outcomes and Evidence

Cascade Health Systems: Outcomes and Evidence
MeasureBaselineResultWindowSource
Signing to start—5 business daysApril 2024ForceFolks onboarding record
Start to first merged pull request—6 business days8–16 April 2024Cascade GitHub merge log
Median intake processing time42 minutes29 minutes, down 31%30 days after releaseCascade Service Cloud case timestamps
New duplicate member records per week21431, down 86%30 days after releaseCascade Health Cloud data audit
Intake deadline31 May 2024Met. UAT signed 24 May 2024.May 2024Cascade UAT sign-off

Discuss the work your team needs

Share the Salesforce work, roles and client review responsibilities. ForceFolks will assess the staffing requirement against that scope.

Discuss your staffing requirement