Pilot client
One real client, tested from start to finish before the API opens to more clients.
Read only. You can read this screen. Only the Super admin changes it.
Pilot in progress. The first full cycle is running. Two issues are open and both are due before PI-3 closes on 30 Oct 2026.
Pilot completed with no errors. 3 full push and pull cycles finished with no platform-side errors. All issues are fixed and the reference case is ready.
Issues open. 2 issues are still open. The platform fix must land before PI-3 closes on 30 Oct 2026. The cycles that ran are listed below.
Push and pull cycles
Cycle 1, pull 29 Sep 2026, 10:13
GET /v1/eligibility/EL-30551 returned 200 with the NPHIES answer in 96 ms.
Cycle 1, push 29 Sep 2026, 10:12
POST /v1/eligibility returned 202. Result id EL-30551.
Cycle 2, push 5 Oct 2026, 09:20
Waiting for the payer to answer. Pull follows when the result is ready.
Cycle 3, pull 3 Oct 2026, 09:06
All three results read. 200.
Cycle 3, push 3 Oct 2026, 09:05
Three checks sent in one call. 202.
Cycle 2, pull 1 Oct 2026, 14:41
Result read. 200.
Cycle 2, push 1 Oct 2026, 14:40
Eligibility check started for a second payer. 202.
Cycle 1, pull 29 Sep 2026, 10:13
GET /v1/eligibility/EL-30551 returned 200 with the NPHIES answer in 96 ms.
Cycle 1, push 29 Sep 2026, 10:12
POST /v1/eligibility returned 202. Result id EL-30551.
Cycle 2, pull 1 Oct 2026, 14:41
Result read returned 504 after 8 s. Platform side. Logged as PI-3-02.
Cycle 2, push 1 Oct 2026, 14:40
Eligibility check started for a second payer. 202.
Cycle 1, pull 29 Sep 2026, 10:13
GET /v1/eligibility/EL-30551 returned 200 with the NPHIES answer in 96 ms.
Cycle 1, push 29 Sep 2026, 10:12
POST /v1/eligibility returned 202. Result id EL-30551.
Issues triage
| Issue | Side | Owner | Due | Status |
|---|---|---|---|---|
| PI-3-01 Token expires before a long poll endsFound in cycle 1 | Platform | SASamir Al-Qadi | 16 Oct 2026 | Fixed |
| PI-3-02 Result read slow for pending checksFound in cycle 1 | Platform | SASamir Al-Qadi | 23 Oct 2026 | Open |
| Issue | Side | Owner | Due | Status |
|---|---|---|---|---|
| PI-3-01 Token expires before a long poll endsFound in cycle 1 | Platform | SASamir Al-Qadi | 16 Oct 2026 | Fixed |
| PI-3-02 Result read slow for pending checksFound in cycle 1 | Platform | SASamir Al-Qadi | 23 Oct 2026 | Fixed |
| PI-3-03 Client sent the payer name in lower caseFound in cycle 2 | Client | PPPharmacy portal vendor | 23 Oct 2026 | Fixed |
| Issue | Side | Owner | Due | Status |
|---|---|---|---|---|
| PI-3-01 Token expires before a long poll endsFound in cycle 1 | Platform | SASamir Al-Qadi | 16 Oct 2026 | Fixed |
| PI-3-02 Result read returns 504 after 8 sFound in cycle 2 | Platform | SASamir Al-Qadi | 23 Oct 2026 | Open |
| PI-3-03 Client sent the payer name in lower caseFound in cycle 2 | Client | PPPharmacy portal vendor | 23 Oct 2026 | Open |
Every issue is fixed or has a due date before PI-3 closes on 30 Oct 2026.
Reference case for the next clients
Ready to shareDraftAgree the scopes before the credentials
The pilot started with Reception only. Scopes were widened after cycle 1 without a new client.
Test in the sandbox with one payer first
Add the second payer only after a full cycle works.
Give the vendor the pull sequence in writing
A pull before the NPHIES answer returns Pending. The client must poll, not retry the push.
Keep one named contact on each side
Questions in the first week were answered in under an hour.
API documentation carries the technical detail.
Pilot client
Open API client
- Client
- Pharmacy portal pilot
- Client ID
- cl_pharm_09ad
- Technical contact
- integration@pharmacyportal.example
- Scopes
- Reception and eligibility (read and write)
- Started
- 28 Sep 2026
- PI-3 closes
- 30 Oct 2026
- Status
- In progressCompleted, no errorsIssues open
Pilot criteria
At least one full push and pull cycle
No platform-side errors in the cycles
Issues triaged and fixed before PI-3 closes
Reference case written for the next client
At least one full push and pull cycle
No platform-side errors in the cycles
Issues triaged and fixed before PI-3 closes
Reference case written for the next client
At least one full push and pull cycle
No platform-side errors in the cycles
Issues triaged and fixed before PI-3 closes
Reference case written for the next client