Back to All
added

11.10.2022 API Release Notes

about 1 year ago by James Woods

Release Date: 11/10/2022

Attachment: 11.10.2022 API Release Notes

What’s New

  1. Add new fields in references section of the verified share API
    1. The verified share API now includes the role and organization for references. This data was previously only available in the data extract and ensures that users of the verified share API will have access to that information now.
  2. Add new field in work_history object for employment type
    1. To better present the data, the work_history section now includes a field that specifies the work history type for attested data in the verified share API. Gaps in employment will now be reflected by "Gap", while periods of employment will be reflected as "Employed".
  3. Add licensing institution field in state_licenses section of the Verified Share API
    1. For medical licenses, the licensing institution (medical board) is now being stored in the verified share API. Previously, this data was only available in the data extract. This can be found in the state_licenses section of the verified share API.
  4. Create URL to send images for "Other Certifications" in the Verified Share API
    1. URLs are now available for the following certifications: basic life support, CPR, advanced cardiac life support, neonatal advanced life support, advanced life support, advanced trauma life support, and pediatric advanced life support. These URLs can be found in the other_certifications section of the verified share API and allow users to pull the images to place in their credentialing system of record.
  5. Use the Credentialer_name and Credentialer_email from the invite API as the "From" email fields
    1. When we received an invite request from the API, we used the API user’s name and email when sending an invitation to the provider. This is used for the “From” email information. As an improvement, we will now use the “Credentialeremail” and the “Credentialer_name” fields from the API to use as the “From” address. As these fields are optional, we will only do this if both are provided. If not, we will revert to the current behavior of using the API user’s information.
      **_Important note:      ** This feature is only available to clients that have enabled us to host records with their DNS provider.