PocketHealth website screenshot

PocketHealth

PocketHealth is a patient-centric medical imaging platform that lets patients access, view, store, and share their diagnostic imaging (DICOM) and reports online, and lets healthcare providers exchange imaging across institutions and networks. PocketHealth also publishes an open, RESTful developer API aimed at RIS/PACS/VNA vendors, letting them embed PocketHealth's patient enrollment, electronic consent, and background record-delivery workflows natively into their own clinical software. The developer API is partner-gated - it is free forever for RIS/PACS vendors, healthcare providers, and physicians, but the full technical reference (base URL, endpoint paths, authentication) is not published on the open web; engaged vendors are assigned a dedicated integration rep who provides testing resources and detailed documentation. As a result the APIs below are modeled from PocketHealth's public developer-program descriptions rather than a public API reference or OpenAPI definition.

PocketHealth publishes 4 APIs on the APIs.io network. Tagged areas include Medical Imaging, Healthcare, DICOM, Image Exchange, and RIS.

PocketHealth’s developer surface includes documentation and 4 more developer resources.

13.0/100 emerging ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
AccessFreemium
4 APIs
Medical ImagingHealthcareDICOMImage ExchangeRISPACSInteroperabilityPatient AccessHealth IT

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/pockethealth: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

PocketHealth Patient Enrollment API

Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Lets a RIS/PACS/VNA vendor enroll patients for PocketHealth access natively...

PocketHealth Electronic Consent API

Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Captures and manages electronic patient consent for sharing diagnostic imag...

PocketHealth Record Delivery API

Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Automates secure background delivery of DICOM imaging studies and associate...

PocketHealth Image Exchange API

Partner-gated capability, modeled from PocketHealth's public Image Exchange product description. Supports provider-to-provider imaging exchange across external hospitals and out...

Pricing Plans 1

Published pricing tiers and plan structures.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Pockethealth Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: pockethealth
url: https://raw.githubusercontent.com/api-evangelist/pockethealth/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
name: PocketHealth
kind: company
description: PocketHealth is a patient-centric medical imaging platform that lets patients access, view, store, and share
  their diagnostic imaging (DICOM) and reports online, and lets healthcare providers exchange imaging across institutions
  and networks. PocketHealth also publishes an open, RESTful developer API aimed at RIS/PACS/VNA vendors, letting them embed
  PocketHealth's patient enrollment, electronic consent, and background record-delivery workflows natively into their own
  clinical software. The developer API is partner-gated - it is free forever for RIS/PACS vendors, healthcare providers, and
  physicians, but the full technical reference (base URL, endpoint paths, authentication) is not published on the open web;
  engaged vendors are assigned a dedicated integration rep who provides testing resources and detailed documentation. As a
  result the APIs below are modeled from PocketHealth's public developer-program descriptions rather than a public API reference
  or OpenAPI definition.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/pockethealth.png
tags:
- Medical Imaging
- Healthcare
- DICOM
- Image Exchange
- RIS
- PACS
- Interoperability
- Patient Access
- Health IT
created: '2026-07-05'
modified: '2026-07-05'
specificationVersion: '0.23'
apis:
- aid: pockethealth:pockethealth-patient-enrollment-api
  name: PocketHealth Patient Enrollment API
  tags:
  - Patients
  - Enrollment
  - Onboarding
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.pockethealth.com/developers/
  properties:
  - url: https://www.pockethealth.com/developers/
    type: Documentation
  description: Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Lets
    a RIS/PACS/VNA vendor enroll patients for PocketHealth access natively from within the vendor's own clinical software,
    with no change to the end-user clinical workflow. Endpoint paths, base URL, and authentication are not published publicly
    and are provided to engaged vendors by a dedicated integration rep. Endpoints are modeled, not confirmed.
- aid: pockethealth:pockethealth-consent-api
  name: PocketHealth Electronic Consent API
  tags:
  - Consent
  - Compliance
  - Privacy
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.pockethealth.com/developers/
  properties:
  - url: https://www.pockethealth.com/developers/
    type: Documentation
  description: Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Captures
    and manages electronic patient consent for sharing diagnostic imaging and reports, so that release-of-records workflows
    can run automatically and securely. Endpoint paths, base URL, and authentication are not published publicly. Endpoints
    are modeled, not confirmed.
- aid: pockethealth:pockethealth-record-delivery-api
  name: PocketHealth Record Delivery API
  tags:
  - Imaging
  - DICOM
  - Reports
  - Delivery
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.pockethealth.com/developers/
  properties:
  - url: https://www.pockethealth.com/developers/
    type: Documentation
  description: Partner-gated developer capability, modeled from PocketHealth's public developer-program description. Automates
    secure background delivery of DICOM imaging studies and associated reports from any DICOM-compliant RIS, PACS, or VNA
    system to a patient's PocketHealth account, without requiring UI or workflow changes. Endpoint paths, base URL, and authentication
    are not published publicly. Endpoints are modeled, not confirmed.
- aid: pockethealth:pockethealth-image-exchange-api
  name: PocketHealth Image Exchange API
  tags:
  - Image Exchange
  - Interoperability
  - Sharing
  - Providers
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://www.pockethealth.com/providers/pockethealth-image-exchange/
  properties:
  - url: https://www.pockethealth.com/providers/pockethealth-image-exchange/
    type: Documentation
  description: Partner-gated capability, modeled from PocketHealth's public Image Exchange product description. Supports provider-to-provider
    imaging exchange across external hospitals and out-of-province networks, with an automated ingestion engine (patient matching,
    order creation, tag morphing) that centralizes inbound and outbound imaging workflows. No public API reference is published
    for this surface. Endpoints are modeled, not confirmed.
common:
- type: DomainSecurity
  url: security/pockethealth-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/pockethealth
- type: Website
  url: https://www.pockethealth.com
- type: Documentation
  url: https://www.pockethealth.com/developers/
- type: Plans
  url: plans/pockethealth-plans-pricing.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/pockethealth"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/pockethealth/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/pockethealth/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.