We call https://clinicaltables.nlm.nih.gov/api/npi_idv/v3/search?terms= many times a day and every so often (once a week or so) we get back a result which is formatted wrongly in that instead of retuning stringified json in the address field, it returns a plan address not stored as json- i.e. a plain 2010 OPPORTUNITY LANE, GLIDE, OR 97443 instead of "{\"line1\":\"123 PARK AVE\",\"line2\":\"APT 7\",\"city\":\"NEW YORK\",\"state\":\"NY\",\"zip\":\"10010\",\"country\":\"US\",\"phone\":\"(555) 555-5555\"}"],
Offhand I can't think why that would be happening. Can you share a specific example of a clinicaltables query that returns data that causes that problem?
We call
https://clinicaltables.nlm.nih.gov/api/npi_idv/v3/search?terms=
many times a day and every so often (once a week or so) we get back a result which is formatted wrongly in that instead of retuning stringified json in the address field, it returns a plan address not stored as json- i.e. a plain2010 OPPORTUNITY LANE, GLIDE, OR 97443
instead of"{\"line1\":\"123 PARK AVE\",\"line2\":\"APT 7\",\"city\":\"NEW YORK\",\"state\":\"NY\",\"zip\":\"10010\",\"country\":\"US\",\"phone\":\"(555) 555-5555\"}"],