lsc-provider-engagement-compliance
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Provider Engagement Compliance (Japan EPPV and MID) setup and troubleshooting. Use when user asks about EPPV, MID, Account Compliance, 取引先コンプライアンス, compliance cycles, Care Program with ProviderEngagementCompliance, Start Compliance Action Plan, Report Compliance Activity, PrvdEngmtComplianceCycle, or reporting on cycles.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-config-migrationSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.
- Distinctive: line 44
Only the Start Compliance Action Plan button moves a plan to In Progress (not DML, API or edit form).
- Very specific: line 55
Run check_eppv_config for an org-wide picture, and diagnose_lsc_issue with the exact symptom.
- Distinctive: line 57
Start missing: Action Plan layout actions list.
- Distinctive: line 61
Never suggest OmniStudio for the mobile tab.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
How to Answer EPPV / Account Compliance Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| Setup checklist, rules, gotchas, reporting | get_lsc_module_docs({ module: "provider-engagement-compliance" }) |
| Overview, what EPPV/MID are, rep experience | search_lsc_knowledge({ query: "EPPV MID Provider Engagement Compliance" }) |
| Check an org's EPPV setup | check_eppv_config() or check_eppv_config({ profileName: "<rep profile>" }) |
| An error or symptom | diagnose_lsc_issue({ symptom: "<error text>" }) (known causes eppv-*) |
| DB Schema records for the feature | list_db_schema({ filter: "ActionPlan" }), create_db_schema, assign to the rep profile |
| Tab / quick action | list_navigation_tabs, add_navigation_tab, list_lsc_actions, create_quick_action |
| Flows, plans, cycles in the org | run_soql on ActionPlan, PrvdEngmtComplianceCycle, AssessmentTask, CareProgram (standard objects) |
| Mobile cache | generate_mobile_metadata_cache({ profileName }) — one profile per call |
Admin Console data, DB Schema and actions use their dedicated tools, never run_soql.
Model in one picture
CareProgram (Category ProviderEngagementCompliance) → CareProgramProduct, ActionPlanTemplateAssignment → ActionPlanTemplateVersion (Final) → Items (PrvdEngmtComplianceCycle) + ItemValues (Name, DurationInDays); ActionPlan (TargetId = HCO, TargetReferenceRecordId = CareProgram, ActionPlanType PrvdEngmtCompliance) → PrvdEngmtComplianceCycle (generated on Start) → completed by AssessmentTask (TaskType PrvdEngmtComplianceTask) on a Completed Visit.
Setup order (what worked)
- Enable feature; permission sets (reps: Core + Field Sales Representative; admins: Commercial Admin + Core).
- Action Plan State picklist values + Admin Console status mappings (distinct value per shipped state), Care Program statuses, Assessment Task record type and field set.
- Action Plan Status read-only for reps (FLS).
- Page layouts: Care Program, Care Program Product, Action Plan Template fields, and an explicit actions list on Action Plan (else no Start button).
- Sharing: Action Plan Template rule; territory sharing or ownership for plans and programs.
- Clone, schedule and activate the four flows (
Update_Assessment_Task_On_Visit_Completion_Clonecompletes cycles). - Account Compliance tab (desktop and mobile navigation), enabled for the rep profile.
- Quick action
AssociateCareProgram("Report Compliance Activity" on the iPad), assigned to the rep profile. - Eleven DB Schema records (
DbSchema_<Object>: CareProgram, CareProgramProduct, ActionPlan, ActionPlanItem, ActionPlanTemplate, ...Version, ...Assignment, ...Item, ...ItemValue, PrvdEngmtComplianceCycle, AssessmentTask), no field filters, assigned to the rep profile. - Generate the cache per profile, then sync the iPad.
Full detail: the module doc support-engineering-eppv-setup-and-troubleshooting.
Rules to state up front
- Only the Start Compliance Action Plan button moves a plan to In Progress (not DML, API or edit form); cycles generate on Start.
- Plan start date: on/after the Care Program start date and not after today.
- Care Program: Announce Date ≥ today; Start ≥ Pre-cycle Start ≥ Announce. No products once announce date is today or earlier (insert at today+2, add product, then set dates to today). No back-dating.
- Final templates/versions are locked; changes need a new template, program and plans.
- Pre-cycle: the iPad excludes the first cycle from completed and total (8 cycles show /7).
- A cycle completes only via Report Compliance Activity on a Completed Visit inside the cycle window, after the flow runs and the iPad syncs. Plain Create Visit never completes one. The
prvd_cmplbatch actions don't write plan progress. - iPad: badge = plan state; cycle chip = cycle whose dates include today; 未開始/進行中/完了 filters are plan-state filters.
- Reporting: no standard cycle report type. Use single-object custom report types and verify against SOQL (a report once showed only Cycles 1–5 of 8). Plan-by-cycle matrix needs the EPPV Cycle Matrix LWC.
Troubleshooting flow
- Run
check_eppv_configfor an org-wide picture, anddiagnose_lsc_issuewith the exact symptom. - "Unknown Account" / "Account and Place cannot be empty": check
ActionPlan.TargetIdand that the account is on the device. - Start missing: Action Plan layout actions list.
- Cycle not completing: AssessmentTask exists, visit Completed and dated in the window, flow active with no faults, then sync.
- One-day-off dates: UTC display.
Never suggest OmniStudio for the mobile tab; use LSC apps or standard LWCs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

