Skip to main content
When a decoded SMART Health Link payload does not contain the U flag, the receiving system retrieves a SMART Health Link manifest instead of a direct encrypted file. The receiving application performs an HTTP POST request to the SHLink url with a JSON request body containing a required recipient field and, when applicable, a passcode. This follows the SMART Health Links specification.

Endpoint

The SHLink URL is obtained from the url field inside the decoded SMART Health Link payload.

Request headers

string
required
Set to application/json to indicate the request body is a JSON object.

Request body

string
required
A string describing the recipient, such as the name of an organization or person, suitable for display to the receiving user.
string
User-supplied passcode when the decoded SHLink payload includes the P flag.
integer
Upper bound on the length of embedded payloads returned in files.embedded.

Example request body

cURL example

Manifest response structure

If the request is valid, the resource server returns a SMART Health Link manifest with Content-Type: application/json.
object
required
SMART Health Link manifest object.
string
Indicates whether files may change in the future.
FHIR List
List resource with metadata related to the contained files.
array
One or more file descriptors.
string
required
Nature of the file content.
url
URL to externally retrievable content.
JWE string
Embedded encrypted file contents.
timestamp
Last time the content was modified.

Example manifest response

Responses

Each encrypted file (files[].embedded, or fetched from files[].location) is a JWE. Decrypt it with the key from the SHLink payload to obtain the FHIR bundle. See Bundle & artifact reference.