PatientView

{
  "service_type": "platform",
  "base_url": "https://patientview.org",
  "auth_method": "none",
  "auth_config": {
    "note": "No public authentication scheme documented. PatientView is a patient-facing health portal, likely authenticated via user session / NHS login rather than standard API keys.",
    "assumed_methods": ["session cookie", "oauth2 (NHS login, unconfirmed)"]
  },
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "PatientView is a free patient portal provided via renal/healthcare trusts in the UK; no commercial pricing for end users."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "patient health record access",
    "renal/kidney care data viewing",
    "test results and lab data display",
    "medication and prescription viewing",
    "appointment and clinical correspondence viewing",
    "patient self-service portal for UK NHS/trust-linked care"
  ],
  "raw_analysis": "PatientView (patientview.org) is a UK-based patient-facing health portal, primarily used in renal and kidney care contexts, allowing patients to view their own clinical data such as blood test results, medications, appointments, and correspondence. The provided description claims it exposes a 'recommended REST API' for integration, however no public API documentation, endpoint list, authentication specification, or developer portal is described or evidenced in the supplied content. There is no public evidence of a generally available developer-facing REST API; access appears to be mediated through clinical organisations and trusts, and authentication is likely tied to NHS login or trust-issued credentials rather than open API keys. As a platform, PatientView is mature within its niche (long-standing UK patient portal used by multiple renal units), but its 'API' is not an openly documented public developer API. For integration purposes, one would need to approach the operating organisation (PatientView is associated with the UK Renal Registry / trusts) directly to obtain access, credentials, and interface specifications. Because no concrete endpoints or auth details are known, endpoints is empty, auth_method is set to 'none' with assumed alternatives documented, and rate limits are unknown. Pricing is effectively free/covered by healthcare provision rather than a commercial API product. Overall maturity: established platform, but limited public developer ecosystem."
}

0/3 tests passed

{
  "overall": 46,
  "dimensions": {
    "token_efficiency": 6.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 5.0,
    "doc_quality": 4.0,
    "auth_simplicity": 3.0,
    "latency": 10.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "type": "free",
    "note": "PatientView is a free patient portal provided via UK renal/healthcare trusts; no commercial pricing for end users."
  },
  "issues": [
    "No public API or structured data export documented — agents cannot programmatically read or act on patient data.",
    "Authentication is gated behind trust-issued credentials and NHS login; no self-serve or agent-friendly onboarding path.",
    "Critical health-data platform but no llms.txt, unclear robots.txt behavior, and non-machine-readable docs.",
    "Health record access is region-locked to UK NHS/trust-linked patients — narrow audience, limited agent utility.",
    "Documentation quality appears minimal; feature descriptions, getting-started guides, and limitations are not readily surfaced."
  ],
  "recommendations": [
    "Publish a public developer/help docs page with clear onboarding steps and supported regions.",
    "Add llms.txt and a well-formed robots.txt to signal agent accessibility.",
    "If permissible, expose a FHIR/HL7-compatible read API so agents can fetch structured results with proper consent.",
    "Improve auth simplicity where policy allows (e.g., NHS login guidance, magic-link flows) and document blockers explicitly.",
    "Provide status/uptime page and security headers to boost reliability perception."
  ]
}