Single-endpoint report
Premera Blue Cross Patient Access API: endpoint report
Everything this project observed about this one endpoint, everything it did not observe, and what would change the result. Free to read, link, print and hand on; there is nothing here behind a sign-in and nothing to buy.
Built to print. Use your browser’s print or “Save as PDF” to keep a dated copy; the page carries its own address and observation date.
Grade on this run
- Grade
- A
- Category
- Payer Patient Access APIs
- Base URL observed
https://opala.tech/patient-access/premera/v1/fhir-r4- Reach on this run
- Reached from 3 of 3 reporting vantages, sitting on 1 network. Vantages on one network are one network's view sampled several times.
- Last answered
- 2026-10-03 (answered on this run)
- Availability
- answered 16 of the last 16 daily checks (100%)
- Observed
- 2026-10-03 15:21 UTC
What was observed, and what was not
This report covers 9 checks. 9 ran. 0 were asked from every reporting vantage and answered by none. 0 were never asked, because nothing was retrieved for them to read. The three are different facts and none of them is a zero: a check that did not run publishes no number, no mark against this endpoint, and nothing below to act on.
Reachability
| Check | State | What this run observed |
|---|---|---|
| R1 | 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 networks |
| R2 | Pass | /metadata responded in 343 ms (median across 3 reachable vantages on one network) |
Capability transparency
Interop readiness
| Check | State | What this run observed |
|---|---|---|
| I1 | Pass | US Core / CARIN / Da Vinci profiles declared in CapabilityStatement.instantiates, rest.resource.supportedProfile |
| I2 | Pass | SMART discovery document present and complete |
| I3 | Pass | OAuth/SMART security service declared in CapabilityStatement |
What each vantage saw
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | reached | answered in 592 ms | HTTP 200 |
github-actions/ubuntu-latest | reached | answered in 299 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 343 ms | HTTP 200 |
Vantages on one network are one network’s view sampled several times. A rule applied to that network’s address space reaches every one of them at once and reads exactly like agreement.
What would change this
Nothing is listed here: every check that ran passed. Checks that did not run are in the section above, and they are not failures.
If this does not match what you see
Every number here describes two public documents at one moment, read from the vantages listed above. If it does not match what you serve, the difference is worth knowing.
Correct or dispute this record. There is no sign-in, no fee, and nothing to buy: this report is free to read, link, print and hand on, and this project collects nothing about the people who read it.
Where this came from
base URL printed as the 'Patient Access API Capability Statement' on the page docs.opala.com publishes as the 'Premera Dev Toolkit'. Live CapabilityStatement retrieved unauthenticated from the davis-ca residential vantage on 2026-09-13: fhirVersion 4.0.1, 33 resource types, 78 supportedProfile canonicals, implementation.url matching the requested base exactly; publisher and software 'Opala', which is Premera's vendor. Attributed to Premera by a link chain from Premera's own site, not by Premera printing this address: https://www.premera.com/visitor/developers, read on 2026-09-18 by a headless-browser render with its sections expanded because the page is built client-side, describes the Patient Access API (protected by the OpenID Connect flow of OAuth 2.0), names Opala as Premera's interoperability partner, and sends developers to https://www.opala.com/developer-toolkit-premera, which redirects to the toolkit page above, and to developersupport@opala.com. Premera's page does not print the Patient Access base URL itself (recorded 2026-09-13). No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.
The same run, as data: this endpoint's JSON, what its CapabilityStatement declares, resource by resource, and every observation on record for it, with the dates it answered and the dates it did not.
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. Grades are comparable within a category only. See how we grade.