OHDSI Prompt Registry

The OHDSI Prompt Registry makes reviewed prompt workflows discoverable through Groundworkers MCP. A pack can publish instructions, JSON Schemas, examples, deterministic Markdown rendering, and an optional user-facing MCP prompt.

To see what is available before choosing a workflow:

Call ohdsi_prompt_registry_catalogue with:

{}

The response lists each active pack, its scope, tags, source, documents, schemas, prompts, renderers, and advertised tool dependencies. Filter by a tag when the catalogue is large:

Call it with a tag filter:

{"tags": ["concept-mapping"]}

Then inspect the pack’s manifest and instructions. A resource-capable client can read the URIs returned in the catalogue. A client without resource browsing can ask for links:

Call ohdsi_prompt_registry_links with:

{"pack": "omop-concept-grounding"}

The registry also exposes a small, stable tool surface:

Declared workflows appear in the MCP prompt list. Current examples include:

rqt_structure_question   # bundled research-question workflow
ocg_ground_concepts      # installed concept-grounding workflow
gdc_classify_fields      # filesystem Groundcrew workflow
gsc_classify_columns     # filesystem Groundcrew workflow

Invoke a prompt by its published name. Prompt arguments are strings; JSON inputs are passed as JSON text:

Call ocg_ground_concepts with:

{
  "mapping_request": "{\"items\":[{\"item_id\":\"dx-1\",\"label\":\"Type 2 diabetes mellitus\"}]}"
}

For a workflow that returns a JSON document, validate it before treating it as an operational handoff:

Call ohdsi_prompt_registry_validate with:

{
  "pack": "omop-concept-grounding",
  "schema": "mapping_decision",
  "document": "{...}"
}

The instructions in each pack state which schemas and domain tools apply. The registry supplies the current schema at read time, so the instructions and contract do not need to be kept in separate prompt copies.

Documentation

Full documentation: https://AustralianCancerDataNetwork.github.io/ohdsi-prompt-registry

• Pack sources — bundled, installed, and filesystem packs, and which one wins when two packs share a name.
• Pack format — the manifest contract every source uses, and how to extend a pack safely.
• Development — the local loop, versioning, and the release process.

Development

uv sync --all-extras --dev
uv run ruff check .
uv run ty check src/
uv run pytest -q

Enable the uv.lock sync hook once per clone:

git config core.hooksPath .githooks

Contribution and labelling rules are in .github/CONTRIBUTING.md.