Hana Compass API

Created By
mhaihqa year ago
API and MCP server for all EHR integration,Med Research via a single unified API
Overview

what is Hana Compass API?

Hana Compass API is a unified API and MCP server designed for seamless integration of Electronic Health Records (EHR) and medical research.

how to use Hana Compass API?

To use Hana Compass API, developers can integrate it into their applications by following the documentation provided on the GitHub repository. This includes setting up authentication and making API calls to access EHR data and research functionalities.

key features of Hana Compass API?

  • Unified API for EHR integration and medical research
  • Supports various data formats for easy integration
  • Comprehensive documentation for developers

use cases of Hana Compass API?

  1. Integrating EHR data into healthcare applications.
  2. Facilitating medical research by providing access to patient data.
  3. Enabling interoperability between different healthcare systems.

FAQ from Hana Compass API?

  • What is EHR integration?

EHR integration refers to the process of connecting different electronic health record systems to allow for seamless data exchange.

  • Is there a cost to use Hana Compass API?

The API is open-source and free to use under the BSD-3-Clause license.

  • How can I contribute to the Hana Compass API?

Contributions can be made by submitting pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mhaihq
Star
5
Language
-
License
BSD-3-Clause license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

12 hours ago
Voyei

an hour ago