Australian CVD Risk Calculator
Iteration3 - ci-build

Australian CVD Risk Calculator - Local Development build (vIteration3) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## SMART App Launch Requirements

The Aus CVD Risk Calculator application, Aus CVD Risk‑i, is a client application that implements the SMART App Launch standard. For clinical systems to integrate and use the application, they will be required to also implement SMART App Launch as a FHIR server following the EHR launch flow.

This implementation guide will not replicate information from the SMART App Launch standard. It will only include information specific to the Aus CVD Risk Calculator. It is recommended integrators read the standard. The launch and authorisation flow are well described in the App Launch section.

### App Registration

SMART App Launch guidance

Systems will require a one-time setup to register Aus CVD Risk‑i.

Aus CVD Risk‑i supplies the following registration details. These details will be also used in the authorization request.

Attribute | Details
--- | ---
Client name | Aus CVD Risk-i
Client ID | aus-cvd-risk-i
Launch URL | https://main.dlnanw1r5u3dw.amplifyapp.com/launch
Redirect URI | https://main.dlnanw1r5u3dw.amplifyapp.com

### Launch Capabilities

SMART App Launch guidance

Aus CVD Risk‑i will mainly be launched from an EHR. Systems are required to implement Smart App Launch following the EHR launch flow.

### Launch Request

SMART App Launch guidance

#### Launch Context

To support App Launch, the EHR will need to store the required launch context in representation and at a secure location accessible by the EHR's "authorize" endpoint. The launch context will be supplied as a `launch` parameter in the launch request using a unique and opaque launch identifier. It will also be verified against the `launch` parameter supplied in the authorization request.

Aus CVD Risk‑i has the following launch context requirements:

Attribute | Optionality | Details
--- | --- | ---
patient | required | Current patient identifier used to retrieve the Patient via FHIR Server. Example: `87a339d0-8cae-418e-89c7-8651e6aab3c6`
encounter | optional | Current patient visit identifier used to retrieve the Encounter via FHIR Server. Example: `6673d31c-3cc3-43bc-adb6-cedb3122d881`
sub | required | Unique identifier of the user as known by the PMS authorization service. Example: `f256d3ba-bb70-4613-a631-825d500c57fa`
preferred_username | optional | Optional username used to login to EHR. Example: `janedoe`
fhirUser | required | Current user identifier used to retrieve the user’s Practitioner resource via the FHIR API. Example: `Practitioner/f256d3ba-bb70-4613-a631-825d500c57fa`

### Authorization Request

SMART App Launch guidance

Aus CVD Risk‑i will request the following access scopes in the authorization request `scope` parameter:

- `launch`
- `openid`
- `fhirUser`
- `online_access`
- `patient/Patient.r`
- `patient/Encounter.r`
- `patient/Condition.s`
- `patient/Observation.cs`
- `patient/Medication.r`
- `patient/MedicationRequest.s`