Enrich, Supplement, and Update

Consider the following scenario for the providerLanguages element:

• Client submits English, French, and Mandarin Chinese.

• Inspection results indicate that:

  • English and French are valid, and no action is required (keep sourceValue)

  • Mandarin is invalid and needs to be removed (update sourceValue)

  • Provider also speaks Portuguese and Russian, which need to be added (enrich sourceValue)

Given this scenario, the providerLanguages data element returned by the API would look like this:

"providerLanguages": { 
    "sourceValue": "English;French;Mandarin Chinese", 
    "standardizedValue": null, 
    "verifiedValues": [ 
        { 
            "value": "English", 
            "outcome": "Valid", 
            "source": "BdxTruth", 
            "date": "2022-11-29T19:25:15.7Z" 
        }, 
        { 
            "value": "French", 
            "outcome": "Valid", 
            "source": "BdxTruth", 
            "date": "2022-11-29T19:25:15.7Z" 
        }, 
        { 
            "value": "Portuguese", 
            "outcome": "Enriched", 
            "source": "BdxTruth", 
            "date": "2022-11-29T19:25:15.7Z" 
        }, 
        { 
            "value": "Russian", 
            "outcome": "Enriched", 
            "source": "BdxTruth", 
            "date": "2022-11-29T19:25:15.7Z" 
        }, 
        { 
            "value": "Mandarin Chinese", 
            "outcome": "Invalid", 
            "source": "BdxTruth", 
            "date": "2022-11-29T19:25:15.7Z" 
        } 
    ] 
} 

• Note: QES evaluates the validity of the client-provided source values only for the following data elements: NPI, Entity Type, Name, Location Name, Ord NPI, Address, Specialty, Phone, Fax, Panel Status (PS), Gender, Office Hours, Languages, Affiliations, Email, Website, Tin, and License.

  QES does NOT evaluate the validity of client-provided source values for: ADA Features, Frequency at Location, Bboard certs, Medicaid License, Race, Ethnicity, Telehealth, Public Transport, Cultural Competency, Taxonomy, or Areas of Expertise. The reason they are not validated is because many of these values are not used by clients or are not stored in an industry-standard way. Therefore, when the recommended action is to enrich one of these data elements, the recommendation is made without regard for whether the client’s own values for these data elements is valid or invalid. The best practice is for clients to make their own determination on whether the enriched values for some of these data elements are useful.