Skip to content
Big Cities Health Coalition logo Big Cities Health Coalition Public Health AI & Tech Exchange
Contribute

Submit a use case

Share a digital tool, data project or AI use case with the coalition. Code is optional: a clear description of what you built and what it took is enough. Nothing is published until it is approved.

Nothing is sent from this page. Your answers stay in this browser until you press a button. You'll need a free GitHub account.

  1. 1. Answer the questions below.
  2. 2. Check your answers, then send them to GitHub.
  3. 3. Press Submit new issue on GitHub — that is what actually submits it.

Sign in to GitHub before you start. If you are not signed in when you send, GitHub can drop your answers on the way through its sign-in page. Sign in to GitHub (opens in a new tab), then come back here.

Before you start, the governance page has the five things reviewers check and the rules on privacy and licensing — you keep ownership of anything you share.

Using an AI agent?

An assistant such as Claude, ChatGPT or Copilot can draft your answers with you. Give it the instructions; they say what each question asks and which answers are allowed. Its answers are shaped by this JSON Schema. Then paste the JSON it gives you below. Screenshots and files are not part of it: add them on this page or in the GitHub issue.

About

0 of 8 sections complete

Section 1 of 8

About

What it is, who built it, and what it changed.

Specific enough that someone scanning a list of names knows what it is.

What kind of solution is it?

Select all that fit. A dashboard fed by a new pipeline is both.

If it involves AI, which of the four coalition categories fits best? (optional)

For AI work only: the HHS-adapted categories the DMWG AI inventory uses. Leave it blank if no AI is involved.

Which public health areas does it serve?

Select all that fit. The first five follow the program areas of the Foundational Public Health Services; the rest are the capabilities every program relies on.

How far along is it?

Pick the stage that matches real use, not the plan.

Shown on the catalog card. Plain language, no jargon.

A number if you have one.

A health department, city, agency or member organization.

Section 2 of 8

How it's built

The tools and technologies behind it, any AI involved, and where it runs.

What part, if any, does AI play? (optional)

Most digital work involves no AI, and that is a fine answer.

If AI is involved, what kinds? (optional)

Select all that apply. Skip it when there is no AI.

Name the languages, platforms, libraries, standards and AI models that matter. One per line, or separated by commas.

Where does it run? (optional)

Select all that apply.

Leave it blank if your own team built it.

Section 3 of 8

Reuse

What it would take for another team to use this.

Who is the least technical person who could get this running?

Judge it by setting the thing up, not by using it afterwards.

What would another team need before they could use this? (optional)

Select all that apply.

GitHub, GitLab, Azure DevOps or any public repository. Code is optional: leave this blank if you are not sharing it.

A report, a blog post or a vendor case study all count.

Anything else worth linking? (optional)

Shared drives, SharePoint, data dictionaries, model cards, container images, vendor pages.

Up to eight images, 15 MB total. No personal information visible.

You can drag image files straight into the GitHub issue on the next screen. If your images are already online, paste their addresses here instead — one per line, optionally followed by | alt text. PNG, JPEG, GIF and WebP images are copied into the repository; anything else is left as a link for a maintainer.

Slide deck or one-pager

Files can't be attached from this page. Drag deck.pdf into the GitHub issue on the next screen and a maintainer will add it to your entry. Over 25 MB, or kept in a shared workspace? Paste a link in “Other resources” instead.

Section 4 of 8

Sharing & licensing

What another health department can get from you, on what terms, and how portable it is.

What can another health department get from you?

Code is optional. A clear account of what you built and what it took is worth sharing on its own.

Under what license is it shared? (optional)

Optional if only a description is shared. The coalition default is a permissive license (MIT, Apache 2.0, CC BY). Your organization keeps authorship.

Government-to-government only, agreement required, contact us — whatever applies. Leave blank for open-licensed resources.

Could it be adapted outside its original vendor ecosystem?

Microsoft-built but portable to AWS is 'partially'.

Which pieces are vendor-specific, and what a team on a different stack would need to swap.

Name it by its slug, the last part of its URL. That entry will show it was adopted by yours. One per line, or separated by commas.

Section 5 of 8

What it took

Money, contracting and approvals — the part a budget or governance conversation needs.

Roughly what did it cost to get it running the first time? (optional)

One-time cost: contracts, build, implementation. A band is fine — nobody expects an exact figure.

What does a normal year cost to run? (optional)

Licences, hosting and usage charges only — staff time belongs in the write-up.

How was this paid for or contracted? (optional)

Select all that apply. This is the question peers ask most and the one that is hardest to find out.

Which internal reviews or approvals did it need? (optional)

Select all that apply. Saying 'not yet reviewed' is more useful to a peer than leaving it blank.

Optional but strongly encouraged. Which populations the output reaches, who it might miss or serve less well, and what you would watch.

Section 6 of 8

Data & access

What data it touches and who sees the output.

Reviewers spot-check. If the answer is no, redact first.

What kind of data does it touch?

Select all that apply. This helps others judge governance and approval effort.

Describe the sources — do not paste sensitive data. One per line, or separated by commas.

Who sees the output?

Pick the widest group that sees anything it produces.

Data-use agreements, retention rules, de-identification steps — the caveats that travel with the resource.

Section 7 of 8

Contact

Someone others can reach out to.

Someone happy to answer questions from another team.

So a peer knows who they are writing to.

Used once a year, when this entry is due to be re-confirmed, so the reminder reaches you. Leave it blank to send it to the maintainers only.

Section 8 of 8

The story

Problem, approach, what it took, results and lessons.

Markdown is supported. Suggested headings: Problem, Approach, Time and resources (data, staffing, cost), Results, Lessons learned, How to reuse.