CI Build - This specification is a draft continuous integration build and is subject to change. It is not ready for limited roll-out or production level use. For a full list of available versions, see the Directory of published versions
Table-3-Interoperability-Recommendations-for-Use-Case-3-Fetch-Document-References
| USE CASE ACTOR | SERVICE SUPPORTED | TECHNICAL ACTOR | Implementation Expectation | PROFILE/STANDARD |
|---|---|---|---|---|
| Consumer | Authenticate User | Client (e.g. EMR) | Optional | Internet User Authorization (IUA) |
| Consumer | Retrieve Patient Identifier | Client (e.g. EMR) | Optional | Use Existing Standard Employed by the Clinical System |
| Consumer | Retrieve Patient Identifier | Patient Demographic Consumer | Optional | PDQm |
| Central Infrastructure | Return Patient Identifier | Patient Identity Registry | Optional | PMIR |
| Consumer | Request Clinical Document References (Operation params) | Client (e.g. EMR) | Expected | Use Existing Standard Employed by the Clinical System |
| Consumer | Generate or Retrieve Clinical Document References (Operation params) | Data Consumer | Expected | CA:FeX-2B: Generate or Retrieve a DocumentReference using $docref Operation |
| Consumer | Request Clinical Document (Resource ID) | Client (e.g. EMR) | Expected | Use Existing Standard Employed by the Clinical System |
| Consumer | Retrieve Clinical Document (Resource ID) | Data Consumer | Expected | Retrieve Document [CA:FeX-3B] |
| Responder | Return Clinical Document References | Data Responder | Expected | CA:FeX-2B: Generate or Retrieve a DocumentReference using $docref Operation |
| Responder | Return Clinical Document | Data Responder | Expected | Retrieve Document [CA:FeX-3B] |
Note: These tables are not exhaustive and do not include all components required for a robust production deployment.
Aspects such as security, privacy, consent enforcement, and patient identity resolution are implementation-dependent and governed by jurisdictional or organizational policy. For authentication choices, including SMART on FHIR and IUA, see Relationship to Other Specifications.
Legend
- Expected – Represents interactions that are typically expected in baseline implementations of CA:FeX.
- Optional – Represents interactions that may apply based on local context, system configuration, or jurisdictional policy.