Access Methods

The Patient Chart supports three access methods, depending on system architecture, workflow requirements, and user context. In all cases, it surfaces data that has already been prepared and stored through Patient360 and other upstream workflows; the access method itself does not initiate upstream retrieval or generate data.

Web App

The Patient Chart is available directly in the Patient360 web app.

Users access the chart through an authenticated session
Patient context is selected within the app
The full chart interface and navigation are available

This method is typically used for direct access and operational workflows.

iFrame

The Patient Chart can be embedded within an external application using an iFrame.

The viewer is launched from an electronic health record (EHR) through SMART on FHIR, which passes the patient context, or embedded with a scoped OAuth 2.0 access token
The host application is responsible for establishing user and patient context
UI elements, such as the header or navigation, may vary depending on embedding configuration

This method supports integration into custom applications and external platforms. For the embedding and single sign-on details, go to Embedded iFrame.

API

The Patient Chart data is available programmatically through the FHIR R4 API.

Access is authorized through OAuth 2.0 using Health Gorilla resource scopes
The API returns chart data rather than the visual viewer
Data is returned in FHIR R4 structures consistent with the rest of the Patient Chart surface

This method supports applications that consume chart data directly. For the resources and endpoints, go to the FHIR API reference. Because the API returns data rather than the visual viewer, the layout, sections, summary, and search described in the viewer pages apply to the web app and iFrame, not the API.

SMART on FHIR

SMART on FHIR is an OAuth 2.0-based launch protocol. In the iFrame method, it launches the viewer from an EHR within an authenticated user session and patient context, passed through SMART launch parameters.

The API method authorizes access through OAuth 2.0 directly, and the web app relies on a direct authenticated session; neither uses the SMART on FHIR launch.

Requirements

All access methods require:

An authenticated user session
A valid patient context
A completed upstream workflow that has made data available in the tenant, such as Patient360 retrieval, Lab Network results, or delivered admission, discharge, and transfer (ADT) and event data

If these conditions are not met, the Patient Chart may display limited or no data.

Integration Considerations

UI presentation may vary depending on access method and embedding context
Patient context handling differs by access method and must be established before rendering the chart