Table 4.1 Interoperability Conformance Requirements for Use Case 4: HCP Requests PS-CA On Demand
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: Clinical FHIR Data Sources are internal to the Clinical Data Repository
PS-CA USE CASE 4: HCP Requests PS-CA On Demand | Mapping of Use Case Actor to Technical Actor and its related Profile or Standard | ||||
USE CASE ACTORS | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE / STANDARD |
PS-CA Consumer | Authenticate User | O | Client (e.g., EMR) | O | Internet User Authorization (IUA) -see RA specifications |
Identify Patient | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | PDQM -see RA specifications | ||
Request Patient Summary on-demand (Patient Identifier) | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Request Patient Summary on-demand (Patient Identifier) | R | Data Consumer | R | CA:FeX (CA:FeX-3D with $summary)-see RA specifications | |
Return Patient Summary Document Bundle | R | Data Consumer | R | Use Existing Standards Employed by the Clinical System | |
Perform transformation between different formats | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF)) | |
| O | Client (e.g., EMR) | O | CA:FMT(e.g., FHIR to CDA, Export to PDF, etc.) -see RA specifications | ||
| Download/Print PS-CA | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
Clinical Data Repository (Local to PS-CA Producer or Central) | Retrieve patient FHIR data resources from internal data sources | R | Data Responder | R | Use Existing Standards Employed by the Clinical System |
Assemble Patient Summary from discrete FHIR resources | R | Data Responder | R | Use Existing Standards Employed by the Clinical System | |
Return Patient Summary Document Bundle | R | Data Responder | R | CA:FeX(CA:FeX-3D with $summary) -see RA specifications | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR -see RA specifications |
Table 4.2 Interoperability Conformance Requirements for Use Case 4: HCP Requests PS-CA On Demand
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: Clinical FHIR Data Sources are internal and/or external to the Clinical Data Repository
PS-CA USE CASE 4: HCP Requests PS-CA On Demand | Mapping of Use Case Actor to Technical Actor and its related Profile or Standard | ||||
USE CASE ACTORS | SERVICE SUPPORTED | OPT | TECHNICAL ACTOR | OPT | PROFILE / STANDARD |
PS-CA Consumer | Authenticate User | O | Client (e.g., EMR) | O | Internet User Authorization (IUA) -see RA specifications |
Identify Patient | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
O | Patient Demographic Consumer | O | PDQM -see RA specifications | ||
Request Patient Summary on-demand Document Reference (Patient Identifier) | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Request Patient Summary on-demand Document Reference (Patient Identifier) | R | Data Consumer | R | CA:FeX (CA:FeX-2B with $docref) -see RA specifications | |
Return Patient Summary Document Reference (include URL to Document Bundle) | R | Data Consumer | R | Use Existing Standards Employed by the Clinical System | |
Request Patient Summary (Document Location/Bundle ID) | R | Client (e.g., EMR) | R | Use Existing Standards Employed by the Clinical System | |
Request Patient Summary (Document Location/Bundle ID) | R | Data Consumer | R | CA:FeX (CA:FeX-3B)-see RA specifications | |
Return Patient Summary Document Bundle | R | Data Consumer | R | Use Existing Standards Employed by the Clinical System | |
Perform transformation between different formats | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF)) | |
| O | Client (e.g., EMR) | O | CA:FMT (e.g., FHIR to CDA, Export to PDF, etc.)-see RA specifications | ||
| Download/Print PS-CA | O | Client (e.g., EMR) | O | Use Existing Standards Employed by the Clinical System | |
Clinical Data Repository (Local to PS-CA Producer or Central) | Retrieve patient FHIR data resources from internal and/or external data sources [Sync or Async] | R | Data Responder | R | Use Existing Standards Employed by the Clinical System |
Assemble Patient Summary when FHIR resource data is retrieval is complete [Sync or Async] | R | Data Responder | R | Use Existing Standards Employed by the Clinical System | |
Generate Patient Summary Document Reference (include URL where Document Bundle is or will be available) | R | Data Responder | R | Use Existing Standards Employed by the Clinical System | |
Return Patient Summary on-demand Document Reference (include URL to Document Bundle) | R | Data Responder | R | CA:FeX (CA:FeX-2B with $docref)-see RA specifications | |
Return Patient Summary Document Bundle | R | Data Responder | R | CA:FeX (CA:FeX-3B)--see RA specifications | |
Central Infrastructure | Identify Patient | O | Patient Identity Registry | O | PMIR -see RA specifications |