API reference · Clinical
EHR embedding: SMART launch and CDS Hooks
SMART on FHIR app launch and a registered CDS Hooks service, so Norvya opens inside the clinician's EHR. The REST cards and chart documents above need none of this registration.
- Who calls it
- useful for Concierge doctors, Independent practices, EMR vendors, Hospitals and health systems
- Before production
- Registration with each EHR vendor's developer programme, then their review.
- Sandbox
- Build against synthetic members first. What each sandbox holds
- Standards
- SMART on FHIR EHR launch; CDS Hooks
Markets that use this family
- Concierge doctors (useful)
- Independent practices (useful)
- EMR vendors (useful)
- Hospitals and health systems (useful)
Protocol endpoints outside /v1
Standard protocol endpoints, called by the EHR itself rather than with a partner token.
- GET
/ehr/launchSMART on FHIR EHR launch (the EHR opens Norvya with iss and launch) - GET
/ehr/callbackSMART authorization callback - GET
/ehr/.well-known/jwks.jsonNorvya's public keys for SMART backend authentication - GET
/cds-servicesCDS Hooks discovery - POST
/cds-services/norvya-patient-viewCDS Hooks patient-view: the card for the open chart - POST
/cds-services/norvya-patient-view/feedbackCDS Hooks card feedback
Generated from the Partner API router and developers_catalog.py. The router docstring is the source of each description.