Skip to main content

groundworkers

Groundworkers is the reusable, read-only capability layer for OMOP vocabulary lookup, concept mapping, source planning, and related analysis. It combines deterministic services with optional embeddings and model-assisted operations.

It does not own patient-level writes, session state, or job lifecycle. Those concerns belong to the calling application; groundcrew is the usual stateful orchestrator.

Choose an interface

Interface Use it when
MCP An agent needs discoverable tools, prompts, resources, and a shared remote runtime.
REST An application needs the curated HTTP workflows for candidate bundles or assisted source planning.
Python A process owns batching, evaluation, or orchestration and can run in-process.

Start with the documentation home, or choose a path directly:

Quick start

Install the package and configure the shared OMOP stack:

pip install groundworkers
omop-config configure groundworkers

Inspect the active configuration and MCP surface before starting a service:

groundworkers --describe

Run MCP over stdio for a client that starts the process, or over Streamable HTTP for a shared service:

groundworkers
groundworkers --transport streamable-http --host 127.0.0.1 --port 8000

REST is a separate, curated interface:

groundworkers --transport rest --host 127.0.0.1 --port 8080

Direct Python

Build the application once and reuse it. Services are optional when their prerequisites are not configured:

from groundworkers.app import build_application
from groundworkers.bootstrap import build_app_config

config = build_app_config()
app = build_application(config)

bundle = app.services.mapping.concept_candidate_bundle(
    "type 2 diabetes",
    domain="Condition",
)

The mapping service in this example requires a configured CDM database. Embedding-backed channels require an embedding model and vector store; text, domain classification, and assisted source planning require a configured chat model. Use groundworkers --describe to see what the current deployment exposes.

Companion repositories

  • groundcrew owns session state and orchestration.
  • omop-graph provides graph-backed OMOP traversal.
  • omop-emb provides embedding stores and indexes.

Metadata

Release files for groundworkers 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for groundworkers 0.6.0
File Size Uploaded
groundworkers-0.6.0.tar.gz 1.3 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for groundworkers 0.6.0
File Interpreter ABI Platform
groundworkers-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.6 MB

Release files / groundworkers-0.6.0.tar.gz

Download URL groundworkers-0.6.0.tar.gz
Size 1.3 MB
Tags Source
SHA-256 checksum
How to use checksums
2d73cdc12c14245c9c3b2791d6ac60c6b5cec6beb21c046193f42b4a2ff5dd67
BLAKE2b-256 checksum
How to use checksums
30112e6d2ea41011c364ce6d2bceefe35ac6f5d792fd9d0cc4da61699f344494
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / groundworkers-0.6.0-py3-none-any.whl

Download URL groundworkers-0.6.0-py3-none-any.whl
Size 346.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b8b4ec66c28d97e1be8030580a8d8c862c06706bf46642400ff58de1fd727b7d
BLAKE2b-256 checksum
How to use checksums
ca1f9c70c4136a495d53f45752448792f72c110b976d1336e867cefac2e27abb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.0 This release

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page