sqllocks-shape-healthcare-codes
Shape plugin: healthcare reference code sets, validators and detectors. It is the code layer under a domain pack: the domain asks it for codes that are real, valid on the date of service, and licensed for the way they are used.
- Code sets: ICD-10-CM, ICD-10-PCS, HCPCS Level II, FDA NDC, RxNorm (prescribable), CMS place
of service, CMS-HCC mappings, AHRQ CCSR, and the international ICD-10 family, all behind one
code model (
CodeSet). Free sets are built from the official source at a pinned release withshape healthcare-codes fetch; licensed sets (CPT, SNOMED CT, UB-04 revenue codes and type of bill, NUCC taxonomy, CARC/RARC, WHO ICD-10, ICD-10-GM, ICD-10-AM) are bring-your-own: you supply the file, a loader reads it, and nothing licensed is shipped. - Risk adjustment: the hierarchies and coefficients of the CMS-HCC, ESRD and RxHCC models
(
hcc_hierarchy,hcc_coefficients, built from the CMS model software), and a reference scoring function (risk_score) for testing generated data; not a certified implementation. - Validators: ICD-10-CM valid and billable on a date of service, NDC valid and marketed on a fill date, NPI check digit with a synthetic never-assigned range, age and sex edits.
- Detectors (
shape.detectors): ICD-10, NDC, NPI, HCPCS, CPT, Medicare MBI and member-id columns. - Wheel size: the wheel is about 0.7 MB (a 0.6 MB starter subset of ICD-10-CM and the code).
The full sets are built on your machine with
shape healthcare-codes fetch.
THIRD_PARTY_NOTICES.md records, for every asset, the source URL, release, licence (quoted from
the source's own page, with the date it was read), and whether it is shipped, fetched or
bring-your-own. the implementation tests records the checks.
import datetime as dt
from shape_healthcare_codes import load, icd10cm_valid_billable
icd = load("icd10cm") # after `shape healthcare-codes fetch icd10cm`
icd10cm_valid_billable(icd, "E11.9", dt.date(2026, 10, 2)) # True
icd10cm_valid_billable(icd, "E11", dt.date(2026, 10, 2)) # False: a header, not billable
The domain-facing API is documented in docs/plugins/healthcare-codes.md.
Metadata
Release files for sqllocks-shape-healthcare-codes 0.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sqllocks_shape_healthcare_codes-0.9.1.tar.gz | 696.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sqllocks_shape_healthcare_codes-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / sqllocks_shape_healthcare_codes-0.9.1.tar.gz
| Download URL | sqllocks_shape_healthcare_codes-0.9.1.tar.gz |
|---|---|
| Size | 696.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7f55f7b0b9348f204ff81bf8b9972353aacf26bc31bba5e4cd36c9848867378
|
|
BLAKE2b-256 checksum How to use checksums |
7add2eb9904c489591edf21eb12413b9a2be7c7abfef3389766de788352d82ed
|
| 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 logRelease files / sqllocks_shape_healthcare_codes-0.9.1-py3-none-any.whl
| Download URL | sqllocks_shape_healthcare_codes-0.9.1-py3-none-any.whl |
|---|---|
| Size | 690.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38f63147e0c2e05131ad386eb86eb8548ddbe4aceaf28b876e38bf3f6ef3598a
|
|
BLAKE2b-256 checksum How to use checksums |
1bc668c0ecebe798bc36db686285df66568d5ded5a04fa1d434ea38c8ec1f91d
|
| 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