suMEDS
suMEDS (pronounced "summed-s", past tense of "sum" + s) creates a compact code catalog for performing tasks
Medical Event Data Standard (MEDS)
datasets. MEDS data should be "summed" in this way in a storage-efficient format, without the need to access the full dataset.
It can be seen as a form of "extended metadata," as we sometimes need more information than vanilla MEDS metadata provides, but don't want to expose our complete dataset (either because of privacy concerns, storage capacity, or token use efficiency for LLMs). It (currently) simply joins canonical descriptions and parent codes to the event and the unique-subject counts, then masks or removes rare codes before writing Parquet, CSV, or JSON.
Polars scans, aggregations, joins, and writes stay lazy. This should mean that it could run with little resources on large MEDS datasets.
Install and run
Normal install:
pip install sumeds
Development
uv sync
uv run suMEDS tests/resources/MIMICIV_DEMO/MEDS_cohort \
--output code-summary.parquet \
--min-subjects 20 \
--split-columns
Or use YAML:
summary:
per_split: false
split_columns: true
privacy:
min_subjects: 20
min_split_subjects: 1
rare_code_action: bucket
rare_code_label: __RARE__
round_counts_to: 5
uv run suMEDS /path/to/MEDS -o summary.parquet -c examples/summary.yaml
# The suffix selects CSV or JSON instead:
uv run suMEDS /path/to/MEDS -o summary.json -c examples/summary.yaml
CLI flags override YAML. The defaults bucket codes seen in fewer than 20 unique subjects and retain exact counts.
Python API
from sumeds import SummaryConfig, summarize
path = summarize(
"/path/to/MEDS",
"code-summary.parquet",
SummaryConfig(min_subjects=20, rare_code_action="bucket"),
)
The output format is inferred from .parquet, .csv, or .json (with
.jsonl/.ndjson also supported). It preserves all code-metadata extension columns and adds
event_count, subject_count, and is_masked. per_split=True emits one row
per split. split_columns=True keeps the total row and adds columns such as
event_count_train and subject_count_train from subject_splits.parquet.
Set min_split_subjects above 1 to suppress rare split-level cells.
Documentation
uv run mkdocs serve
uv run mkdocs build --strict
See the documentation site for the data flow, complete CLI and YAML reference, output schema, Python API, and privacy limitations.
Development
uv run pre-commit run --all-files
uv run pytest
uv run mkdocs build --strict
The included integration test uses tests/resources/MIMICIV_DEMO/MEDS_cohort when present.
Metadata
Release files for sumeds 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sumeds-0.1.3.tar.gz | 10.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sumeds-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.0 kB
Release files / sumeds-0.1.3.tar.gz
| Download URL | sumeds-0.1.3.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35234caefe48d56eac26c02a0c4dffe4c152990cf859ba4a715c8cbe4c8b0884
|
|
BLAKE2b-256 checksum How to use checksums |
c60a8343131761c1f26fc0d5a43555d97b012a82cfb1e58970d25e96edbccd96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jul 23, 2026.
Transparency logRelease files / sumeds-0.1.3-py3-none-any.whl
| Download URL | sumeds-0.1.3-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbae7e5fb51873f6126cbfd11ea4fa57fbb28080744b5b6f46ee7dc9cda0b43c
|
|
BLAKE2b-256 checksum How to use checksums |
f48335232f6d0aee5627425c42a99e29d9efbacf5d4d52be46cc34cacff8467b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jul 23, 2026.
Transparency logSecurity for sumeds 0.1.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sumeds-0.1.3.tar.gz
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 Jul 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.