Master the Salesforce Health Cloud Accredited Professional (WI24) Health-Cloud-Accredited-Professional Exam with Confidence!

• A is correct because obtaining verified parental consent before collecting and storing any personal information of children is one of the mainrequirements of COPPA. The consent must be obtained in a way that ensures that the person providing consent is the child’s parent or legal guardian, such as using a credit card, digital signature, or video conference.
• B is correct because disclosing the organization’s privacy policy to parents and obtaining their consent is another requirement of COPPA. The privacy policy must explain what information the organization collects from children, how it uses and discloses it, and what rights parents have to review or delete their children’s information.
• C is incorrect because ensuring that Bloomington Caregivers’ system implementation partner has met all COPPA regulations during the build phase is not a consideration for the company, but for the partner. The company is ultimately responsible for complying with COPPA, regardless of who builds their system.
• D is correct because implementing appropriate security measures to safeguard children’s personal information is another requirement of COPPA. The organization must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children.

References: : Children’s Online Privacy Protection Act (COPPA) : Children’s Online Privacy Protection Rule ("COPPA")

The design considerations that the administrator has to be aware of when creating the application forutilization management are:

• Each care request has to have an associated case. A case is the standard Salesforce object that represents a carerequest in Health Cloud4.
• New care requests can be created using the ‘Create Care Request’ component. This component allows users to create a new care request from any page in the Health Cloud console5.
• Path can be used to visually represent the status of a care request. Path is a standard Salesforce feature that displays the stages of a process, such as a care request, and guides users along the steps in Salesforce Lightning Experience6.
• Care request functionality is not included in the Health Cloud managed package. It requires installing the Utilization Management unmanaged package for Health Cloud and assigning the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.
• Care requests do not have empower components that can be exposed within Communities. Empower components are custom Lightning components that allow patients or members to view and manage their health information in Communities. Care requests are not part of the empower components.

According to the Salesforce documentation, PurchasePlan is an object in Health Cloud that stores information about a plan purchased by an employer or an individual from a payer. PurchasePlan is to be used as a template for creating MemberPlan records for each member enrolled in the plan. MemberPlan is an object in Health Cloud that stores information about a member’s enrollment in a plan, such as effective date, termination date, coverage type, and benefits.

The three key considerations when complying with HIPAA regulations using Salesforce Shield in conjunction with Bloomington Caregivers’ data strategy are ensuring that sensitive data is encrypted both in transit and at rest, configuring data retention policies to ensure that records are retained for the appropriate length of time, and implementing audit trails and regularly reviewing them to detect unauthorized access attempts. Salesforce Shield provides these features as part of its platform encryption, event monitoring, and field audit trail capabilities.

List of Patient/Member Conditions (B), Gender ©, and Date of Birth and Age (E) arethree types of basic Patient or Member information that are displayed on the Patient info component. Primary Care Coordinator (A) and Thumbnail of Chatter Photo (D) are not displayed on the Patient info component.

According to the [Health Cloud Integration and Interoperability Guide], the new clinical data model in Health Cloud is aligned with FHIR R4 standards, which is the latest version of the FHIR specification. Health Cloud supports data exchange with both HL7 and FHIR enabled systems, using different methodssuch as MuleSoft connectors, Salesforce APIs, or third-party integrations. Most EHR data exchange today is still done via legacy HL7 v2 – simple application interface, which is a widely adopted standard for exchanging clinical and administrative data. Health Cloud does not have a FHIR server, but it can connect to external FHIR servers using APIs or MuleSoft connectors. The new clinical data model in Health Cloud is not aligned with HL7 v2-simple application standard, which is a different standard from FHIR.

Expression Set Templates are the prebuilt feature that the payer should leverage to implement predefined rules for its prior authorization request review process. Expression Set Templates are reusable sets of expressions that can be used to evaluate business logic and trigger actions based on the results.

The administrator should add the respiratory therapist to the patient’s Care Team and grant Read or Read/Write access as needed. This is the out-of-the-box Health Cloudfeature that allows the administrator to share patient data with other users who are involved in the patient’s care. The Care Team is a group of users who can collaborate and communicate on a patient’s health record.

 Code Sets are the entity inthe new data model of Health Cloud that can be used to store mappings between different coding systems such as ICD and HCC codes. Code Sets are a collection of codes that represent a specific concept or value in a terminology system1.

Reference and details below.

 According to the Salesforce documentation3, there are two ways to restrict access to an entire patient/member list or to specific columns of that list:

• Sharing setting: Sharing settings control the access level that users have to records owned by other users. You can use sharing settings to grant or restrict access to an entire list of records based on criteria such asrole hierarchy, public groups, or manual sharing3.
• Field Level Security: Field level security controls the access level that users have to individual fields withina record. You can use field level security to grant or restrict access to specific columns of a list based on profiles or permission sets3.