xCures API
Product · API / developer platform by xCures
Build with clinical clarity using source-linked, FHIR-compliant data.
A RESTful developer platform for accessing structured, source-linked clinical data. It enables healthcare technology teams to integrate FHIR R4-compliant patient histories and AI-ready clinical extractions directly into their own applications and workflows.
- Languages
- English
Category: Electronic Health Records
- APIs and SDKs
- RESTful API with FHIR R4 support
- Platforms
- API
- Deployment
- Cloud (AWS)
- Integrations
- EHRs, HIEs, QHINs, and TEFCA networks
- Interface Type
- RESTful API
- Data Standard
- FHIR R4
- RESTful interface for source-linked clinical data
- Standardized FHIR R4 and OMOP data outputs
- Full traceability to source document, page, and paragraph
Overview
The xCures API is a developer platform that provides programmatic access to the xCures Clinical Clarity Engine for healthcare organizations and technology partners. It delivers normalized, source-linked clinical data through a RESTful interface, enabling developers to embed verifiable patient information directly into their own applications. The API supports industry standards by mapping data to FHIR R4 resources and OHDSI-normalized concepts. Every data element retrieved through the API maintains full traceability, linking back to the specific source document, page, and paragraph. Beyond standard data retrieval, the platform provides specialized documentation and tooling for integrating AI agents safely into clinical workflows.
Core API Capabilities
- RESTful Interface: The API provides a RESTful interface for accessing normalized, source-linked clinical data from the xCures platform.
- FHIR R4 Mapping: Extracted clinical data is mapped to FHIR R4 resources to ensure downstream interoperability with modern healthcare systems.
- Source Traceability: Every data element includes provenance metadata and citations that link back to the exact source document, page, and paragraph.
- Management Tooling: The platform includes built-in tools for managing patients, medical records, and structured clinical data.
AI Agent Integration
- Agent Skills and Logic: Developers can provide AI agents with specific call orders, retries, and status codes to ensure safe and reliable API usage.
- Skill Configuration: AI agents can be configured with specific skills to interact with protected endpoints and handle complex data retrieval tasks.
- Status Code Handling: The documentation provides guidance on how agents should interpret and act upon various API status codes and error responses.
Developer Experience
- Secure Authentication: The API uses API keys and bearer tokens to secure access to protected clinical data endpoints.
- Project-Based Routing: Requests require a ProjectId header to route calls to the correct organizational environment and data silo.
- Comprehensive Documentation: The API Hub provides full request and response models, error definitions, and status codes for all available endpoints.
Use cases
- Healthcare technology companies embed source-linked clinical data into their own platforms via API to solve unstructured data problems.
- Developers build new healthcare products on top of the xCures data layer using normalized FHIR R4 resources.
- AI engineering teams give agents the skills and status codes needed to safely interact with clinical data for automated workflows.
- Data teams retrieve longitudinal patient records with 100% source provenance for use in internal analytics and research systems.
Specifications
- APIs and SDKs
- RESTful API with FHIR R4 support
- Platforms
- API
- Deployment
- Cloud (AWS)
- Integrations
- EHRs, HIEs, QHINs, and TEFCA networks
- Interface Type
- RESTful API
- Data Standard
- FHIR R4
- Vocabulary Standards
- SNOMED, LOINC, RxNorm
- Authentication Type
- API Keys and Bearer Tokens
- Required Headers
- ProjectId
- Infrastructure Platform
- Amazon Web Services (AWS)
How it works
- Authentication Setup: Developers set up API keys, bearer tokens, and the required ProjectId header to access protected endpoints.
- API Integration: Integrate the RESTful API into existing systems or new products to retrieve structured clinical data.
- AI Agent Configuration: Configure AI agents with specific skills, retry logic, and status code handling for safe data operations.
FAQ
What data standards does the API support?
The API maps extracted clinical data to FHIR R4 resources and normalizes concepts to OHDSI Standardized Vocabularies like SNOMED, LOINC, and RxNorm.
Can I use the xCures API with AI agents?
Yes, the API Hub includes specific documentation for giving AI agents the call order, retries, and skills they need to use the API safely.
How do I authenticate with the xCures API?
Authentication is handled through API keys and bearer tokens, and developers must include a ProjectId header in their requests.
Added by AntSpace from public sources (docs.xcures.com).