Table 1.1 Interoperability Conformance Requirements for Use Case 1: HCP Creates PS-CA
Option 1: Document Repository/Registry Pattern
PS-CA USE CASE 1: HCP Creates 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 |
PS-CA Producer | Authenticate User | O | Client (e.g., EMR) | O | |
Identify Patient | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | |||
Retrieve clinical data from local data sources (Patient Identifier) | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Assemble and review Patient Summary | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Update Current Valuesets and ConceptMaps | O | Client (e.g., EMR) | O | ||
Omit or Mask Data based on Jurisdictional Policy | O | Client (e.g., EMR) | O | Jurisdictional Requirement | |
Save PS-CA to Document Repository | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
R | Document Source | R | |||
Document Repository (Local to PS-CA Producer or Central) | Save PS-CA to Document Repository | R | Document Recipient | R | |
| Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR |
Table 1.2 Interoperability Conformance Requirements for Use Case 1: HCP Creates PS-CA
Option 2: FHIR Health Information Exchange (HIE) Pattern
PS-CA USE CASE 1: HCP Creates 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 |
PS-CA Producer | Authenticate User | O | Client (e.g., EMR) | O | |
Identify Patient | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | |||
Retrieve clinical data from local data sources (Patient Identifier) | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Assemble and review Patient Summary | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Update Current Valuesets and ConceptMaps | O | Client (e.g., EMR) | O | ||
Omit or Mask Data based on Jurisdictional Policy | O | Client (e.g., EMR) | O | Jurisdictional Requirement | |
Save PS-CA to Document Repository | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
R | Data Source | R | |||
Document Repository (Central)* | Save PS-CA to Document Repository | R | Data Recipient | R | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | |
*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'.