Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Healthcare / PatientView
PatientView logo

PatientView

69
AI ReadinessAI-Aware (B+)69/100
See full scorecard
Community OpenAPI document · agent-readyHealthcareEhr Emrnone15 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read a PatientView user's basic details, available observation types, and observations, and read or save patient management diagnoses and surgeries. Authenticates through a login operation that returns a session token; the spec declares no separate security scheme.

Use for: Log in and read a patient's basic details, List the observation types available for a user, Get a user's observations for a given type, Read the patient-entered observations for a user

Not supported: Does not handle appointment booking, messaging, or account registration. Use for reading PatientView user details, observations, and patient management records only.

The PatientView API reads patient health records for the PatientView renal patient portal, so an application can retrieve a patient's basic details and their clinical observations. You log in to obtain a session token, then read a user's basic information, the observation types available for them, and their observations, including patient-entered readings. Patient management endpoints read and save diagnoses, lookup types, and surgeries for a user within a group. The API is organised around a user id that identifies whose records are being read.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the PatientView to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PatientView, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpatientview.org%2Fpatientview" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpatientview.org%2Fpatientview" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PatientView API.

Log in to obtain a session token and log out to end it

Read a patient's basic details

List the observation types available for a user

Read a user's observations, including patient-entered readings

Read patient management diagnoses and lookup types

Save patient management records and surgeries for a user

Use Cases

Patterns agents use PatientView API for, with concrete tasks.

★ Agent-Driven Health Record Lookups

An AI agent connected through Jentic logs in, reads a user's basic details and observations, and summarises them so a clinician can ask for a patient's recent readings in plain language. The agent reads the available observation types first, then fetches the observations for the type requested.

Read this user's latest blood pressure observations and summarise the trend

Observation History Retrieval

An application reads a user's observations of a given type over time, including the readings the patient entered themselves, so it can chart a measurement's history. It uses the available observation headings to know which types exist for the user before requesting them.

List the observation types for this user and return the full history for their weight readings

Patient Management Records

A workflow reads and saves patient management data such as diagnoses and surgeries for a user within a group, so a care record stays current. It reads the lookup types first to use valid codes, then saves the record.

Read the diagnosis lookup types, then save a new diagnosis record for this user in their group

Key Endpoints

15 endpoints — the patientview api reads patient health records for the patientview renal patient portal, so an application can retrieve a patient's basic details and their clinical observations.

METHOD

PATH

DESCRIPTION

POST

/auth/login

Log in

GET

/patient/{userId}/basic

Get basic patient information

GET

/user/{userId}/observations

Get observations for a user

GET

/user/{userId}/observations/{code}

Get observations of a certain type

GET

/user/{userId}/availableobservationheadings

Get available observation types for a user

GET

/patientmanagement/diagnoses

Get patient management diagnoses

POST

/auth/login

Log in

GET

/patient/{userId}/basic

Get basic patient information

GET

/user/{userId}/observations

Get observations for a user

GET

/user/{userId}/observations/{code}

Get observations of a certain type

GET

/user/{userId}/availableobservationheadings

Get available observation types for a user

GET

/patientmanagement/diagnoses

Get patient management diagnoses

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

P

PatientView

- AI-Aware (B+)
69/100
90
Foundational Compliance
63
Developer Experience & Jentic Compatibility
44
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
90

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

44

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
23%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PatientView API by hand means calling its login operation to get a session token, passing that token on later calls, and mapping observations by their type codes. Through Jentic you install once, import PatientView from the API Directory, and your agent calls it.

Permission scoping

PatientView puts the user id in the URL path, so a rule can limit your agent to reading one user's records. You choose which operations it may call, so you can allow reading observations while leaving the save operations out, and every call it makes is logged.

Credential isolation

PatientView authenticates through a login operation rather than a stored API key, so your agent obtains a short-lived session token at login and passes it on later calls. There is no long-lived key for Jentic to hold, and the login exchange stays inside your own instance.

Intent-based discovery

Agents search Jentic by intent such as 'read a user's observations' or 'get a patient's basic details', and Jentic returns the matching PatientView operation with its input schema so the agent calls the right endpoint without reading the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

DrChrono API

→

Electronic health record platform for patients, appointments, and clinical data

Choose this when you need a full EHR platform rather than a renal patient portal's record reads.

Complementary

openEHR API

→

Open standard and API for structured, vendor-neutral clinical records

Use alongside when clinical data needs to be stored or exchanged in a standardised openEHR form.

FAQs

Specific to using PatientView API through Jentic.

Is there a PatientView MCP server?

You don't need an MCP server to give your agent the PatientView API. Jentic connects it directly from the API Directory: import it and your agent can log in and read a user's records and observations straight away, with no extra server to run and no tool definitions to load into the agent's context.

Can I limit what my agent is allowed to do with the PatientView API?

Yes. Because PatientView puts the user id in the URL path, you can write a rule that limits your agent to reading one user's records. You also choose which operations it may call, so you can allow the read operations while leaving the save operations out, and every call it makes is logged.

What authentication does the PatientView API use?

The PatientView API declares no security scheme in its OpenAPI spec. Instead it exposes a login operation that returns a session token, and later calls include that token to identify the user. There is no long-lived API key to hold.

Can I read patient-entered observations with the PatientView API?

Yes. The API reads a user's observations by type, including the readings the patient entered themselves, and it lists the observation types available for that user. So an agent can retrieve both clinical and patient-entered values for a measurement.

What are the rate limits for the PatientView API?

The OpenAPI spec does not specify rate limits for the PatientView API. For current guidance, see the PatientView documentation at https://www.patientview.org.

How do I read PatientView records through Jentic?

Import the PatientView API from the Jentic API Directory, then have your agent issue a request such as 'read this user's recent observations'. Jentic matches the intent to the right operation and returns its input schema so the agent builds the correct request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GET STARTED

Start building with PatientView API

Explore with Jentic One
View OpenAPI Document