Core logic for working with FHIR data.
Most users will not use this directly, but may use google.fhir.views or
other higher-level libraries for working with FHIR data at scale.
1 maintainer
Metadata
1 maintainer
Release files for google-fhir-core 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| google_fhir_core-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / google_fhir_core-0.11.0-py3-none-any.whl
| Download URL | google_fhir_core-0.11.0-py3-none-any.whl |
|---|---|
| Size | 304.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e09581efa9fa0b92985098f1a69c9ef3b2ecf889f4d16386398d13556114102
|
|
BLAKE2b-256 checksum How to use checksums |
3226c3c9b2e2eb8e836f74fe0cc8a6e8863d55018b3ac6162885e0dbb62166d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for google-fhir-core 0.11.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
