How Orbital Lite STS works
A clinician clicks the HIE link in the patient's chart. Orbital Lite STS confirms who they are, adds the active patient's identifier, and posts a signed SAML assertion to the HIE, which opens the viewer on that patient.
Launch in patient context
User identity and patient identifier travel together in one signed assertion, using the SAML profile each HIE expects. That is the difference between single sign-on and landing on the right record.
Uses the sign-in you already have
Authenticates against Active Directory or LDAP, a nonce or shared secret passed by the EHR, individual passwords, or client certificates, so clinicians never get another password.
HIE profiles built in
Ready-made profiles for CRISP, etHIN, Quality Health Network, Clinical Connect HIE and Ontario’s provincial SSO standard. See the full list. New profiles can be added as a service.
Audit logging
Every authentication and launch is logged with the user, patient identifier, destination and time. Logs can be forwarded to your SIEM or log repository for privacy monitoring.
Runs in your environment
Installs on Windows Server with IIS and a relational database inside your network, with modest resource needs. Radius Works handles installation and configuration with your team.
Roadmap
Support for OAuth 2.0, OpenID Connect and SMART on FHIR app launch is on our roadmap. Ask us about current status and timelines.