Table 3.1 Interoperability Conformance Requirements for Use Case 3: Patient Views/Consumes PS-CA
Note: For details about Profiles/Standards listed in the tables below, please refer to Reference Architecture v0.2.0 DFT-Ballot (RA) standards.
Option 1: Document Repository/Registry Pattern
PS-CA USE CASE 3: Patient Views/ Consumes PS-CA | Mapping of Use Case Actor to Technical Actor and its related Profile or Standard | ||||
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE / STANDARD |
Patient Portal | Authenticate User | O | Client App | O | Internet User Authorization (IUA) -see RA specifications |
Identify Patient | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | PDQM -see RA specifications | ||
Request Patient Summary References (Patient Identifier) | R | Client App | R | Use Existing Standards Employed by the Clinical System | |
Request Patient Summary (Patient Summary References) | R | Client App | R | Use Existing Standards Employed by the Clinical System | |
| Return Patient Summary References | R | Document Consumer | R | MHD -see RA specifications | |
| Return Patient Summary | R | Document Consumer | R | MHD -see RA specifications | |
Perform transformation between different formats | O | Client App | O | Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF)) | |
O | Client App | O | CA:FMT (e.g., FHIR to CDA, Export to PDF, etc.) -see RA specifications | ||
Download/Print PS-CA | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
Save to Portable Media | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
O | Portable Media Creator | O | XDM(Future scope)-see RA specifications | ||
Document Repository (Local or Central) | Retrieve PS-CA References from Document Repository | R | Document Responder | R | MHD -see RA specifications |
Retrieve PS-CA from Document Repository | R | Document Responder | R | MHD -see RA specifications | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR -see RA specifications |
Table 3.2 Interoperability Conformance Requirements for Use Case 3: Patient Views/Consumes PS-CA
Note: For details about Profiles/Standards listed in the tables below, please refer to Reference Architecture v0.2.0 DFT-Ballot (RA) standards.
Option 2: FHIR Health Information Exchange (HIE) Pattern
PS-CA USE CASE 3: Patient Views/ Consumes PS-CA | Mapping of Use Case Actor to Technical Actor and its related Profile or Standard | ||||
USE CASE ACTOR | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE / STANDARD |
Patient Portal | Authenticate User | O | Client App | O | Internet User Authorization (IUA) -see RA specifications |
Identify Patient | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | PDQM -see RA specifications | ||
Request Search Patient Summary (Patient Identifier) | R | Client App | R | Use Existing Standards Employed by the Clinical System | |
| Request Patient Summary (Bundle ID) | R | Client App | R | Use Existing Standards Employed by the Clinical System | |
| Return Patient Summary Compositions | R | Data Consumer | R | CA:FeX -see RA specifications | |
Return Patient Summary | R | Data Consumer | R | CA:FeX -see RA specifications | |
Perform transformation between different formats | O | Client App | O | Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF)) | |
O | Client App | O | CA:FMT(e.g., FHIR to CDA, CDA to FHIR, Export to PDF, etc.)-see RA specifications | ||
Download/Print PS-CA | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
Save to Portable Media | O | Client App | O | Use Existing Standards Employed by the Clinical System | |
O | Portable Media Creator | O | XDM(Future scope)-see RA specifications | ||
Document Repository (Local or Central)* | Retrieve Patient Summary Compositions from Document Repository | R | Data Responder | R | CA:FeX -see RA specifications |
Retrieve Patient Summary Bundle from Document Repository | R | Data Responder | R | CA:FeX -see RA specifications | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR -see RA specifications |
*For Option 2, Document Repository use case actor is a logical role enacted by the Data Recipient which is described in detail in the 'Companion Guide: Reference Architecture.'