1 Choose the health data to share

These example documents use the European EHR Exchange Format (EEHRxF) and contain synthetic test data only. You can also use a FHIR Bundle of your own.

Loading documents…

Use my own FHIR Bundle

2 Choose how to share it (all optional)

A short description that the receiver sees before opening the data. It is stored in the link itself, so it should not contain sensitive information.

0/80

The receiver must enter it before the data is released. The passcode is not part of the link or QR code, so share it separately: say it out loud, or send it some other way. After 5 wrong attempts the link is locked for good. This app does not save the passcode.

After this time the server refuses to release the data, and the receiver's app shows that the link has expired. You can also revoke a link at any time from My links.

Tells the receiving app that it may keep this link and check it again later for updated data (the L flag), rather than fetching the data once. This is useful for ongoing care relationships. This demonstrator can't update the data behind a link, so the flag only tells the receiver what you intend.

The selected document is sent over HTTPS to . The server encrypts it with a new random key and stores only the encrypted copy. The key is part of the link, so anyone who has the link (and the passcode, if you set one) can read the data.

Settings

New links are created on this server. Existing links keep working on the server they were created on.

If this is set, links and QR codes start with this web address (https://viewer…#shlink:/…), so a phone camera can open them directly in a viewer app. Apps that understand SMART Health Links read the part after the #.