Attested state keys added to state

Overview

The Verified share API endpoint surfaces state license information from verified sources, providers (attested), and FSMB. FSMB state license information shows up in state_licenses as attested and in fsmb_info with a lot more data that comes in from that source. Because FSMB is not considered a primary source, the endpoint included the attested license number and state under state_licenses and all other information along with the license number and state under fsmb_info.

This made for a clunkier experience by partners who ingest data from the API because it requires them to create conditional logic on their end that specifies if the attested state license number is from FSMB and they also want to gather the institution then they should pull that from fsmb_info. Rather, state_licenses has become the area of the endpoint where they go to gather all state license information now and if they want specific data that comes from FSMB then they should pull that from fsmb_info.

Solution

Created new attested state license keys to populate FSMB data in state_licenses.

attested.state_license.initial_date - The initial date of the state medical license of the practitioner as supplied by FSMB.
attested.state_license.expiration_date - The expiration date of the state medical license of the practitioner as supplied by FSMB.
attested.state_license.license_status - The license status of the state medical license of the practitioner as supplied by FSMB.
attested.state_license.institution - The licensing institution of the state medical license of the practitioner as supplied by FSMB or the provider.

These keys should populate when an attested state license number is coming from FSMB.
If the attested state license number was provided by the clinician, then only the attested.state_license.license_number and attested.state_license.state should populate. The other attested state license keys should return as null.