Skip to content

Tags: OMOPHub/omophub-mcp

Tags

v1.5.2

Toggle v1.5.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
v1.5.2 prep (#14)

* chore: release version 1.4.0 with new FHIR tools and improvements

- Added three new tools for FHIR-to-OMOP concept resolution: `fhir_resolve`, `fhir_resolve_batch`, and `fhir_resolve_codeable_concept`.
- Comprehensive test suite for FHIR tools and client resolution
- Fixed non-null assertions in HTTP transport and updated bracket notation for header access.
- Updated tool count from 9 to 12 in server initialization.

* fix: enhance error handling in HTTP transport tests

- Updated error handling in HTTP transport tests to assert specific error types and messages when a socket error occurs during uploads, improving test reliability and clarity.

* chore: remove `fhir_resolve_batch` tool and update documentation

- Removed the `fhir_resolve_batch` tool from the FHIR-to-OMOP concept resolver, reducing the tool count from 12 to 11.
- Updated the CHANGELOG and README to reflect the removal of the batch resolution functionality.
- Adjusted server initialization logs and tests to align with the updated tool count.

* fix: update documentation for `get_concept_by_code` tool

- Revised the description of the `get_concept_by_code` tool to improve clarity and consistency in the documentation, ensuring proper understanding of the parameters and their significance.

* chore: update package-lock.json for version 1.4.0

- Bumped package version from 1.3.0 to 1.4.0.
- Updated dependencies, including @babel/parser and @biomejs/cli packages to version 2.4.15.
- Ensured all package resolutions and integrity checks are current.

* fix: enforce validation for FHIR coding entries

- Updated the FHIR tools to require non-empty and non-whitespace values for the `system` and `code` fields in coding entries.
- Added a test case to ensure that invalid coding entries are correctly rejected, enhancing input validation and error handling.

* chore: release version 1.5.0 with new features and improvements (#10)

* chore: update Cloud SDK setup action to version 3 in deployment workflow

* chore: add coverage reporting to CI workflow

- Integrated Vitest for running tests with coverage.
- Added step to upload coverage reports to Codecov using the provided token and slug.

* docs: add Codecov badge to README for coverage visibility

* fix: enhance FHIR tools response handling for unmapped concepts

- Updated the FHIR tools to present a concept_id 0 best match as "unmapped" instead of a successful match.
- Modified the response text to clarify when no OMOP standard concept is found.
- Added a test case to verify the new behavior for unmapped concepts.

* chore: release version 1.5.1 with updated semantic search API path

- Changed the `semantic_search` tool to use the new canonical API path `GET /v1/search/semantic`.
- Updated the changelog to reflect this change and ensure backward compatibility with the legacy path.

* chore: release version 1.5.2 with updated dependencies

- Bumped `vitest` and `@vitest/coverage-v8` devDependencies to version 4.1.8.
- Updated version in package.json and package-lock.json to 1.5.2.
- Added changelog entry for the new release.

* chore: adjust coverage thresholds in Vitest configuration

- Updated the statement coverage threshold from 93% to 90% to accommodate changes in Vitest 4's coverage measurement.
- Added comments explaining the rationale behind the new threshold and the largest gap in coverage.

---------

Co-authored-by: alex-omophub <sdk@omophub.com>

v1.5.1

Toggle v1.5.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
v1.5.1 prep (#13)

v1.5.0

Toggle v1.5.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
v.1.5.0 prep (#11)

v1.4.0

Toggle v1.4.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: release version 1.4.0 with new FHIR tools and improvements (#8)

* chore: release version 1.4.0 with new FHIR tools and improvements

- Added three new tools for FHIR-to-OMOP concept resolution: `fhir_resolve`, `fhir_resolve_batch`, and `fhir_resolve_codeable_concept`.
- Comprehensive test suite for FHIR tools and client resolution
- Fixed non-null assertions in HTTP transport and updated bracket notation for header access.
- Updated tool count from 9 to 12 in server initialization.

* fix: enhance error handling in HTTP transport tests

- Updated error handling in HTTP transport tests to assert specific error types and messages when a socket error occurs during uploads, improving test reliability and clarity.

* chore: remove `fhir_resolve_batch` tool and update documentation

- Removed the `fhir_resolve_batch` tool from the FHIR-to-OMOP concept resolver, reducing the tool count from 12 to 11.
- Updated the CHANGELOG and README to reflect the removal of the batch resolution functionality.
- Adjusted server initialization logs and tests to align with the updated tool count.

---------

Co-authored-by: alex-omophub <sdk@omophub.com>

v1.3.1

Toggle v1.3.1's commit message
chore: release version 1.3.1 with bug fixes and improvements

v1.3.0

Toggle v1.3.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: release version 1.3.0 with new features and fixes (#6)

* chore: release version 1.3.0 with new features and fixes

- Introduced per-client API key resolution via `Authorization: Bearer` header for hosted deployments.
- Added Cloud Run deployment workflow and root endpoint support for cleaner hosted URLs.
- Enhanced CORS support for cross-origin Bearer token requests.
- Fixed `list_vocabularies` to fetch all pages and corrected `map_concept` response handling.
- Updated version numbers in Dockerfile, package.json, server.json, and README to reflect the new release.
- Improved tools to resolve client per-request for multi-client hosted mode.

* refactor: improve API key handling and server creation

- Updated `resolveApiKey` to return undefined instead of throwing an error when no key is provided, supporting hosted mode.
- Modified `createServer` function to accept an optional API key.
- Enhanced `OmopHubClient` constructor to handle undefined API keys gracefully.
- Adjusted deployment workflow to remove unnecessary environment variable for API key.
- Improved error logging for missing API keys in stdio mode.

* style: format log message for clarity

- Reformatted the log message for missing API key in hosted mode to improve readability by adding line breaks.

---------

Co-authored-by: alex-omophub <sdk@omophub.com>

v1.2.2

Toggle v1.2.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #5 from OMOPHub/links-update

chore: release version 1.2.2 with updated dashboard links and test as…

v1.2.1

Toggle v1.2.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #4 from OMOPHub/links-update

chore: release version 1.2.1 with updated API key links and version n…

v1.2.0

Toggle v1.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #3 from OMOPHub/composit-tools

chore: release version 1.2.0 with new features and fixes

v1.1.0

Toggle v1.1.0's commit message
chore: update .gitignore and CHANGELOG for version 1.1.0 release

- Added new tokens to .gitignore to prevent sensitive information from being tracked.
- Updated CHANGELOG to reflect the addition of streamable HTTP transport, health check endpoint, and scoped npm package name change to @omophub/omophub-mcp.
- Modified README to update package references and usage instructions for the new package name.