SMART launch & CDS Hooks

Two ways to put Norvya inside a clinician's EHR. Most integrations need only the first.

Without EHR registration

With a partner token: find the patient's member_ref from your record number and birth date, fetch the same cards Norvya's CDS Hooks service returns (in the CDS Hooks card format) and render them in your own UI, and file the pre-visit brief as a FHIR DocumentReference. Medical practices only; each patient's sharing choices apply.

• POST/v1/patients/matchFind a patient's member_ref from your MRN and date of birth
• GET/v1/patients/{member_ref}/cardsCDS Hooks-format cards for one patient, to render in your own UI
• GET/v1/patients/{member_ref}/brief/documentThe pre-visit brief as a FHIR R4 DocumentReference, ready to file in your chart

SMART launch and a registered CDS Hooks service (built, gated)

Standard protocol endpoints called by the EHR itself, not with a partner token. They are built and switched off until Norvya is registered with, and reviewed by, each EHR vendor's developer programme.

• 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

Reference: EHR embedding: cards and chart documents and EHR embedding: SMART launch and CDS Hooks.