Public surface / Payer Patient Access APIs

AvMed Patient Access API

This endpoint declares a solid public surface with minor gaps.

Current grade B

Reachability100

Capability transparency100

Interop readiness38

Observed surface

Base URL: https://avmp.interop.avmed.com/api/v1/avmp
Category: Payer Patient Access APIs
Availability: answered 1 of 1 checks so far; availability is reported once 14 observations exist
Vantage agreement: reachable from all 3 vantages, which are 3 hosts on one network (github-actions): one network's view sampled 3 times, not 3 independent networks

Interpretation

A grade describes two public discovery documents at one point in time. It does not inspect patient data, authenticated behavior, or clinical quality.

Read the scoring method →

Findings

Reachability100

Pass: /metadata answers with HTTP 2xx over HTTPS: reachable from all 3 vantages, which are 3 hosts on one network (github-actions): one network's view sampled 3 times, not 3 independent networksR1 Spec ↗
Pass: /metadata responded in 202 ms (median across 3 reachable vantages on one network)R2 Spec ↗

Capability transparency100

Pass: fhirVersion declared: '4.0.1' (expected 4.x)T1 Spec ↗
Pass: software name and version declaredT2 Spec ↗
Pass: 9 resource types declaredT3 Spec ↗
Pass: 9/9 declared resources document their interactionsT4 Spec ↗

Interop readiness38

Needs attention: 9 profile canonical(s) declared in rest.resource.profile, none of them US Core, CARIN, or Da Vinci; also checked rest.resource.supportedProfile, instantiates, imports, meta.profileI1 Spec ↗
Not observed: no vantage retrieved .well-known/smart-configuration on this run, so whether it is published is unknownI2 Spec ↗
Pass: OAuth/SMART security service declared in CapabilityStatementI3 Spec ↗

Observed since 2026-08-20; no changes to declared capability recorded.

Registry provenance

How this entry was verified

live CapabilityStatement fetch (fhirVersion 4.0.1, software HiPaaS 4.0.1 1.35.0). The base URL is printed under the literal heading 'Base URL' in AvMed's own Patient Access API Documentation PDF (2026), linked from avmed.org/en/for-developers. The document's implementation block describes 'SHP' with a sentara.com URL - AvMed is Sentara-owned and the page routes developer support to the Sentara Health Plans CMS Interoperability support team - so the platform is the parent's; attribution to AvMed rests on AvMed publishing this exact base in its own materials (recorded 2026-08-19). No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.

Share this endpoint's grade

Link the badge back to this evidence page so readers can inspect the current findings.

<a href="https://fhir.chelseakr.com/endpoint/avmed-patient-access/">
<img src="https://fhir.chelseakr.com/badge/avmed-patient-access.svg"
alt="FHIR Scorecard: grade B"></a>

This is an observational snapshot of a public, unauthenticated surface. It is not an audit, a ranking of care quality, or a statement about anyone's regulatory compliance. See how we grade.