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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago