AccessHealthData API Documentation
Everything you need to fetch, normalize, and use nationwide patient medical data.
A simple, modern API for retrieving normalized FHIR JSON from clinical networks. Designed for developers who want to integrate healthcare data without fighting HL7, C-CDA, or TEFCA complexity.
Overview
The AccessHealthData API provides programmatic access to nationwide clinical data, normalized to clean and consistent FHIR R4 JSON. Fetch longitudinal medical histories, retrieve updates, process documents, and store normalized records—all through a secure REST API.
Built for developers. HIPAA-ready. Clear pricing. No sales calls.
What You Can Do With the API
Fetch a complete medical history from nationwide networks in a single API call.
Convert HL7 v2, C-CDA, PDFs, and free text into validated FHIR R4.
Maintain longitudinal FHIR JSON with storage billed by GB.
Access specific resource types: Conditions, Medications, Labs, Encounters, etc.
Receive notifications when new clinical data becomes available for a patient.
Use mock/synthetic data with unlimited calls—no PHI, no BAA required.
Quickstart Code Examples
Fetch a Patient's Full Medical History
GET /v1/patients/{patient_id}/historySubmit a PDF for Normalization
POST /v1/normalize/pdfRetrieve FHIR Resources
GET /v1/fhir/{resourceType}?patient={patient_id}Subscribe to Webhooks
POST /v1/webhooksEach endpoint includes request/response examples, schema definitions, and sample cURL, Python, JavaScript, and Go code.
Authentication
Authentication is performed using scoped API keys. Keys can be created, revoked, and rotated via the dashboard.
- Auth Method: Bearer token
- Key Types: Production (PHI) and Sandbox (synthetic data)
Protect your keys as you would any credential.
Rate Limits
We enforce fair-use rate limits per account and per key. Limits scale automatically with tier and usage volume.
Rate limits are designed to be generous and non-blocking for typical data workflows. You can request higher limits via the dashboard.
Data Models
FHIR R4 Normalized Schema
All normalized output follows FHIR R4 resource definitions with AccessHealthData extensions for:
- Provenance
- Source metadata
- Normalization confidence
- OCR confidence (for PDFs)
- Validation results
Raw Clinical Documents (optional)
You may optionally request raw C-CDA, HL7, or PDF artifacts for audit or downstream processing.
Environments
Synthetic data
Unlimited calls
Free for all users
Real clinical exchange
Requires BAA
Standard rate limits
Usage-based pricing
Error Handling
All endpoints return structured error responses with:
- HTTP status code
- Error type
- Developer message
- Remediation guidance
- Correlation ID for support
Webhooks
Use webhooks to receive:
- New clinical documents available
- Updated patient summaries
- Failed normalization events
- Storage threshold alerts
- Data export completion
Your webhook endpoints must support TLS and respond with 2xx status codes.
Examples & SDKs
We provide examples in:
- cURLPythonJavaScript/TypeScriptGo
SDKs for Python, Node.js, and Go are in active development.
API Versioning
We maintain stable versioning with backwards-compatible updates. Breaking changes are communicated via dashboard and email notifications.
Current API Version: v1
Next Stable Release: v1.1 (Q4)
Support
- Paid tiers include email support.
- Scale tier includes Slack channel access.
- Enterprise accounts include dedicated support engineering.
Support contact: devsupport@accesshealthdata.com