The US Healthcare Finder API is linking to this site:

Have Questions? See if someone has already answered your question here, or ask a new question

They use the tag, and the tag info here at least explains something, but nothing on their page indicates that users are sent to an independent Q&A site.

Should we contact them with a request to at least update their page saying they are linking here?

How can this best be done? We have the same issue with the Department of Labor at developer.dol.gov.
An attempt to contact them with a request to update their page failed.

  • Is anyone from there answering questions or contributing to this site?
    – philshem
    Jun 30, 2017 at 12:36
  • Minor comment: they use the healthcare-finder tag, not the healthcare-finder-api tag. Jun 30, 2017 at 12:57
  • @philshem [healthcare-finder-api] isanswered:1 returns 13 questions with answers. I went through the profiles of all 'answerers' (that includes you), but there's nothing there.
    – user4293
    Jun 30, 2017 at 12:58
  • Maybe @jon-booth (opendata.stackexchange.com/users/3118/jon-booth), judging from this answer
    – user4293
    Jun 30, 2017 at 12:58
  • @StanislavKralin Weird. That tag does not exist here. All the more reason to get that page fixed.
    – user4293
    Jun 30, 2017 at 13:02
  • @JanDoggen, to your last comment: see this question. Jul 5, 2017 at 6:01
  • @JanDoggen DOL finally did get back to me, I apologize for not passing it along. Essentially the contact was 3rd party contractor, who had already moved on from the project. He said he would try and pass the information along...
    – albert
    Jul 18, 2017 at 16:49
  • @albert Thanks. Please add that under the other question.
    – user4293
    Jul 18, 2017 at 17:59

2 Answers 2


The answer is snail mail. Write to the department head setting out your complaint and asking them to arrange contact with the correct person.


The best approach in these types of situations to simply reach out to the group pointing users here and hope they are responsive.

If/when they are unresponsive, try seeking out an underlying repository that the group/users rely on, ideally in GitHub. If one can be found, file an issue; there's no guarantee that they'll be more responsive than they haven't been, but at very least you've publicly filed and have done the due diligence.

You must log in to answer this question.