Field-level protection and classification of sensitive clinical fields

Key Takeaway

Use field permissions, also called field-level security, to control who can see or edit a sensitive field. Page layouts, roles, and data classification don't block access to a field.

Clinical records hold protected health information (PHI), so an Agentforce Health design must control who can see or change each sensitive field and record why that field is sensitive. Field permissions control access to individual fields. Data classification labels each field with its sensitivity and the regulations that apply to it. Salesforce Shield adds encryption at rest and tracking of who accessed data.

Layers of data access

Salesforce data access works in layers:

Object permissions decide whether a user can use an object at all.
Field permissions, also called field-level security, decide which fields on that object the user can see or edit.
Record-level sharing decides which records the user can reach.

Field permissions protect one sensitive field without hiding the whole object, so a user can work with a record and still never see a protected value on it.

Salesforce Accredited Agentforce Health Professional Study Guide

Checklist progressProgress

0/167Learned

Checklist progressProgress

0/167Learned

Given customer requirements, determine how to create the solution for Agentforce Health features according to best practices

0/2

Given customer requirements, understand how to model patients, providers, healthcare facilities, etc., using the appropriate Agentforce Health objects

0/14

Given customer requirements, determine how to create the proper application solution design leveraging Agentforce Health best practices

0/5

Given customer requirements, determine when to use specific Agentforce Health capabilities

0/8

Given customer requirements, determine how to create the design solution for a specific Agentforce Health vertical to meet those requirements

0/6

Given the business processes/requirements, determine how to create the solution design utilizing best practices and Agentforce Health modules

0/5

Given a customer's business objectives and goals, define success-metrics/KPIs and configure Salesforce to enable reporting on these metrics

0/5

Given a customer's security/compliance requirements, design and implement the appropriate organizational security and data access considerations

0/8

Record access model for patient and member person accounts

Learn this concept

Field-level protection and classification of sensitive clinical fields

Learn this concept

Shield Platform Encryption for protected health information at rest

Learn this concept

Authentication, session controls and security baseline for health users

Learn this concept

Patient and caregiver data access on Experience Cloud sites

Learn this concept

Identity Verification before disclosing protected health information

Learn this concept

Consent capture for patient communications and data use

Learn this concept

Auditing and monitoring access to patient health data

Learn this concept

Given a customer's external systems and data requirements, determine the optimal integration strategy for the customer's Salesforce org

0/7

Given a customer's business requirements, design the future state business processes

0/4

Given the data requirements, create a migration strategy considering the legacy /future state system landscape ensuring accuracy and integrity

0/9

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers. 757 members and growing.

Go to Discord

Field-level protection and classification of sensitive clinical fields

Key Takeaway

Use field permissions, also called field-level security, to control who can see or edit a sensitive field. Page layouts, roles, and data classification don't block access to a field.

Layers of data access

Salesforce data access works in layers:

Object permissions decide whether a user can use an object at all.
Field permissions, also called field-level security, decide which fields on that object the user can see or edit.
Record-level sharing decides which records the user can reach.

Field permissions protect one sensitive field without hiding the whole object, so a user can work with a record and still never see a protected value on it.