Amazon HealthLake
Amazon HealthLake is a HIPAA-eligible service that gives healthcare providers, health insurance companies, and pharmaceutical companies the ability to store, transform, query, and analyze health data at scale in the cloud. It uses the Fast Healthcare Interoperability Resources (FHIR) standard.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon HealthLake the way a machine reads it — 234 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon HealthLake scores 71.6/100 (exemplar), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon HealthLake
Each block below is one kind of artifact we hold for Amazon HealthLake. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon HealthLake #X Amz Target=HealthLake.CreateFHIRDatastore API
The #X Amz Target=HealthLake.CreateFHIRDatastore API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.createfhirdatastore.
Amazon HealthLake #X Amz Target=HealthLake.DeleteFHIRDatastore API
The #X Amz Target=HealthLake.DeleteFHIRDatastore API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.deletefhirdatastore.
Amazon HealthLake #X Amz Target=HealthLake.DescribeFHIRDatastore API
The #X Amz Target=HealthLake.DescribeFHIRDatastore API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.describefhirdatastore.
Amazon HealthLake #X Amz Target=HealthLake.DescribeFHIRExportJob API
The #X Amz Target=HealthLake.DescribeFHIRExportJob API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.describefhirexportjob.
Amazon HealthLake #X Amz Target=HealthLake.DescribeFHIRImportJob API
The #X Amz Target=HealthLake.DescribeFHIRImportJob API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.describefhirimportjob.
Amazon HealthLake #X Amz Target=HealthLake.ListFHIRDatastores API
The #X Amz Target=HealthLake.ListFHIRDatastores API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.listfhirdatastores.
Amazon HealthLake #X Amz Target=HealthLake.ListFHIRExportJobs API
The #X Amz Target=HealthLake.ListFHIRExportJobs API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.listfhirexportjobs.
Amazon HealthLake #X Amz Target=HealthLake.ListFHIRImportJobs API
The #X Amz Target=HealthLake.ListFHIRImportJobs API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.listfhirimportjobs.
Amazon HealthLake #X Amz Target=HealthLake.ListTagsForResource API
The #X Amz Target=HealthLake.ListTagsForResource API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.listtagsforresource.
Amazon HealthLake #X Amz Target=HealthLake.StartFHIRExportJob API
The #X Amz Target=HealthLake.StartFHIRExportJob API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.startfhirexportjob.
Amazon HealthLake #X Amz Target=HealthLake.StartFHIRImportJob API
The #X Amz Target=HealthLake.StartFHIRImportJob API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.startfhirimportjob.
Amazon HealthLake #X Amz Target=HealthLake.TagResource API
The #X Amz Target=HealthLake.TagResource API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.tagresource.
Amazon HealthLake #X Amz Target=HealthLake.UntagResource API
The #X Amz Target=HealthLake.UntagResource API from Amazon HealthLake — 1 operation(s) for #x amz target=healthlake.untagresource.
Scroll within the panel for all 13 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Amazon HealthLake
POSTMANArazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Amazon HealthLake Create FHIR Data Store and Wait Until Active
Create a FHIR data store and poll its status until it becomes ACTIVE.
ARAZZOAmazon HealthLake Delete FHIR Data Store and Confirm Removal
Delete a FHIR data store and poll its status until it reports DELETED.
ARAZZOAmazon HealthLake Provision FHIR Data Store and Export Data
Create a FHIR data store, wait until ACTIVE, then export FHIR data and wait until COMPLETED.
ARAZZOAmazon HealthLake Provision FHIR Data Store and Import Data
Create a FHIR data store, wait until ACTIVE, then import FHIR data and wait until COMPLETED.
ARAZZOAmazon HealthLake Start FHIR Export Job, Poll, and List
Start a FHIR export job, poll it until COMPLETED, then list all export jobs.
ARAZZOAmazon HealthLake Start FHIR Import Job and Wait Until Completed
Start a FHIR import job and poll its status until it reaches COMPLETED.
ARAZZOAmazon HealthLake Start FHIR Import Job, Poll, and List
Start a FHIR import job, poll it until COMPLETED, then list all import jobs.
ARAZZOScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Healthlake Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Healthlake Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
FHIR Compliance
Fully compliant with the FHIR R4 standard for healthcare data interoperability.
HIPAA-Eligible
HIPAA-eligible service for storing and processing protected health information.
Integrated Data Import
Bulk import FHIR-formatted health data from Amazon S3 with automated validation.
Data Export
Export FHIR health data to Amazon S3 for analytics, archiving, or migration.
Integrated Search
Query FHIR resources using standard FHIR search operations for clinical workflows.
Automated De-identification
Built-in de-identification capabilities for removing PHI from health data.
Analytics Integration
Integrated analytics with Amazon Comprehend Medical and other AWS analytics services.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Healthlake Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon HealthLake API Rules
SPECTRALAmazon HealthLake API Rules
SPECTRALJSON Schema 76
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessDeniedException
JSON SCHEMAAmazonResourceName
JSON SCHEMAAuthorizationStrategy
JSON SCHEMABoolean
JSON SCHEMABoundedLengthString
JSON SCHEMAClientTokenString
JSON SCHEMACmkType
JSON SCHEMAConfigurationMetadata
JSON SCHEMAConflictException
JSON SCHEMACreateFHIRDatastoreRequest
JSON SCHEMACreateFHIRDatastoreResponse
JSON SCHEMADatastoreArn
JSON SCHEMADatastoreFilter
JSON SCHEMADatastoreId
JSON SCHEMADatastoreName
JSON SCHEMADatastorePropertiesList
JSON SCHEMADatastoreProperties
JSON SCHEMADatastoreStatus
JSON SCHEMADeleteFHIRDatastoreRequest
JSON SCHEMADeleteFHIRDatastoreResponse
JSON SCHEMADescribeFHIRDatastoreRequest
JSON SCHEMADescribeFHIRDatastoreResponse
JSON SCHEMADescribeFHIRExportJobRequest
JSON SCHEMADescribeFHIRExportJobResponse
JSON SCHEMADescribeFHIRImportJobRequest
JSON SCHEMADescribeFHIRImportJobResponse
JSON SCHEMAEncryptionKeyID
JSON SCHEMAExportJobPropertiesList
JSON SCHEMAExportJobProperties
JSON SCHEMAFHIRVersion
JSON SCHEMAIamRoleArn
JSON SCHEMAIdentityProviderConfiguration
JSON SCHEMAImportJobPropertiesList
JSON SCHEMAImportJobProperties
JSON SCHEMAInputDataConfig
JSON SCHEMAInternalServerException
JSON SCHEMAJobId
JSON SCHEMAJobName
JSON SCHEMAJobStatus
JSON SCHEMAKmsEncryptionConfig
JSON SCHEMALambdaArn
JSON SCHEMAListFHIRDatastoresRequest
JSON SCHEMAListFHIRDatastoresResponse
JSON SCHEMAListFHIRExportJobsRequest
JSON SCHEMAListFHIRExportJobsResponse
JSON SCHEMAListFHIRImportJobsRequest
JSON SCHEMAListFHIRImportJobsResponse
JSON SCHEMAListTagsForResourceRequest
JSON SCHEMAListTagsForResourceResponse
JSON SCHEMAMaxResultsInteger
JSON SCHEMAMessage
JSON SCHEMANextToken
JSON SCHEMAOutputDataConfig
JSON SCHEMAPreloadDataConfig
JSON SCHEMAPreloadDataType
JSON SCHEMAResourceNotFoundException
JSON SCHEMAS3Configuration
JSON SCHEMAS3Uri
JSON SCHEMASseConfiguration
JSON SCHEMAStartFHIRExportJobRequest
JSON SCHEMAStartFHIRExportJobResponse
JSON SCHEMAStartFHIRImportJobRequest
JSON SCHEMAStartFHIRImportJobResponse
JSON SCHEMAString
JSON SCHEMATagKeyList
JSON SCHEMATagKey
JSON SCHEMATagList
JSON SCHEMATagResourceRequest
JSON SCHEMATagResourceResponse
JSON SCHEMATag
JSON SCHEMATagValue
JSON SCHEMAThrottlingException
JSON SCHEMATimestamp
JSON SCHEMAUntagResourceRequest
JSON SCHEMAUntagResourceResponse
JSON SCHEMAValidationException
JSON SCHEMAScroll within the panel for all 76 ·
JSON Structure 76
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Healthlake Access Denied Exception Structure
JSON STRUCTUREHealthlake Amazon Resource Name Structure
JSON STRUCTUREHealthlake Authorization Strategy Structure
JSON STRUCTUREHealthlake Boolean Structure
JSON STRUCTUREHealthlake Bounded Length String Structure
JSON STRUCTUREHealthlake Client Token String Structure
JSON STRUCTUREHealthlake Cmk Type Structure
JSON STRUCTUREHealthlake Configuration Metadata Structure
JSON STRUCTUREHealthlake Conflict Exception Structure
JSON STRUCTUREHealthlake Create Fhir Datastore Request Structure
JSON STRUCTUREHealthlake Create Fhir Datastore Response Structure
JSON STRUCTUREHealthlake Datastore Arn Structure
JSON STRUCTUREHealthlake Datastore Filter Structure
JSON STRUCTUREHealthlake Datastore Id Structure
JSON STRUCTUREHealthlake Datastore Name Structure
JSON STRUCTUREHealthlake Datastore Properties List Structure
JSON STRUCTUREHealthlake Datastore Properties Structure
JSON STRUCTUREHealthlake Datastore Status Structure
JSON STRUCTUREHealthlake Delete Fhir Datastore Request Structure
JSON STRUCTUREHealthlake Delete Fhir Datastore Response Structure
JSON STRUCTUREHealthlake Describe Fhir Datastore Request Structure
JSON STRUCTUREHealthlake Describe Fhir Datastore Response Structure
JSON STRUCTUREHealthlake Describe Fhir Export Job Request Structure
JSON STRUCTUREHealthlake Describe Fhir Export Job Response Structure
JSON STRUCTUREHealthlake Describe Fhir Import Job Request Structure
JSON STRUCTUREHealthlake Describe Fhir Import Job Response Structure
JSON STRUCTUREHealthlake Encryption Key Id Structure
JSON STRUCTUREHealthlake Export Job Properties List Structure
JSON STRUCTUREHealthlake Export Job Properties Structure
JSON STRUCTUREHealthlake Fhir Version Structure
JSON STRUCTUREHealthlake Iam Role Arn Structure
JSON STRUCTUREHealthlake Identity Provider Configuration Structure
JSON STRUCTUREHealthlake Import Job Properties List Structure
JSON STRUCTUREHealthlake Import Job Properties Structure
JSON STRUCTUREHealthlake Input Data Config Structure
JSON STRUCTUREHealthlake Internal Server Exception Structure
JSON STRUCTUREHealthlake Job Id Structure
JSON STRUCTUREHealthlake Job Name Structure
JSON STRUCTUREHealthlake Job Status Structure
JSON STRUCTUREHealthlake Kms Encryption Config Structure
JSON STRUCTUREHealthlake Lambda Arn Structure
JSON STRUCTUREHealthlake List Fhir Datastores Request Structure
JSON STRUCTUREHealthlake List Fhir Datastores Response Structure
JSON STRUCTUREHealthlake List Fhir Export Jobs Request Structure
JSON STRUCTUREHealthlake List Fhir Export Jobs Response Structure
JSON STRUCTUREHealthlake List Fhir Import Jobs Request Structure
JSON STRUCTUREHealthlake List Fhir Import Jobs Response Structure
JSON STRUCTUREHealthlake List Tags For Resource Request Structure
JSON STRUCTUREHealthlake List Tags For Resource Response Structure
JSON STRUCTUREHealthlake Max Results Integer Structure
JSON STRUCTUREHealthlake Message Structure
JSON STRUCTUREHealthlake Next Token Structure
JSON STRUCTUREHealthlake Output Data Config Structure
JSON STRUCTUREHealthlake Preload Data Config Structure
JSON STRUCTUREHealthlake Preload Data Type Structure
JSON STRUCTUREHealthlake Resource Not Found Exception Structure
JSON STRUCTUREHealthlake S3 Configuration Structure
JSON STRUCTUREHealthlake S3 Uri Structure
JSON STRUCTUREHealthlake Sse Configuration Structure
JSON STRUCTUREHealthlake Start Fhir Export Job Request Structure
JSON STRUCTUREHealthlake Start Fhir Export Job Response Structure
JSON STRUCTUREHealthlake Start Fhir Import Job Request Structure
JSON STRUCTUREHealthlake Start Fhir Import Job Response Structure
JSON STRUCTUREHealthlake String Structure
JSON STRUCTUREHealthlake Tag Key List Structure
JSON STRUCTUREHealthlake Tag Key Structure
JSON STRUCTUREHealthlake Tag List Structure
JSON STRUCTUREHealthlake Tag Resource Request Structure
JSON STRUCTUREHealthlake Tag Resource Response Structure
JSON STRUCTUREHealthlake Tag Structure
JSON STRUCTUREHealthlake Tag Value Structure
JSON STRUCTUREHealthlake Throttling Exception Structure
JSON STRUCTUREHealthlake Timestamp Structure
JSON STRUCTUREHealthlake Untag Resource Request Structure
JSON STRUCTUREHealthlake Untag Resource Response Structure
JSON STRUCTUREHealthlake Validation Exception Structure
JSON STRUCTUREScroll within the panel for all 76 ·
Examples 38
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Healthlake Tag Example
EXAMPLEScroll within the panel for all 38 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Clinical Data Repository
Create a centralized FHIR-compliant repository for clinical data from multiple sources.
Health Data Exchange
Enable interoperable health data exchange between healthcare providers and payers.
Population Health Management
Analyze aggregated health data to identify trends and manage population health programs.
AI-Powered Clinical Insights
Apply machine learning to FHIR data to generate clinical insights and predictions.
Research Data Platform
Create de-identified research datasets from FHIR health records for clinical studies.
Resources
Every other property we hold for Amazon HealthLake — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-healthlake · machine-readable index on apis.io