Question 1
A global MedTech company, Vitality Health, is consolidating three regional Salesforce orgs (AMER, EMEA, APAC) into a single global org. Each region has a custom Patient__c object, but the data models have critical differences in fields, validation rules, and relationships to a custom Medical_Device__c object. The architect must design a unified, scalable data model that complies with GDPR and HIPAA, tracks device service history efficiently, and supports an anticipated volume of over 80 million patient records within two years.
Key Requirements:
- A single, global representation of a Patient.
- Strict compliance with regional data privacy laws (GDPR/HIPAA).
- A scalable many-to-many relationship between Patients and their assigned Medical Devices, including a detailed service history for each device assignment.
- High performance for patient record retrieval and reporting.
Which data model should the architect recommend to meet these complex requirements?
Answer and explanation
Correct answer: A
This is the optimal solution. Person Accounts provide a standard, scalable way to represent individuals, combining Account and Contact functionality, which is ideal for a Patient model. A junction object (Device_Assignment__c) correctly models the many-to-many relationship and can hold rich details like service history. Record types on the Person Account effectively manage regional variations in layouts and processes, while standard field encryption and security features can be leveraged for GDPR/HIPAA compliance.