In order to maximize the clinicians experience, a smooth transition between the EHR and Atticus is essential. This can be done effectively by passing information about the current user, encounter and patient.

Atticus supports multiple ways that vary in technical complexity, safety and convenience for the end user.

An overview of supported integration techniques

Technique Safety 🛡️ End-user convenience 🎯 Technical complexity ⚙️
URL parameters + Azure AD 🔒🔒🔒 🌟 🧠
oAuth2 Implicit flow 🔒🔒 🌟🌟 🧠🧠
oAuth2 Authorization Code flow 🔒🔒🔒 🌟🌟 🧠🧠🧠
SMART on FHIR (preferred) 🔒🔒🔒🔒 🌟🌟🌟 🧠🧠🧠

URL parameters + Azure AD

Integrating using URL parameters and connecting your Azure AD tenant is the simplest and fasted way to get started with Atticus.

  1. Launching Atticus using a parametrized URL Atticus is launched from your systems through a parametrized url…

    Entrypoint: https://<project-subdomain>.tiro.health/patients/dispatch

    An overview of the available parameters.

    URL parameter description expected format example values
    patient (required) unique identifier for current patient string Dds39fFHQ
    encounter unique identifier for current encounter, this should be globally unique across patients string Dds39fFHQ
    practitioner unique identifier for current practitioner string Dds39fFHQ
    age (deprecated) integer number representing current patient's age integer 23
    dob formatted string that represents the date of birth of a patient.
    Preferred format: IS08601 IS08601 1972-04-02
    sex term indicating the patient's sex; valid options are male, female, other .
    Cfr. Any code defined by FHIR AdministrativeGender male
    template string pathologie-aanvraag

    Make sure that all parameters are URL encoded so they are correctly interpreted by the browser.

    Additional information on the parameters

  2. Provide SSO through a one-click sign-in button by connecting Azure AD To Do

  3. Enable auto logout for shared computers To Do

SMART on FHIR

To do