Loading
Salesforce now sends email only from verified domains. Read More
Administer Health Cloud
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Upload Provider Roster Data Files from Cases

            You are here:

            1. Salesforce Help
            2. Docs
            3. Administer Health Cloud

            Upload Provider Roster Data Files from Cases

            Upload provider roster data that you receive via cases in the form of Case-Related Files to the Provider Network Management data model in Data 360.

            Required Editions

            Available in: Lightning Experience

            Available in: Enterprise and Unlimited Editions of Health Cloud with the Health Cloud Provider Network Management Add-on and Genie Data Platform Starter licenses
            User Permissions Needed
            To create cases "Create" on cases
            To view cases "Read" on cases
            To update cases "Edit" on cases
            To run data ingestion Health Cloud admin permission set
            Important
            Important To use this feature, ensure that the Roster File Mapping feature is enabled in your Salesforce org.

            Before you begin:

            • Make sure the Related tab is available on the Case page layout to show the Case-Related Files.
            • Verify that the roster file does not have field names over 40 characters.
            • Avoid spaces in field names.
            • Make sure the dates are in yyyy-mm-ddThh:mm:ssZ or yyyy-mm-dd format, and Boolean fields are set to TRUE or FALSE, or the data upload will fail.

            Each case can contain multiple Case-Related Files. Follow these steps for each file.

            1. In your Provider Network Management app, click the Cases Object tab from the navigation bar or select Cases from the object menu.
              You can use the list view dropdown menu to select different lists.
            2. Select the case that you want to work on.
            3. To view the Case-Related File list, select the Related tab.
            4. Click the dropdown menu for the specific file you want to process.
            5. Select Set Staging.
              Staging uploads data from the source CSV file, checks for any schema issues, and creates a runtime Target PNM Canonical DLO. We recommend waiting 5 minutes for the staging to complete. Refresh the page to see the process status change to completed and receive a confirmation message.
            6. From the dropdown, click Create Dataset Mapping to create a mapping to map the columns of the roster file to the canonical data lake object columns.
              1. On the source node, click Configure.
                In the Settings section, we recommend using ProviderNPI as the primary key. Make sure that the content ID is auto-selected and do not make any edits to it. In addition, make sure all roster file columns to be uploaded are selected.
              2. Click Save.
              3. Leave the transform node as is and select the write back node and then click Configure.
                Make sure Use existing Data Lake Object is checked. Then, for each field, check if the fields are correctly mapped.
              Note
              Note You can automate your field mapping with Einstein if you have the required permission. See, Map Related Fields by Using Einstein.

              When you create a mapping for a specific use case, update the Status from InReview to Completed when the DPE mapping is done.

            7. Click Select Mapping.
              Choose a mapping for the source file to map to the canonical dataset. You can choose from the default or custom-mapping definitions created for your org.
              Note
              Note You can select a mapping when the incoming roster file schema is the same as that for the selected mapping definition.
            8. Before running data ingestion:
              • Ensure that the ProviderNpi, ProviderNpiIsActive, ProviderFirstName, and ProviderLastName have values in the roster file and are included in the mapping.
              • Confirm that the CareService, CareSpecialty, and CareTaxonomy entities are present and match the values in the roster file. Identify these entities by using the Name field for CareService and CareSpecialty, and the Code field for CareTaxonomy.
              • Create a business account to represent the provider organization. Use the BusinessAccountId canonical field to capture the Account ID, which serves as a lookup from the HealthcarePractitionerFacility entity to indicate that a provider is working at a specific facility.
              • To ensure records are created in junction entities, make sure that associated records are created in the parent entities, such as HealthcareProviderSpecialty, HealthcareProviderTaxonomy, HealthcarePractitionerFacility, and HealthcareProviderService objects.
            9. To upload data from the source file to the Health Cloud Provider Network Management objects, click Run Data Ingestion.

            The time for the data upload can vary depending on the file size. To monitor the upload progress, go to Monitor Workflow Services in Setup. When the DPE processing status is complete, check the field level upload logs under the File Process Logs tab.

             
            Loading
            Salesforce Help | Article