Application Launches

On the Apps page for each application, there is a new tab called Launches. This tab provides information about all the time taken for each launch of the application against each gateway. It provides a breakdown of the various times involved in the process of an application launch. 
Each launch is recorded along with times in a table. 

Application launch times are in three categories:

1. SMART Launch: Time taken from the click to launch the application at the EHR (i.e. EHR launch activated request) to the time when interopiO has issued a token to the application.
   This event is recorded by interopiO and will be present if the SMART launch portion of the launch completes successfully.
   • If during the SMART launch process, there are errors, then this event will not be logged either. This could happen if there is an issue with getting authorization from the EHR or the any other issues getting a token from interopiO®.
2. App Ready: Time from EHR launch activated request to event time of application-provided event for App Ready.
   • Each application that is registered on interopiO® is able to send  an App Ready event indicating the time and duration it took for the application to be considered ready which is when the page loads with basic information. In case this event is not sent by the application, this field will be empty.
3. App Launch Complete: Time taken from EHR launch activated request to event time of application-provided event for App Complete.
   • The App Complete event has to be provided by the application when it considers the application to be fully useable after it has loaded all necessary data.  In the absence of this event, this field will be empty.

For further details on how to send application events to interopiO, see https://support.interopio.com/hc/en-us/articles/360041549832-Application-Logging

A quick summary is do something similar as the following call:

curl --request POST \
  --url https://interopio-dev.com/logging/apps/test/standard-deploy-te/client-creds/event \
  --header 'Authorization: bearer <token to iO>' \
  --header 'Content-Type: application/json' \
  --data '{
	"loggingDto": {
		"appId": "client-creds",
		"accountId": "test",
		"environmentId": "standard-deploy-te",
		"httpErrorCode": "200",
		"body": "body on: app 2022-12-01 14:02:36 -0700",
		"containsPhi": false,
		"sessionId": "sessionId1234",
		"logLevel": "DEBUG"
	},
	"analyticsReportInteropioEvents": {
		"accountId": "test", "environmentId": "standard-deploy-te",
		"gateway_id": null,
		"timestamp": null,
		"url": null,
		"auth_principal_username": null,
		"event_type": "App Ready",
		"cds_service_id": null,
		"cds_service_override_id": null,
		"cds_service_set_id": null,
		"cds_service_invocation_origin": null,
		"cds_service_invocation_tenant": null,
		"num_cards_returned": null,
		"http_response_code": null,
		"duration": 3234,
		"cds_user_in_context": null,
		"cds_patient_in_context": null,
		"cards_returned": null
	}
}'

Launches Tab

The screenshot below is an example of the launches tab with empty App Ready and App Launch Complete fields due to the application not providing this information.

App Launch Inspect:
To get further details about each launch, click into the record and further details about the launch are presented. This detail is mainly used for debugging if there are issues with the launch or to look at further detail where each step in the launch process is listed and the associated duration is specified.

This is illustrated in the two screenshots below.

In the table above the duration for each event is presented in the Event Duration column whereas the accumulated duration of all events is calculated as a running total starting from the first event at the bottom "EHR to interopiO: Launch Sequence Activated".