Prorenata Journal is automatable through its REST API

Prorenata Journal is automatable through its REST API. The integration guide says the API covers the system's functionality and is what Prorenata's own frontend uses. Each integration request sends an Authorization header with the word Token and an API token. Tokens are issued by Prorenata Support. The guide shows how to create a patient, read and write journal entries, lock and sign an entry, and transfer a patient, on paths under /api/v2/patients/. One admission example is a POST whose query string is not a valid filter. The opened OpenAPI 3.0.3 document lists 980 current externally accessible paths. Most version-2 paths accept either a sessionid cookie or the Token header. A smaller set, including /api/integration/v1/, also accepts the header PRNJ-API-AUTH-KEY. The external patient paths shown accept the Token header. The same OpenAPI text says the generated reference is incomplete and inaccurate in places, especially required request fields. This record is Prorenata Journal from Prorenata AB, not CGM TakeCare or Cambio COSMIC. No first-party MCP server was established from the pages opened here. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 6.

Best path today: api · Overall automatability: 6/10