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.