Norvya DevelopersGuides
How the platform behaves across families. The API reference says what each call does; guides say how tokens, consent, errors, webhooks and the sandbox work.
Get started
Quickstart
Get a token, list your members, then call your market's endpoints.
Authentication & tokens
OAuth 2.0 client credentials; tokens last about 15 minutes and carry only the scopes you request.
EMR vendor tokens
One credential across every practice that approves you: GET /v1/practices, then a token per practice.
Sandbox & access
Synthetic members, sandbox kinds, credentials, limits, resets, and how to request access.
Core concepts
Members, member_ref & consent
Pseudonymous references per partner, ext:<your id>, section-by-section sharing.
Scopes
Every scope, what it allows, and who can hold it.
Errors & limits
Stable machine codes in detail, 429 with Retry-After, GET /v1/usage.
Audit & data handling
Every read of member data is written to a hash-chained audit log, or refused.
Pagination, idempotency & time zones
Three paging styles, natural keys for safe retries (no Idempotency-Key header), offsets on every instant.
Events
Standards
FHIR R4 & Bulk Data
US Core-shaped R4 resources, the per-patient record and the asynchronous Bulk Data export.
HL7 v2 (ADT, VXU, syndromic)
ADT A01–A04 in over HTTPS; VXU, QBP and syndromic ADT (2.5.1) out to public health.
SMART launch & CDS Hooks
Cards and chart documents with a partner token today; SMART launch and a registered hook service after EHR review.
Standards & terminologies
LOINC, UCUM, SNOMED CT, ICD-10-CM, CVX, RxNorm and the formats in and out, with how sure each use is.