Table 2.1 Interoperability Conformance Requirements for Use Case 2: HCP 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 2: HCP Views/ Consumes PS-CA

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 References (Patient Identifier)

R

Client (e.g., EMR)

R

Use Existing Standards Employed by the Clinical System

Request Patient Summary (Patient Summary References) 

R

Client (e.g., EMR)

R

Use Existing Standards Employed by the Clinical System

Return Patient Summary References RDocument ConsumerRMHD -see RA specifications
Return Patient Summary RDocument ConsumerRMHD -see RA specifications

Perform transformation between different formats 

O

Client (e.g., EMR)

O

Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF))

OClient (e.g., EMR)OCA:FMT (e.g., FHIR to CDA, Export to PDF, etc.) -see RA specifications
Download/Print PS-CAOClient (e.g., EMR)OUse Existing Standards Employed by the Clinical System

Update Current ValueSets and ConceptMaps

O

Client (e.g., EMR)

O

SVCM-see RA specifications

Document Repository (Local to PS-CA Producer 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 2.2 Interoperability Conformance Requirements for Use Case 2: HCP 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 2: HCP 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

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 Search Patient Summary (Patient Identifier) 

R

Client (e.g., EMR)

R

Use Existing Standards Employed by the Clinical System

Request Patient Summary (Bundle ID) 

R

Client (e.g., EMR)

R

Use Existing Standards Employed by the Clinical System

Return Patient Summary Compositions RData ConsumerRCA:FeX -see RA specifications
Return Patient SummaryRData ConsumerRCA:FeX -see RA specifications

Perform transformation between different formats 

O

Client (e.g., EMR)

O

Use Existing Standards Employed by the Clinical System (Render to Specific Format (PDF))

OClient (e.g., EMR)OCA:FMT (e.g., FHIR to CDA, CDA to FHIR, Export to PDF, etc.) -see RA specifications
Download/Print PS-CAOClient (e.g., EMR)OUse Existing Standards Employed by the Clinical System

Update Current ValueSets and ConceptMaps

O

Client (e.g., EMR)

O

SVCM-see RA specifications 

Document Repository (Local to PS-CA Producer or Central)*


Retrieve Patient Summary Compositions From Document Repository

R

Data Responder

R

CA:FeX -see RA specifications

Retrieve Patient Summary Bundle 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'.

  • No labels