DFT - For a full list of available versions, see the Directory of published versions

UC-03: Patient Views/Obtains Personal PS-CA

A Patient or Subject of Care accesses/views and can retrieve a copy of their own PS-CA to support unscheduled/scheduled local care, or for any other purpose.

Implementation Option 1: MHD

Scenario: Patient Portal Retrieves PS from MHD Document Registry – (MHD* IHE Profile).

Assumption: Patient Summary-CA is stored in Central or Local (Decentralized) Document Repository.

Implementation Option 1: This sequence diagram provides the option of using the MHD IHE profile, including a Document Repository actor and supporting HL7 FHIR standards.

Note: Additionally, this sequence diagram includes the CA:FMT Interoperability Specifications that handle transformations to and from various formats (e.g. FHIR to PDF, CDA, etc.). The Document Repository in this scenario can be either (1) central or (2) at PS-CA Producer (the source where the document was produced). The Document Consumer actor would query the appropriate repository.

Sequence Diagram

Implementation Option 2: CA:FeX

Scenario: Clinical Solution A Retrieves Patient Summary-CA from Central Document Repository

Assumption: Patient Summary-CA is stored in Central Document Repository

Implementation Option 2: This sequence diagram provides the option of using the CA:FeX Interoperability Specifications that provide support for saving and retrieving a Patient Summary-CA to and from a Document Repository (Local to PS-Producer or Central). This profile includes a Data Consumer and a Data Responder actor. Additionally, this sequence diagram uses the 'Search Data' and 'Retrieve Data' FHIR operations.

Note: Additionally, this sequence diagram includes the CA:FMT Interoperability Specifications that handle transformations to and from various formats (e.g. FHIR to PDF, CDA, etc.). Additional details will be included in the PS-CA Interoperability Specifications.

Support for Use Case 3 is not limited to the transactions currently specified in the sequence diagrams. The $summary operation (CA: FeX-3D) is also a valid approach for fulfilling this use case, and other relevant transactions defined in CA:FeX may be applicable depending on implementation details. As the specification evolves, additional guidance or examples may be provided to clarify the range of supported transactions.

Sequence Diagram

---