Phenostore — Beta
Managed healthcare data storage, built for application workloads.
Phenostore is a managed datastore for applications working with healthcare data. Store JSON resources, retrieve and search them through a practical subset of the FHIR R4 API, and build with Go and Python SDKs that handle authentication for you.
Phenostore is designed for low-latency reads and writes, flexible data ingestion, and straightforward integration. It is a fit for teams that need a managed home for FHIR-shaped data without operating their own FHIR server.
Request beta access · Read the quickstart · Go and Python SDKs
Principles
- Application performance. Designed around operational reads, writes, and indexed searches.
- JSON throughout. Work with JSON resource documents. The Python SDK uses dictionaries and the Go SDK uses
json.RawMessagefor resource bodies, so applications can choose their own resource models. - Configurable validation. Choose whether supported validation checks are skipped, reported as warnings, or enforced on writes. Validation can be configured by resource type; a request can ask for stricter checking.
- Tenant isolation. Data access is scoped to the authenticated tenant and authorized stores and operations.
- Practical FHIR compatibility. Use familiar FHIR R4 patterns while checking the supported capabilities for your workload.
What you can do
Create, read, update, and delete supported resource types; search resources; retrieve version history; and submit transaction or batch bundles. Use the REST API directly or the Go and Python SDKs for common operations.
Compatibility and scope
Phenostore targets FHIR R4 and implements a selected set of capabilities. It is not a fully conformant FHIR server. Validation covers supported structural and terminology checks; it does not provide arbitrary FHIR profile validation. References between resources are not checked for existence.
Use the authenticated /metadata endpoint under your store's FHIR base URL to
inspect supported resource types, interactions, and search parameters. Check
specific integration requirements with us during beta onboarding.
Request beta access
Email hello@phenoml.com with the subject Phenostore beta access. Tell us what you are building, which resource types and operations you need, and your expected data volume and request patterns. We will discuss fit and the onboarding steps.
To make API requests, you will need your Phenostore API URL, tenant ID, store ID, client ID, and client secret. Use the values supplied during onboarding in the REST quickstart and Go and Python SDK examples.