Sequence Diagrams

The CA:FeX sequence diagrams illustrate how to apply CA:FeX and related IHE profile implementation patterns to support FHIR-based Health Information Exchange (HIE) use cases. They group together actors and transactions from multiple profiles including CA:FeX to address the scope of the use cases.

Sequence Diagram Overview:

The following guidance explains how to interpret the sequence diagrams:

• The Data Consumer role varies depending on the client type:
  • HCP: A Clinical Solution (e.g., an EMR used by a Health Care Provider) that requests and retrieves clinical information from a Clinical Data Repository.
  • Patient: A Patient Portal used by the patient (Subject of Care) to request and retrieve their own clinical information from a Clinical Data Repository.
• The legend in the bottom-right corner describes the different system components, actors and transactions that are necessary to carry out this 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, etc.) but included as a white note. These foundational requirements are assumed to be in place prior to executing the use case.
• The blue swim lanes group a sequence of processes (along with their required actors and transactions) that are needed to occur to satisfy this use case. The diagrams should be read from left to right and top to bottom.
• Red note boxes highlight key contextual information and important implementation considerations.
• For more information on core IHE Profiles and specific Canadian implementation guidance, refer to the Reference Architecture available here.

Additional Considerations

The sequence diagrams in this section do not represent all possible combinations of IHE profiles and transactions. For example, the ITI-83 transaction can be used in place of ITI-78 when the preferred implementation pattern is PIXm/PMIR.