Intely Onboarding Guide

Below you’ll find a guide on how to create an Intely account and get started on the platform by creating instances for Epic and Cerner. Please forward to any other applicable team members.

Start by navigating to the Login/Sign Up screen at https://app.stg.intely.io/

In the top right corner of the screen or below the login box, select ‘Sign Up’ to begin creating an Intely account. Fill in all necessary detail and select ‘Create Account’

You will be prompted to verify your email by providing the code sent to the email registered to the Intely account.

Once the account has been validated, you’ll be taken back to the login screen where you can begin accessing the Intely Platform. After successful login, you’ll be taken to the Intely Platform Dashboard.

From the Dashboard, select the user icon in the top right corner of the screen to view the user menu. Select the ‘Settings’ option to view the User/Organization settings.

Once you are in the user settings (My Profile), scroll to the bottom section of that screen where you find Personal Access Token. Select ‘Create New Token’ to begin generating a new access token.

A pop up should appear where you can give the token a name, effective date range (predefined or custom), and the appropriate permissions for access.

Once you have this done and your Personal Access Token created you can navigate to Connect and begin creating the instances for Epic and Cerner.

You can navigate back to the dashboard from the Settings view by clicking either the Intly logo in the header or the home icon.

From the Dashboard, select the ‘Connect’ option in the lower left corner under ‘Applications’

Once on the Connect dashboard, select Instances to launch into your instances. As this is a new account, there won’t be any instances, but you can go ahead and set up the Epic and Cerner apps in your account.

Select the ‘Create Instance’ button and then select the applicable public application to set up.

For Epic, select the Epic tile and populate the appropriate details into the form:

A few important notes in regard to the API

  • Call POST /noauth/user/login/token with your username and personal access token
    • The defaultOrganizationId is the Current-Organization-Id for the subsequent API requests
  • Call GET /app/instances with the access token from the /noauth/user/login/token route
  • The _id property is the Instance-Id header value in the /emr routes
    The appId property is the App-Id header value in the /emr routes

If you have any questions, please don’t hesitate to reach out to the team!