Scenario: Clinical Solution Submits Clinical Data to a Central Clinical Data Repository.
Assumption: Clinical Information (FHIR Resource) is stored in a Clinical Data Repository.
This sequence diagram provides the option of using the CA:FeX Interoperability Specifications that provide support for submitting data (e.g., Single FHIR Resources) to a central Clinical Data Repository. This specification includes a Data Source and a Data Recipient actor. Additionally, this sequence diagram uses the 'Submit Resource' CA:FeX-1C transaction.
Sequence Diagram Overview:
Below provides guidance on how to read the sequence diagram:
- This sequence diagram illustrates how the different standardized actors of a system should interact with each other to carry out specific standardized transactions, and the order in which the transactions and interactions occur when UC-03 Create and Submit Data of the CA:FeX Specification is executed.
- The legend on 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 are pre-requisite conditions for this use case and it is assumed that these will be satisfied.
- 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. These are to be read from left to right and top to bottom.
- The red note boxes describe important information and notes that provide more context for the sequence diagram.
- For more information on core IHE Profiles and specific Canadian implementation guidance, refer to the Reference Architecture available here.
Additional Considerations
The sequence diagrams included in this section do not showcase all of the possible combinations of IHE profiles and transactions that can be used for a particular implementation pattern. For example, ITI-83 transaction can be used in place of ITI-78 if the preferred implementation pattern is PIXm/PMIR.
