Big Nasty Pharma (BNP)

AI-Assisted Study Note

This page brings together public scenario links and AI-assisted research notes for study use. Start with the scenario brief, make your own attempt, and open the spoiler section only when you are ready to compare.

Scenario Snapshot

Field	Detail
Start here	Discovery index
Scenario source	Community scenario
Current status	Live
First public date	2021-02
Primary source	Open primary source
Coverage available	Scenario brief + Discussion or analysis

Why This Scenario Matters

• This entry is included because it appears in the public CTA scenario corpus and has enough public evidence to track for study use.

Only Open If You Have Attempted the Scenario

The section below contains public follow-up links, board-call material, and AI-assisted notes compiled from those public sources.

Open follow-up links, Q&A, and analysis

Follow-Up Links

• Discovery index
• Analysis reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• Clinical Trial Data: “How do you handle the requirement for CNS vs. Psychoactive team data silos? Why choose Private OWD for the Compound object?”
• Dose History LDV: “With 5M+ dose records per trial cycle, how will your ‘Patient Adherence’ reports remain performant? What is your Big Object query strategy?”
• SLA Milestones: “The scenario requires side-effect reviews within 8 hours. Why use Entitlement Management over simple Flow-based alerts?”
• Identity for Patients: “Which identity license did you choose for the 100k patients? Is Social Sign-on appropriate for clinical trial participants?”
• Sentinel Integration: “Describe the technical handshake between Salesforce and the Sentinel Safety API. Is this Request-Response or a Polling pattern?”

Common Mistakes

• PII/PHI Security Gaps: Using standard Chatter for “Patient-Staff Messaging” without addressing HIPAA compliance or Shield encryption-at-rest.
• Missing Recruitment Hard-Gates: Failing to make the “Government Permit Verification” a mandatory gate in the onboarding flow before clinical activity can start.
• Vague Archiving: Simply saying “we will archive data” without explaining how staff will access 7 years of regulated dose history for FDA audits.
• Data Load Sequencing: Failing to load Compounds and Trials before Participants, leading to orphan records and migration errors.

Strong Patterns

• Health Cloud Program Model: Leveraging the Health Cloud Care Program and Care Plan objects to map naturally to trial protocols and patient tasks.
• Shield for HIPAA: Mandating Shield (Deterministic Encryption and Field Audit Trail) to satisfy strict pharmaceutical regulatory requirements.
• Mobile Publisher for Patients: Providing a branded mobile app with “Store and Forward” capabilities for patients to log side effects in areas with poor connectivity.

Strategic Insights

• The “Life Sciences” Test: BNP tests the architect’s ability to handle highly regulated global environments (FDA/EMEA) while managing massive transactional dose data.
• Global Governance: Requires a strong CoE to maintain a unified global drug development process while allowing for regional regulatory differences.

Additional Notes

• Focuses on clinical trials, drug development lifecycles, and strict security silos for CNS vs. Psychoactive drugs.