1
Launch in context
SMART App Launch provides patient context and authorizes the workflow through the EHR.
Built for the moment a medication list needs a second look.
RxOpsis launches in context, reads the selected patient's medication data, normalizes drug identity, and presents clear warning summaries without moving tokens into the browser.
2
Read medications
The backend requests active medication resources from the FHIR server for the selected patient.
3
Normalize identity
Medication names and codings are mapped toward RxNorm identifiers where available.
4
Display warnings
Warnings are summarized by severity, source, and relevant medications in a compact review surface.
A practical safety lens for active medications.
RxOpsis is designed as a decision-support companion: fast to launch, plain about evidence sources, and easy to extend as validated drug interaction services are added.
Patient-specific
Runs from the current SMART patient context instead of relying on manual drug entry.
Server-side OAuth
Keeps access tokens on the backend and gives the UI only the summary it needs.
Source-aware
Shows warning provenance so clinicians can distinguish label-based signals from curated DDI data.
Ready for Epic registration paths.
The app is structured for a hosted launch service at app.rxopsis.com, with a separate public website at www.rxopsis.com. That keeps public content and authenticated clinical workflows under one domain family while preserving clean operational boundaries.
- OKSMART launch URL: https://app.rxopsis.com/launch
- OKOAuth callback URL: https://app.rxopsis.com/callback
- OKPublic website URL: https://www.rxopsis.com