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
url field inside the decoded SMART Health Link payload.
Request headers
Set to
application/json to indicate the request body is a JSON object.Request body
A string describing the recipient, such as the name of an organization or person, suitable
for display to the receiving user.
User-supplied passcode when the decoded SHLink payload includes the
P flag.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 withContent-Type: application/json.
SMART Health Link manifest object.
Indicates whether files may change in the future.
List resource with metadata related to the contained files.
One or more file descriptors.
Nature of the file content.
URL to externally retrievable content.
Embedded encrypted file contents.
Last time the content was modified.
Example manifest response
Responses
- 200
- 401
- 404
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.