Scenario:  Patient-facing application (Mobile App, Patient Portal, or proprietary Patient Viewer Application) requests access to a shareable copy of their Patient Summary in SHLink format.

Assumption:  The Patient Summary either exists or is generated on demand. This step occurs prior and is transparent to the SHLink generation.

Implementation Option:  This sequence diagram provides the option of using the CA:SHL Interoperability Specifications that provide support for requesting generation of a Shareable Health Link to their Patient Summary from a Clinical Data Repository. This profile includes an SHLink Requester and an SHLink Creator actor. Additionally, this sequence diagram uses the 'Generate SHLink' CA:SHL-1 transaction.

The server-side generates the SHLink and upon receival, the SHLink is typically converted in a QR code format, that can be downloaded by the patient and saved onto their phone or other media. The SHLink optionally contains a viewer URL that is recognizable by a browser and can display information related to the SHLink. 

Sequence Diagram Overview: 

Below provides guidance on how to read the sequence diagram:  

• This sequence diagram illustrates how the different standardized actors of systems should interact with each other to carry out specific standardized transactions, and the order in which the transactions and interactions occur when Use Case 5 of the Patient Summary-CA is executed.
• The legend on the bottom right corner describes the different system components, actors and transactions that are necessary to carry out this particular use case. 
• The green swim lane is a simplified view of the actors and transactions required by the Foundational Profiles, defined here, in addition to the other ones that are not explicitly illustrated on the diagram (e.g. ATNA, CT) but included as a white note. These are pre-requisite conditions for this particular use case and it is assumed that these will be satisfied. 
• The blue swim lanes groups sequence of processes (along with their required actors and transactions) that are needed to occur to satisfy this particular use case. These are to be read from left to right and top to bottom. 
• The red note boxes, if present, describe important call outs, information and notes that provide more context for the sequence diagram. 
• This sequence diagram includes the CA:SHL Interoperability Specifications. Additional details will be included in the PS-CA Interoperability Specifications.
• For more information on core IHE Profiles and specific Canadian implementation guidance, refer to the Reference Architecture.